The short version
The strongest protection in AdjiCera is architectural: your recordings, transcripts, and study or meeting material are produced and stored on your own device and never reach us. There is no meeting bot, and nothing is uploaded to a cloud recorder. The one exception is the optional Prime AI features, which send only the text you choose to a third-party provider. This page describes how we protect the small amount of data we do hold, how AdjiCera Call is protected, and how to report a security issue. It describes our current practices; it is not a warranty.
Your recordings never leave your device
Audio and video you record — lectures, meetings, and any call recording you start in AdjiCera Call — are written to your own machine. We do not receive them, upload them, or store them on any server. There is no meeting bot that joins your calls, and no cloud recording pipeline. Because the material most people care about is never in our possession, the most damaging kind of breach is one we are structurally unable to have.
Transcription and study material run locally
Transcription, speaker labelling, summaries, action items, flashcards, quizzes, study notes, concept maps, and meeting analytics are generated on your device by software that runs on your computer. They are not sent to us to be processed and are not stored by us. This is a property of how the products are built, not a policy we could quietly change without re-engineering them.
The one exception: optional Prime AI
Prime AI features are optional and off unless you choose to use one. When you do, only the text you select — typically a transcript excerpt plus your question — is transmitted through our servers to a third-party AI provider, which generates the response. We do not store the content of these requests or the responses. The provider processes the text under its own terms. If you would rather nothing leave your device, do not enable Prime — every core feature works locally without it. What Prime sends and does not store is described in full in our Privacy Policy.
Accounts and sign-in
Sign-in is email-only — there are no passwords to steal, reuse, or leak. When you sign in we issue a random session token tied to your email address, which expires on its own. Your account holds only what is needed to run your subscription and support you; your recordings and content are not part of it and stay on your machine under your control. Deleting your account does not delete your recordings, because we never had them.
Data in transit and at rest
Traffic between the software and our servers is encrypted in transit. The limited account, subscription, and device records we keep are held with our cloud infrastructure provider behind authenticated interfaces, and access is limited to what is needed to operate the service. Your card details are handled directly by our payment processor and never reach our servers. No system is perfectly secure, and we do not claim otherwise — but keeping your recordings and transcripts on your device, and not on ours, removes the highest-value target entirely.
AdjiCera Call
Calls are protected in transit, and AdjiCera Call’s signaling and chat are end-to-end encrypted. The encryption key is derived from a secret carried in the invite link — in the part of the link that browsers do not transmit to a server — so it stays between the people who share the link, and our servers cannot read this traffic. When a direct connection between participants is not possible, encrypted call data is relayed through connectivity infrastructure so the call can still connect. We do not record, store, or transcribe the contents of your calls. Full details of the cross-network relay behaviour are available on request. For exactly what our servers can and cannot see, and how long connection records are kept, see our Privacy Policy.
Updates
Software updates are delivered through the app. Keeping AdjiCera up to date is the best way to make sure you have the latest fixes and improvements.
Reporting a vulnerability
If you believe you have found a security vulnerability in AdjiCera, please tell us. Email support@adjicera.com with enough detail to reproduce the issue, and give us a reasonable opportunity to investigate and fix it before disclosing it publicly. We welcome good-faith reports and will acknowledge yours. Please do not access or modify data that is not yours, and do not run tests that degrade the service for other people.
Contact
support@adjicera.com for security reports and responsible disclosure. info@adjicera.com for anything else.