1. Scope of this notice
This draft describes information handling for the ContinuePDF website and its browser-based PDF tools. References to “we”, “us”, and “our” mean the operator of ContinuePDF. The operator's legal identity and applicable legal obligations must be confirmed before this draft is adopted.
Document processing is separate from website visits, support messages, optional saved-data features, and analytics or advertising. Local PDF processing does not mean the website collects no information.
2. Your documents
The PDF tools process document content in your browser. The current document workflow passes files between tools and the editor locally rather than uploading them to a ContinuePDF document-processing server. Temporary document-upload endpoints have been retired.
A downloaded or exported file is saved under your control on your device. Closing a tool does not delete your original files or downloads. Optional session history can include filenames, and saved text settings can contain text you enter, such as a recent watermark. These are distinct from the PDF's contents.
Do not include confidential document contents in a contact message unless they are necessary for your request. Information you send through the contact form is transmitted to the service, unlike a file selected for local PDF processing.
3. Information handled by the service
- Contact information: the name, email address, subject, and message you submit through the contact form, together with a submission timestamp.
- Optional saved data: preferences, tool settings, recent text values, and session history that can include filenames and tool-use timestamps when the corresponding saved-data functions are used.
- Usage information: visited pages and interactions such as outbound-link clicks and scrolling. The separate first-party usage API can receive tool identifiers, timing information, browser details, screen resolution, language, time zone, and other supplied usage metadata when invoked.
- Technical information: network requests expose information such as an IP address, requested URL, browser headers, and request time to the servers receiving them. Site infrastructure uses request information for delivery, diagnostics, and abuse prevention.
- Privacy settings: consent choices and notice preferences stored in your browser. An IP-based lookup selects a coarse consent region (EEA/UK/Switzerland, California, or other); it does not request GPS location.
Not every visitor uses every saved-data function. A browser identifier or usage record is not necessarily anonymous simply because it does not contain a name.
4. How information is used
Information supports the functions you request, remembering settings, responding to messages, operating and protecting the website, and understanding use and performance. Analytics and advertising tags also measure visits and interactions.
The legal basis for each purpose, including any consent, contractual necessity, legal obligation, or legitimate interest relied on, requires owner and legal confirmation before adoption. This draft does not assert that a particular legal basis or exemption applies to every activity.
6. Service providers and disclosures
Hosting, database, and network providers process information necessary to deliver and operate the service. Fonts and software libraries requested from third-party content-delivery services also disclose request information to those services. Analytics and advertising providers process the information received by their tags.
See Google's privacy policy and the Microsoft Privacy Statement for provider information. Following an external link takes you to a service with its own practices. This locally stored policy draft does not load Termly.
Information may also need to be disclosed to respond to valid legal requirements or protect the service and its users. The final notice must identify any other actual recipients or disclosure purposes; none are assumed from a generic template.
7. Saved data and retention
The following describes the implemented first-party retention rules, not a confirmation that all production cleanup and legacy-data removal have been activated. Expiry, removal from active storage, and erasure of backups are different events.
- New session records
- Records accepted by the retained-data service stop being returned 24 hours after the latest save. This can include saved filename history.
- New detailed usage logs
- Records accepted by that service stop being returned 7 days after they are saved. This is not a deadline for Google or Microsoft data.
- Preferences, tool settings, recent values, and aggregate usage counters
- These have no automatic deletion deadline in the current implementation. Aggregate counters are approximate and are not used for billing or authoritative quotas.
- Contact messages
- The contact store has no automatic deletion deadline in the current implementation. A retention period and request-handling process need owner approval.
- Browser storage and the ownership cookie
- The ownership cookie has a 90-day browser lifetime. Its expiry or removal does not delete saved server records. Other browser storage depends on its type and your browser's settings.
Expired records and cleanup
Cleanup removes expired new session and detailed-log rows from active PostgreSQL storage on a successful run. The operating objective is the next successful five-minute cleanup pass, conditional on an independent scheduler being active, database availability, and sufficient capacity. This draft does not confirm that production scheduling is active. Outages or a backlog can delay deletion.
The retained-data service refuses new saves when a successful cleanup has not completed within 15 minutes. This safeguard is not evidence that older stored records or provider backups have been erased.
Older records and provider backups
Some older records remain in legacy key-value storage. The application withholds expired values, but removing their stored copies requires separate, controlled maintenance. They are not automatically migrated or bulk-deleted by the new session and log retention system. Legacy erasure is not represented as complete.
Deleting an active database row does not immediately erase database recovery history, backups, or underlying storage media. Provider backup, infrastructure-log, and third-party analytics retention periods have not been confirmed for this draft. No fixed erasure deadline is promised for those systems.
8. Your rights and requests
Depending on your location and applicable law, rights may include access, correction, deletion, a portable copy, restriction of processing, objection, withdrawal of consent, and opting out of certain sales, sharing, or targeted advertising. You may also have the right to complain to a privacy regulator. These rights can be subject to conditions and exceptions.
Use the contact form to make a privacy request and describe the information or activity concerned. Verification may be needed to protect your information. Do not send a password, identity document, or PDF merely to make an initial request.
There is no self-service account deletion or data-export workflow represented by this notice. Clearing a browser identifier can make it harder to associate a request with saved data; contact us before clearing it if you want help identifying that data. A request does not by itself establish that deletion has occurred.
9. Security and international processing
The service uses measures such as browser-scoped signed cookies for optional saved data, restricted administrator access, and request limits. No website, browser, or storage system can guarantee absolute security.
Hosting and third-party providers may process information outside your country. Actual processing locations, contractual safeguards, and any required transfer mechanism must be confirmed before adoption. This draft does not promise that all website information stays in your country or on your device.
10. Children's information
If you believe a child has submitted personal information through the service, contact us to request review and appropriate action. The intended age range and any age-specific consent requirements need to be confirmed before the final policy is adopted; this draft does not claim an unverified age limit or exemption.
11. Changes to this notice
An approved replacement should be published on this page with its effective date. Later material changes should be communicated as required by applicable law. The date above records preparation of this draft only, not approval.
12. Contact
For privacy questions or requests, use the ContinuePDF contact form and identify the request as privacy-related. The form collects your name, email address, subject, and message as described above. The final notice must also provide the operator's confirmed legal identity and any legally required contact or representative details.