Aveexia · legal information
Security and Trust
Last updated: October 17, 2026 · v2026-10-17
How the service is built
Aveexia is built with separation between customers, least privilege and clear boundaries between users, AI models and the customer’s systems. Actions that can have financial consequences require confirmation or human handoff.
Where data is
- Application servers and background jobs: Render, Frankfurt (Germany).
- Database and sign-in: Supabase, Zurich (Switzerland).
- Cache, queues and session state: Redis Cloud, Paris (France), with TLS.
- Website and dashboard: Vercel, global edge network with HTTPS.
- AI responses and voice use external providers that may process data outside the EU/EEA, see the subprocessor register.
Encryption and protection
- All traffic to the service is protected with HTTPS/TLS and HSTS.
- Data at rest is encrypted by our infrastructure providers.
- The website sends security headers, including Content-Security-Policy and X-Content-Type-Options, and the API is rate limited.
- Secrets such as API keys are stored as environment variables at the providers and not in the code repository.
Separation between customers
Each customer’s data belongs to a workspace. Access is checked on the server against the signed-in user’s permissions, and the database uses Row-Level Security as an additional safeguard. Cache and queues are scoped per workspace.
Access
- Role-based access in each workspace.
- Sessions use time-limited tokens in httpOnly cookies.
- Internal access to production systems is limited to what is needed for operations and support.
AI and data
Only what is needed for the answer is sent to the AI provider: the conversation and relevant excerpts from the customer’s knowledge sources. Answers are based on the customer’s own material. Aveexia does not train its own models on Customer Data.
Deletion and backups
Conversations are deleted automatically after 90 days, and a workspace can be deleted in full. Backups at the database provider are overwritten on its cycle. See the retention matrix.
Incidents
We have a documented incident procedure: detect, contain, investigate and inform. If a personal data breach concerns the customer’s data, we notify the customer without undue delay and no later than 48 hours after we become aware of it, so the customer can assess its notification to the competent supervisory authority (72 hours under Article 33 GDPR). If the breach concerns data for which Aveexia itself is responsible, we notify IMY.
Report a vulnerability
If you find a security issue, email security@aveexia.com. Describe what you found and how to reproduce it. We reply within five working days. We do not regard good-faith research that does not harm data or other users as a breach of contract, and ask that you give us reasonable time to fix the issue before you publish. The contact details are also in security.txt.
Certifications and assurance
Aveexia holds no third-party certifications such as SOC 2 or ISO 27001 today, and does not claim to. We build security into the product first, and a formal certification is something we aim to take on over time. If you require a security or GDPR review as part of procurement, we are happy to carry it out together with you.
If your procurement needs material now, for example answers to a security questionnaire or a walkthrough of how we handle GDPR and personal data, get in touch. Questions about security and the DPA: security@aveexia.com. Version 2026-10-17.