Privacy Policy
qovox-parser runs inside your users’ browsers. We designed it so that we cannot see your documents, because they never reach us.
1. Summary
The qovox-parser SDK (“SDK”) parses PDF and DOCX files locally in the end user’s web browser. We (“Qovox”, “we”) do not receive, store or have access to any document you or your users process with the SDK. The only data the SDK sends to us is a small license check, described below.
2. Documents and their content
Documents are read into browser memory, parsed by code running on the device, and the result is handed to your application. We do not collect the file, its name, its size, its extracted text, or anything derived from it. You decide what your own application does with the parsed output; that is covered by your privacy policy.
3. What the SDK sends to us
To enforce license terms, the SDK calls our license API when it starts and about once an hour afterwards. These requests contain only:
| Data | Why | Retention |
|---|---|---|
| License key | Identify the license being used | For the life of the license |
Website domain (the browser’s Origin header) | Check it against your allowed-domain list | Last-seen domain kept on the license record |
| SDK version | Support and compatibility | Not stored beyond the request log |
| IP address (inherent to any web request) | Abuse and rate limiting | Held in memory for rate limiting; not written to your license record |
Optional usage counters (only if you enable reportUsage) | Show document/page counts in your dashboard | Aggregated per day, per license |
These requests carry no cookies and no end-user identifiers. We do not combine them with other data to profile individuals.
4. Your account (customers)
If you create a dashboard account we store your email address, a salted and hashed password (never the plain password), your plan and billing status, and the names, domain lists and creation dates of your license keys. License keys are stored only as one-way hashes; the full key is shown once at creation and we cannot recover it. Payment details are handled by our payment provider and are not stored by us.
5. This website
This website does not use advertising or analytics cookies. The dashboard keeps a sign-in token and your API setting in your browser’s local storage so you stay signed in; you can remove them by signing out or clearing site data. The live demo on the home page parses the file you drop in your browser and does not upload it.
6. Sharing
We do not sell personal data. We share data only with infrastructure and payment providers that process it on our behalf, with authorities where legally required, or in connection with a business transfer, always subject to this policy.
7. Your rights
Depending on where you live (for example under the GDPR or CCPA) you may request access to, correction of, export of, or deletion of your account data. Deleting a license key from the dashboard removes its record. To delete your account or exercise any right, contact privacy@qovox.example. Because we hold no document data, there is none to export or delete.
8. Security
Session tokens are signed with Ed25519, passwords are hashed with scrypt, and license keys are stored hashed. No system can be perfectly secure; please report vulnerabilities to security@qovox.example.
9. Children
The service is intended for businesses and developers and is not directed to children under 16.
10. Changes
If we change this policy in a material way we will update the date above and notify account holders by email. We will never change the core promise, that documents are not collected, without explicit notice and opt-in.
11. Contact
Questions: privacy@qovox.example.