QUANTBLOCKS

QuantBlocks Privacy Policy

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 policy describes exactly what data QuantBlocks does and does not collect, per tier. The claims here are matched to the system's actual data flows and are verified by automated audits (spec §7, §21 INV-1).

1. The core rule: Local stays local

On the Local tier, your research data — records, notes, thesis text, Decision Log entries, watchlists, imported My Data, Sample Universe edits, and anything derived from them — never leaves your browser. It is stored in local browser storage on your device.

The only network communication the Local tier makes is a license/entitlement check: an opaque license token is sent to the QuantBlocks entitlement endpoint, and a signed membership response (tier, status, validity date, founder flag) comes back. That check carries no research data, structurally: the entitlement system has no fields for research content. See the Data Ownership & Local/Cloud Boundary Statement.

2. Plus/Pro opt-in data flows

Cloud sync and backup are Plus-tier features and are opt-in only. No research data is transmitted until you explicitly enable sync; enabling sync is the single moment research data leaves your browser, and it is user-initiated.

When you opt in:

• Sync/backup traffic is encrypted in transit (TLS 1.2+).
• Stored research blobs are encrypted at rest with AWS KMS using per-user data keys (envelope encryption), so each account's data is cryptographically isolated. At launch, keys are managed by QuantBlocks (not zero-knowledge/end-to-end); we state this plainly so the trust claim is accurate.
• Encrypted backups are retained on a rolling 30-day point-in-time-restore window.
• On account deletion, your data is purged and your per-user encryption key is scheduled for destruction within 30 days or less, after which encrypted backups are cryptographically irrecoverable. Deletion is logged.

Discipline metrics (Pro leaderboards) are computed client-side; only aggregate scores of opted-in users are synced for ranking. Raw research records never enter the metrics system.

3. Data categories we process

• Billing data — processed by Stripe (name, email, payment method, subscription state). QuantBlocks never sees or stores full card numbers.
• Subscription/entitlement data — customer identifier, tier, subscription status, period end, founder flag. Stored in QuantBlocks' subscription datastore (AWS). Contains no research data.
• Activation email — your email address is used to deliver activation links/license keys and transactional receipts, via AWS SES.
• Opt-in synced research data (Plus/Pro only) — encrypted as described above.
• Aggregate discipline scores (Pro, opt-in only) — numeric aggregates only; never raw records or symbols.

4. Processors

Stripe (payments and billing), Amazon Web Services (hosting, storage, email via SES). Each processes data only to provide their service to QuantBlocks.

5. Your rights

You may request access to, export of, and deletion of your data. Export of your own research data is built into the product at every tier, including after cancellation. Account-level export and deletion flows are available wherever accounts exist (Plus/Pro). Contact details are published on quantblocks.fund.

6. What we do not do

• No sale of personal data.
• No advertising trackers in the product.
• No collection of Local-tier research content, ever.
• No ticker-level aggregation of user research into popularity or sentiment feeds.

7. Changes

Material changes will be versioned, dated, and posted at this URL before taking effect.

---

Cross-references: Terms of Service · Data Ownership & Local/Cloud Boundary · Subscription Terms