Privacy Policy
Last updated: 19 November 2026 · Custom Software Solutions LLC
In short
We collect what running the product requires: your account, what your agents do, and what you pay. We do not sell your data and we do not train our own models on it. Paid models are routed to providers who contractually do not train on it either — free models are the exception, and we say so at the point you pick one. You can export your data and close your account at any time; closing stops everything at once, and we delete the data within 30 days of your asking us to.
This summary is for convenience only. The full text below is what applies.
This policy explains how Custom Software Solutions LLC ("we") handles personal data in connection with Choreo. It covers our website, the application, and the agent runtime.
1. Two different roles — and which one applies
This distinction determines who owes whom what, so it comes first.
- We are the controller for data about our own relationship with you: your account, your billing, our website analytics, our security logs, and our support correspondence. This policy governs that data.
- We are a processor for the content you and your agents put into the Service — files, prompts, messages, connected mailboxes, call transcripts, database rows. If that content contains other people’s personal data, you are the controller and we act on your instructions. Your obligations to those people are yours; the Data Processing Addendum sets out the Article 28 terms.
2. What we collect
2.1 Account and identity
- Name and email address, and a bcrypt hash of your password.
- Where you sign in with Google, the identifier, email address, verified status and display name Google returns. We never receive your Google password.
- Email-verification and password-reset tokens, stored only as hashes.
- Your workspace, plan, role, and team memberships.
2.2 Content you provide
- Prompts, conversations, uploaded files, workspace files and the output of your agents.
- Agent configuration: system prompts, capability policies, schedules, skills and blueprints.
- Data reached through connectors you authorise — for example mailbox contents, calendar entries or repository files — while an agent is acting on it.
- Messages exchanged on channels you connect, and transcripts of calls your agents handle.
- Long-term memories your agents store, which you can view and delete.
2.3 Credentials and secrets
API keys, OAuth tokens and site logins you store are held in a secrets vault, encrypted, and are never returned to the browser after you save them. Where an agent uses a stored login, the value is injected at the point of use and is not written to logs or transcripts. See Section 8 of the Terms.
2.4 Usage, telemetry and security
- Model usage records: provider, model, token counts, cost, and which agent and project the call belonged to.
- Run and audit records: what an agent did, which tools it called, which connectors it reached, and whether the action succeeded.
- Security logs: request metadata, IP address, user agent, authentication outcomes and events our detection rules flag. For requests that send data through the website, the log also keeps the first 1,000 characters of what was sent, with passwords, keys and tokens removed. That can include the email address you sign in with and the beginning of a message you write to an agent. These logs are kept for up to 12 months and are used only to detect and investigate abuse and to find faults.
- Website analytics, described in Section 3 — deliberately narrow.
2.5 Payment
Payments are processed by Stripe. We store your Stripe customer and subscription identifiers, plan, billing status and invoice history. We never receive or store your full card number, CVC or expiry.
2.6 What we ask you not to send
Do not put special-category data, government identifiers, full payment card numbers, children’s data, or data regulated by HIPAA, PCI-DSS, FERPA or GLBA into the Service unless we have agreed in writing to receive it. The Acceptable Use Policy states this as a rule; we repeat it here because it is also a privacy expectation.
3. Website analytics
Our analytics are first-party and deliberately designed to fit the audience-measurement exemption. If you visit from Europe we ask first all the same: none of the analytics cookies is set until you accept them in the banner. Elsewhere you are not met by a consent wall, and:
- No third-party advertising or tracking pixels, no cross-site profile, no data sold or shared with data brokers.
- IP addresses are never stored raw. We keep a salted SHA-256 pseudonym and a coarse /24 prefix, using a salt that rotates daily and is held only in memory, so the pseudonym cannot follow anyone across days. Both are erased after 30 days.
- Visitor identifiers expire after 180 days; aggregates after 25 months.
- Only a closed, predefined list of event names is accepted. Query strings are stripped from recorded paths so a token in a URL is never retained.
- Global Privacy Control and Do Not Track signals are honoured automatically, and you can opt out at any time using the control at the end of this section.
If we ever add an advertising pixel, cross-domain linking or session replay, that exemption stops applying and we will ask for consent before doing so.
4. Cookies
We set a small number of cookies: session and refresh cookies for signing in, a preview cookie scoped to a single project, three analytics cookies (cho_vid, cho_sid, cho_ft), and one that keeps your answer about them. There are no advertising cookies. The Cookie Policy lists each one, its purpose and its lifetime.
5. Why we may use your data (legal bases)
| Purpose | Basis (UK/EU GDPR) |
|---|---|
| Providing the Service and your account | Performance of a contract |
| Billing, credits and collections | Contract; legal obligation |
| Security, abuse prevention and audit logging | Legitimate interests; legal obligation |
| Product analytics and reliability | Legitimate interests |
| Service and security notices | Contract; legitimate interests |
| Marketing email | Consent (withdrawable at any time) |
| Defending legal claims | Legitimate interests |
6. What we do not do
- We do not sell personal information, and we do not share it for cross-context behavioural advertising — as those terms are defined by the CCPA/CPRA and comparable state laws.
- We do not use Customer Content to train our own models.
- We do not read your workspace content except as Section 7 describes.
7. When a human at our end can see your content
We do not routinely monitor Customer Content. Access is limited to named operators and occurs only:
- when you ask us to look at something in support;
- when we are investigating a specific abuse report, security incident or suspected violation; or
- where the law compels it.
Every operator action against the administrative surface is written to an append-only audit record identifying the operator, the action and the time.
8. Model providers — the part that matters most
Your prompts and content are sent to the model provider selected for each agent. Which provider that is, is your choice.
- Paid models (platform credits or your own key) are routed to providers whose API or enterprise terms state that inputs and outputs are not used to train their models. They may retain data briefly for abuse monitoring under their own terms.
- Free models are different, and it is the whole reason they are free.
- For the shared-data classes, your prompts and the model’s outputs are shared with the provider (OpenAI) and used to train their models. Do not send anything confidential.
- For stealth models, the publisher is an unidentified third party reached via OpenRouter. Your prompts and outputs are retained by them; their terms claim no training use, but that cannot be verified.
- Your own key means that provider’s terms govern that traffic directly.
The AI Disclosures document expands on this, and Subprocessors lists every provider we route to.
9. Sharing
We disclose personal data only to:
- Subprocessors that run the Service, each under a written contract — the current list is at Subprocessors;
- Third parties you connect, at your instruction. Where your agent calls a service or your carrier places a call, that provider’s own privacy policy applies to what you send it;
- Authorities, where legally required. We will notify you unless prohibited from doing so; and
- An acquirer, in a merger, acquisition or asset sale — with notice, and with this policy continuing to apply until replaced.
10. International transfers
We operate from the United States, and our subprocessors may process data in the United States, the EEA and elsewhere. Where personal data leaves the UK/EEA we rely on Standard Contractual Clauses (with the UK Addendum where applicable) or another lawful transfer mechanism, together with the technical measures in Section 12.
11. How long we keep things
| Data | Retention |
|---|---|
| Account and workspace data | While the account is open, and after it is closed until you ask us to delete it |
| Customer Content (files, conversations, workspaces) | Until you delete it; after the account is closed, until you ask us to delete it — then within 30 days of the request |
| Analytics IP pseudonyms and /24 prefixes | 30 days |
| Analytics visitor identifiers | 180 days |
| Analytics aggregates | 25 months |
| Security and access logs | Up to 12 months |
| A fingerprint of the address that received the welcome credit | Kept after the account is closed or deleted |
| Operator audit records | Retained — they are the accountability record |
| Billing and invoice records | As tax and accounting law requires (typically 7 years) |
| Backups | Rolling, overwritten on their own cycle |
Closing your account (Delete account, in your account settings) revokes access immediately and stops every agent. It does not delete your data: that is kept until you ask us to delete it. Write to [email protected] and the deletion is completed within 30 days of your request, from live systems, and from backups as those backups age out. Anonymised and aggregated statistics that can no longer identify anyone may be kept indefinitely.
To give the welcome credit once per inbox, we keep a fingerprint of the email address that received it. It is a one-way value made with a secret key: it cannot be turned back into the address, it is not linked to an account, and we use it only to check whether an address has already had the credit.
When we delete an account on request, we remove its content, its files, its stored keys and its users. Some records remain. Our logs keep their entries until they age out, within 12 months at most; they can hold IP addresses, browser details and the email address used to sign in. Our record of actions taken by our own staff is kept, and names the account by an internal id. For about a day after an account is closed, we keep the internal ids of its users, so that an old sign-in cannot be used again. The fingerprint described above is kept. Payment records stay with our payment processor, Stripe, for as long as tax and accounting law requires. Backups still hold the account until they expire on their normal cycle.
12. Security
- Encryption in transit (TLS) and at rest, including disk volumes.
- Passwords hashed with bcrypt; credentials held in a secrets vault, never in application logs.
- Tenant isolation enforced in the database itself through row-level security, in addition to application checks.
- Agent code runs in isolated containers with dropped capabilities, no new privileges, and no access to database credentials or platform API keys — those live only behind a capability gateway that agents reach with short-lived, scoped tokens.
- Outbound requests are validated and pinned to the address that passed validation, so an agent cannot be redirected into internal infrastructure.
- Least-privilege operator access, with an audit record for every action.
No system is perfectly secure. If a breach affects your personal data we will notify you and any regulator as the law requires, without undue delay. Report a vulnerability to our security page.
13. Your rights
If you are in the UK, EEA or Switzerland
You may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests; and you may withdraw consent at any time without affecting prior processing. You also have the right to lodge a complaint with your supervisory authority.
If you are in California or a comparable US state
You may request to know, delete or correct your personal information, and to obtain it in a portable form. You may exercise these rights through an authorised agent, and we will not discriminate against you for exercising them. We do not sell or share personal information, so there is nothing to opt out of on that front; we honour Global Privacy Control regardless.
How to exercise them
Much of this is self-service: export or delete your workspace data in the app, and close your account from Settings. To have a closed account’s data deleted, email [email protected]; the deletion is completed within 30 days of the request. For anything else, email [email protected]. We respond within 30 days (45 for California requests, extendable once with notice), and we may need to verify your identity first.
If your request concerns data another Choreo customer put into the Service, contact that customer. They are the controller; we will forward your request to them and assist them in responding.
14. Children
The Service is not for anyone under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, write to [email protected] and we will delete it.
15. Automated decision-making
We do not make decisions producing legal or similarly significant effects about you by automated means. If you configure agents to do so about other people, you are the controller of that processing and the obligations are yours — see Section 9 of the AI Disclosures.
16. Changes
We will update this policy as the product changes. The date at the top always reflects the current version; for material changes we will notify you by email or in the application before they take effect.
17. Contact
Privacy and data rights: [email protected]
General support: [email protected]
Postal: Custom Software Solutions LLC, 8 The Green #18856, Dover, DE 19901, United States
Who you are contracting with
Custom Software Solutions LLC8 The Green #18856
Dover, DE 19901
United States