Privacy Policy
Your account data and private work deserve clear boundaries.
Effective October 16, 2026 · CodeMerchant by Divide-By-0
CodeMerchant analyzes projects you deliberately submit. It keeps source handling narrow, records source-free findings, and gives you controls over scanning and retained account data.
1. Scope
This Privacy Policy covers CodeMerchant websites, accounts, GitHub connections, supplemental project context, quality scans, valuation reports, remediation tools, and agent interfaces. It describes personal information practices and the separate handling of private source material.
2. Information you provide
Account data includes your email address, password verifier, optional Google identity, optional GitHub profile, and the Data License version and acceptance time. Organization context can include additional software used, company size, years in operation, and miscellaneous notes. Submitted content includes supplemental filenames, private-repository identifiers, code, configuration, task-tracker exports, and Git history you choose to scan. Privacy requests and support details are also retained.
3. Information collected through use
CodeMerchant records installation and repository metadata, scan timing and status, API-token metadata, security events, derived quality metrics, valuations, finding categories and counts, relevant file paths, and exact commit hashes matched by the public-history check. We also retain signup referral sources (a referring hostname or UTM source label), using a first-party cookie for up to 30 days. We do not retain referring URL paths or query strings. Aggregate signup and repository-progress reports help us understand usage. Hosting infrastructure may create short-lived request, security, and performance logs.
4. How submitted source is processed
Private source is read in bounded Worker memory. Supplemental uploads are stored privately in Google Cloud Storage and processed by background Google Cloud Run jobs; PDF text extraction and image OCR produce derived report signals. Repository file bodies, patches, matched personal values, and credentials are discarded after the scan request. Original supplemental files are retained privately for CodeMerchant admin review and future analysis, even if automatic extraction fails; scan completion does not delete these attachments. Reports retain categories, counts, scopes, paths, and derived metrics. Repository code, CI workflows, and tests stay unexecuted.
5. Purposes
When you request a remediation PR, selected source with detected private values masked is sent to Google Gemini to plan constrained edits. Source is not stored by CodeMerchant after the request. Information is used to authenticate accounts, connect requested sources, run selected quality and privacy checks, generate indicative valuations, create user-requested remediation pull requests, support coding-agent access, prevent abuse, troubleshoot failures, answer privacy requests, improve reliability, prepare tasks and RL environments, share samples with prospective labs, and complete commercial licensing under the accepted Data License.
6. Service providers and external destinations
Codex Sites and its Cloudflare infrastructure host the application and D1 database. Google handles Google sign-in when chosen. GitHub handles repository authorization and remediation pull requests. Software Heritage receives exact Git commit hashes for archive-presence checks; repository names and source are not sent to Software Heritage. Google Cloud Storage and Cloud Run process supplemental uploads; OCR runs inside the processing job. A configured agent reviewer receives metadata and aggregate signals only. Customer source is kept away from external PII and secret-scanning APIs. Separately from automated scanning, the accepted Data License authorizes selected samples to prospective labs under confidentiality and evaluation restrictions, and delivery of purchased materials to buyers for any lawful purpose, including AI training, fine-tuning, testing and evaluation, creating reinforcement-learning environments, resale, sublicensing, characterization, analysis and processing. Buyer deals are authorized by default, subject to the Data License notice and 24-hour veto process. The seller authorizes resale by default, subject to the notice and veto process below. Public releases are prohibited.
7. Personal information sales and advertising
CodeMerchant sells no personal information and serves no behaviorally targeted advertising. Project samples and sales concern selected materials under the accepted Data License; account personal information is not included in those samples or sales.
8. Legal bases and disclosures
Processing supports the service you request, account and system security, legal compliance, and legitimate product operations. Information may be disclosed when you direct a connection or remediation action, to infrastructure providers acting for CodeMerchant, during a corporate transaction with appropriate safeguards, or when law requires disclosure.
9. Retention
Account identifiers and reports remain while the account is active, subject to your rights and the Data License. Raw submitted source currently follows the ephemeral rule above. You may terminate the Data License for all or specified Submitted Materials through the account-linked request form or by email. On receipt, we stop new use, sharing, and sales of the affected materials, delete operational copies and derivatives containing or reconstructing them within 30 days, and require contractors, providers, and evaluation-only sample recipients to do the same. Isolated backups are deleted within 90 days. Only the restricted legal and source-free records described in Section 7 of the Data License may remain, and we confirm completion and any retention basis in writing. Previously completed buyer licenses survive termination; we identify those licenses on request. You may separately request a return copy within 90 days; requesting return and termination together does not extend deletion deadlines. Additional legal access and deletion rights remain available. API tokens expire after 90 days. OAuth states expire after 10 minutes. Privacy requests remain as an accountability record.
10. Security
CodeMerchant uses encrypted GitHub tokens, hashed API tokens, salted password derivation, short-lived installation tokens, bounded scans, source-free reports, secure session cookies, and least-purpose data flows. Every system carries residual risk, so credentials found by a scan should be revoked and rotated before sharing a project.
11. Your choices and rights
You can select individual GitHub repositories or an entire organization, optionally attach context to each selected repository, change GitHub App access, uninstall the App, sign out, and let tokens expire. Depending on location, you may request access, correction, export, deletion, restriction, or objection and may appeal a response through the same request channel. Identity verification protects account data before fulfillment.
12. International use and children
CodeMerchant infrastructure may process information in the United States and other locations used by its hosting providers. CodeMerchant is intended for adults and business users and is unavailable to children under 13.
13. Changes
Material updates will appear here with a revised effective date and, when appropriate, an in-product notice. Continued use after the effective date means the updated policy applies to later activity.
Optional Google Analytics
If you allow analytics, Google receives public-page views, referring website origins, bounded campaign labels, browser and device information, and analytics cookie identifiers. Tracking stays off until you choose Allow analytics. Private account and repository pages, email addresses, source material, and URL query strings are excluded. Advertising personalization and Google signals are disabled. You can decline or withdraw consent using Analytics preferences on any public page; withdrawal stops collection and removes our Google Analytics cookies.
How Google uses information from sites that use its services
14. Data License, contact, and requests
The Data License governs submission, evaluation, ownership promises, acceptance, payment, and any later commercial transaction. Submit a secure account-linked request for access, correction, export, deletion, or another privacy question, or email team@codemerchant.ai.