Privacy Policy

Version v2.0 · Effective 6 August 2026 · Blend by David Labs

This Privacy Policy explains how David Labs (“we”, “us”) collects, uses, stores, and deletes personal data when you use Blend (the “Service”). By creating an account or uploading a data export, you acknowledge this Policy. Material updates bump the version above.

1. Who we are

Controller: David Labs. Product: Blend — a personal cinematic film generated from life-stream exports you voluntarily provide (e.g. Instagram, Google Photos, and future lanes such as LinkedIn archives or Cursor JSONL). Contact: privacy@davidlabs.ca.

2. Data we process

Depending on what you connect or upload, we may process:

• Account data: Google sign-in identifiers, email, display name, avatar URL.
• Acceptance code: a private 6-digit code claimed at signup (not a login password); required as operational consent every time you load a dump for mulching, and for destructive actions.
• Source exports you upload: Instagram Meta export ZIPs; Google Takeout (Photos metadata); future LinkedIn archives; Cursor / agent JSONL; other lane dumps you explicitly choose.
• Derived analysis: themes, findings, storyboard text, render manifests, optional share links.
• Billing: Stripe customer / checkout metadata and coin wallet balances (card data stays with Stripe).
• Technical logs: IP address, user agent, timestamps on consent and security-relevant events.

We do not require access to Instagram DMs, passwords, or full-resolution photo libraries as a default product path. Google Photos processing targets metadata indexes where possible — not bulk original media upload to models.

3. What we do not do

• We do not sell your personal data.
• We do not use your exports to train third-party foundation models for unrelated products.
• We do not publish your analysis or film unless you create a share link or otherwise choose to share.
• We do not claim Instagram OAuth can replace a full activity export; dump-based lanes are explicit uploads you control.

4. Purposes & legal bases

• Provide the Service (parse → analyse → storyboard → render → play/share) — contract / your request.
• Acceptance-code gates on dump mulching and destructive actions — consent and security.
• Payments and fraud prevention — contract and legitimate interests.
• Security, abuse prevention, and legal compliance — legitimate interests / legal obligation.
• Optional AI narration, atmospheric video, or music generation — consent and contract (feature-flagged).

5. AI & subprocessors

Processing runs on infrastructure we operate or contract (notably Google Cloud). Feature-flagged services may include Cloud Text-to-Speech, Vertex / generative video, and future music generation. Prompts and derived artefacts may be sent to those providers solely to fulfil your render. Subprocessors are bound by their terms and our configuration; we do not authorise them to sell your identity data.

6. Retention

• Raw upload archives: targeted deletion within ~24 hours after successful parse (or sooner on wipe/delete).
• Temporary render assets: short-lived (order of days) unless needed for an active job.
• Account, wallet, consent records, and finished Blends: until you delete them or close your account.
• Share links: until you revoke or they expire.
• Billing records: as required by tax and payment law.

7. Sharing & international transfers

We share data with infrastructure and payment providers only as needed to run the Service. Data may be processed in regions where those providers operate (including outside your country). Where required, we rely on appropriate transfer mechanisms offered by those providers.

8. Your controls

• Hide findings before render.
• Choose whether a Blend is shared, and revoke share links.
• Delete individual Blends or your entire account using your acceptance code.
• Request access or deletion via Settings or privacy@davidlabs.ca.
• See Data Deletion instructions for platform compliance requests.

9. Security

We use encryption in transit (HTTPS), access-controlled cloud storage, least-privilege service accounts, and acceptance-code confirmation for destructive operations. No method is perfectly secure; please protect your Google account and keep your acceptance code private.

10. Children

The Service is not directed to children under 16 (or higher age required in your jurisdiction). Do not use Blend if you are under that age.

11. Changes

We may update this Policy. The version and effective date above will change. Continued use after a required re-consent means you accept the updated Policy.

12. Contact

Privacy questions: privacy@davidlabs.ca. Also see Terms of Use, Data Deletion, and in-product Acceptance code.

This document is product legal copy for Blend. Have counsel review before production launch in new jurisdictions.