Trust
Security
Your projects, files and photos are your business. This page describes how aeuix one protects them, in enough detail that you can judge for yourself. It is written for clients, their IT teams and security researchers.
Architecture
- Hosting. The web app is served by Vercel. The database, sign-in, file storage and server functions run on Supabase in the United States, on infrastructure operated by Amazon Web Services. Both providers hold SOC 2 Type II reports.
- Encryption in transit. Every connection uses HTTPS with TLS 1.2 or newer. HTTP requests are redirected to HTTPS. The apps use App Transport Security.
- Encryption at rest. Database volumes, backups and stored files are encrypted at rest with AES-256 by our providers. Sign-in sessions on iOS are kept in the Keychain.
Access control
- Row-level security. Every read and write is checked inside the database against the signed-in user’s company and role. A client user cannot reach another company’s rows even if they guess an identifier; the rule is enforced by the database, not only by the app.
- File access. Files are stored in private buckets and served through short-lived signed links. Storage rules mirror the database rules: a client can only read their own company’s files, and photo shoots stay private until Aeuix marks them visible to the client.
- Roles. Aeuix team members have access to client work in order to do it. Finance data (invoices, Stripe) is limited to team members with finance access. Billing can be hidden from individual client members.
- Read-only previews. When an Aeuix administrator previews a client user’s view for support, every write is blocked, nothing is recorded as that user’s activity, the preview expires within an hour, and each use is logged.
- Sandboxed review accounts. App Store reviewers use a separate demo company containing only made-up data.
- Secrets. API keys and signing keys live only in provider secret stores; none are in the app or in source control. Provider accounts are protected with strong, unique passwords and multi-factor authentication.
Sign-in
- Accounts are created by Aeuix; there is no public sign-up. Sign-in is by password or a one-time email link. Password resets are sent only to the account’s email address.
- Sessions use short-lived access tokens that are refreshed automatically and revoked on sign-out.
- Integrations (the Claude connector) use OAuth 2.1 with consent shown only to Aeuix administrators, and every action they take is logged.
Change history, Trash and backups
- Every change to shared records is written to an activity log by the database itself (who, when, what changed, old and new values), so it cannot be bypassed by any client, app or integration. Administrators can restore a previous value from it.
- Deleted items go to Trash for 30 days before permanent removal, including their files.
- The database is backed up daily and backups are kept for seven days. Restores are tested when the schema changes.
Photos and face data
Face detection and matching run in the browser of the Aeuix team member uploading a shoot, using an open-source model served from aeuix.com. Photos are not sent to any face-recognition service. The face templates that result are stored with the shoot, restricted to that company, and are never exposed to client browsers; clients receive only face positions and names. See the Face Data Notice.
Application security
- User-written content (notes) is sanitised before rendering to prevent script injection. Uploaded files are served as downloads or previews, never executed.
- Server functions validate the caller’s identity on every request and re-check their role from the database.
- Dependencies are kept current; production builds contain no debug, demo or test data.
- Logs from providers are retained for a short period and used only for security and troubleshooting.
- The apps report crashes, errors and load times to our own database (no third-party SDK, no account identity) and the database checks every part of the service every five minutes, so outages and regressions are seen and fixed quickly. Users can switch their reports off in Settings.
Incident response
If we confirm a security incident that affects your information, we will contact your company’s primary contact without undue delay, and within 72 hours of confirmation, with what happened, what information was involved, what we have done and what you should do. We will also notify authorities where the law requires it.
Responsible disclosure
If you believe you have found a security vulnerability in aeuix one, please email will@aeuix.com with “Security vulnerability” in the subject. Include steps to reproduce. We will acknowledge within two business days, keep you informed, and credit you if you wish. Please do not access other people’s data, disrupt the service, or publish the issue before we have fixed it; researchers who follow these rules will not face legal action from Aeuix.
Questions
Client IT teams are welcome to ask for more detail, including our providers’ compliance reports, at will@aeuix.com.