Security at Alori
Last updated: November 19, 2026
This page explains how Alori protects the data businesses keep in it. It is written for the people who review vendors before their company signs up. For a question it doesn't answer, write to security@alori.dev.
Compliance status
Alori runs on Vercel and Convex, which both hold SOC 2 Type 2 reports (Vercel Trust Center, Convex security).
Alori itself has not been audited for SOC 2 yet. We plan to start a SOC 2 Type 2 audit and will update this page with the expected date once the audit firm is engaged.
Alori Inc. is based in Québec and follows Québec's privacy law (Law 25). Our Privacy Officer is Maxime Lavoie (max@alori.dev). Our privacy policy covers what we collect, how long we keep it and your rights.
Infrastructure
- Database and backend: Convex, on Amazon Web Services. Alori's own database is in Canada (Montréal). Each business's app has its own database in its country: Canada (Montréal) for Canadian businesses, the United States (Virginia) for US businesses.
- Web hosting: Vercel, for alori.dev and for every business's app.
- Background work: DigitalOcean in Toronto, for building and deploying apps, phone call audio and long AI tasks.
- Files: Cloudflare R2 in North America, for call and meeting recordings and imported attachments.
Each business's app is a separate Convex project and a separate Vercel project, on its own address under aloriapp.com, apart from alori.dev. One business's app cannot read another's database.
Every company that touches customer data is listed, with what it does and where, on our subprocessors page.
Data protection
- Data travels over HTTPS (TLS) and is encrypted at rest by our hosting providers.
- The tokens that connect a business's other software (Gmail, Google Calendar, Slack, Shopify, QuickBooks and others) are encrypted again by Alori with AES-256-GCM under a separate key. Logins a person saves for their personal assistant are encrypted under another key and never shown to the AI model.
- Passwords are stored as secure hashes. API keys and the tokens Claude uses to reach Alori are stored only as hashes, so we cannot read them back.
- Links to recordings and files are signed and expire after one hour (five minutes for downloads).
- Backups are taken automatically, and we have tested restoring them.
Access control at Alori
- Every Alori staff account (email, code, hosting, database, payments) requires two-factor sign-in.
- Only the people who need it have access to production systems. Access is given person by person and removed the day someone leaves.
- When staff open a customer's account to help, for example at the business's request, each visit and each change is logged.
Security in the product
- Sign-in: Google, Microsoft or email and password. A forgotten password is reset with a code sent by email. Sign-up has a bot check.
- Roles: an owner decides what each teammate can see and edit, module by module. Only admins can change the team, roles, billing, API keys, or delete the app.
- History: deals, tickets, tasks, orders and conversations keep a record of who changed what and when.
- Your data, your way out: the data API reads every record. Deleting an app or an account deletes its data within 30 days, including its files.
- Webhooks: messages Alori receives from Stripe, Twilio, Resend, Slack, Shopify, Google, Microsoft and others are checked for their signature. Webhooks Alori sends to your own software are signed too.
AI and your data
Alori uses AI to answer in chat, write drafts, transcribe calls and run bots. To do that, the text or audio needed for one task is sent to an AI provider:
- OpenRouter, which routes to models from Anthropic, OpenAI and Google;
- Moonshot AI, for the model the developer bot writes code with;
- Deepgram, to turn speech into text;
- ElevenLabs, to give a bot its voice on phone calls.
These providers do not use your data to train their models, and neither does Alori. A business's data is used only to do what that business asked. Recordings, transcripts and chats stay in the business's own app until the business deletes them or the app.
Incident response
We keep a register of every security and privacy incident. If an incident affects a business's data, we tell that business without undue delay, with what happened, what data is involved and what we are doing about it. When the law requires it, we also notify the Commission d'accès à l'information du Québec and the people concerned.
Report a vulnerability
If you find a security problem in Alori, write to security@alori.dev with the steps to reproduce it and what an attacker could do. We answer within two business days.
Please give us a reasonable time to fix it before you share it, don't access or change data that isn't yours, and don't degrade the service for others. If you follow these rules in good faith, we won't take legal action against you.
Documents on request
Under a non-disclosure agreement, we share with customers and prospects:
- a summary of our most recent outside penetration test;
- our security policies (access, incident response, backups, vendor management, change management);
- an overview of our architecture;
- a completed security questionnaire, or help filling in yours.
Ask at security@alori.dev.