Security and privacy
Your prompts are yours
We don't store chat prompts or answers. You decide whether anything is cached, which providers can see your data, and who on your team can do what.
Data
What we keep, and what we don't
| Data | Kept? | Details |
|---|---|---|
| Chat prompts and answers | Not stored | Usage records keep the model, token counts, cost and timing only. |
| Responses API conversations | Not stored | It is stateless; you send the whole conversation each time. |
| Response cache | Only if you ask | Per account, for one hour by default and up to 24 hours. Off under zero retention. |
| Video prompts | Stored unless zero retention | Kept so you can find and poll your jobs. Zero retention stops it. |
| Your provider keys | Encrypted | Checked with the provider before saving, then stored encrypted. |
| Your API keys | Hashed | Shown once when created. We keep a hash, so we can't show a key again. |
Providers handle your requests under their own terms. Models on the free plan may keep request data, so don't send secrets to them. To skip providers that may train on API data, send "provider": { "data_collection": "deny" }.
Controls
Privacy controls you can turn on
- Mask personal data
- Emails, card numbers, phone numbers and secret keys are replaced with
[EMAIL],[CARD],[PHONE]and[SECRET]before a prompt reaches the provider. For the account, or per request withX-Sparrow-Redact: on. - Zero retention
- Also stops storing video prompts and turns off the response cache for the account.
- Choose providers
- Allow or block providers by name, and skip any that may train on prompts with
data_collection: deny.
Masking is pattern based, so treat it as a safety net rather than a guarantee.
Accounts
Access and keys
- Keys scanners recognise
- Keys start with
sk-sc-v1-. If GitHub finds one in public code, we disable it within seconds, email the owners and admins, and send akey.leakedwebhook. - Spend limits per key
- A lifetime or monthly limit on every key, so a leaked or runaway key always has a ceiling. Disabled keys are rejected within a second.
- Roles
- Owner, admin, developer and billing. Developers can't make payments; billing members can't see API keys.
- Two-factor sign-in
- Protect your sign-in with an authenticator app.
- Audit log
- Every change to keys, members and settings, with who made it and when.
- Encrypted in transit
- The site and the API are served over HTTPS only.
Report a problem
Found a security issue?
Please tell us before you tell anyone else, and give us a reasonable time to fix it. We'll reply within one working day.
Email support@sparrowcodes.com with “Security” in the subject, the steps to reproduce, and what you think the impact is.
Don't access other people's data, and don't run tests that could hurt the service for others.
Read our privacy policy and terms.
Questions about your data?
Write to us and we'll answer in plain words.