DocSpell
PricingDocsSign in

Legal

  • Terms of Service
  • Privacy Policy
  • Refund Policy
  • Cookie Policy
  • Acceptable Use

Privacy Policy

Last updated 27 September 2026

This explains what DocSpell collects, why, who else touches it, and what you can do about it. We collect as little as we can to run the product, and we don't sell anyone's data.

What we collect from you

  • Account details. Your email address and name, and your profile picture if you sign in with a provider that has one. Sign-in is handled by Clerk.
  • Your content. Doc spaces, pages, images and logos you upload, your branding settings, and the settings you choose for AI generation.
  • GitHub connection. If you connect GitHub, an access token (so we can read the repositories you pick), your GitHub username, and the repository, branch and paths you choose for each doc space.
  • Billing. If you pay, Stripe processes your payment. We store your Stripe customer and subscription IDs and your plan. We never see or store your full card number.
  • Usage records. A record of each AI generation you run (when, how many files and pages, and whether it worked) so we can enforce plan limits and show you your history.

What we collect about your readers

When someone views a published docs page, our server records a page view so you can see what gets read. Each view stores the page, the time, the country (from our hosting provider), the kind of device (desktop, mobile or tablet), and the referring website's domain only, never the full URL. Visitors are counted with a one-way hashed identifier made from their IP address and a secret key; the IP address itself is never stored. No cookies and no tracking scripts are used for this. Page views are deleted after 180 days, and views by the doc space's owner aren't recorded.

Your source code

During an AI generation, DocSpell fetches the files you selected from GitHub and sends them to Google's Gemini API to write the pages. We don't store your source code; we keep the pages it produces. Google processes that content under its Gemini API terms, and depending on the service tier, Google may keep it and use it to improve its products. If that doesn't work for your code, don't run generation on that repository. Inline “Edit with AI” sends only the text you selected.

Cookies and local storage

We only use what the product needs to work: Clerk's cookies to keep you signed in, a Cloudflare security cookie when bot protection kicks in, and your browser's local storage to remember light or dark mode. There are no advertising, analytics or cross-site tracking cookies. The Cookie Policy lists each one.

Who else processes data

These providers run parts of DocSpell for us and only get what they need for their part:

  • Cloudflare: hosting, the database, file storage and custom domains.
  • Clerk: sign-in and account management.
  • Stripe: payments and subscriptions.
  • GitHub: reading the repositories you connect.
  • Google (Gemini API): writing and rewriting pages with AI.

Some of these providers process data outside your country, including in the United States. We rely on their standard contractual protections for those transfers.

Why we use it

To provide the service you signed up for (running your account, hosting and publishing your docs, generating pages and processing payments), to keep it secure and stop abuse, to meet legal obligations such as tax records, and to answer you when you get in touch. We don't use your content to train AI models.

How long we keep it

  • Account data and content: until you delete them or your account.
  • Reader page views: 180 days.
  • Billing records: as long as tax and accounting law requires.
  • Backups: overwritten on a rolling basis after deletion.

Your choices and rights

You can export any doc space as Markdown from its settings, edit or delete your content at any time, disconnect GitHub, and delete your account from your account page, which removes your doc spaces, pages and usage records. Depending on where you live, you may also have the right to access, correct, move or erase your data, or to object to how we use it. Email hello@docspell.devand we'll help. You can also complain to your local data protection authority.

Security

Data is encrypted in transit, access is limited to what's needed to run the service, and published content is sanitised before it's shown to readers. No system is perfectly secure, so if you find a problem, please tell us at hello@docspell.dev.

Children

DocSpell isn't meant for anyone under 16, and we don't knowingly collect their data.

Changes

If we change this policy in a meaningful way, we'll let you know by email or in the app before it takes effect. The date at the top always shows the latest version.

Contact

Anything about privacy: hello@docspell.dev.

DocSpell

Docs written from your actual code. Edit them, publish them, keep them honest.

hello@docspell.dev

Product

  • How it works
  • Screens
  • Pricing
  • Questions

Resources

  • Documentation
  • Sign in
  • Create an account

Legal

  • Terms of Service
  • Privacy Policy
  • Refund Policy
  • Cookie Policy
  • Acceptable Use

Company

  • Contact
  • Report a problem
  • Talk to us about Team

© 2026 DocSpell. Made for people who'd rather ship than write docs.