Privacy Policy
Plain-language pilot version. It describes what BranchToBrowser actually collects and does in v1.
The fit checker runs in your browser. It does not upload, clone, or send your code anywhere. A brief is only shared if you choose to copy or download it and send it to us.
1. What we collect
- Contact email you provide
- Public repo URL, project name, and one-sentence description
- Framework and build command, if you provide them
- Your confirmations (you own the repo / have permission; it contains no secrets)
- Job and payment state (for example: eligible, paid, delivered, refunded) — card data itself is handled by the payment provider, never by us
2. What we do not collect
Secrets, passwords, tokens, API keys, private code, and card numbers. Intake is designed to reject secret-dependent repos before checkout, and you should never send us secrets in any form.
3. How data is used
Only to: review eligibility, fulfil the ship, send delivery or failure emails, reconcile payment and refunds, debug eligibility and build gates, and support a broken delivery if you contact us.
4. Retention — 7 days for code and raw logs
- Temporary clone and working files: deleted within 7 days after delivery or refund, whichever comes first.
- Raw build logs: deleted within 7 days after delivery or refund. We keep only summarised diagnostics (error class, attempt count, patch hash).
- Audit metadata we retain: job ID, repo URL, commit SHA, eligibility decision and reason codes, payment state, attempts summary, artifact hash, deployment provider and public URL, and refund ID if any. No secrets and no full source are retained in audit metadata.
- Your source code is never retained beyond the 7-day window.
5. Sharing
Only with the providers needed to run the service: a payment provider for checkout and refunds, an email provider for delivery emails, and a hosting provider for deployment. We do not sell personal data, and we do not sell data to advertisers or data brokers.
6. Security
Credentials for payment, email, and hosting are held outside the build worker. Build jobs do not have access to payment or email credentials, and secrets must never appear in logs.
7. Your rights
You may request deletion of your audit metadata where the law requires it, subject to payment and tax record retention that we must keep. Contact us via pilot support: support@branchtobrowser.com.
8. Changes
If we make material changes to this policy, we will post the updated version on this page and update its effective date.
9. Contact
BranchToBrowser pilot support: support@branchtobrowser.com