Privacy Policy

Overview

Limetry evaluates agent actions against policies you define. When you run Limetry yourself, evaluation and audit data stay on systems you control unless you send them elsewhere. This website (limetry.com) is separate from your evaluation server.

What we collect

• Self-run deployments: policies, evaluation results, and audit events in your store. We do not receive this data unless you configure external telemetry or grant support access.
• Website: standard analytics and logs for limetry.com (see cookie notices when applicable).
• Optional third-party services you configure: if you enable your own analytics, error reporting, or other integrations on a Limetry deployment or this site, those providers process data under their terms.

Action intents and free-form fields

Evaluate and record APIs accept structured fields such as action_type, resource, optional metadata, and (on record) details. Free-form fields can contain whatever the calling agent sends. Limetry is not a chat logger and does not require transcripts. Integrators should send only fields needed for policy decisions.

Before audit retention, Limetry scrubs known secret key names, strips URL query/userinfo from resource, and defaults to audit_mode=minimal (decision projection only). Set audit_mode=forensics on a policy when you need redacted metadata/details for investigations. See the data minimization guide.

What we do not do

Limetry does not custody funds, hold private keys on your behalf, or execute payments. We do not sell personal data.

How we use data

For this website, we use collected data to operate limetry.com, improve reliability, respond to support requests, and meet legal obligations. For self-run deployments, you control how data on your systems is used.

Retention

Retention on systems you control is configured by you (for example LIMETRY_AUDIT_RETENTION_DAYS). Website analytics retention follows the tools configured for limetry.com.

Contact

Privacy questions: privacy@limetry.org