QUANTBLOCKS

QuantBlocks Data Ownership & Local/Cloud Boundary Statement

Version: 0.1.0-draft · Dated: 2026-07-12 · Status: DRAFT — pending counsel review. Live charges are blocked until counsel sign-off is recorded (see docs/legal/REVIEW_LOG.md).

This is the plain-language statement of who owns your data and exactly where it lives. The Terms of Service, Privacy Policy, and Subscription Terms all reference this statement; its claims match the system as built (spec §7, §17) and are verified by automated audits every release.

1. You own your research data

Everything you create in QuantBlocks — records, notes, thesis text, Decision Log entries, watchlists, imported data — is yours. You can export it at any time, in every existing format, at every tier, including after cancellation.

2. Local keeps research data in your browser

On the Local tier, your research data stays in your browser. It is stored in local browser storage on your device and is never transmitted to QuantBlocks or anyone else.

The only thing the Local tier sends over the network is a membership check: an opaque license token goes to the QuantBlocks entitlement endpoint, and a signed response (tier, status, validity date, founder flag) comes back. That exchange contains no research content — the entitlement system has no fields that could carry it.

3. Cloud sync is a Plus opt-in, and only that

Cloud sync and encrypted backup exist only on the Plus tier and above, and are off until you explicitly turn them on. Enabling sync is the single moment research data leaves your browser, it is user-initiated, and it is clearly stated when it happens. Disabling sync leaves a complete local copy. When you upgrade from Local, nothing is transmitted until you complete the explicit opt-in, your original local copy is retained until you confirm a successful sync, and a full export is offered at the migration moment.

4. No silent deletion, ever

Your research data is never silently deleted — not by sync, conflict resolution, cancellation, or migration. Destructive actions are explicit, and reversible or exportable.

5. Verification, not promises

These are structural properties, verified by automated audits: the Local build contains no network code path capable of carrying research data, and the audit runs on every release.


Referenced by: Terms of Service · Privacy Policy · Subscription Terms