Privacy Policy
Last Updated: November 6, 2026
No Google Analytics, Meta Pixels, or invasive telemetry. Only strictly necessary first-party session cookies.
Your notes, terminal logs, brand kits, and compiled PDFs are never used to train or fine-tune AI models.
Local MCP mode keeps all files and Typst compilation on your own disk with zero operator visibility.
01. Introduction & Statutory Scope
Doc Buddy, is committed to safeguarding personal data and maintaining transparent processing standards across our Web Portal, Model Context Protocol (MCP) Server runtimes, and developer APIs.
This Privacy Policy is structured to comply with:
- India's Digital Personal Data Protection Act, 2023 ("DPDP Act")
- The EU & UK General Data Protection Regulation ("GDPR")
- The California Consumer Privacy Act ("CCPA") & CPRA
02. Data Fiduciary & Architectural Roles
Under India's DPDP Act and the GDPR:
Data Fiduciary (Data Controller): Doc Buddy Private Limited is the Data Fiduciary determining the purpose and means of personal data processed through Doc Buddy.
Data Principal (Data Subject): You, the registered developer or customer whose personal data is processed.
Data Processors: Cloud and payment providers engaged under contractual terms to execute infrastructure operations.
03. Categories of Personal Data Collected
We collect only the minimum personal data strictly necessary to fulfill document generation and account functions:
Email address, hashed password (PBKDF2/Supabase Auth), optional organization name. Google OAuth imports email, display name, and avatar URL.
Polar.sh customer ID, subscription ID, active tier, and billing timestamps. We never receive or store raw credit card numbers.
Client ID (e.g., claude-desktop), device label, and last-used timestamp. Single-use codes expire in 5 minutes; JWT tokens expire in 30 days.
Brand company name, custom hex accent color, footer confidentiality notice, and compilation metadata (title, theme, compile time, expiration).
04. MCP Server: Data Processing & Ephemerality
Local Mode (stdio): Processing occurs completely on your local workstation. Output files and quota databases remain on your local disk. Doc Buddy operators have zero access or custody.
To support AI prompt debugging, the MCP Server includes an automated Request Inspector (inspector.py). When generate_designed_pdf runs, incoming DocumentPayload records are held in memory (last 100 requests) and written to output/requests/req_*.json. Logs can be cleared at any time via /debug/ui or HTTP DELETE /debug/requests.
Third-Party Flowcharts: Mermaid diagrams are base64-encoded and rasterized via HTTPS to https://mermaid.ink/img/..., with offline fallback.
SSRF Hardening: Remote images are downloaded with strict IP filters blocking loopback, link-local, carrier-grade NAT, and private network ranges.
05. ZERO AI Model Training Guarantee
Doc Buddy does NOT use your notes, terminal output, code snippets, Brand Kit settings, or compiled PDF files to train, retrain, fine-tune, or evaluate any artificial intelligence or machine learning models.
06. Strictly Necessary Cookies & Zero Trackers
We operate a tracker-free platform. We do not load Google Analytics, PostHog, Mixpanel, or advertising pixels. We use only strictly necessary first-party cookies:
| Cookie Name | Purpose | TTL | Security |
|---|---|---|---|
| docbuddy_session | Platform session authentication | 30 days | HTTP-Only, Secure, SameSite=Lax |
| sb-*-auth-token | Supabase SSR authentication | Session | HTTP-Only, Secure, SameSite=Lax |
| inspector_session | Request Inspector auth | Session | HTTP-Only, SameSite=Lax |
07. Third-Party Data Sub-Processors
We transfer personal data only to verified cloud sub-processors bound by data protection agreements:
| Sub-Processor | Location | Activity | Data Scope |
|---|---|---|---|
| Supabase Inc. | USA (AWS) | PostgreSQL & Auth | Emails, credentials, tokens, metadata |
| Google LLC | USA / Global | OAuth 2.0 Auth | Email, display name, avatar URL |
| Polar.sh / Stripe | USA / EU | Merchant of Record | Customer ID, tier, billing period |
| Render Services Inc. | USA / EU | Cloud Hosting | HTTPS traffic, server connection logs |
| Cloudflare Inc. | Global Edge / R2 | Object Storage (Opt.) | Compiled vector PDF binaries |
| Mermaid.ink | Global CDN | Diagram Rendering | Base64 Mermaid diagram syntax |
08. Lawful Grounds for Processing
Processing is conducted under: (1) Contract Performance (account delivery, license validation, PDF compilation); (2) Legitimate Interests (platform security, rate limiting, debugging); (3) Legal Obligations (tax and financial accounting); and (4) Consent (voluntary beta waitlist).
09. Data Retention & Deletion
- Account Data: Retained until account deletion. Deletion cascades to profile, tokens, and records.
- Compiled PDFs: Retained for configured TTL (7–30 days) or until user deletion.
- OAuth Codes: Permanently deleted after single use or 5 minutes.
- Inspector Logs: FIFO ring buffer capped at 100 requests or purged on user command.
10. Your Rights (DPDP Act, GDPR & CCPA)
India DPDP Act 2023: Right to access summary of data, right to correction/erasure, right to grievance redressal, right to nominate.
GDPR / UK GDPR: Right of access, rectification, erasure, restriction, data portability, and objection.
California CCPA/CPRA: Right to know, delete, correct, and opt-out. Notice: We do NOT sell or share personal data for behavioral advertising.
12. Updates to This Policy
We may update this policy periodically to reflect architectural changes or regulatory updates. Continued use of our Services represents acceptance of modified terms.