Privacy policy
What ENSEMBLE collects, why, and who touches it. Effective October 24, 2026.
Policy
What we collect
Account information (name and email) when you sign up or sign in with Google; the strategy prompts, scripts, and results you create on the platform; billing records for paid usage; API keys you generate; and standard technical logs (IP address, browser, request metadata) used for security and debugging.
How we use it
To operate the service: authenticate you, build and run your models, meter and bill usage, respond to support requests, and keep the platform secure. We also measure product usage, including signups, first successful model runs, and paid subscriptions. We record tagged referral sources and the first connection and successful tool use for a connected assistant, using your account ID to avoid counting reconnects as new customers. These analytics events contain no credentials, tool arguments, or research results. We do not sell your personal information, and we do not use your models or prompts to train models or share them with other users.
Processors we rely on
ENSEMBLE runs on established infrastructure providers, each processing only what its role requires: WorkOS (sign-in and identity), Stripe (payments — we never see full card numbers), Supabase (database and file storage), Vercel and Railway (hosting), Modal (isolated model execution), and Anthropic (translating your strategy descriptions into code; prompts are processed to generate your strategy and are not used for model training under our agreement).
Cookies and analytics
Session cookies keep you signed in. PostHog provides product analytics and session replay; Vercel provides traffic and performance analytics. If you accept optional Google cookies, Google Analytics measures visits and completed signups and shares conversion reporting with Google Ads. We may also match your first collected payment to a Google ad using its click identifier, payment time, currency, and amount. We keep your consent and click identifier with your billing record for this purpose, with a 90-day attribution window. Advertising personalization is off. You can reject or withdraw permission using Cookie settings in the footer, and we honor Global Privacy Control. Withdrawal stops future matching; reports already delivered may remain. Meta and Reddit browser tags and their server-side conversion delivery remain disabled. We do not send strategy prompts, backtest contents, email addresses, or phone numbers to Google Analytics or Google Ads.
Retention and deletion
Your data is retained while your account is active. Deleting a model moves it to private Trash for 30 days and stops sharing and automatic updates. You can restore it during that period or permanently delete it sooner. After 30 days, its stored code, drafts, builds, and runs are automatically purged from the active database. Minimal support records containing account and model IDs, action, and time are kept for 30 days after each deletion, restoration, or purge; they contain no strategy content. Billing records are retained separately. Deleted data may remain in backups until those backups expire and is not available through the product. To delete your account or request erasure, email support@ensemble.markets; we retain only information needed for billing, legal obligations, and resolving disputes.
Security
Credentials are handled by dedicated identity and payment providers rather than stored by us; API keys are revocable at any time from the dashboard; model code executes in isolated sandboxes; and access to production data is limited to what operating the service requires.
Connected assistants and plugins
When you connect ENSEMBLE to Claude, ChatGPT, Codex, or another assistant through OAuth, the assistant can send requested tool arguments to ENSEMBLE and receive results available to your linked account. These can include your account ID and available profile name and email, asset filters, strategy prompts, scripts, model inputs, allocations, and backtest results. WorkOS handles account authorization. Data returned to the assistant is also subject to that service's privacy policies and controls. Disconnecting a plugin does not delete research stored in ENSEMBLE; the retention and deletion controls above continue to apply.
Changes and contact
If this policy changes materially, we will note it here with a new effective date. Questions or requests about your data: support@ensemble.markets.
Questions: support@ensemble.markets