Privacy Policy

Codegraff, including graff, CodeDB, CodeDB Pro, Harness, the Codegraff gateway, and codegraff.com, is the property of The Standard Harness Company of Singapore. The Standard Harness Company of Singapore is responsible for the personal data described in this policy. In this policy, “Codegraff”, “we”, and “us” mean The Standard Harness Company of Singapore.

We process your code to generate embeddings. We do not keep that content. Our managed CodeDB embedding service applies zero data retention (ZDR) to embedding content for all users, including free users. Inputs and outputs are processed transiently in memory to fulfill the request; they are not logged, cached, or written to persistent storage by the embedding service.

• Covered content: request bodies, source code and snippets, candidate file paths, task or search text, and generated embedding vectors.
• No hosted repository index: we do not retain a copy of your repository or create a server-side vector index from embedding requests.
• Analytics are separate: content-free usage and service metadata may be stored as described below. ZDR does not mean that no operational records exist.

Depending on the retrieval mode and local index, CodeDB may send your query and bounded code snippets or paths for embedding. Building a semantic index sends batches of source chunks. The resulting index and vectors are stored on your device, under your control. For an on-device retrieval call that sends no query or source text to the embedding service, pass semantic: "local" to codedb_context.

This ZDR policy covers the managed CodeDB embedding service we operate. If you set CODEDB_EMBEDDINGS_URL to a custom endpoint, that provider’s retention policy applies. Your coding client, its model providers, and other connected services also have their own policies. See the CodeDB data and privacy documentation and our Terms of Service.

CodeDB client telemetry is enabled by default. It measures tool usage, latency, response sizes, startup and index statistics, software version, and platform. It does not include source code, file contents, file paths, or query text. Disable client telemetry with CODEDB_NO_TELEMETRY=1 or --no-telemetry.

To operate and protect the hosted embedding service, we also maintain installation and authentication records, usage counters, and request metadata. These may include installation or account identifiers, public installation keys and certificate status, client version and platform, model, input counts and character counts, response status, latency, region, and network-derived rate-limit identifiers. These records can be associated with an installation or account; they are not all anonymous. They do not contain embedding inputs or outputs.

We use these content-free records for usage reporting, reliability, capacity planning, authentication, and abuse prevention. Retention follows those operational purposes; the embedding-content ZDR policy does not apply to these records. Disabling client telemetry does not disable hosted-service authentication, accounting, or rate limits. You may contact us about access or deletion of records associated with your account or installation.

In addition to the CodeDB service metadata above, we collect the following account, billing, and CodeDB Pro telemetry data:

On public blog posts, we measure browser-reported active time and maximum article scroll depth. Across public website pages and blog posts, we record aggregate delivery counts by page, format, status, and coarse reported crawler family. A random identifier exists only for the current page view; no analytics cookies or cross-page visitor IDs are used. Reports can be incomplete or automated and do not prove human or agent reading.

We honor Do Not Track and Global Privacy Control signals. Custom website analytics do not store IP addresses, full user-agent strings, query strings, account IDs, or article content. Records are retained for 30 days and deleted by a daily cleanup job. Cloudflare platform logs have separate retention.

Transient embedding processing is described above. Our usage analytics and client telemetry do not record:

• File paths or file contents
• Search patterns or queries
• Embedding request bodies or generated vectors

Full card or bank details stay with Stripe. Infrastructure providers may process network and access metadata under their own retention policies; this is separate from our content-free application analytics and the embedding-content ZDR commitment.

• Email: to deliver your license key and send transactional messages (no marketing without consent)
• Stripe IDs: to manage subscriptions, billing portal access, and automatic top-ups you explicitly enable
• CodeDB Pro session summaries (if Pro telemetry is on): to compute your personal dashboard stats and anonymous aggregate counters on the public landing page

We share data with:

• Stripe: payment processing. Their privacy policy applies to your payment data.
• Resend: transactional email delivery.
• Cloudflare: infrastructure and edge network.

We do not sell your data to any third party.

Under GDPR and CCPA you have the right to:

• Access: request a copy of data we hold about you
• Deletion: request erasure of your account and data
• Telemetry opt-out: for CodeDB, set CODEDB_NO_TELEMETRY=1 or pass --no-telemetry. For CodeDB Pro, use codedb-pro config set telemetry=off.

To exercise these rights, email hi@codegraff.com. We action deletion requests within 30 days.

We set one first-party HttpOnly cookie (cg_session) when you log in to the dashboard. It expires after 30 days. We also set a cg_ref cookie (30 days) if you arrive via a referral link. No tracking or advertising cookies are used.

Privacy questions: hi@codegraff.com