This Privacy Policy explains how dochost ("dochost", "we", "us", or "our") collects, uses, and protects your personal information when you use dochost.io and our publishing services. By using dochost, you agree to the practices described in this policy.
We may collect the following types of information:
- Account Information: Your name and email address when you sign up, including details shared by Google or GitHub if you sign in with a social provider.
- Authentication Data: If you create an account with email and password, we collect your password to create and authenticate your account. It is converted into a salted, one-way hash by our authentication system; we store the hash and do not retain your plaintext account password. We also process session identifiers and access tokens needed to keep you signed in and authorize connected clients such as the browser extension.
- Content You Publish: The HTML, Markdown, and files you paste or upload to create public pages. Pages you publish are accessible to anyone with the link.
- Page-Protection Passwords: If you choose to password-protect a published page, we collect the page password to create or change that protection. We immediately replace it with a salted PBKDF2-SHA256 hash on our server. When someone later enters the password to unlock the page, our server processes it transiently to compare it with the stored hash. We do not store or log plaintext page passwords. A page-protection password is separate from your dochost account password.
- Usage Data: Information about how you interact with dochost, such as pages visited, links created, views on your published pages, and interactions with the browser extension's controls.
- Device Information: Technical details such as IP address, browser type, and operating system.
- Payment Information: When you subscribe to a paid plan, payments are processed by Stripe. We do not store your full card details.
We use your information to:
- Create and host the pages you publish and serve them at their public links
- Provide, maintain, and improve dochost
- Manage your account and process subscriptions
- Provide customer support and respond to your requests
- Detect, prevent, and address abuse, fraud, and technical issues
- Comply with legal obligations
dochost is a publishing tool. Any page you publish is public by default and can be viewed, shared, and indexed by search engines. Do not publish confidential or sensitive personal information. You can delete a page at any time, though cached copies may persist elsewhere outside our control.
We offer an optional Chrome browser extension ("Publish to dochost") that lets you publish AI-generated HTML and Markdown directly from ChatGPT (chatgpt.com, chat.openai.com), Claude (claude.ai), Google Gemini (gemini.google.com), Google AI Studio (aistudio.google.com), Grok (grok.com), and DeepSeek (chat.deepseek.com). The extension is governed by this same Privacy Policy. Specifically:
- Page access and website content: On the supported sites above, the extension reads the page locally in your browser to detect AI-generated code and Markdown blocks and add a "Publish" button next to them. This reading happens on your device; website content leaves your browser only when you choose a specific block and click Publish.
- Website content and publishing settings we collect: When you click Publish, we collect the website content you select — the specific HTML or Markdown block — plus the publishing settings you submit, such as visibility, custom link, optional page-protection password, and branding preference. We send this data to our publishing endpoint to create your page, exactly as if you had submitted it on dochost.io. We store the published content and related page metadata so we can host, serve, update, delete, rate-limit, and moderate the published page. We do not collect other page content, unselected conversation text, full URLs or URL paths, browsing activity outside the supported sites, keystrokes, mouse movements, or clicks outside the extension's own controls.
- Anonymous install ID: The extension generates a random identifier stored locally in your browser. It is sent with publish requests and analytics events to prevent abuse (rate limiting) and to measure usage. It is not tied to your identity unless you sign in.
- Limited browsing and interaction analytics: The extension sends anonymous usage events to PostHog, including event counts, interactions with the extension's own controls (for example, opening the publish panel or clicking Publish), the hostname of the supported site where the event occurred, content format, and extension version. This lets us measure use and detect when a supported site's layout change breaks the extension. It does not send unpublished page content, unselected conversation text, full URLs or URL paths, or any browsing activity outside the supported sites.
- Passwords and signed-in publishing: The extension does not read or collect your dochost account password or passwords you enter on supported AI websites. You sign in directly on dochost.io, and the extension receives an API access token — not your account password — so it can publish to your account. If you type an optional page-protection password in the extension's publish panel, the extension sends that password over HTTPS only when you click Publish. It is not saved in local extension storage, included in analytics, or shared with PostHog. Our server immediately converts it to a salted PBKDF2-SHA256 hash and does not retain the plaintext value.
- Local storage: The extension keeps a random install ID, API access token, display name, plan tier, review-prompt state, and a record of pages published from that browser (a content fingerprint, published URL, and timestamp) in Chrome's local extension storage. Published-page records stop being used after seven days, but may remain locally until they are pruned, you clear the extension's storage, or you uninstall the extension. The extension does not store account passwords, page-protection passwords, conversation text, or complete unpublished content there. You can revoke the extension's API key in your dochost account settings; clearing extension storage or uninstalling the extension removes its local copy. The extension does not load or execute remote code.
- Sharing: Extension data is not sold. Published content is shared publicly at the generated dochost link according to the visibility you choose. We share extension-related data only with service providers that help us operate the publishing service: Cloudflare for hosting, storage, and network delivery; PostHog for the extension analytics described above; and Google Web Risk, which receives URLs extracted from submitted content so we can check them for malware, phishing, and unwanted software. Google Web Risk does not receive the full submitted document unless the document itself consists of a URL.
We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.
Where your data is stored. Published pages and uploaded files are stored in Cloudflare object storage, and your account and page metadata are stored in our database hosted on Cloudflare's infrastructure. Payment data is held by Stripe, and analytics events by PostHog, under their own terms.
How long we keep it.
- Published pages: Pages published on a Free account expire automatically — 7 days by default, or 3 days for a private (unlisted) page — after which they are removed and no longer served. Paid plans (Pro, Max, lifetime) create permanent pages, and one-time paid extensions keep a page online for the duration purchased or permanently if you choose the forever option. You can delete any page at any time.
- Account data: We keep your account information for as long as your account is active. When you delete your account (or ask us to), we delete the associated personal data, except where we must retain it to meet a legal obligation.
- Passwords and authentication data: Account password hashes are retained while the corresponding email/password account is active. A page-protection password hash is retained until you remove the password or delete the page; the plaintext password is not retained. Server-side API key records remain until you revoke the key in your account settings or delete your account.
- Anonymous sessions: An anonymous publishing session is retained for 30 days.
- Browser extension data: Published-page records stop being used after seven days but may remain in local storage until pruned. Other local extension data remains until you clear the extension's storage or uninstall the extension. The install ID is sent to our servers with publish and analytics requests, as described in the Browser Extension section, and server-side rate-limit records are retained only as long as needed to enforce abuse limits.
- Analytics, email, and payment data: Analytics data is retained by PostHog and Plausible, transactional email data by Resend, and payment records by Stripe according to their respective retention policies.
We do not sell your personal data, and we do not share it with third parties except: (a) with the service providers listed below who process data on our behalf to operate dochost; (b) content you choose to publish, which is public by design and viewable by anyone with the link; and (c) where required by law or to protect our rights, users, or the public.
We rely on the following third-party providers to operate dochost:
- Cloudflare for network delivery, application hosting, database infrastructure, and object storage. Cloudflare may process published content, account and page metadata, IP addresses, request headers, and other data needed to deliver and secure the service.
- PostHog for product and browser-extension analytics. PostHog receives the usage events, anonymous identifiers, and limited technical properties described above, but not unpublished document content or passwords.
- Plausible for cookieless website and published-page analytics. Plausible receives page paths, browser/user-agent information, IP addresses for aggregate geolocation and visitor counting, and limited event properties; it does not receive passwords.
- Google Web Risk for publish-time safety checks. It receives URLs extracted from submitted content so we can check them for malware, phishing, and unwanted software; it does not receive passwords.
- Stripe for subscription and one-time payment processing. Stripe receives the account, transaction, and payment-method data needed to process payments; we do not store full card details.
- Resend for verification, password-reset, and other transactional emails. Resend receives the recipient name, email address, and email content needed to deliver those messages; it does not receive account or page-protection passwords.
- Google and GitHub when you choose social sign-in. The selected provider processes the sign-in request and shares the profile and authentication data needed to connect your account.
- Google AdSense for advertising on dochost's own marketing and documentation pages. Google receives the request data (including IP address, user agent, and the page URL) needed to select and measure ads, and may set or read advertising cookies on your device.
These providers process data under their own terms. We do not sell your personal data.
Publish to dochost's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use user data only to provide or improve the extension's single purpose — publishing content that the user explicitly selects to dochost — and for security, abuse prevention, legal compliance, and internal operations that support that purpose. We do not use or transfer extension user data for personalized or interest-based advertising, creditworthiness or lending decisions, or sale to data brokers. Humans may access user data only with the user's specific consent for support, when necessary for security or abuse investigation, when required by law, or after the data has been aggregated and anonymized for internal operations.
dochost shows ads from Google AdSense on its own marketing and
documentation pages so the free tier can stay free. Pages published by authors
(/d/... and author subdomains) carry no ad code at all — we do not
monetize content our users publish, and advertisers are not given access to it.
What this means for your data:
- Google, as a third-party vendor, uses cookies to serve ads on dochost.
- Google's use of advertising cookies enables it and its partners to serve ads
to you based on your visit to dochost and/or other sites on the Internet.
- Third-party vendors and ad networks may also use cookies to serve ads based
on your prior visits to this or other websites.
- We do not share your account data, document content, or email address with
advertisers, and we do not use published content to target ads.
How to opt out. You can turn off personalized advertising from Google at
Google Ads Settings, and read how Google
uses information from sites that use its services at
Google's advertising technologies page.
To opt out of third-party vendor cookies more broadly, use
aboutads.info or, in the EU,
youronlinechoices.eu. Opting out stops ads
from being personalized; you may still see non-personalized ads.
See our Cookie Policy for the cookie categories involved.
Depending on your location, you may have the right to access, correct, or delete your personal data, or to object to certain processing. To exercise these rights, contact us.
We may update this Privacy Policy from time to time. We will post any changes on this page with an updated date.
If you have any questions about this Privacy Policy, please contact us or email admin@dochost.io.