Privacy Policy
This Privacy Policy describes how Document Blueprint ("we", "us", "our") collects, uses, shares, and protects information about you when you use our service. We respect your privacy and are committed to handling your data carefully and transparently.
1. Information we collect
1.1 Account information
When you create an account we collect: your email address, your display name (if provided), and your authentication identifier from Google (when you sign in with Google). If you sign up for a paid plan, Stripe collects your payment information directly; we never see or store your payment-card details.
1.2 Content you upload
The service is a document-automation platform. You upload documents (PDFs and other file types), define templates, and create cases. The content you upload, including any personal data contained within those documents, is processed and stored to provide the service.
1.3 Sensitive data
The service supports storing sensitive personal data (Social Security Numbers, dates of birth, financial account numbers, tax identifiers, driver's license numbers, passport numbers, payment card numbers, medical record numbers, patient identifiers, and similar data) under the access controls described in Section 5 below.
You are responsible for ensuring that you have legal grounds to process any personal data you upload, including data of third parties (your customers, employees, clients, patients).
1.4 Integration data
When you connect Gmail to send emails, we request the gmail.compose OAuth scope, which we use to create drafts in your account, to send an email when you click Send, and to send the emails of automations you set to send. When you connect a Gmail mailbox for automations, we request gmail.readonly, gmail.compose and calendar.events: we use them to read incoming messages matching your automation rules, to compose draft emails on your behalf, to send the emails of automations set to send, and to create, update and remove the reminder events your automations or the chat assistant add to your Google Calendar.
When an automation ingests a message, the sender address and subject line are always stored on the resulting case: they identify where a document came from and cannot be switched off. Each automation then offers two capture choices: Files (attachments), ON by default, and Body, which is OFF by default; you must explicitly enable it per automation if you want the email body stored. When Body capture is enabled, the body of matching messages is stored on the corresponding case until you delete the case. When Body capture is disabled, the email body is never written to our database. Deleting a case removes its stored sender, subject, and any captured body.
When you connect your Google Drive account, we request drive.readonly and drive.file OAuth scopes. We use these to read files you have configured for ingestion and to save files we generate.
We send an email from your Gmail when you click Send on a screen that shows the whole email, or when an automation whose email step is set to send runs. Otherwise the service composes Gmail drafts in your account, which you review and send yourself.
1.5 Usage and technical data
We collect technical data automatically when you use the service: IP address, browser type and version, device characteristics, the pages you visit, and timestamps. We use this for security, performance monitoring, and product analytics. See Section 6 for cookie details.
1.6 Electronic signatures
The portal includes a "Review & Sign" flow for signing documents electronically. When you sign, we record the signature evidence contemplated by the E-SIGN Act and UETA: your name and email, the consent disclosure you accepted, the time of each signature action, your IP address and browser user agent, and tamper-evident hashes of the signed document and the signature images. These records are kept for seven years (see the data retention policy). If you save a signature image for reuse, it is stored with your account until you replace it or delete your account.
2. How we use your information
We use the information we collect to:
- Provide, maintain, and improve the service.
- Process documents you upload, run AI extraction on them, fill your templates, and generate outputs.
- Authenticate you, secure your account, and prevent abuse.
- Communicate with you about the service (account notices, security alerts, billing receipts, important updates).
- Send you product-update email, but only if you asked for it. This is optional, it is never a condition of creating or keeping an account, and you can withdraw it at any time without affecting your use of the service. Account, security, and billing messages are separate: those are part of the service and are not marketing.
- Comply with legal obligations and enforce our Terms of Service.
We do not sell your personal information. We do not use your content for advertising. We do not use your content to train any AI model; see Section 3.
3. AI processing
The service uses Google's Gemini API to extract structured data from your documents, to fill template fields, and to run the chat assistant. Specifically:
- What is sent. When you trigger autofill, document extraction, or AI-assisted features, the relevant document content (PDF text, image data, prompts containing case data) is transmitted to Google's Gemini API. When you use the chat assistant, your messages, the attachments you add to them (including audio and video), and the case data its tools read are transmitted as well. Values of fields your workspace lists as sensitive are removed from the case data we send; a document that contains such a value is still read in full when you run extraction on it.
- Retention by Google. Per Google's published Gemini API terms, prompts and responses sent to the Gemini API are not used for model training. Google logs prompts and responses for a limited period for abuse monitoring. We do not store separate copies of extraction prompts. Chat assistant conversations, with their attachments, are stored in your account until you delete them or the account.
- Structured and open-ended output. Template extraction uses a structured-output mode: the model fills constrained fields you have defined. The chat assistant and prompt outputs you configure generate free text from your instructions, case data and attachments.
We do not share your content with any other AI provider.
4. How we share information
We share your information only as described below:
- Service providers. We share information with vendors that process data on our behalf to provide the service: Google (Firebase hosting, Authentication, Firestore database, Cloud Storage, KMS, Gemini API), Stripe (payments), SendGrid (transactional email), HubSpot (customer relationship management: your account email, display name, how you found us, and whether you opted in to product-update email). These providers are bound by data-processing terms aligned with applicable law. The complete list, with the categories of data each one processes, is on our Subprocessor List.
- Compliance and legal process. We may share information when required to comply with valid legal process, prevent fraud or abuse, or protect the rights, property, or safety of users, the public, or us.
- Business transfers. If we are acquired or merge with another entity, your information may be transferred as part of that transaction. We will notify you and provide choices where required by law.
- With your consent. We share information with third parties when you direct us to (e.g., when you grant a collaborator access to a case via the portal).
We do not sell your personal information. We do not share your information for cross-context behavioral advertising.
5. Data security
Security controls, and where they fall short today:
- Encryption in transit. All connections to the service use TLS 1.2 or higher.
- Encryption at rest. Your data and files are encrypted at rest by Google Cloud using Google-managed keys: Firestore for case data and field values, Cloud Storage for uploaded documents. The app adds no encryption of its own, and no value or file is encrypted under a key of its own.
- Sensitive fields. A workspace admin can list fields as sensitive. Values of a listed field are kept in a separate record for each case rather than on the case itself. Only the account owner and teammates holding the Manage Sensitive Data capability in that workspace can read that record, and our database rules enforce that for reads from the browser as well as on our servers. Browsers cannot write the record. Teammates write it only through actions that require the same capability; automation ingestion, automation inputs, and a portal client's own answers and signatures also write it, since those values arrive through them. Listed values are not sent to an AI model (see Section 3).
- Auto-detection. When an automation ingests a document and a template is attached to it, or when extraction is run again on a file in a case, we match the names of the fields extracted from that document against a fixed list of patterns: Social Security numbers, dates of birth, financial and tax identifiers, driver's licence and passport numbers, payment card numbers, and medical identifiers. A match is redacted from the copies of the extraction stored alongside the file and on the run record. The full value is still written to the case: to the separate record above when the field is on the workspace's sensitive list, and to the case itself otherwise. Detection matches field names rather than the contents of a value, and does not run on ingestion without a template. The pattern list is fixed: an administrator cannot change it or switch it off, and adds protection by listing fields as sensitive instead.
- Audit log (not yet in use). The app defines a per-account audit collection that only our servers can write to and only the account owner can read, but nothing writes to it today. Access to sensitive field values is not recorded, and no IP address or user agent is recorded for it. We do not retain these records for seven years: whatever the collection holds is deleted with the account.
- Access control. Account access is enforced by Firebase Auth session cookies. Server actions and API routes verify authorization on every request. Multi-tenancy is path-isolated. One person operates the service. No screen in the app lets us read your cases, documents or field values, and there is no impersonation or sign-in-as feature; operator access happens through the Google Cloud console, and those administrative actions are recorded in Google's audit logs. Signing out deletes the browser's copy of the session cookie on that device. Sign out everywhere, in your account settings, ends every session on the server: any other copy of the cookie stops working on its next request.
No system is perfectly secure. If we discover a breach affecting your data, we will notify you and any required regulator within the timeframe required by applicable law.
6. Cookies and tracking
We use a limited set of first-party cookies:
- Necessary cookies:
session (authentication), _legal_consent (your cookie-banner choice). These are always set; you cannot opt out without losing access to the service.
- Analytics cookies:
_ga and _ga_* (Google Analytics 4), and x_attr (remembers the campaign or referrer that brought you to the site, so we can attribute signups to marketing sources). Set only if you accept analytics in the cookie banner.
- Experiment cookies:
x_rid (a random identifier that assigns A/B variants on marketing pages). Set only if you accept experiments in the cookie banner.
We do not use third-party advertising cookies and we do not share cookie data with ad networks. See our Cookie Policy for full details, including how to change your preferences.
7. Data retention
- Account data is retained as long as your account is active. After deletion, account data is removed within 30 days, except where retention is required for legal, accounting, or fraud-prevention reasons.
- Cases and documents are retained as long as you keep them. You can delete cases at any time from the dashboard. Deletion removes data within 30 days, except as noted above.
- Audit logs for sensitive-data access are not retained for a fixed period. The audit collection records nothing today, and it is deleted with the account.
- Billing records are retained for at least seven years to comply with tax and accounting obligations.
For the full retention schedule (authentication tokens, AI processing, operational logs, email logs, backups, and manual vs automated enforcement), see our data retention policy.
8. Data residency
Your data is stored in the United States. Database records are held in Google's nam5 multi-region, which Google replicates across separate US regions. Files are held in Google Cloud Storage in the United States, currently in the us-east1 region. The application and its background processing run on Google Cloud in US regions: currently us-east4 for the web application and us-central1 for background processing, and the handlers that record storage usage as files are added and removed run in us-east1. Content sent for AI processing is processed by Google's Gemini API, listed with our sub-processors. We do not currently offer EU data residency. Customers subject to EU data localization requirements should contact us before onboarding.
9. Your rights (GDPR, CCPA, and other privacy laws)
Depending on your jurisdiction, you may have rights to:
- Access the personal information we hold about you.
- Correction of inaccurate personal information.
- Deletion of your personal information (subject to legal retention obligations).
- Portability of your personal information in a machine-readable format.
- Object to or restrict certain processing.
- Withdraw consent for processing based on consent.
- Lodge a complaint with your data protection authority.
To exercise these rights, email privacy@documentblueprint.com. We will respond within 30 days (or 45 days for CCPA requests). For the full process, including what info to include, our identity verification steps, response timelines, and how to appeal, see our Data Subject Rights process.
We do not sell personal information. California residents have the right to opt out of the "sale" or "sharing" of personal information. If your browser sends a Global Privacy Control (GPC) signal, we treat it as a decision to decline non-essential cookies, unless you have already made an explicit cookie choice of your own.
10. Restricted data and regulated industries
See Section 4 of our Terms of Service for the full list of restricted-data categories. In short:
- Protected Health Information (PHI) under HIPAA. Requires a Business Associate Agreement before upload. Contact legal@documentblueprint.com.
- PCI cardholder data. Prohibited; we are not PCI-DSS certified.
- Classified, ITAR-controlled, EAR-controlled, FedRAMP-restricted. Prohibited.
- Attorney-client privileged. Allowed under existing controls; configure visibility carefully.
11. Children
The service is not directed at children under 13 (or under 16 in the EU/UK). We do not knowingly collect personal information from anyone in those age groups. If you believe a child has provided us with personal information, contact privacy@documentblueprint.com and we will delete it.
12. International data transfers
If you are located outside the United States and use the service, your information will be transferred to and processed in the United States. By using the service you consent to this transfer. We rely on Standard Contractual Clauses or other valid transfer mechanisms where required.
13. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. When we make changes that materially affect your rights or our processing of your personal information, we will require you to re-accept the updated policy before continuing to use the service.
14. Contact
For privacy inquiries or to exercise your rights: privacy@documentblueprint.com
For legal notices: legal@documentblueprint.com