Privacy

Your account

An account is an email address and a password, or a Google sign-in if you use one. Turning on two-factor authentication stores the enrolled factor against your account, never the codes themselves. Passwords are held by the authentication service described under Who processes data; Docssier never sees them.

What you write

Guides, SOPs, sections, categories, notes, tags, screenshots and hub branding belong to your account. They are stored so the product can show them to you and publish the ones you publish. They are not sold, not shared with other accounts, and not used to train anybody's model.

The capture extension

The recorder does nothing until you press Start capture. From then until you stop, it records the accessible name of what you click, what you type, the tab's title and address, and screenshots of the tab.

What somebody types into a password, email, phone, number or card field never enters a step. The recorder does not read those values, so they are not written into a guide and not uploaded with one.

Those fields are also covered in the screenshot, inside your own browser, before the image is stored or uploaded: the areas are pixelated into the file itself rather than hidden by something laid over it. It is on by default and can be turned off in the extension. In the one case where the image cannot be redrawn at all — no canvas, a picture that will not decode — the areas are recorded as a cover over the original instead, and the original is what gets stored.

A screenshot is a picture of the tab as it was, so anything visible on screen when you take it is in the image. The editor has a blur tool for the parts that should not be published, and what it covers is pixelated into the stored file itself rather than hidden by the page — the copy a reader could download does not hold the original underneath.

Steps and screenshots go to your own Docssier account, over the session your browser already holds on an open Docssier tab. The extension never asks for a password. Nothing is sent to any other service, no analytics are collected, and no code is fetched and run — every script is in the package Chrome installed.

People who read a help center

A reader is given a random token, kept in their own browser. It is not an identity: it says nothing about who they are, it is not shared between hubs, and clearing site data starts them over.

Opening a doc records which doc, which hub, and when, against that token. It does not record an IP address, a browser, or the page they came from. A helpful or not-helpful vote is recorded the same way.

If a hub has the chat turned on, what a reader types is stored so the conversation is still there tomorrow, and so a ticket has something to show the person answering it. Anything a reader puts in a message is up to them; the chat does not go looking for personal details.

Referral links

A referral link leaves a code in the browser for 90 days so a signup can be credited to whoever sent it. Following one records the path visited and the host of the referring site — the host only, never the full address, because which page somebody was reading before they arrived is not ours to keep.

Doc AI

When a reader asks Doc AI a question, the question and the relevant published docs from that hub are sent to the AI provider named below to produce an answer. Doc answers from that hub's own published docs and cites the guide and step each answer came from. When the docs do not cover it, Doc opens a ticket instead of guessing.

AI-written text inside the product is marked as AI-written until a person has reviewed and accepted it.

Who processes data

Docssier runs on services that hold data on its behalf. Hosting, the database, file storage and authentication are provided by Lovable Cloud, which runs on Supabase. AI features are served by Anthropic. Email your account sends — ticket replies and notifications — goes through Resend using the sending address you configure. Traffic is served through Cloudflare. Payments on a paid plan are processed by Stripe, which handles your card details directly; Docssier never sees or stores them. If you joined the early access mailing list, that list is held by Drip. Signing in with Google involves Google.

What Docssier does not do

Docssier adds no third-party analytics and no advertising trackers to the app, the marketing site, or the help centers it publishes. There is no ad network, no data broker, and no cross-site profile. The counts an account sees about its own docs are the ones described above and nothing more.

Keeping and deleting

What you write stays until you delete it. Deleting a guide, an SOP or a hub removes it and what hangs off it. To delete an account and everything in it, write to privacy@docssier.com and it will be done.

Asking about any of this

Write to privacy@docssier.com. If something on this page does not match what the product does, that is a bug in the page and worth reporting as one.