Get the app
← All tools
DAMNPDFS / INFORMATION

Your files stay close.

What we process, what we retain, and how you can clear it.

Document processing

Browser tools process your files on your device. The processing badge identifies the location before you run an operation. Temporary cloud processing uploads the selected files to a private Google Cloud Storage bucket and uses short-lived worker folders.

Cloud copies are deleted when the completed job is acknowledged or cancelled, or when their one-hour expiry is reached. Cleanup runs independently of document workers. Cloud documents are separate from public feedback and anonymous usage records.

Local storage and downloads

Your latest workspace may be saved in this browser’s IndexedDB, up to 100 MB, for at most four hours. Re-saving does not extend a file’s deadline. Invoice drafts have the same four-hour limit. Expired copies are removed while the app is open; when the browser is closed, they are removed before restoration on your next visit.

Use Privacy & local data to clear document copies immediately. Downloads you save yourself are under your control. Theme, favourites and reusable workflow presets stay on your device until you clear them or browser storage.

Tool engines, fonts and local AI/OCR model downloads can be cached separately from documents. Use Clear offline cache in Privacy & local data to remove stored offline copies without deleting your document workspace.

App installation measurement

Known advertising campaign names are retained in this browser for seven days to attribute install-page visits, installation clicks, browser-confirmed installs and app opens. We store aggregate counts and estimated distinct browsers; we do not retain arbitrary URL parameters. Opening uninstall instructions is measured as intent only, not a confirmed uninstall. Browser privacy signals are respected.

After installation or the first standalone app launch, we offer an optional notification invitation. Your choice stays on this device so we do not repeatedly ask. Notification invitations and successful opt-ins are counted separately.

Optional app notifications and private feedback

If you enable notifications, we store your browser’s push endpoint and encryption keys in our private database for up to 180 days after subscription or renewal. A random authorization token stays on your device; only its hash is stored on the server. These records are separate from documents and analytics. Browser push providers deliver the encrypted announcement. We do not include your files or document contents in notifications.

Turn notifications off in the Updates panel to remove the server subscription. You can also revoke permission in your browser or operating system; invalid subscriptions are removed when delivery fails. Uninstalling an app may not immediately notify our server. Notification delivery records expire after 30 days. Announcements are public and remain in the app inbox.

The optional prompt after a result download sends your tool ID, rating and comment privately to the creator. These responses expire after 90 days and are not public reviews. Please leave out document contents and personal information. A local reminder timestamp limits this invitation to once every 14 days. The separate tool review form explicitly identifies public reviews.

Agent accounts and credits

Only agent automation requires email verification. We retain your email and a random account ID to maintain your monthly allowance across devices. Hostinger sends sign-in emails from contact@toil-labs.com. Codes expire after 10 minutes, are stored as keyed hashes, and can be redeemed once. Never share a sign-in code with a coding agent.

A secure, HTTP-only cookie remembers your sign-in for 30 days. Server sessions store hashed tokens. Sign out in Agent access to remove the cookie and revoke your connected agent sessions. Account credit totals are retained for up to 125 days; operation deduplication records for 32 days. They contain counts and request fingerprints, not document contents. Temporary result handles are retained for 10 minutes.

Accounts remain until deletion is requested through the contact page. Account records are separate from anonymous analytics. Manual document tools do not require an account.

If you send a message from Agent access, we store your message, topic, verified email, account ID and a snapshot of your credit usage privately for up to 90 days. The creator can review these in the admin dashboard to respond to feedback and understand demand. Messages are not public reviews and do not contain your documents unless you type their contents. Please do not include sensitive information.

AI providers

You choose the provider, model and API key for external AI features. Your key stays in tab memory for the session and is excluded from document metadata and application logs. A transient relay is used when the provider cannot be called directly from the browser.

Selected document content is sent to your chosen provider when you run an external AI operation. The provider’s terms and retention rules apply to that processing. Local OCR and built-in models do not require an external API key. Forget the key in AI settings whenever you finish.

Sharing and feedback

Peer-to-peer file transfers use WebRTC encryption, recipient acceptance and an integrity check. Room signaling, chat and whiteboard updates use temporary server coordination. Rooms expire after one hour. Reviews you choose to submit are public; avoid including personal or document information.

Usage and operational data

Vercel Web Analytics measures anonymous page visits and traffic sources; Speed Insights measures page performance. Our first-party analytics records public page/tool IDs, tool starts and outcomes, coarse click locations, navigation/control categories, coarse device size, approved campaign labels and time spent on visible pages. Agent activity is counted separately from human tool runs. We do not record document contents, filenames, typed values, AI keys or payment credentials. Private document previews, drawings and form content are excluded from click capture. URL query strings and fragments are removed from analytics URLs.

Usage analytics starts automatically without a permission banner. First-party measurement uses a random session identifier in tab memory and a random browser identifier in local storage for at most 90 days. If local storage is unavailable, measurement uses the session identifier only. It helps estimate active browsers across days; it does not identify a person. Active-browser counts use anonymous aggregate sketches, with approximately 3.25% relative estimation error. Raw events contain no browser/session identifier, expire after 90 days and are kept in the private DamnPDFs Firestore database; daily aggregates expire after 400 days. These records are separate from temporary documents.

Do Not Track and Global Privacy Control signals take priority. You can remove the random browser identifier by clearing this site’s browser storage. Ad blockers, browser privacy signals and offline visits can reduce measured totals. Historical aggregate sketches cannot be linked back to, or individually removed for, a browser.

The earlier successful-use counter contains no stable visitor identifier and expires after thirty days; duplicate-event markers expire after two days. Operational request logs omit query strings, credentials and document bodies. Admin analytics requires private server authorization; it is not exposed through the public tool catalog.

Questions or record requests

Use the contact page for privacy questions, corrections or requests concerning feedback records.