QDS Sentinel

Privacy Policy

Quantum Data Solutions, LLC ("QDS") · Effective October 10, 2026 · Version 1.2 · Feature disclosures clarified October 12, 2026

QDS Sentinel is currently in invite-only closed beta. This policy covers how we collect, use, and protect information during the beta and beyond.

QDS Sentinel is operated by Quantum Data Solutions, LLC, registered in Arizona, USA. This company identity correction does not change the data practices described below.

1. Who We Are

QDS Sentinel is a trading policy oversight and guardrails platform operated by Quantum Data Solutions, LLC ("QDS," "we," "us," or "our"). We are not a registered investment advisor or broker-dealer. Nothing in Sentinel constitutes investment advice.

Contact: hello@qdsventures.com

2. What We Collect

We collect only what is necessary to provide the service:

Account information: email address and a securely hashed password (PBKDF2-SHA256, 600,000 iterations). We never store your plain-text password.
Optional passkeys: credential identifiers, public keys, a name you choose, supported transport/backup indicators, and registration/use timestamps. Your private key, face, fingerprint and device PIN stay with your authenticator or device provider; Sentinel does not receive them.
Optional push alerts: a browser subscription endpoint, its notification encryption keys, a device label and delivery status. Alerts may show a symbol and policy rule on your device, including its lock screen depending on your settings.
Broker connection and account data: encrypted SnapTrade connection secrets, selected-account identifiers, and periodic portfolio snapshots (positions, orders, and balances). We do not receive or store your broker password.
Oversight events: policy evaluation results (allow, flag, block) for each agent action we review. These form your audit trail.
Policy and API data: policy settings, Policy Assistant prompts, Guardian API key metadata and hashes, optional registered agent identifiers, names, owner-declared models, versioned mandate summaries, key bindings, status and usage timestamps, submitted trade/account context, sandbox evaluations, caller-reported order activity and its link to an evaluation, and resulting evaluations. API keys are shown once when created; the server stores hashes and display prefixes. If you enter or create a key in the developer portal, its plaintext is kept in that browser tab’s session storage until forgotten, sign-out or the browser session ends.
Optional shared policy packs: when you publish a pack, we store a snapshot of your saved rules, its policy version, name, description, unverified publisher label, code and timestamps. Any approved Sentinel account with the code can read that snapshot. Your account email and owner identifier are not included; avoid personal or confidential information in the text you choose.
Beta, support, and usage data: beta application responses, feedback, timestamps, IP addresses used for abuse controls, and operational/error logs. We also record limited first-party usage events, such as app opens, onboarding choices, saved templates, replay initiation, policy-pack publication/application and export initiation, to understand setup and improve the service. We do not use advertising trackers or sell data for targeted advertising.
Billing data: payment processing is handled entirely by Stripe. QDS never sees or stores your card number.

3. How We Use Your Data

To provide, operate, and improve the QDS Sentinel service.
To detect and prevent abuse, fraud, and security threats.
To send you transactional emails (account verification, password reset, billing receipts). We do not send marketing emails without your explicit opt-in.
To provide passkey sign-in and device policy alerts when you enable them, and security emails when a passkey is added or removed.
To comply with applicable law.

We do not sell, rent, or share your personal data with third parties for advertising.

4. Broker Data and SnapTrade

Sentinel connects to supported brokerage accounts through SnapTrade, a third-party brokerage connectivity provider. Sentinel requests data-access connections and receives periodic account snapshots used for oversight. SnapTrade's connection portal handles brokerage authentication. QDS does not receive your broker password, and Sentinel does not place trades on your behalf.

5. Data Retention

Account data: retained while your account is active. You may delete the account in the app or contact us for help with a verified request.
Broker snapshots: the latest encrypted snapshot for each watched account is refreshed in place and retained while the connection or account is active.
Oversight events (audit log): retained for the duration of your subscription. You may export your full audit log at any time from the app.
API keys: active and revoked key hashes/metadata are retained while the account is active for security and audit purposes.
Sandbox records: sandbox evaluations and activity reports are outside the live oversight trail and become unavailable after seven days. Expired rows are removed on use and by bounded scheduled cleanup; physical deletion can follow expiry while a cleanup backlog is processed. Minimal first-sandbox activation and key/security events follow the ordinary account lifecycle.
Registered agents, activity reports and policy packs: metadata and live reports remain while the account is active. Revoking an agent or pack preserves its historical metadata; a revoked pack code stops resolving. Successful account deletion purges registered-agent, sandbox and published-pack records. Pack rules already copied into another account’s policy or exported by its recipient are not remotely erased.
Passkeys and push: passkeys remain until removed, password reset or account deletion. Registration/sign-in challenges expire after five minutes. Push subscriptions remain until turned off, invalidated by the provider, password reset, sign-out-everywhere or account deletion. Signing out attempts to disable alerts on that browser; if it fails, review your browser notification settings.
Deleted accounts: the deletion workflow removes linked account data, API-key, registered-agent, sandbox and owner-published policy-pack records, policies, oversight events, feedback, telemetry, and beta/waitlist records from active application storage. A non-user-linked deletion event may remain. Minimal operational state also retains an opaque internal user ID and unlinked fingerprints of retired snapshot keys to prevent delayed requests from recreating deleted data. These records contain no broker secrets, financial transactions, balances, planning profiles, or user-linked audit history and are not used for customer analytics. Residual encrypted copies may persist temporarily in infrastructure-provider backups and age out under provider retention controls, unless longer retention is required by law.

6. Security

We take security seriously:

Passwords are hashed with PBKDF2-SHA256 (600,000 iterations) — we cannot recover your password.
Broker tokens and portfolio snapshots are encrypted at rest using AES-256-GCM with HKDF-derived keys.
All data in transit is protected by TLS 1.2+.
The API enforces rate limiting and account lockout to defend against brute-force attacks.
Oversight events are internally hash-chained to help detect local alteration.

No system is perfectly secure. If you discover a vulnerability, please disclose it responsibly to hello@qdsventures.com.

7. Cookies and Local Storage

Sentinel uses browser session storage for the signed-in session token; it is cleared when the browser session ends and can also be revoked by logout. The developer portal also keeps an API key you explicitly enter or create in this tab’s session storage. Forget key removes that saved value; sign-out clears the portal’s saved browser state. Local storage holds app preferences, optional agent defaults, setup/checklist state and request collections you explicitly save. Saved request bodies can include trade and account inputs; use fictional data on shared devices. Recognized credentials are redacted from saved collections, history and portal exports. Browser-stored values are accessible to code running on Sentinel’s origin; they are not an encrypted credential vault. We do not use advertising cookies or tracking pixels. We use Cloudflare Turnstile for bot protection.

8. Third-Party Services

Device/browser push providers: Apple, Google, Mozilla or Microsoft route notifications to your subscribed device. Notification payloads are encrypted to the browser; providers still receive delivery metadata and apply their own retention policies. Your device/browser provider may also store or sync your private passkeys according to your device settings.
Cloudflare: infrastructure, DNS, and edge security. Cloudflare Privacy Policy.
SnapTrade: brokerage connectivity. SnapTrade Privacy Policy.
Stripe: payment processing. Stripe Privacy Policy.
Resend: transactional email delivery. Resend Privacy Policy.

9. Your Rights

Depending on your jurisdiction, you may have rights to access, correct, export, or delete personal data, and to appeal or complain about a privacy decision. You may disconnect brokerage access and delete your account from the app. For other requests, email hello@qdsventures.com. We will verify the request and respond within the period required by applicable law.

10. Children's Privacy

Sentinel is not directed at or intended for use by individuals under 18 years of age. We do not knowingly collect personal data from minors.

11. Changes to This Policy

We may update this policy as the service evolves. Material changes will be communicated by email or an in-app notice at least 14 days before they take effect. Continued use of Sentinel after the effective date constitutes acceptance of the updated policy.

12. Contact

Questions about this policy? Email hello@qdsventures.com. We aim to respond within 5 business days.