CentamilX · Version 1.0-draft · Effective 7 July 2026 · Pending ratification by counsel; the ratified version will replace this page.
This policy explains what we collect, why, where it goes, and your choices, for visitors to our sites, trial users, and customers of the CentamilX platform.
Account data: name, email, company name, authentication identifiers (we use Clerk for sign-in; passwords never reach us). Business content: what you and your team exchange in chats, boardrooms and projects, files you sync, onboarding answers, and the memory your AI Employees build from your inputs. Connector data: data from services you connect (e.g. Gmail, Calendar) strictly under the scopes you grant, with credentials stored encrypted. Billing data: plan, invoices, GSTIN/address if you provide them; card numbers are handled by Stripe and never touch our servers. Operational data: audit events, usage and cost metering, device and log data, and trial-session limits (an anonymous counter cookie).
To run your workspace and your AI Employees; to route your requests through AI models; to hold consequential actions for your approval; to bill you; to keep the platform safe (rate limiting, abuse and runaway detection, audit); to support you when you contact the CentamilX office; and to send service messages (briefs, receipts, alerts, you control the morning-brief email in Settings). We do not sell personal data, and we do not use one customer's content to serve another customer.
Your prompts and relevant workspace context are processed by large language models (currently Anthropic's, via API) to produce your team's work. Our provider agreements do not permit them to train their general models on your API content. Quality-control checks (our QA reviewer) may process message content to block fabrications or leaks before they reach you.
Sub-processors that host and run the service: Vercel (hosting), Neon (database), Anthropic (AI models), Stripe (payments), Clerk (authentication), Google (only for connectors you enable and our own transactional mail), GitHub (code and encrypted operational backups). Each processes data only to provide their service to us. We disclose data if required by law, and then as narrowly as lawful.
We use strictly necessary cookies: your session (signed, expiring), Clerk's auth cookies, and an anonymous trial counter. No advertising trackers.
Active workspaces: retained while you use the service. After cancellation or expiry: 90 days, so you can return intact; then scheduled deletion. Audit ledger events (operational metadata, not your content) are append-only and retained for governance. Backups roll off within 30 days.
You can access and export your data, correct it, delete it (subject to legal record-keeping), disconnect connectors, pause or remove AI Employees, and cancel entirely, all self-serve or via the CentamilX office. Depending on your jurisdiction (e.g. GDPR, DPDP Act, CCPA) you may have statutory rights to access, rectification, erasure, portability, and objection; write to privacy@centamil.com and we honor them without discrimination.
Tenant isolation enforced at the database layer (row-level security), encrypted connector credentials, signed sessions that fail closed, rate limiting, quotas and runaway detection, append-only audit, tested backups, and monitored uptime. Report concerns to security@centamil.com, a human reads it.
Our sub-processors operate globally (primarily the US and EU). Where required, transfers rely on appropriate safeguards such as standard contractual clauses; details available on request.
The service is for businesses and not directed to children under 18; we do not knowingly collect their data.
Material changes are notified 14 days in advance to account holders. Questions or requests: privacy@centamil.com, or the CentamilX office in your workspace.