Your spreadsheets contain sensitive data. Here's exactly how we handle it, and why you can trust our infrastructure.
Your workbooks are not ephemeral, because the product would not work if they were: you come back to a conversation days later and the file is still there. We keep the original file and the SQLite representation we derive from it in Supabase Storage, for as long as you keep the account.
You can delete a file or your whole account at any time. See retention and quotas below for what happens when you go over your storage limit.
All data in transit uses TLS 1.2+. Data at rest (files, database, account info) is encrypted with AES-256 in Supabase. API keys are stored as a SHA-256 hash— the plaintext key is shown once, at creation, and we cannot recover it afterwards.
The hosted chat is powered by Claude. When you ask a question about a workbook, the relevant file content is sent to Anthropic's API for processing. Anthropic does not train on data submitted through its API.
The MCP server has no such step: your own AI client calls our tools directly, and no file content passes through Anthropic on our side.
We do not inspect, analyze, or use your file contents for any purpose beyond providing the Service. We do not train AI models on your data. We do not sell or share your data with third parties.
If you upload a password-protected workbook, the password is used in-memory for decryption by Apache POI and never stored, logged, or transmitted beyond the processing service.
User authentication is managed by Supabase Auth, with email and password or a magic link. MCP clients authenticate with a bearer API key over HTTPS, or through our OAuth 2.0 endpoints with PKCE.
Every plan comes with a storage allowance covering the original files and their SQLite representations: 1 GB on Free, 20 GB on Pro.
Nothing is deleted the moment you cross the line. If an account stays over quota for more than 7 days, a daily job frees the stored files of the oldest conversations — archived ones first — until the account is back under its limit.
Freeing a file does not erase the conversation. We keep the file name and a SHA-256 hash of the original, so re-uploading the exact same file restores the conversation where it left off. A different file is rejected: the hash has to match.
Delete your account and everything goes with it — files, conversations, keys — within 30 days. Billing records are kept for 10 years, as French tax law requires.
We build on best-in-class cloud platforms so we can focus on the product, not on reinventing security. Each partner maintains rigorous compliance programs independently audited.
Web hosting, API routing, edge network
Our Next.js application runs on Vercel's edge network, providing global low-latency access. Vercel maintains SOC 2 Type II compliance and undergoes regular third-party security audits.
All traffic is served over HTTPS with automatic TLS certificate management. DDoS protection is built into the edge layer.
Authentication, database, file storage
Supabase manages our authentication (email/password, magic links), the PostgreSQL database, and the storage buckets holding your original files and their SQLite representations. Built on AWS infrastructure with encryption at rest (AES-256) and in transit (TLS).
Row Level Security (RLS) ensures users can only access their own data. Database backups are encrypted and retained per our retention policy.
Java Excel processing service
Our Apache POI + LibreOffice processing runs on Railway as an isolated container. Files are received via internal service-to-service calls (authenticated with a shared secret), processed in memory, and the response returned. This service keeps nothing: the stored copy lives in Supabase, not here.
The container runs as a non-root user with no persistent storage attached. Cold starts provision a fresh environment each time.
Claude models behind the hosted chat
When you use the chat on agentixl.com, your question and the relevant content from your workbook are sent to Anthropic's API so Claude can answer and drive the tools. This does not apply to the MCP server, where your own AI client talks to us directly.
Anthropic does not train its models on data submitted through the API, and retains API inputs and outputs only as long as needed to provide the service and enforce its policies.
Payment processing
All payment processing is handled by Stripe. We never see, store, or process credit card numbers. Stripe is a PCI DSS Level 1 certified service provider — the highest level of certification in the payments industry.
Subscription management, invoicing, and refunds are all handled through Stripe's secure infrastructure.
Your AI agent Vercel (API) Railway (Java) Supabase
│ │ │ │
├── upload(file) ──────────────►│ │ │
│ ├── POST /convert ─────────►│ │
│ │ (file bytes + secret) │ │
│ │ ├── Decrypt (if needed) │
│ │ ├── Convert .xls → .xlsx │
│ │ ├── Recalculate formulas │
│ │ ├── Parse with Apache POI │
│ │◄── SQLite representation ─┤ │
│ │ │ (nothing kept here) │
│ │ │ │
│ ├── Store original + SQLite ───────────────────────────►│
│ │ (AES-256 at rest, counts against your quota) │
│◄── sessionId ─────────────────┤ │ │
│ │ │ │
├── ls / cat / grep ───────────►│ │ │
│ ├── Read stored SQLite ────────────────────────────────►│
│ │◄─────────────────────────────────────────────────────┤
│◄── results ───────────────────┤ │ │The Java service holds file bytes in memory only for the length of a call. The durable copies — your original file and the SQLite representation the tools read — live in Supabase Storage until you delete them or a quota eviction frees them.
The hosted chat adds one step to this picture: Vercel also sends your question and the relevant workbook content to Anthropic's API, so Claude can answer and decide which tools to call. Using the MCP server from your own AI client skips that step entirely.
Yes. We keep the original file and the SQLite representation we derive from it in Supabase Storage, encrypted at rest, so your conversations and tool calls still work when you come back tomorrow. They count against your storage quota and you can delete them at any time.
In the hosted chat, yes: questions and the relevant workbook content go to Anthropic's API so Claude can answer. Anthropic does not train on API data. Through the MCP server, no — your own AI client calls our tools directly, and whatever it does with the results is between you and that provider.
Nothing for 7 days. After that, a daily job frees the stored files of your oldest conversations — archived ones first — until you are back under quota. The conversation survives, and re-uploading the exact same file (verified by SHA-256) brings it straight back.
Stored files are encrypted at rest. We do not have tooling to browse user files. Access to infrastructure is restricted to the engineering team with MFA-protected accounts.
Supabase runs on AWS US regions. Railway runs on US infrastructure. Anthropic processes API requests in the US. Vercel serves from the nearest edge location. All inter-service communication uses TLS.
Yes. We minimize data collection, provide data export and deletion on request, and all our sub-processors maintain GDPR compliance. Our entity (Dalae SAS) is incorporated in France and subject to EU data protection law.
The password is transmitted over TLS to the processing service, used in-memory to decrypt the file via Apache POI, and immediately discarded. It is never logged, stored, or transmitted to any other system.
Questions about security? Reach out.
Contact security@dalae.fr