Security Practices

Clear file handling

• Browser-native workflows keep supported processing inside the active browser session.
• Advanced workflows identify when the selected file requires server-backed processing for the requested operation.
• Online tool screens check live availability and applicable limits before accepting a request.

Temporary request safeguards

• Server-backed processing uses a request workspace for the selected operation rather than permanent cloud-drive storage.
• File type, size and request inputs are validated before processing.
• HTTPS, origin restrictions, timeouts and workload limits protect the request path.
• Temporary request workspaces are subject to the active backend cleanup policy.
• PDF passwords are not intended to appear in product analytics or application logs.

User responsibilities

Use a strong unique password when protecting a PDF, preserve an original copy, and do not process a sensitive document on a shared or untrusted computer. Only unlock a file when you know the current password and have permission.

Responsible disclosure

Report a reproducible security issue privately to anjandev325@gmail.com. Do not access another user’s data, disrupt the service or publish sensitive exploit details before a reasonable remediation period.