Your team's work,kept safe and yours.
DIA runs on servers in the EU, encrypts every connection and gives admins the controls to decide how their team uses AI. Here is how it is built.
How your data flows
A request from your team to a model and back, and where your data rests in between.
- Two-factor sign-in
- Owner, Admin, Member
- Web application firewall
- DDoS protection
- Scoped to your workspace
- Uploads virus-scanned
- Only the models you allow
- Credit limits enforced
- No training on your data
- Under their API terms
- Daily and continuous
- Restore tested weekly
What keeps your work safe
- TLS on every connection
- Hosted in the EU
- Web application firewall
- DDoS protection
- Virus-scanned uploads
- Daily encrypted backups
- Weekly restore tests
- Not used to train models
- Two-factor sign-in
- Owner, Admin and Member roles
- Permissions that fail closed
- Audit log
- Credit limits per member
- Disposable chats
- Deleted means deleted
- Every staff action logged
Your data
Your work stays yours.
What you bring to DIA is there to answer you. You decide what it remembers, and what you delete is gone.
Not used to train models
DIA reaches every model through the providers' business APIs. Under their API terms, providers don't train on your prompts or files.
Memory you can see
See everything DIA remembers, grouped as personal or workspace, and delete any of it. Forgotten facts aren't filed again, and memory from private chats never reaches shared ones.
Disposable chats
A private chat that deletes itself when you close it, or after an hour idle. Nothing to clean up afterwards.
Deleted means deleted
Deleted chats and workspaces leave the app at once and are permanently purged within 30 days, files included.
Connectors on a short leash
Google Drive only sees the files you pick or DIA creates, and Calendar starts read-only. DIA asks before it writes and can't delete.
Private from partners
If your workspace comes through a DIA partner, they see account and usage details. Never your chats.
Infrastructure
Built and run in the EU.
Servers in Germany, backups in Finland, and every layer in between locked down by default.
Servers in Germany
The app runs on Hetzner servers in Falkenstein, Germany, inside the EU.
Backups you can count on
Daily backups plus continuous database archiving, encrypted and kept off-site in Finland on immutable storage. A restore is tested automatically every week.
Encrypted in transit
TLS on every connection, with HSTS. Traffic between our own servers inside the cluster is encrypted too.
Shielded at the edge
Cloudflare sits in front of DIA with a web application firewall and DDoS protection, and every API is rate-limited against abuse.
Isolated by design
Each service has its own database and every request is scoped to its workspace. Between services, traffic is denied unless allowed.
Uploads scanned
Every upload is checked for viruses and infected files are removed immediately. Uploads that are never used are cleaned up after 24 hours.
Watched around the clock
Monitoring with alerts runs day and night. Logs are scrubbed of credentials, email addresses and chat content before they leave our servers.
Staff access, locked down
DIA's staff tools have their own sign-in with required two-factor authentication. Every staff action is logged, and the tools never show chat content.
In transit
Encrypted from your browser to the model.
Every request travels over TLS, from your browser to DIA and from DIA to the model provider. Between our own servers, traffic is encrypted too.
Control
Admins decide how AI is used.
Owners and Admins set the rules for the whole workspace, and every permission check fails closed.
- Allowed modelsChoose which models the workspace can useYour pick
- Credit limitA monthly limit for each memberPer member
- Reasoning effortCap how hard models thinkMedium
- Who can share chatsDecide who can share by link or inviteAdmins
- Web searchLet DIA look things up on the webOn
- Private chatsChats only their owner can seeOn
- Public linksTurning them off ends every existing linkOff
- Disposable chatsChats that delete themselvesOn
Three clear roles
Owner, Admin and Member. Every permission check fails closed: if a check can't complete, the answer is no.
Sign-in you can tighten
Members sign in with Google or email. From the Team plan, a workspace can require two-factor authentication; Business adds verified email domains and can turn Google sign-in off.
Invite links that expire
Invite links are stored hashed and can expire after 1, 7 or 30 days.
Audit logBusiness
About 30 kinds of events, from members, roles and limits to models, settings, plans, credits, chat moves and file downloads. Kept for a year, exportable to CSV, visible to Owners and Admins.
Questions
Security questions, answered.
- No. DIA calls every model through the providers' business APIs, and under their API terms providers don't train on your prompts or files.
- In the EU. The app runs on servers in Falkenstein, Germany, and encrypted backups are kept off-site in a separate EU location in Finland.
- Every connection uses TLS with HSTS, and traffic between our servers inside the cluster is encrypted too. Cloudflare's web application firewall and DDoS protection sit in front of the app.
- Shared chats are visible to your workspace, and private chats to the person who owns them. DIA's staff tools never show chat content, and a DIA partner sees account and usage details, never your chats.
- Deleted chats and workspaces disappear from the app immediately and are permanently purged within 30 days, files included. Disposable chats delete themselves when you close them, or after an hour idle.
- Yes, on the Business plan. Owners and Admins get an audit log of about 30 kinds of events, kept for a year and exportable to CSV.
- Write to us through the contact page or at [email protected]. Send your security review questions there too.
Every model, on terms you control.
Start free with your team, or talk to us about your security review.