Privacy Policy

Last updated: October 4, 2026

usedocs.app (“usedocs”, “we”, “us”) keeps a SaaS team’s help center accurate. It hosts the help center, proposes article edits from the team’s code, drafts articles from customer questions, and runs an assistant that answers customers from those articles. This policy explains what data we process for workspace members (our customers), for the readers and visitors of help centers they publish, and for visitors to usedocs.app.

Data we process

Account data: your email address, name, and workspace membership when you sign in with Google, GitHub, or a magic link.
Workspace content: articles, collections, drafts, proposed edits, version history, translations, changelog entries, uploaded images, help center settings, and anything you import from a docs site, Zendesk, Intercom, GitBook, Notion, or an OpenAPI file.
Code data, if you connect GitHub: pull request and release titles and links and the list of changed file paths. Diffs and file excerpts are read to suggest edits and check articles, held only for that request, and not stored. Details: how usedocs handles your code.
Imported tickets, if you import them: conversations from Zendesk, Intercom, Help Scout, Crisp, Plain, HubSpot, or a CSV file, used to find questions your docs do not answer.
Assistant conversations: visitor questions, answers, sources, feedback votes, and contact details a visitor chooses to leave.
Help center readers: if a workspace makes docs private, the emails on its readers list, when each reader last signed in, one-time sign-in links (stored only as a hash), and a session cookie set after sign-in.
Help center analytics: article views, searches that found nothing, and “Was this helpful?” votes, without identifying the reader.
Technical data: IP addresses for abuse prevention and rate limits, and standard request logs.
Website analytics on usedocs.app: Google Analytics 4 (measurement ID G-DGX6HJBYQD) and Piqo (site ID xnmuh7sm) load only if you click Accept on the cookie banner. Change your choice by clearing site data for usedocs.app, or use the Google Analytics opt-out add-on.

How we use data

We use data to run the service: sign you in, host your help center, suggest edits and drafts, answer questions from your published articles, send the emails you ask for (sign-in links, alerts, digests), bill your subscription, and prevent abuse. We do not sell personal data and we do not use your content or code to train AI models.

AI processing

Answers, drafts, proposed edits, checks, and translations are produced by language models running on Cloudflare Workers AI, inside the request that needs them. Nothing usedocs writes is published to your help center until someone in your workspace approves it, except translations you choose to publish automatically.

Cookies and local storage

usedocs.app uses a session cookie to keep you signed in to the dashboard, and consent based analytics cookies described above.
Help centers set a reader session cookie only after a reader signs in to private docs, and remember the reader’s light or dark choice in local storage.
The assistant widget keeps its size, its launcher position, and a random token in local storage on the site it runs on. The token lets that browser reopen its own conversations for 90 days; we store only a hash of it, and clearing site data removes it.

Retention

Assistant messages are deleted after 90 days, gap records after 180 days, and closed conversations after one year.
Sign-in links for help center readers expire after one hour and work once. Sign-in attempt counters are kept for up to a day.
Deleted articles stay in Recently deleted for 30 days. Version history keeps up to 50 earlier versions per article.
Workspace content stays until you delete it or delete the workspace.

Your rights

Export: workspace owners can export from Settings → Export and delete, or call GET /api/account/export and GET /api/bots/:id/export while signed in.
Delete: workspace owners can delete the workspace from Settings → Export and delete, or call DELETE /api/account with { "confirm": "DELETE" }.
Help center readers and visitors: contact the company that runs the help center; they control its readers list and conversations. We will help them answer your request.
Contact: hello@usedocs.app

Sub-processors

Cloudflare: hosting, storage, search, queues, browser screenshots, and AI (Workers, Durable Objects, D1, R2, Vectorize, Queues, Browser Run, Workers AI).
Dodo Payments: payments, as merchant of record.
context.dev: reads public web pages you ask us to import or check.
AutoSend: transactional email such as sign-in links and alerts.
Google Analytics and Piqo: website analytics on usedocs.app, with consent.
Services you connect: GitHub, Notion, Linear, Slack, Discord, Microsoft Teams, and the helpdesks you import from receive or send only what that connection needs.