Effective Date: November 15, 2026

Privacy Policy & Data Governance

Codasift is engineered with a strict local-first privacy architecture. This document sets out our strict Zero-Code-Storage architecture and commitment, explicit data retention lifecycles, and compliance with GDPR, CCPA/CPRA, and India DPDP Act 2023.

01Zero-Code-Upload by Default & Opt-In Cloud Policy

Developer TL;DR:100% on-device AST processing by default. Your code never touches our servers unless you explicitly opt into upcoming cloud workspaces.
100% Local-First by Default • Strictly Opt-In Cloud Sync

Codasift is designed and distributed as an offline-first developer tool. When you install and run Codasift CLI, 100% of your source code, AST trees, git diffs, and exported context stay strictly on your local device. We never transmit or store your source code on our servers by default. Upcoming Cloud Pro & Team Workspaces features are strictly opt-in; code is never uploaded unless you explicitly configure and authorize cloud sync.

Codasift never stores, caches, or inspects your source code on our servers without explicit user opt-in.

  • 100% Local On-Device Processing by Default: When using the Codasift CLI (Free or Local Pro), Abstract Syntax Tree (AST) parsing, symbol extraction, dependency graph generation, and context exports occur entirely on your local workstation without cloud uploads.
  • Strictly Opt-In Cloud Collaboration: Upcoming experimental Cloud Pro & Team Workspaces are fully opt-in. In local mode, zero repository code or AST data is ever uploaded. When explicitly opted into cloud collaboration, only authorized team workspaces synchronize, and code is never used for model training or secondary telemetry.
  • Zero Proprietary Code Ingestion: Codasift operates on a local-first paradigm. When using the CLI locally, your source code, git diffs, directory trees, and environment variables remain 100% on your workstation. In the rare or unforeseen event that an anomalous edge-case causes code snippet metadata to reach telemetry, Codasift commits to promptly purging and permanently expunging any such data upon discovery or notification to support@mail.codasift.dev.

02Zero AI Training Policy & BYOK Scope

Developer TL;DR:We never train AI models on your code. When you use your Google Gemini key, prompts travel directly to Google without routing through Codasift servers.

Zero Model Training: Codasift strictly never uses, shares, or sells your codebase metadata, summaries, or developer prompts to train, fine-tune, or align proprietary or third-party artificial intelligence models.

Third-Party BYOK Notice (Google Gemini): When you configure and use your own Google Gemini API key within Codasift, code context payloads and prompt requests transmit directly from your workstation to Google Cloud / Google GenAI endpoints. Google’s data retention, transit encryption, and potential model training policies are governed exclusively by your direct terms of service and enterprise agreements with Google Cloud. Codasift has no visibility into, control over, or liability for Google’s independent data processing practices.

03User-Controlled Cloud Sync & Ephemeral Processing

Developer TL;DR:Cloud sync is 100% opt-in. AI proxy payloads exist solely in ephemeral RAM for <30 seconds and are purged immediately. Deleting a workspace purges all cloud context permanently.
Cloud Features are Strictly Opt-In and User-Executed

Cloud workspace coordination is never activated automatically. Only if you explicitly choose to authenticate and run cloud sync commands (e.g. codasift sync or team workspace links) does Codasift coordinate structural metadata with our encrypted cloud coordination layer. You retain full, sovereign control to disconnect, revoke, or permanently hard-delete any cloud workspace data at any time.

User-Controlled Cloud Sync: If you explicitly opt into Cloud Workspace Sync (available in preview tiers), structural context summaries are retained on our encrypted cloud coordination layer only for as long as you choose to keep that workspace actively synced.

Ephemeral AI Provider Processing: Any data relayed through our cloud proxy for automated context enhancement is strictly ephemeral. It resides in volatile memory (RAM) solely for the microsecond duration required to execute the API request (<30 seconds), is never written to disk, and is immediately purged upon response delivery.

User-Controlled Workspace Deletion: When you choose to delete a synced workspace or project from Codasift, all associated context summaries and records are permanently deleted from our cloud infrastructure and active caches. We retain your cloud workspace data only for as long as you choose to keep the sync active.

04Explicit Data Retention Schedule

Developer TL;DR:Source code: 0s retention. RAM payloads: <30s. Rate logs: 30 days max. Account deletion instantly purges all database collections.
Data CategoryStorage LocationRetention PeriodPurge Mechanism
Source Code & AST DataLocal Workstation Only0 Seconds (Never Transmitted)Local client filesystem control
Cloud Sync Context SummariesEncrypted Cloud InfrastructureUntil user initiates deletionPermanent deletion upon workspace removal
Ephemeral AI PayloadsVolatile RAM Only<30 Seconds (In-Transit)Automated memory expulsion
Account & License RecordsSecure DatabaseDuration of active accountImmediate via self-serve dashboard / purged across all collections
Consent Audit Receipts (GDPR Art. 17(3)(e))Secure Database (Zero-PII)Statutory Limitation PeriodZero-PII irreversible salted HMAC commitment & ECDSA signature (no plaintext email or user IDs retained)
Security & Rate-Limit LogsApplication Log Aggregators30 Days MaximumAutomated log rotation & purge

05Zero Payment Card Data Collection

Codasift does not process, capture, transmit, or store credit card numbers, CVVs, expiration dates, or bank account details. All payment checkout workflows are hosted and processed exclusively by Dodo Payments (Merchant of Record), a PCI-DSS Level 1 compliant payment processor. Codasift receives only an encrypted, cryptographically verified webhook event containing order IDs and license entitlement confirmation.

06Infrastructure Safety Telemetry & Secret Scrubbing

To safeguard our API infrastructure against denial-of-service attacks and automated fraud, our backend maintains minimal HTTP operational telemetry:

  • HTTP request method, route accessed, status code, request duration, and payload byte size.
  • Device Slot Entitlement: A hardware-anchored deterministic UUIDv5 identifier derived from one-way hashed OS entropy in volatile RAM, stored locally on your workstation (~/.codasift/machine_id) paired with an anonymized hardware tag derived via SHA-256 hash of your local hostname (e.g. Device-a8f3b9c1). Raw hardware parameters (such as macOS ioreg device trees or platform serials) are evaluated exclusively in volatile memory, never persisted in raw form, and never transmitted across the network.
  • Rate-limiting buckets in Redis to prevent brute-force attacks against authentication endpoints.
  • Backend Operational Logging (Axiom): Server-side API telemetry and error monitoring are streamed asynchronously to Axiom Inc. for real-time performance auditing, latency monitoring, and service reliability. This is strictly server-side: when you install the local CLI (pip install codasift), it operates 100% locally on-device. Zero terminal logs, developer workstation code, AST trees, or file contents are ever shipped to Axiom.
  • Client-Side UX Telemetry (PostHog): For web application navigation and error diagnosis, we utilize PostHog with strict Total Privacy masking (maskAllInputs: true and maskTextSelector: '*'). All on-screen text, code previews, and project titles are irreversibly masked with asterisks prior to transmission. Telemetry is routed via first-party reverse proxy to defend against third-party data tracking. Users may opt out of UX telemetry at any time via our Cookie Preferences banner.

Zero-Leakage Scrubbing: Telemetry ingestion pipelines aggressively scrub all Authorization headers, Google Gemini API keys, JWT access tokens, OTP verification codes, and passwords before logging. Raw client IP addresses are not stored in permanent analytical data stores.

07International Regulatory Compliance & Consumer Rights

Developer TL;DR:Full compliance with GDPR, CCPA/CPRA, and India DPDP Act 2023. Self-serve 1-click account and data erasure available in your dashboard.

GDPR (European Union & United Kingdom)

Under the General Data Protection Regulation (GDPR), you possess the Right to Access, Right to Rectification, Right to Data Portability, and the Right to Erasure (“Right to be Forgotten”). You can exercise immediate self-serve deletion of your account and all associated license records, machine identifiers, and cloud workspaces directly in your Dashboard Settings (Danger Zone), or by emailing support@mail.codasift.dev.

Legal Claims Defense (GDPR Art. 17(3)(e)): When an account is hard-deleted, all personal data is permanently wiped across our database collections. In strict accordance with GDPR Article 17(3)(e), Codasift preserves solely an immutable, Zero-PII cryptographic audit receipt (an irreversible HMAC-SHA256 commitment of the claimant's email paired with an ECDSA P-256 digital signature) to verify affirmative Terms of Service acceptance in post-erasure disputes without retaining any plaintext personal data.

Local Client Data & Software Uninstallation: Deleting your account permanently deletes all server-side and cloud records from our infrastructure. We cannot delete your local data. Because Codasift executes locally on your device, local AST context files, repository configurations, and cached credentials remain solely under your control on your machine. To completely remove local data, you must manually uninstall the CLI (pip uninstall codasift) and remove the local configuration folder (~/.codasift).

CCPA / CPRA (California Consumer Privacy Act)

We provide California residents with notice at or before collection. Codasift does not sell, rent, or share personal information with third parties for cross-context behavioral advertising. You may submit requests to know or delete personal information without discriminatory treatment via the dashboard self-serve deletion mechanism or by contacting privacy operations.

Digital Personal Data Protection Act 2023 (India)

In accordance with Section 8 and Section 12 of the Digital Personal Data Protection Act 2023, Codasift acts as a Digital Data Fiduciary. We process personal data solely with lawful consent and for specified, legitimate technical purposes. Data Principals have the explicit right to withdraw consent and obtain erasure of personal data through our self-serve dashboard or by contacting our Privacy Team at support@mail.codasift.dev.

Designated Grievance Redressal Officer:

Grievance Officer: Legal & Compliance Team

Email: support@mail.codasift.dev

Jurisdiction: Berhampur, Odisha, India

EU AI Act Transparency Disclosures

Codasift provides code analysis tools that integrate with local AI models (such as Ollama) or user-supplied external foundation model endpoints (such as Google Gemini). Codasift does not deploy black-box autonomous decision engines affecting human rights or biometric profiling.

08Third-Party Sub-Processors & Infrastructure

To deliver our software services, Codasift engages authorized third-party sub-processors who adhere to rigorous data protection agreements (DPAs) satisfying GDPR Article 28 and DPDP Act provisions:

Sub-ProcessorPurpose & Processing ScopeData LocationCompliance Standard
Dodo Payments Inc.Merchant of Record, payment gateway, subscription management, invoicing, tax remittanceUnited States / GlobalPCI-DSS Level 1, SOC 2
Vercel Inc.Frontend web application hosting, Edge middleware routing, global CDN asset delivery, and SSL/TLS terminationGlobal Edge Network / United StatesISO 27001, SOC 2 Type II, GDPR DPA
Render Services, Inc.Backend FastAPI application server execution, API routing, and secure container infrastructureUnited States (Oregon / Frankfurt AWS Regions)SOC 2 Type II, ISO 27001, GDPR DPA
MongoDB AtlasEncrypted database storage for user profiles, hashed hardware IDs, license tokens, and cloud sync recordsAWS / GCP Data Centers (US/EU)ISO 27001, SOC 2 Type II, GDPR DPA
Redis / Cloud Memory CacheIn-memory rate limiting, token expiration blacklist, transient session cachingCloud VPC (Ephemeral RAM)Encrypted in-transit (TLS 1.3), SOC 2
Google Cloud / Google GenAIFoundation model inference endpoint for user-configured BYOK features (direct workstation to API)Global (Google Cloud)ISO 27001, SOC 2/3, GDPR DPA
Resend Inc.Primary transactional email delivery, security OTP verification codes, account deletion verifications, and account alerts via HTTPS APIUnited States / GlobalSOC 2 Type II, GDPR DPA
Google LLC (Gmail API)Transactional email delivery, security OTP verification codes, account deletion security alerts, password resets, and subscription receipts via Gmail REST API (over secure HTTPS port 443)Global (Google Cloud)ISO 27001, SOC 2/3, GDPR DPA
Cloudflare, Inc. (DNS, Edge SSL & Turnstile)Authoritative DNS resolution, domain edge routing, SSL/TLS termination, privacy-preserving bot detection, brute-force defense, and adaptive security challenge verification (GDPR Art. 6(1)(f) Legitimate Interest)Global Edge NetworkISO 27001, SOC 2 Type II, GDPR DPA
Axiom Inc.Server-side structured operational logging, API performance telemetry, and backend error diagnostics (strictly scrubbed; zero client/CLI code ingestion)United States / Cloud (AWS)SOC 2 Type II, GDPR DPA, HIPAA Compliant
PostHog Inc.Product navigation analytics, error tracking, and session diagnostics with Total Privacy masking (zero plaintext UI/code ingestion)United States / EU CloudSOC 2 Type II, ISO 27001, GDPR DPA
Cloudflare Turnstile Privacy & Bot Defense Architecture:

We deploy Cloudflare Turnstile to protect authentication and account endpoints from automated abuse, credential stuffing, and bot attacks. When adaptive security verification is required, Cloudflare analyzes technical telemetry (such as IP address, browser headers, and challenge interaction signals) to evaluate human interaction. This processing is strictly necessary for platform integrity and is carried out under our legitimate interest in platform security (GDPR Art. 6(1)(f)). Cloudflare operates as a data processor under an executed Data Processing Addendum, processes verification telemetry solely to validate human presence, and does not harvest personal data to build advertising profiles or track users across unaffiliated sites. Product analytics are processed via PostHog solely on our behalf to diagnose performance issues; PostHog does not sell personal data or track users across unaffiliated sites. Any IP address processing by our infrastructure or analytics sub-processors is strictly limited to coarse geographic lookup (country/region level) and network security defense, and is never used for behavioral advertising or user profiling. For additional details, see the Cloudflare Privacy Policy.

Zero-Marketing Communications Policy (CAN-SPAM 16 CFR § 316.3 & GDPR Art. 6(1)(b)/(f)):

Codasift maintains a strict Zero-Marketing Policy: we send zero promotional newsletters, sales solicitations, or ad marketing emails. Email dispatches are strictly limited to essential operational notifications (one-time verification passcodes, account deletion security alerts, password resets, and subscription receipts). Because these messages are essential security and billing communications, they cannot be unsubscribed from under electronic communications regulations.

Google API Services User Data Policy & Limited Use Disclosure:

Codasift's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, our application utilizes the https://www.googleapis.com/auth/gmail.send scope strictly to transmit transactional account security notices, verification codes, and purchase receipts requested by users. We do not use Google user data to develop, train, or fine-tune generalized artificial intelligence (AI) or machine learning (ML) models, nor do we transfer or sell Google API user data to third parties, data brokers, or advertising networks.

09Cookies, Local Storage & Tracking

Codasift uses strictly necessary cookies and browser local storage solely for session authentication, security, and interface preferences. We do not use third-party marketing or advertising tracking cookies.

Functional UI Display Flags: To preserve your visual interface preferences across visits without requiring remote server tracking, we maintain lightweight on-device flags in browser local storage:

  • codasift_beta_banner_dismissed_v2: Remembers when you close the early access announcement bar so it does not obstruct your view on subsequent visits.
  • cf_cookie_dismissed_v1: Remembers when you close the cookie preferences dialog without selecting an option.

These functional keys store solely binary strings ("true"), contain zero tracking data, personal identifiers, or behavioral telemetry, and are never transmitted to our backend servers.

Analytics Strictly Opt-In: Performance diagnostics via PostHog remain strictly opt-in and disabled by default. When a user closes or dismisses the cookie banner without clicking "Accept All", PostHog analytics remains completely inactive and opted out.

For a complete, exhaustive registry of every cookie and storage mechanism, please review our dedicated Cookie Policy.

10Policy Updates & Advance Notice Commitment

Standard 30-Day Notice: If we make material modifications to this Privacy Policy, we commit to providing at least thirty (30) days (1 month) advance notice before changes take effect, posted prominently on our website or sent via email to registered users.

Immediate Security & Statutory Compliance: In situations where immediate updates are necessary to address critical cybersecurity vulnerabilities, protect user rights, or comply with statutory court mandates, amendments will take effect immediately upon publication. We will provide prompt notice in all cases.

11Contact & Data Protection Officer

For any questions, data subject requests, or privacy inquiries:

Privacy Team: support@mail.codasift.dev

Security Inquiries: support@mail.codasift.dev

Grievance Redressal: support@mail.codasift.dev