Privacy Policy
Draft - pending legal review
This policy is published for review. It is not yet a final legal document.
Risicare is operated by Conscience Labs Pvt. Ltd., F-221 Jai Vihar, New Delhi 110043, India (“Risicare”, “we”, “us”). Privacy enquiries and rights requests: privacy@risicare.ai.
This policy explains what Risicare collects when you use the platform, how long it is kept, who it is shared with, and what you can ask us to do with it. Risicare is an observability platform for AI agents: the data we hold is mostly telemetry your own software sends us.
1. What we collect
Agent telemetry (spans and traces). When you instrument an agent with our SDK we receive one record per operation: identifiers, timings, status, the model and provider used, token counts and cost, plus your own service and environment names.
Prompt and completion content. The text of your LLM calls — prompts, completions, tool inputs and tool outputs — is captured only when content capture is on. Both SDKs default it off: you must set trace_content=True (Python) or traceContent: true (JavaScript) to send it. When it is sent, it is stored on the span record itself.
Account data. If you sign in with GitHub or Google we store the email address, name and avatar URL those providers return.
Operational logs. Administrative actions are recorded in an audit log that includes the originating IP address and browser user-agent string.
Contact form. If you write to us through this website we collect the name, email address, company, region and message you provide, together with the IP address the request arrived from and the time you gave consent. The request is stored as a record on the platform, where our staff work it, and a copy is also sent to us by email.
Usage data: API call timestamps, endpoint paths, and response codes for rate limiting and abuse prevention. No request bodies are logged at the infrastructure level.
We also use account and usage metadata to operate and improve the service and to understand how it is used. This metadata is, per project, counts of traces, spans, scores, errors and tokens, and the names of the models and providers your spans report; per organization, counts of members and API keys, days with dashboard activity, and the agent framework you declare when you ask for access; and timestamps. The content of your prompts and completions is never used for analytics.
Billing data. When you buy a paid Plan or Pack we keep your billing name, address, GST registration number if you give one, plan, invoices and payment status. Card details are collected and held by Razorpay, our payment processor; we do not see or store them.
2. Redaction
Before telemetry is written to storage we run an automatic redaction pass over it. Credential-shaped values (tokens, keys, authorization headers) are redacted everywhere. Personal-data patterns — email addresses, phone numbers, national identifiers, payment card numbers and IP addresses — are redacted from content fields.
Redaction is pattern-based and always on; it is not a setting you can turn off, and it is not a guarantee. It reduces exposure, it does not eliminate it. If your prompts carry personal or confidential data you do not want us to hold, turn content capture off.
3. How long we keep it
How long we keep your data depends on your organisation's plan. Each record is stamped with its plan's retention period when it is written and is physically deleted, not hidden, within 1 day after that period ends, except (a) failed-delivery copies kept for up to 7 days for recovery and (b) backups retained for up to 30 days; deletions are not re-applied to restored backups. Deleted data cannot be recovered.
| Plan | Traces, spans, sessions, agent data, prompt and completion content, evaluation and scorer results, scores, diagnosis evidence |
|---|---|
| Start | 30 days |
| Build | 90 days |
| Team | 180 days |
| Enterprise | 365 days, or longer by agreement |
If you upgrade, we promptly extend the period of data not yet deleted to the new plan's period; a small number of records written during the switch may keep the older period. If you downgrade, the shorter period applies to data recorded after the change; data already recorded keeps its period. Data recorded before 3 November 2026 keeps the 90-day period that applied when it was recorded, unless you upgrade.
Error diagnoses: when a diagnosis runs, the original error message, stack trace, diagnosis reasoning, and the context messages and spans are copied into it; these are deleted on the schedule above, measured from the diagnosis. The verdict record (root cause, classification, confidence, suggested fixes and timing) is kept for the life of the project and is deleted on request.
- Usage analytics derived from your account (counts and timestamps, no content): kept as daily and weekly aggregates; identifiers in them are pseudonymised within 30 days of account deletion.
- Account and billing data: kept while the account exists. Invoices, credit notes and the payment records they are based on are tax records. We keep them for the period Indian tax law requires (currently eight years) and they are not deleted or pseudonymised on request; the personal data in them is limited to the billing details you gave us.
- Audit logs: kept for at least 1 year; never shortened by plan.
- Contact-form requests: no automatic expiry; deleted once acted on, or on request.
Telemetry passes through an in-memory queue on its way into storage. Records there are transient and are consumed within seconds under normal operation.
4. Who we share it with
We use the following processors. We do not sell your data and we do not use it to train models.
- Amazon Web Services: hosting for all platform data, in the Mumbai region (ap-south-1).
- Together AI — the large-language-model provider used by our diagnosis pipeline. See the disclosure immediately below.
- Resend — delivery of the email generated by this website's contact form.
- GitHub and Google (sign-in): email and public profile.
- Razorpay (payment processing): billing details and payment status.
About the Together AI transfer. When a diagnosis runs, the failing trace's error message and stack trace are sent to Together AI together with the surrounding spans — which, where content capture is on, includes your prompts, completions, tool inputs and tool outputs. Two things bound this today. First, a diagnosis runs when you ask for one on a specific trace, or, if you have asked us to turn it on for a project, automatically when a trace in that project errors; automatic diagnosis is off by default. If neither applies, no trace content is sent to any LLM provider. Second, we do not currently have a signed data processing agreement with Together AI. We are resolving that, and we are telling you rather than implying otherwise.
5. Your rights
You can ask us for access to, a copy of, correction of or deletion of your data, or object to or restrict how we use it, and you can complain to your data protection authority. Write to privacy@risicare.ai. We act on rights requests on request, run by our staff, and complete them within 30 days. Deletion can target a session, an agent or a set of traces and covers the telemetry stores (spans, traces, sessions, agent records, content, evaluations, scorer results, scores and diagnosis evidence); it does not delete your account, organisation, API keys, webhooks, alert rules, audit logs or project configuration unless you ask us to close the account. A copy is provided as JSON Lines. Backups follow section 3: deletions are not re-applied to restored backups. Invoices, credit notes and the payment records they are based on are tax records. We keep them for the period Indian tax law requires (currently eight years) and they are not deleted or pseudonymised on request; the personal data in them is limited to the billing details you gave us.
6. Security
Data is encrypted in transit. Database volumes use provider-managed volume encryption. API keys are stored as SHA-256 hashes, never in plaintext.
The bound on that: volume-level encryption protects against disk theft and snapshot leakage. It does not protect data in use on a running host, and we do not currently run database-level transparent encryption.
7. Cookies
The application sets cookies required to keep you signed in: a session cookie and an authentication cookie scoped to our domain. We do not use advertising cookies, and we do not load third-party analytics or tracking scripts.
8. Breach
In the event of a personal data breach, we will notify affected users and, where required by GDPR Article 33, the relevant supervisory authority within 72 hours of becoming aware.
9. Changes
We will email account holders at least 30 days before a material change to this policy takes effect, and update the date at the top. Other changes take effect when posted.
10. Contact
Conscience Labs Pvt. Ltd., F-221 Jai Vihar, New Delhi 110043, India. Privacy enquiries and rights requests: privacy@risicare.ai. Security reports: security@risicare.ai.