Privacy Policy

Plain-language summary. Docket helps you record scope changes. We collect the account and project data you give us, plus limited technical data (including the IP address and timestamp captured when a client approves a change — that is the point of the product). We do not sell your data. We share it only with the vendors that run the service (email, file storage, payments, and—only with your consent—analytics) and when the law requires it.

This Privacy Policy explains how Docket ("Docket", "we", "us") collects, uses, and discloses information in connection with the Docket scope-change management service at scopedocket.com (the "Service"). It applies to account holders ("Customers") and to the clients who submit and approve change requests through a Customer's links ("Client Users").

For Client Users, the Customer is the controller of the request and approval data they collect through Docket; Docket acts as a processor on the Customer's behalf for that data.

1Information we collect

Information you provide

Account data — your name, email address, password (stored only as a salted hash), and organization name when you sign up.
Project and change data — project names, client details, scope-change requests, impact assessments (days and cost), summaries, internal notes, and any files or reference links you or your clients upload.
Client submissions — when a Client User submits or approves a request, the email address they enter and the content of their request or decision.
Communications — messages you send us at hello@scopedocket.com.

Information collected automatically

Approval evidence — when a change is approved or declined, we record a timestamp, the approver's email, and the IP address of the request, together with a cryptographic signature over the approved statement. This audit record is a core function of the Service and is retained as part of the Customer's permanent project log.
Authentication cookies — a session cookie set after sign-in to keep you logged in. These are strictly necessary for the Service to function.
Analytics — on our public website pages we use Google Analytics to understand aggregate, non-identifying traffic patterns (such as page views and referrers). Where prior consent is legally required — including the EEA and the UK — analytics cookies are not loaded until you opt in through our cookie banner. Elsewhere analytics runs by default, and you can opt out of website analytics at any time using the cookie preferences control shown on every public page; we also honor the Global Privacy Control browser signal as an opt-out.
Product milestones — if you create an account while analytics is enabled, we store the Google Analytics identifier from that visit alongside your workspace and use it to report three milestone events to Google Analytics from our servers: the first time you share a client request link, the first client request received, and the first approval. These events carry only that identifier, the event name, and your plan name. They never include your or your clients' names, email addresses or IP addresses, and never any project, request, or approval content. We use them to understand which channels bring us workspaces that are actually put to use. If you decline analytics, no identifier is stored and none of these events are sent. We do not load analytics scripts or set analytics cookies inside the signed-in application.
Consent preferences — your cookie choices are stored in your browser's local storage by our self-hosted consent banner. They are not sent to us or to any third party, and clearing your browser storage resets them.
Server logs — standard request metadata (IP address, browser/user-agent, timestamps) generated by our hosting and used for security and reliability.
Connected apps — if you connect an AI assistant to Docket (see AI assistants you connect below), we store a record of that connection: the app's name, the workspace and permissions you granted, when you connected it, and when it was last used. We never store the access credentials themselves, only hashes of them. You can see and revoke these connections under Settings → Connected apps.

Payment information

Paid subscriptions are processed by Stripe. We do not receive or store full card numbers; Stripe handles card data directly and provides us with limited billing metadata (such as plan, status, and the last four digits of the card). See Stripe's privacy policy.

2How we use information

To provide, maintain, and secure the Service, including authentication and the generation of signed approval records.
To send transactional email — verification, approval notifications, and account-related messages.
To process subscriptions, billing, and plan limits.
To respond to support requests and communicate about the Service.
To detect, prevent, and investigate abuse, fraud, and security incidents.
To comply with legal obligations and enforce our Terms of Service.
With your consent, to measure which marketing channels lead to workspaces that are actively used — see Analytics and Product milestones above.

We rely on the following legal bases (where the GDPR or similar laws apply): performance of our contract with you, our legitimate interests in operating and securing the Service, your consent where required, and compliance with legal obligations.

3How we share information

We do not sell personal information and we do not share it for cross-context behavioral advertising. We disclose information only as follows:

Service providers (sub-processors) — vendors that operate parts of the Service under contract and on our instructions:

Provider	Purpose	Data involved
Resend	Transactional email delivery	Recipient email, message content
Cloudflare R2	File and attachment storage	Uploaded files
Stripe	Subscription billing and payments	Billing details, card data (held by Stripe)
Database & application hosting	Running the Service and storing your data	All account, project, and change data
Google Analytics	Website analytics (consent-based, public pages only) and workspace milestone events	Website: usage data, cookie identifiers, IP address. Milestones: analytics identifier, event name, plan name

AI assistants you connect — Docket can be connected to an AI assistant, such as Claude or ChatGPT, through our MCP connector (see Connect Docket to an AI assistant). Nothing is shared until you connect an assistant and approve access. Once you do, when the assistant calls one of Docket's tools on your behalf, we send it the data that tool returns, such as project names, change requests, client and approver names and email addresses, impact assessments, and approval records, limited to what your role in the workspace can see. The assistant's provider is not our sub-processor: you choose and authorize it, and it handles that data under its own terms and privacy policy. We do not receive your conversations with the assistant, only the tool requests it sends us. If you instruct the assistant to send an approval link, we email the approver exactly as if you had sent it from the dashboard. You can revoke an assistant's access at any time under Settings → Connected apps, which stops any further data being sent to it. Revoking does not delete data the assistant has already received; that is governed by its provider.
Between Customer and Client Users — request and approval data is shared between the Customer and its client as an inherent part of the workflow.
Legal and safety — when required by law, legal process, or to protect the rights, property, or safety of Docket, our users, or the public.
Business transfers — in connection with a merger, acquisition, or sale of assets, subject to this Policy.

4Data retention

We retain account and project data for as long as your account is active. Approval and audit records are retained as part of the Customer's project log so they remain available as evidence. When you delete a workspace or close your account, associated data is deleted or anonymized within a reasonable period, except where we must retain it to comply with legal obligations, resolve disputes, or enforce our agreements. Backups are purged on a rolling schedule.

5Security

We use technical and organizational measures to protect personal information, including encryption in transit (TLS), hashed passwords, scoped access controls, and cryptographic signing of approval records. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

6International transfers

We and our sub-processors may process information in countries other than your own, including the United States. Where required, we rely on appropriate safeguards such as the EU Standard Contractual Clauses for such transfers.

7Your rights

Depending on where you live, you may have the right to access, correct, delete, or port your personal information, to object to or restrict certain processing, and to withdraw consent. To exercise these rights, contact us at hello@scopedocket.com. We will respond as required by applicable law. If you are a Client User, requests about data a Customer collected through Docket may be directed to that Customer as the controller, or to us — we will forward them as needed.

If you are in the EEA or UK, you may also lodge a complaint with your local data protection authority. If you are a California resident, you may exercise rights under the CCPA/CPRA; we do not sell or share personal information as those terms are defined.

8Children's privacy

The Service is intended for business use and is not directed to children under 16. We do not knowingly collect personal information from children.

9Changes to this Policy

We may update this Policy from time to time. When we do, we will revise the "Last updated" date above and, for material changes, provide additional notice. Continued use of the Service after an update constitutes acceptance of the revised Policy.

10Contact

Questions about this Policy or your data? Email hello@scopedocket.com.