Trust & privacy
What we promise, and what we can't.
Most privacy pages are a list of reassurances you have no way to verify. This one is written to be checked: where a guarantee is real, we say how you can confirm it, and where a product genuinely needs a network or a third party, we name it.
What holds
Every guarantee here is checkable.
Logue runs on your device, and works with no network at all
Transcription, diarization, summaries, search and writing all run on your Mac through Apple Silicon. Recordings are never uploaded, there is no account to create, and unplugging the network changes nothing about what works.
No bot joins your calls
Logue captures system audio directly. Nobody on the call sees a participant they didn't invite, because there isn't one.
You can read the code
Logue is MIT-licensed and the source is public. Privacy claims about an app you cannot inspect are just claims — these ones you can check, or fork.
Encrypted at rest, and the key never leaves the Mac
Meetings, transcripts and audio are encrypted with AES-256-GCM and always stay that way. Documents are too, unless you deliberately turn on plain markdown storage — which trades encryption for ordinary .md files you can edit anywhere, and which Logue explains before enabling.
What doesn't
The limits, stated plainly.
Every one of these is something a reader might reasonably assume goes the other way. They belong here rather than in a policy nobody opens.
Three things can leave your Mac, and only if you switch them on
Logue is offline out of the box. Web search sends your search query and nothing else — never a document, a meeting or a transcript. Deep Research does the same, repeatedly. And you may point Logue at an external model instead of the one on your Mac, which does send content to that provider; it is off unless you configure it. Update checks fetch a version file from GitHub. The Chrome extension talks to Logue over your Mac's loopback address, so nothing on that route reaches the network at all.
Aria cannot be local, and we won't pretend otherwise
Aria's whole job is arranging work between you and another person, which means a network and a server. What we commit to instead is narrower and checkable: your payment is held until you approve the finished job, you can keep every booking as something you approve first, and you can clear what Aria remembers about you at any time.
Everything Aria collects, itemisedChaise is a hosted service, and it holds your clients' details
A shop's book cannot live on one phone: staff share a day and clients book from a browser, so appointments, client names and phone numbers sit on a server we run. That server is in Canada and the records do not leave the country. Chaise takes no payments — the shop keeps taking money exactly as it does now — and the client relationship stays the shop's, not ours.
This website uses Google Analytics
Page views and download clicks, so we can tell which pages are doing their job. It is the one third-party script on the site. Block it and nothing here stops working.
The waitlist and invite forms go to a third party
Submissions are delivered through Web3Forms so an email address reaches us without us running a server for it. Aria's waitlist asks for your email, your city, and whether you're hiring or working. Chaise's invite form asks for your name, your mobile number and your city — no email, because we call. Neither asks for anything else.
ChatBro is retired and unmaintained
It left the App Store and receives no updates, including security updates. If you still have it installed, treat it as end-of-life software.
Privacy Policy
The full detail: what's collected, where it's stored, how long it's kept, and your rights over it.
Read itTerms & Conditions
What we're on the hook for, what you agree to, and how disputes get resolved.
Read itSomething here look wrong, or want a question answered directly? Tell us — we'd rather fix the page than have it be quietly inaccurate.