Last updated 25 September 2026
Privacy policy
What personal data Worksi processes for Worksi AI Control, why, for how long, which sub‑processors are involved, and your rights.
Worksi · worksi.ai · info@xeoo.io
On this page
This policy explains what personal data Worksi (worksi.ai) processes when you visit this website, create an account or use Worksi AI Control, why we process it, and what choices you have. Questions: info@xeoo.io.
Two roles
- For account and website data, such as your name and email address as a user or a message you send through the contact form, Worksi decides how the data is used.
- For Customer Data, meaning what your applications send through the Service (prompts, responses, telemetry, end‑user identifiers), we act on behalf of your organization and follow its instructions and settings. Your organization decides what is sent and how much of it is stored.
What we collect and why
| Data | Examples | Why | How long |
|---|---|---|---|
| Account data | Name, email address, password hash (argon2id), organization name, role, whether your email is verified | To create and secure your account and provide the Service | While your account exists |
| Session and security data | IP address, browser user agent, sign-in times, active sessions | Security, rate limiting, the session list and the audit log | Sessions until they expire or are revoked; audit events permanently |
| Contact and upgrade requests | Name, email, company, topic, plan of interest, seats, message, IP address, user agent | To answer you, arrange plans and filter spam | As long as needed to handle the request and our business relationship |
| Usage metering | Monthly counts of gateway requests, traced spans and LLM-assisted diagnoses per organization | To apply and show plan limits | Monthly counters, kept for about 70 days |
| Product analytics | Pages viewed and key actions in the console by signed-in users, stored by us | To understand which features are used and improve them | 400 days |
| Verification, password reset, invitations, trial reminders, usage warnings and the alerts you configure | To operate the Service | Alert deliveries are logged per channel; other emails are not kept after sending | |
| Customer Data | Telemetry as described below | To provide the Service to your organization | According to your plan’s retention |
We do not use third-party advertising or analytics trackers, and we do not sell personal data.
Customer Data and capture modes
Each environment has a capture mode that decides how much prompt and response content is stored:
- Full: previews of inputs and outputs (up to 2,000 characters) are stored, and complete payloads over 16 KiB are stored in object storage.
- Redacted (the default): previews are stored after sensitive values are replaced: email addresses, phone numbers, payment card numbers, US social security numbers, IBANs, IPv4 addresses, API keys, JSON web tokens, bearer tokens and passwords.
- Metadata only: no previews. Only hashes, counts, tokens, cost, timings, status and error types are stored.
Redaction is pattern-based. It does not detect names, postal addresses or free-text personal data, so use metadata-only capture for such workloads. End‑user identifiers must be pseudonymous; attributes, tags and names of agents, workflows and tools are stored as sent and are not redacted.
| Customer Data | Kept for |
|---|---|
| Spans with their previews | Your plan’s retention (14, 30 or 90 days; custom on Enterprise) or your organization’s shorter setting |
| Full payloads over 16 KiB (full capture only) | 90 days |
| Hourly metrics and run summaries (no content) | Up to 800 days for hourly metrics; run summaries until your organization is deleted |
| Business outcomes | Up to 800 days |
| Exports you create | 7 days |
| Incidents, diagnoses, configuration and registry | Until you delete them or your organization is deleted |
| Audit log | Permanently, as a tamper-evident record |
| Backups | Up to 365 days, then deleted on schedule |
Sub-processors
| Sub-processor | What it does for us | When |
|---|---|---|
| Amazon Web Services | Hosting, databases, object storage, email delivery and backups | Always, for the hosted Service |
| OpenAI | LLM-assisted incident diagnosis and embeddings for semantic search, from incident evidence (stored previews, already redacted or absent), never full payloads | Only when these features run with the platform’s OpenAI key. You can switch them off with feature flags or connect your own OpenAI or OpenAI‑compatible credential instead. |
The model providers you configure (for example your own OpenAI, Anthropic or DeepSeek account) receive your requests as your providers, under your agreements with them; they are not our sub-processors. Alert destinations you configure (email addresses, Slack, webhooks) receive incident notifications containing the title, severity, agent, workflow and a link, never payloads.
Security
We protect data with tenant isolation on every query, encryption in transit and at rest, encrypted secrets, hashed credentials and a tamper-evident audit log. Details: security.
Where data is stored
The hosted Service runs on Amazon Web Services in a single region, and your data stays in that region except when it is sent to the model providers, alert destinations and sub-processors described above. Ask us which region applies to your organization.
Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, and to object to or restrict its processing. Email info@xeoo.io and we will respond. If your data reached us as Customer Data of an organization (for example as an end user of one of our customers’ apps), please contact that organization first; we will help it respond. You can also complain to your data protection authority.
Deleting your organization
Organization owners can ask us to delete their organization at info@xeoo.io. We then delete its telemetry, stored payloads, exports and all operational data from our databases and storage. Audit events are kept as the permanent record, and backups are deleted as they reach the end of their retention.
Children
The Service is meant for businesses and developers and is not directed at children.
Changes
We publish every update to this policy on this page with a new effective date, and we notify organization owners by email before material changes take effect.