Spanvero — Privacy Policy

Last updated: June 16, 2026 Effective date: June 16, 2026

This Privacy Policy explains how Cynosure LLC, a Florida limited liability company ("Spanvero", "we", "us"), handles information when you use the Spanvero application and website (the "Service"). It is written in plain English. The short version: Spanvero is privacy-conscious and built to collect as little as possible. By default we do not store your AI-provider API keys on our servers (two opt-in features — key-vault sync and GPU auto-launch — are the only exceptions, and they store the key encrypted), and we take $0 markup on compute, so we have no reason to track your usage of third parties. We use only privacy-first, cookieless analytics (see Section 8).

1. The one-paragraph summary

• Your prompts and outputs from local models never leave your device and never reach our servers.
• By default, your provider API keys live in your browser/device's local storage, not on our servers. The only exceptions are two opt-in features — Pro key-vault sync and GPU auto-launch (connecting a GPU vendor like RunPod) — which store an encrypted key on our server, and only if you turn them on (see Section 5).
• What we do store on our server is the minimum to run accounts: your email, a securely hashed password, and session data, plus (if you go Pro) the continuity data you ask us to sync.
• We never see your full payment card. Pro is sold by Cynosure LLC and your card is processed by our payment processor (Stripe), who handles the card details so we don't (Section 7).
• We do not sell your personal data. We do not run third-party ad trackers.

2. Who is the data controller

The data controller for account data is Cynosure LLC (a Florida LLC, operating as Spanvero), contactable at [email protected]. For payment-card data, our payment processor (Stripe) acts as a processor of your card transaction on our behalf and as an independent controller for its own compliance purposes (Section 7). For third-party AI providers and GPU vendors you connect with your own key, those companies are independent controllers of the data you send them (Section 6).

3. What we collect — and, importantly, what we don't

3.1 What we collect (server-side)

3.2 What we do not collect or store on our servers

• By default we do not store your provider API keys on our servers. They are kept locally in your browser (in the spanvero.v1 local-storage entry on your device). The only exceptions are two opt-in features that store an encrypted key on our server: Pro key-vault sync, and GPU auto-launch (connecting a GPU vendor like RunPod) — see Section 5.
• We do not receive your local AI prompts or outputs. Local-model inference runs on your hardware; it never transits our servers.
• We do not store your full payment card number. Our payment processor (Stripe) handles the card data (Section 7).
• We do not run third-party advertising/marketing trackers, and we do not sell personal data.

4. How your information is used

We use the limited data we hold to:

• Provide and secure the Service — authenticate you, keep you logged in, run Pro features you enable.
• Operate Pro billing — confirm your subscription status via our payment processor's webhook (we receive a subscription/entitlement status, not your card data).
• Prevent abuse and debug — investigate security issues and fix bugs.
• Understand and improve the Service — privacy-first, cookieless aggregate analytics (page views, top pages, referrers) that collect no personal data (see Section 8).
• Communicate with you — account and security emails, and (only if you opt in) occasional product emails.

We rely on these legal bases (for GDPR/UK GDPR users): performance of a contract (running your account and Pro), legitimate interests (security, abuse prevention, improving the Service), consent (optional emails and the opt-in key-vault sync), and legal obligation (e.g. tax and financial records for the sales we make).

5. Your API keys, in detail (the part that matters most)

• Default (free + local): Keys you enter are stored only on your device, in your browser's local storage, so the app can send requests directly from your browser to your chosen provider using your key. They are not transmitted to or stored by Spanvero's servers.
• Security caveat — browser storage is not a vault. Local/session/browser storage is readable by JavaScript running on the page, which means a successful cross-site-scripting (XSS) attack or malicious browser extension could in principle read anything stored there, including a key or session token. Industry guidance treats browser storage as convenient but not maximally secure for secrets. We mitigate this (strict content-security practices, scoping, and keeping keys off our servers), but you should treat any key you paste into any browser app — including ours — as something to rotate if your device is compromised, and prefer keys with the narrowest scope and lowest spend limits your provider allows.
• Optional Pro key-vault sync: If — and only if — you explicitly enable key-vault sync, an encrypted copy of your key may be stored on our server to sync it across your devices. Keys are encrypted before being stored, and you can disable sync and purge synced keys at any time from settings. We will publish the specifics of the encryption model in-app before this feature is generally available.
• Optional GPU auto-launch (orchestration): If — and only if — you connect a GPU-vendor account (e.g. RunPod) so Spanvero can start and stop GPUs for you, that vendor API key is stored encrypted (AES-256-GCM) on our server and used only server-side to launch/stop your GPUs and to relay your inference to them; it is never exposed to your browser and never sent to anyone but that vendor. You can disconnect and delete the stored key at any time from Settings. This is the one path where a key you provide is deliberately held (encrypted) on our server, because the automation runs there on your behalf.

6. Third-party AI providers and GPU vendors

When you use your own key (or rent your own GPU), your prompts, inputs, and outputs go directly to that third party (e.g. OpenAI, Anthropic, OpenRouter, RunPod, Vast). That third party — not Spanvero — receives and processes that data under its own privacy policy. We are not a party to, and do not control, what they collect or how they use it. Please read each provider's privacy policy. Because we take $0 markup and don't intermediate the call, we generally don't see the content of those third-party requests.

7. Payments and our payment processor

Cynosure LLC (Spanvero) is the seller of record for Pro. We use a third-party payment processor (currently Stripe) to process your card — the processor is not the seller, it handles the card transaction on our behalf.

• Your card data is handled by the payment processor (a PCI-compliant provider), not by us. The checkout page where you enter card details is hosted by the processor, so we never see or store your full card number.
• The processor shares with us only what we need to grant entitlements and keep records — typically your email, country, and subscription/payment status — via a secure webhook. We do not receive your full card number.
• The payment processor also processes your card data as an independent controller under its own privacy policy for its fraud-prevention and compliance purposes. Cynosure LLC — not the processor — is responsible for the sale and for any sales tax we must collect.

8. Cookies and local storage

Spanvero is intentionally light on tracking.

We do not use third-party advertising or cross-site tracking cookies. Our analytics (Cloudflare Web Analytics) is cookieless and collects no personal data, so it sets no tracking cookies. Because our essential storage is required to run the app you chose to use, and our analytics sets no cookies, this does not require a consent banner under most frameworks — but confirm cookie-consent requirements for your audience (EU/UK/California) with your lawyer.

9. Data retention

• Account data (email, hashed password, sessions) is kept while your account is active.
• Pro sync data is kept while sync is enabled and you have an account.
• Operational logs are kept for up to 90 days, then deleted or anonymized.
• Local-storage data (keys, session, settings) lives on your device until you clear it, log out, or clear your browser storage.
• On account deletion, we delete or anonymize your account data within 30 days, except where we must retain limited records for legal/tax purposes (e.g. a record of a sale we made).

10. Your rights and choices

• Access / portability: request a copy of the account data we hold.
• Correction: update your email/account info in settings.
• Deletion ("right to be forgotten"): delete your account and request erasure of associated data.
• Withdraw consent: turn off optional emails or key-vault sync at any time.
• Local data: clear your keys/session instantly by logging out or clearing browser storage.

Depending on where you live, you may have additional rights:

• EU/UK (GDPR/UK GDPR): the rights above plus the right to object/restrict processing and to lodge a complaint with your supervisory authority.
• California (CCPA/CPRA): rights to know, delete, correct, and opt out of "sale"/"sharing." We do not sell or share your personal data as those terms are defined.

To exercise any right, contact [email protected]. We'll verify your identity and respond within the time the law requires.

11. Security

We take reasonable measures to protect your data, including: passwords stored only as secure hashes (Better-Auth); bearer-token auth scoped per user with per-user data isolation; keeping provider API keys off our servers by default; HTTPS in transit; and access controls on our database. No method is 100% secure — see the browser-storage caveat in Section 5. If we ever suffer a breach affecting your personal data, we will notify you and any required authorities as the law requires. We will publish our hosting region, encryption-at-rest status, and backup practices in-app once the production service is deployed.

12. International users and data transfers

The Service is operated from the United States, and your data may be processed there and in any country where our infrastructure or our payment processor operates. If you are in the EU/UK and we transfer data outside it, we rely on appropriate safeguards (e.g. Standard Contractual Clauses) where required. Our payment processor independently handles its own cross-border payment-data compliance.

13. Children

The Service is not directed to anyone under 18, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us data, contact [email protected] and we will delete it.

14. Changes to this Policy

We may update this Policy. We'll change the "Last updated" date and, for material changes, notify you in-app or by email. Continued use after the effective date means you accept the update.

15. Contact

• Controller: Cynosure LLC (a Florida LLC, operating as Spanvero)
• Privacy contact / email: [email protected]
• Website: https://spanvero.com
• Mailing address: Available on request via [email protected]
• EU/UK representative (if required): Not applicable
• Payment processor (card data): Stripe — see its privacy policy at checkout (Section 7).

Last updated June 16, 2026. Spanvero is operated by Cynosure LLC, a Florida limited liability company. Questions? [email protected].

Privacy · Terms · How we stay honest · Pricing · Open the free advisor →