Privacy & Data
How Kyra handles your data.
Privacy & Data
What Kyra receives
When your SDK calls evaluate, Kyra receives:
- The tool call name and parameters
- Agent and session identifiers
- The
userIdyou provide - Any additional
contextyou include
PII stripping
All three SDKs strip PII from captured LLM HTTP traffic before it leaves
your infrastructure. The following patterns are detected and replaced with
[REDACTED]:
- Email addresses
- Phone numbers
- Credit card numbers
- National ID numbers
- IP addresses
userId is preserved — it is a governance identifier for audit tracing.
Stripping runs on your machine, inside the SDK, before any network call to Kyra.
To disable (if you handle PII stripping upstream):
KyraClient(api_key="...", pii_stripping=False) # Pythonnew KyraClient({ apiKey: '...', piiStripping: false }) // TypeScriptkyra.NewClient(kyra.WithPIIStripping(false)) // GoData retention
Audit events are retained according to your org's retention policy. Contact hello@kyratech.io to configure custom retention for Enterprise plans.
GDPR / DPDPA
Kyra acts as a data processor. Your organization is the data controller. A Data Processing Agreement (DPA) is available on request at legal@kyratech.io.
Questions
Contact legal@kyratech.io.