Avelle Security
No password, nothing for you to install, nothing to learn. And even someone who owns your mailbox can’t make it do anything sensitive.
Avelle Security, Avelle’s security base, is included in the base, for everyone.
A difference in construction, not a feature
Any product that connects to your mailbox inherits the account’s identity. It has no other notion of “who” than the account: stolen account, obedient assistant.
Avelle holds its authority outside your Microsoft account. The rights register, the signing key and the phone of each authorized person live on Avelle’s computer, on your premises. You can’t add that with an update once you’ve built on the provider’s identity.
Four things an owner needs to know
Security costs no time.
The vast majority of requests, drafts, lists, contact details, summaries, looking up a file, ask for nothing, day or night. Only actions that write into your data, send data out to a third party outside the rules you approved in writing, or touch things in bulk, are protected.
A sensitive action is one tap.
The authorized person’s phone gets a notification that says exactly what; Face ID, done. Like paying with your phone. The confirmation is good for that one action, once. No smartphone? A text message is enough.
The alarm reaches the device the attacker doesn’t have.
If someone holds your mailbox and asks for something sensitive, you get the notification, for a request you never made. “Refuse and report” freezes the mailbox on the spot. You are warned before anything sensitive goes out.
Even we can’t.
Agensee can pause Avelle at your place; Agensee cannot approve a sensitive action. Every software version is signed by two people; your computer refuses any unsigned code; every action we take at your place appears in your Sunday report.
What protects your data
Rights per person, never per Avelle.
Avelle fills in and delivers only what the person asking could see themselves. A request outside their rights: refused, management informed. An employee who leaves: no rights left, the same day. Your internal rules hold, even through Avelle.
The most sensitive data is never read.
Social insurance and health card numbers, medical data, passwords: Avelle never reads them, so it can never deliver them, not even to management. The banking data it reads to reconcile your payments never goes out: never in an email, never in a draft, never delivered to anyone. That reconciliation uses no model; account numbers are used for matching in memory and are never written anywhere.
A document never gives orders.
A file, a PDF, a forwarded email that says “management authorizes…” carries no weight. Avelle refuses, quotes the passage to the person who asked and to management, and logs it. It can’t be tricked with a doctored form.
Avelle never opens a file, it reads it.
No application is launched. Anything that can carry code is refused outright and flagged. Your Microsoft antivirus is the first line; Avelle is the second.
What protects the device
Avelle’s computer knows where it is.
Movement or power loss reported within the minute. Moved without authorization, it reports its location. Stealing Avelle’s computer gets you nothing.
A stop button outside email.
PAUSE by phone, for one mailbox or for everything, in a minute; resume through the same channel. You keep control even if your Microsoft is compromised.
Avelle prepares before it asks.
The form is already filled, the change already worked out. The tap releases, it doesn’t trigger. The result is already in the inbox when you approve.
What hands control back to you
The log that says what went out.
A hacked mailbox never tells you what was read. Avelle does: in one command, everything it delivered or wrote over a time window, reversible. That is the incident register Law 25 requires, ready.
Avelle notices the intrusion before the first request.
A new forwarding rule or auto-reply on a mailbox, a risky sign-in: alert on your phone, Avelle paused for that mailbox. You learn about the breach from Avelle, not from a customer.
Temporary delegation.
An absent owner names someone, for a set time, from their phone. It switches itself off. No “just this once” that bypasses the system.
What the log shows, and what it doesn’t
The log shows what Avelle did, for whom, with which data. It does not show what people do, does not read their work and measures no one. Rights per person are the rules your organization already has; Avelle applies them. Security protects your team; it doesn’t watch it.
Under the hood
- Avelle’s computer encrypted, no inbound ports, keys in the keychain, secrets rotated in ten minutes.
- Fleet code signed by two people, refused if unsigned.
- Microsoft permissions at the strict minimum, limited to managed mailboxes, every call in your audit log.
- SIN, health card numbers, medical data and passwords never read by Avelle; banking data never goes out: no email, no draft, no delivery.
- Avelle never sends an email in your name on its own initiative: what it writes for you is a draft reviewed by a human; what goes out on its own, invitations by email and replies on your social accounts, goes out under rules you approved in writing.
- Nightly encrypted copy of Avelle’s state in your library; the data doesn’t leave your tenant.
- Written retention and automatic purge.
- Nightly attack tests on every function: doctored form, impersonated requester, active file, unsigned version, moved computer; each must refuse, or nothing ships.
- A “what Avelle will never ask you” page handed to your staff.
- In the contract: MFA on every authorized account, theft protection on every enrolled phone.
Frequently asked questions
What if someone steals my mailbox?
They can ask Avelle for what you usually ask for, drafts, lists, and it all lands in the mailbox they already hold. They can’t do anything sensitive: nothing that writes into your data, nothing that goes out to a third party outside your written rules, nothing in bulk. Those actions require a confirmation on the authorized person’s phone, tied to the exact action; and that phone is what warns you that a request you never made just came in.
What if my phone is stolen?
Approval requires your face or fingerprint. A lost phone is paused with one call and re-enrolled in person, never by email. We require device theft protection on every enrolled phone.
What if Agensee is the problem?
We can pause Avelle at your place; we cannot approve a sensitive action: that approval comes from your authorized person’s phone, not from an account, not from us. Every software version is signed by two people; every action we take on your Avelle appears in your weekly report.
What about a booby-trapped file?
Avelle never opens a file, it reads it: no application is launched, and anything that can carry code is refused outright, which is reported to you. Your Microsoft antivirus is the first line; Avelle is the second.
What about a document with instructions for Avelle?
A document never gives orders. “Management authorizes…” written in a PDF carries no weight: Avelle refuses, quotes the passage to the person who asked and to management, and logs it.
What if I’m on vacation?
You name someone, for a set time, from your phone; the delegation switches itself off. Nothing gets bypassed “just this once”.
Where does my data go?
On your Avelle, on your premises, in your Microsoft 365. To write, the necessary text is sent to an inference provider named in our privacy policy, never used for training, deleted within 30 days; what Avelle doesn’t read (SIN, health card, medical, passwords) never leaves, and neither does the banking data from your payment reconciliation: that reconciliation uses no model. A large share of the work uses no model at all.
Does Avelle watch my staff?
No. The log shows what Avelle did, for whom, with which data. It does not show what people do, does not read their work and measures no one.
Take my mailbox. Try it.
On the discovery call, we show you live: you hold the owner’s mailbox, you ask for a financial form, and it’s their phone that rings. Thirty minutes, no deck. We name your constraint and tell you honestly whether we start, or whether you wait.