Security
The safest server is the one your file never reaches
Most services protect your documents with a policy. SwiftPDFEdit protects them with a data path: the processing happens on your device, so there is nothing in transit to intercept and nothing at rest to breach.
The model
Six properties, all checkable
Nothing here rests on trusting a promise. Each point is either visible in your own browser or written into the code we ship.
Client-side execution
Our PDF engine — parsing, editing, rendering, export — is JavaScript delivered to your browser and executed on your CPU. The server's only job is to serve the application itself, like handing you a toolbox.
Nothing is uploaded to be processed
There is no processing queue, no temp directory and no deletion timer to trust, because merging, splitting, converting and editing all happen where the file already is. The one deliberate exception is saving: a finished PDF reaches your account only when you press Done.
Verifiable, not just claimed
Open your browser's developer tools, watch the network panel, and run a document through any tool. You will see the application load once — and no document bytes leave your machine. We invite exactly this scrutiny.
Hardened delivery
The application is served exclusively over TLS, with X-Content-Type-Options: nosniff, X-Frame-Options: SAMEORIGIN, a strict-origin-when-cross-origin referrer policy, and a Permissions-Policy that denies camera, microphone and geolocation outright.
Sessions you can't read out of a script
Signing in sets a short-lived, httpOnly, SameSite=Lax access-token cookie — invisible to page JavaScript by design. Plan limits and paid features are enforced by the account API on every request, not by the interface asking nicely.
Minimal data footprint
A free account is required, so we hold an email address and a plan — and nothing whatsoever about the documents you open. Analytics are aggregate page and tool counts: pathname only, never query strings, skipped entirely when your browser sends Do-Not-Track.
Full inventory
What actually leaves your device
The complete list, including the parts that are not flattering. If something is not here, we do not receive it.
Your document's contents
Only when you press Done to file it in My Documents
Never for processing. You can delete a saved document from My Documents at any time.
Your email address
At sign-up, and whenever you sign in
Needed to hold your account and apply plan limits. Passwords are stored hashed, never in the clear.
Page views and tool counts
As you navigate, unless Do-Not-Track is on
Pathname only — no query strings, no file names, no document metadata, and nothing from the admin console.
Card and billing details
Never — they go straight to Stripe
Checkout is handled by our payment provider. We never see a full card number.
The file you dropped on a tool
Never
It is read into your browser's memory, rewritten there, and handed back to you as a download.
Don't take our word for it
Verify the whole claim in about a minute
This is the entire audit. It needs no special access and no cooperation from us.
Open the network panel
Press F12 (or ⌥⌘I on a Mac) and switch to Network. Leave it recording while you work.
Run a real document through a tool
Merge two PDFs, or rotate a scan. Watch the request list while the work happens.
Read the list
You will see the application's own scripts load, and then nothing carrying your file. No request body contains your document, because the merge ran on your CPU.
For reviewers
What this means for regulated work
Because documents are processed locally, using SwiftPDFEdit is comparable to using a desktop application from a data-handling perspective: your organization's files remain within your organization's devices and network. For many teams this dramatically simplifies vendor review — there is no data processing relationship over your document contents, because no document contents are ever processed on our side.
That said, compliance decisions belong to your compliance team. If you are handling data governed by HIPAA, GDPR special categories, or similar regimes, review our Privacy Policy and involve your own advisors. Enterprise customers can request our security documentation package via [email protected].
Responsible disclosure
We welcome reports from security researchers. If you believe you have found a vulnerability in SwiftPDFEdit, email [email protected] with reproduction details. We commit to acknowledging reports within two business days and will credit researchers who wish to be named once a fix ships.
Put a real document through it
With the network panel open, if you like. That is the shortest path from reading this page to believing it.