Privacy policy

What files you upload

• PDF documents — the document you want to modify (for example, a contract or form).
• Signature or image assets — when a tool asks for an image, you may upload common formats such as PNG or JPEG (depending on the tool). These are used only to place the visual on your PDF.

We do not ask you to upload files unrelated to the task; do not upload sensitive data you do not need for the workflow.

How files are processed

When you run a tool, your browser sends the file (or references to server-side temporary files, depending on the implementation) to our API. The server loads the PDF, applies your placement (signature, stamp, logo, etc.) using the PDF engine we operate, and returns a result file for download. Processing happens so you can complete the task you requested; we do not use your files to train public machine-learning models.

In some deployments, very large uploads may use direct cloud storage (for example, signed uploads to a bucket) so the request can stay within platform limits. In that case the object is still processed by our service under the same retention and deletion practices described below, unless your deployment uses a different policy documented separately.

Temporary storage and deletion

The API may store uploaded or intermediate files on the server disk only as long as needed to complete the job and to respect safety limits. Typical behavior includes:

• Files are associated with short-lived identifiers and stored under a temporary directory on the server.
• When a job finishes or is abandoned, the file is removed when the server releases the identifier, or automatically after a maximum retention window (on the order of one hour for typical temp-file handling), whichever comes first, with periodic cleanup sweeps.
• We do not use your files as a permanent library; they are not intended for long-term storage on our side.

Exact retention can vary by deployment (for example, cloud object lifecycle rules). If you self-host or use a different backend configuration, apply those rules in addition to this policy.

What user data we collect

In the current public phase, we do not require an account to use the tools. We may process:

• Content you send — PDFs and images as described above.
• Technical data — such as IP address, user agent, and request metadata, as typically logged by hosting providers and load balancers for security and debugging.

If we introduce accounts, billing, or optional profiles, we will describe what is collected and why on this page and in any signup flows.

Cookies and analytics

The site may use essential cookies or similar storage needed for the app to function (for example, session or preferences). We do not rely on third-party advertising cookies in the core product described here.

If we add analytics or marketing tools that use cookies or similar technologies, we will update this policy and, where required by law, provide consent or opt-out mechanisms.

Third-party services

The website and API may be hosted by infrastructure providers (for example, a frontend host and a container/cloud platform). Those providers process data on our behalf under their agreements and may be located in specific regions. If you use optional cloud storage for large uploads, your file may be transmitted to that provider’s storage for the duration of processing.

We choose providers to support reasonable security and availability; we do not sell your uploaded PDFs.

Contact for privacy requests

For questions about this policy, access requests, or deletion requests where applicable, contact us at:

We are setting up a dedicated channel for privacy-related requests and will publish contact details here soon. Until then, visit our contact page (a contact form is on the way) or the help center.

Changes to this policy

We may update this page when our product, hosting, or legal requirements change. The “Last updated” date at the top will change when we revise the policy. Continued use of the site after updates means you accept the revised policy, unless applicable law requires otherwise.