Trust
PII handling
In short. Seylo holds a small, fixed set of personal data about the people who use it — enough to sign them in, secure their accounts, keep the audit trail and bill their organisation. It is not designed to hold personal data from inside your workloads.
1. Personal data about Seylo users
| Data | Purpose | Protection |
|---|---|---|
| Email address and display name | Sign-in, roles, notifications, audit trail | Visible only within your organisation |
| Password | Sign-in, if you do not use SSO | Stored only as a salted scrypt hash |
| Authenticator secret and recovery codes | Multi-factor authentication | Secret encrypted with AES-256-GCM; recovery codes hashed |
| IP address and user agent per session; sign-in attempts | Showing you your sessions; detecting credential attacks | Sign-in attempts deleted after 30 days by default |
| Actions in the audit trail, with the actor’s email | Accountability for every change | Append-only in the application |
| Billing details (legal name, address, country, GSTIN if given) and billing email | Invoicing | Used for billing only; invoices kept as tax and accounting records |
| Record of emails sent (recipient, type, time) | Delivery troubleshooting | No message bodies kept; deleted after 30 days by default |
| GitHub login and access token, if you connect GitHub | Git integration | Token encrypted with AES-256-GCM |
2. Who can see it
- Members of your organisation, according to their role. Administrators manage members and roles.
- Seylo staff, only through an emergency-access path that is recorded in your organisation’s audit trail.
- The sub-processors that host the Service, under contract.
We do not sell personal data, use it for advertising, or share it with data brokers.
3. Personal data inside your workloads
Seylo does not need the data your applications process, and is built to leave it where it is:
- Secret values — where credentials and keys usually live — never leave your cluster.
- Raw logs, metrics and traces stay in your cluster. Log lines returned through Seylo’s queries are redacted on the way out, and redaction is applied before evidence reaches an AI feature.
- What Seylo does store from your cluster is configuration: resource names, labels, annotations, image tags, environment and ConfigMap settings.
Keep personal data out of configuration. Do not put personal data in resource names, labels, annotations or plain-text environment variables; put sensitive values in Secrets, which Seylo never reads.
4. AI features
AI features are off until an administrator turns them on. When they run, redaction is applied to the evidence before it is sent to the model provider your organisation chose. Do not turn on a Seylo-provided evaluation model for production data; see sub-processors.
5. Requests and incidents
To see, correct or delete personal data, follow our Privacy Policy. If we become aware of a breach affecting personal data, we will notify affected organisations within 72 hours of becoming aware of it and, where the law requires, the Data Protection Board of India and other authorities.