Data and privacy
What Parel stores about a call and an account, for how long, where, and the legal pages that make the promises.
The pages that bind
- Privacy Notice: what we collect, why, for how long, who processes it, your rights under India's Digital Personal Data Protection Act.
- Terms of Service, Refund Policy, Acceptable Use Policy, Security, Data Processing Terms for business customers.
This page is the short version for someone building on the API. Where it and a legal page disagree, the legal page wins.
What a call leaves behind
| Data | Kept for | Then |
|---|---|---|
The call record: tool, time, outcome and class, price in paise, latency, the key that made it, your client_tag, the source's call reference | 12 months | Aggregated into daily totals per team and tool; the row is deleted |
| Your inputs | Stored only as keyed hashes (an HMAC), never in the clear | Deleted with the call record |
| The raw result of a call | 24 hours after the call finishes (up to 90 days during the closed beta), and only when the call carried an idempotency_key (it is what a replay returns) | Set to null by the hourly housekeeping job |
| Holds and ledger entries (amounts, never inputs) | Forever: they are the money record | Ledger entries are append-only and a hold is never deleted (it is only marked settled or released); erasure removes personal fields, never amounts |
Technical logs: request ids, IP-derived rate-limit buckets (hashed), client names such as claude-code/2.x | Rate-limit buckets 10 minutes; logs and error reports 90 days | Expire |
Inputs are never written to logs or alerts; an error report carries ids, not inputs. The source receives the inputs a tool needs plus an anonymous team and key id, never your name or email.
During the closed beta, with your agreement when you sign up, we keep the inputs of your tool calls and their results for up to 90 days to improve the tools, delete them when you ask at hello@parel.si, and return to the shorter periods above at public launch.
What an account leaves behind
Name, email and sign-in details for the life of the account, then up to 3 years for dispute handling or until you ask for erasure. API keys are stored as one-way hashes; a revoked key's hash is kept 12 months for the audit trail. Backups are kept 90 days under a lock and then disappear.
Where
The database and sign-in run in Mumbai; the API and dashboard run in Singapore; the data source and a few named partners are abroad. The full list of processors and regions is in the Privacy Notice and the Data Processing Terms, and the three lists are kept identical.
What we never do
- Sell, share or reuse your queries or results, or show one customer's results to another.
- Log raw personal data: emails, phone numbers and names are hashed before any write.
- Store an API key in the clear, or hard-delete a money record.
- Put personal data in a URL or a support ticket title.
Other people's data
When you ask a tool to find or verify an email or to read public posts, you choose the purpose and you are the data fiduciary for that data; the Acceptable Use Policy applies. A person who was looked up and writes to us gets a reply within 30 days; we hold no raw copy after 24 hours, only a keyed hash.
Asking
Erasure, correction or a copy of your data: write to hello@parel.si from the team owner's registered address. Grievances are acknowledged within 48 hours and resolved within 30 days.
This page as Markdown: /docs/data-and-privacy.md. Something wrong or missing: hello@parel.si.