PDF AcroForm EditorOpen Editor

Privacy Policy — PDF AcroForm Editor

Effective date: 2026-06-30

This policy describes how SyneticSoft SRL (“we”, “us”) handles information when you use the PDF AcroForm Editor.

Two modes of use

The editor is available in two ways, and your privacy expectations depend on which one you use.

No-account, browser-local use

The current version of PDF AcroForm Editor works entirely in your browser without an account. In this mode:

  • We do not collect your name, email address, or any account information.
  • We do not upload, process, or store your PDF files or project files on our servers.
  • All PDF editing happens locally in your browser, on your own device.
  • We cannot open, view, or access the documents you edit.

This is the default mode today.

Cloud Studio

Cloud Studio is an optional tier that lets you save projects, sync across devices, and collaborate. It requires an account and stores your project files and account information on our servers. Cloud Studio is governed by the Cloud Studio privacy addendum. This policy covers the no-account, browser-local editor.

What we collect

We collect anonymous usage analytics to understand how the editor is used and to prioritize improvements. Analytics are provided by a self-hosted instance of Umami, a privacy-focused analytics platform.

What “action” means

When we log an action, we mean a coarse event type only. For example:

  • pdf:imported — a PDF was imported.
  • pdf:exported — a PDF was exported.
  • field:created — a form field was created.
  • field:deleted — a form field was deleted.
  • project:saved — a project file was saved.
  • project:loaded — a project file was loaded.
  • undo, redo, preview:enabled.

An action does not include the file name, the file contents, any text inside the PDF, field labels, signer names, project names, or anything you type into the editor.

Examples of collected events

  • Page views.
  • PDF import and export actions (event type only).
  • Project save and load actions (event type only).
  • Field creation and deletion actions (event type only).
  • Undo/redo and preview mode usage.
  • Caught error categories (without error messages or stack traces).

These events contain coarse counts and action types only.

What we never collect in the no-account editor

Even when an action is logged, we do not collect:

  • File names of uploaded or downloaded PDFs.
  • Contents of your PDF files.
  • Field names, labels, or values.
  • Signer names or roles.
  • Project names or project file contents.
  • Text, images, or annotations you add to a document.
  • Your name, email, or any account information.
  • Your IP address or precise location.

We also do not use cookies.

Error tracking

We use a self-hosted instance of GlitchTip to collect JavaScript errors and stack traces. This helps us diagnose crashes and bugs. Error reports do not include your PDF files, field names, signer names, or project content. Stack traces include only module basenames from the compiled application, and DOM click breadcrumbs are disabled so clicked element text does not leak. We do not attach user-provided data to error reports.

How analytics data is hosted

Analytics data is sent to a domain owned and operated by SyneticSoft SRL. No third-party analytics provider receives your data.

Your rights

Depending on your jurisdiction, you may have rights to access, correct, or delete personal data we hold about you. Because the no-account editor does not collect personal data, there is typically no personal data to access or delete. If you have a question or request, contact us at the address below.

Contact

SyneticSoft SRL

For privacy questions, email: privacy@syneticsoft.dev

Changes to this policy

We may update this policy as the product evolves. The effective date at the top of this page reflects the latest revision. The Cloud Studio addendum describes how account and file data is handled for Cloud Studio users.