This Privacy Policy explains what information Orgmee ("the App", "we", "us") handles, how it is used, and the choices you have. By installing or using the App you agree to this Policy. If you do not agree, do not use the App.
The App is provided by Adapto Solutions. For any privacy question, contact us at support@adaptosolutions.in.
Orgmee is designed to keep as much of your data on your own device as possible. Call recordings, transcripts and the AI summaries generated from them are created and stored on your phone by default. Features that send data off your device (cloud transcription, cloud summarization, cloud backup, AI chat) are optional and are described below. We do not sell your personal information to anyone.
As of 14 August 2026 this extends to everything you write or say in the App. Your Orgmee Notes, your AI Chat messages, and your Plan My Day recordings together with the transcripts and summaries made from them are stored in files on your device, not in your cloud account. What stays in your cloud account for those items is metadata — how many notes you have, how many words long something is, whether a note has a date on it, when a chat was last used — never the text itself.
The trade-off is worth understanding before you rely on it. Because that content is only on your phone, it is not something we hold or can produce for you. If you uninstall the App, lose or reset your device, or clear its storage without a backup, the text is gone, and signing in on a new phone will not bring it back — you will see the item's metadata with its content missing.
So that the split is clear in one place, here is everything that does reach our servers. Your account details (name, email, profile photo, verified phone number and the country it belongs to, and your previous number if you have changed it). For each recorded call: the other party's name and number as your phone reports them, plus the date, duration, call type, any label you added, and — only if you use cloud sync or backup — links to where an artifact is stored. For your notes, chats and day plans: counts, labels, dates-used and word counts, never the text. Your phone number and display name also sit in a lookup entry so other Orgmee users can call you and send you notes (section 3(e)). If you send an Orgmee Note to another user, that note passes through our servers on its way to them, but its title and text are encrypted on your phone first and we cannot read them (section 3(o)). Everything else — the recordings themselves, transcripts, summary text, note text, chat messages, day-plan content — stays on your device.
Some of that is another person's information, not yours. A call record holds the name and number of the person you spoke to. They are not an Orgmee user and have not agreed to anything with us. We keep only that identifying metadata, never the audio or transcript of your call — but you should know it is there, and section 14 explains how such a person can contact us about it.
Encrypted backup is the way out of that, and it is your choice to switch on. Orgmee can package your notes, chats, day plans, summaries, transcripts and (optionally) recordings into a single encrypted file and upload it to YOUR OWN Google Drive, on a schedule you pick. We never receive that file. It is encrypted with AES-256 before it leaves the phone, and by default the key that opens it is held in your own account so that restoring on a new phone just works — which does mean we could technically read that key, though not the file itself, which is in your Drive and not ours. If you set a backup passphrase instead, the key is derived from something only you know and we cannot open the backup under any circumstances; the trade is that a forgotten passphrase makes it permanently unrecoverable. See section 3(m).
a) Account information. When you sign in (e.g. with Google), we receive your name, email address, profile photo and, where available, phone number, to create and secure your account. This is stored using Google Firebase Authentication and Cloud Firestore.
b) Phone verification. To unlock internet (app-to-app) calling, you must verify your phone number. On Android, the App first tries Truecaller, if it is installed — Truecaller verifies your number using your Truecaller profile via an authentication flow with Truecaller's own servers. If Truecaller is not available, is not usable, or you decline it, the App instead verifies your number with a one-time SMS code sent through Firebase. Your verified phone number is then stored on your account.
c) Call information. If you use the App as your phone dialer, the App may record the audio of your calls and generate transcripts and summaries. It also reads your device call log and contacts to label calls with a name and number. Recordings, transcripts and the summaries generated from them are stored on your device, and are not uploaded to us. Call metadata (name, number, date, duration) is stored in your private cloud account (Firestore) so it is available across your sessions; for a summary, that metadata is limited to counts and sizes — such as how many action items it contains and how many words long it is — and never the summary text itself. For internet (app-to-app) calls placed between two Orgmee users, your live call audio is transmitted through Agora's real-time network to connect the call. Agora does not record or retain a copy of the call — the recording, if the call is recorded, is captured and saved locally on your phone, the same as any other call.
d) Contacts. The App reads your contacts solely to show a caller's name instead of a bare number. Contact data is used on your device for this matching and is not uploaded to us as a contact list.
e) Your discoverability to other users. Once you verify your phone number, a lookup entry (your phone number, name and account id) is created so other Orgmee users can find you to place an internet call or send you an Orgmee Note — similar to how a messaging app matches your contacts against its other users. The entry also holds a public encryption key generated on your phone, which is what lets someone encrypt a note to you that only your device can open; the matching private key never leaves your phone, and we never receive it. Any signed-in Orgmee user can look up an entry by phone number; the entry does not expose anything else about you. Deleting your account (Settings → Delete Account) removes this entry immediately — see section 8 for the full timeline.
f) Voice memos, Orgmee Notes and reminders. Content you create ("Plan My Day" memos, notes, reminders) is stored on your device. For an Orgmee Note, the title, the text and the date you set are all held in a file on your phone; your cloud account keeps only counts and flags — how many words the note has, and whether it has a date at all, never what that date is. The one exception is a note you deliberately send to another Orgmee user, which has to travel through our servers to reach them — see section 3(o) for exactly what that involves. For a Plan My Day memo, both what you spoke and the AI summary generated from it stay on your device; your cloud account keeps the memo's label (for example "Plan · Sat, 4 Jul"), whether it has been summarized yet, and word counts. Speaking a voice memo uses your device's own speech-recognition service to convert it to text — on some devices this is handled entirely on-device, while on others your device's operating system may send the audio to its speech-recognition provider (e.g. Google) to produce the text. This is a function of your device's operating system, not something Orgmee's own servers receive or store.
g) AI Chat. Your chat messages — both what you send and the replies you get back — are stored on your device, not in your cloud account. The name you give a chat is held in that same file, so it stays on your device too. Your cloud account keeps only when the chat was last used and how many messages it holds. Sending a message does transmit content off your device: the message, together with context the App assembles from your recent Orgmee Notes and call summaries, is sent to Google's Gemini API using an API key you provide. This is the one feature that sends what you have written to a third party, it runs only when you use it, and it goes to Google under your own key rather than to us.
h) Optional cloud transcription / summarization. If you choose a cloud AI engine in Settings, the relevant call recording or transcript is sent to Google's Gemini API (using your own API key) to be processed. If you keep the default on-device engines, this content is NOT sent off your device for that purpose.
i) Optional cloud backup. If you use "Sync to Cloud", recordings and transcripts are uploaded to YOUR OWN Google Drive account under your Google credentials. We do not receive or retain copies of those files.
j) Diagnostic logs. The App keeps a local activity log to help diagnose problems. This log may contain phone numbers and technical events, but never call audio, transcript text or summary text. A log is only sent to us if YOU tap "Submit Logs". When you do, the log file and basic details (your account id, email, phone, app version and device model/OS) are sent to us to investigate the issue you reported.
k) Contact messages. If you use "Contact Us" in Settings, the message you write is sent to us together with your account id, email, phone, app version and device model, so we can read and reply to it. Like diagnostic logs, a submitted message is kept only as long as needed and is not removed by deleting your account — we keep a record of what was reported to us.
l) Analytics and crash data. We use Google Firebase Analytics and Crashlytics to understand feature usage and to receive crash reports. These collect app-event information (such as which features are used, setting choices, counts and durations) and device/diagnostic information, tied to a pseudonymous identifier, which we review in aggregate to help us improve the App and its stability. They do not receive your call audio, transcripts, summaries, notes, contact names or the phone numbers of people you call.
m) Encrypted backup and restore. If you switch on Backup & Restore, the App builds a single compressed, encrypted archive of your on-device content — Orgmee Notes, AI Chat messages, Plan My Day transcripts and summaries, call summaries and transcripts, and call recordings if you leave that option on — together with the metadata needed to put them back in the right place. It is uploaded to YOUR OWN Google Drive under your Google credentials, into an "Orgmee" folder you can see and delete. We do not receive it, and it is encrypted on the phone before upload, so Google stores only ciphertext. Backups are tied to your Orgmee account rather than your phone number, so changing your number does not affect them. Only what changed since the last backup is uploaded each time. You choose the schedule (daily, weekly, monthly, or manual only), whether recordings are included, and whether backups may use mobile data — the default is Wi-Fi only. You can restore from Settings at any time, and the App offers a restore when you sign in on a phone that has no Orgmee content on it yet.
n) Your backup encryption key. By default the key is generated on your device and kept in your own private area of your Orgmee account, so restoring needs nothing more than signing in. Being straight about what that means: we could technically read that key, though not your backup itself, which sits in your Drive and not ours. If you would rather nobody but you can open a backup, set a backup passphrase — the key is then wrapped using a value derived from your passphrase (Argon2id), only that wrapped form is stored, and the passphrase never reaches us. Backups taken before you set it stay readable. If you forget it, neither you nor we can recover those backups.
o) Sending an Orgmee Note to another user. You can send one of your notes to another Orgmee user, and unlike everything else in section 3(f) that content does leave your phone — so here is precisely what happens to it. The note's title, its text and its colour are encrypted on your device before they are sent, using the public key published by the person you are sending to (section 3(e)). Only their device holds the key that opens it. We cannot read the note at any point — not while it is waiting, not if it is declined, and not if it is never collected.
What we do hold on that record, unencrypted, is the information needed to route and schedule it: your name, phone number and account id; the recipient's phone number and account id; the date and time you put on the note; and its status (sent, delivered, accepted or declined). The date is deliberately not encrypted, because the receiving phone has to be able to schedule the reminder before the note itself is opened. If that date is itself sensitive, keep it out of the note's title and text — those are the parts we cannot see.
The encrypted content is deleted as soon as the recipient's phone collects it, leaving only a short status record so your app can show you whether it arrived. A note that is never collected — because the recipient has not opened the App, or because it never passed their delivery settings — is deleted automatically 30 days after it was sent. Your own copy of what you sent stays on your device, in your sent list.
Who can send you a note is your choice, and is restrictive by default. Out of the box, a note only reaches you if the sender's number is saved in your phone's contacts; one from a number you have not saved is simply not delivered. You can widen this to anyone, or block an individual sender, in Settings. For the sender's part, the App does not report back whether a note passed the recipient's contacts filter — a note that was not accepted for delivery looks the same to the sender as one not yet picked up, so this cannot be used to test whether someone has your number saved.
One consequence of the encryption worth stating plainly: because the private key that opens notes sent to you lives only on your phone and is not included in your backup, reinstalling the App, clearing its data or moving to a new phone makes any notes still in transit to you permanently unreadable — by you and by us. Notes already accepted are unaffected, and a sender can simply send again.
We use the information above only to: provide the App's features; keep your account secure; back up and sync your own data at your request; diagnose problems you report; and improve the App's reliability. We do not use your call content to build advertising profiles, and we do not sell it.
Where UK or EU data protection law applies to you, we rely on the following legal bases under Article 6 of the UK/EU GDPR for the processing described above:
Performance of a contract — to provide App features you've chosen to use, such as your account, syncing metadata across your devices, and internet calling between Orgmee users.
Legitimate interests — to keep the App secure and reliable (diagnostics, crash reporting, aggregate analytics), and to provide features like transcription and summarization that you've chosen to turn on, which we consider necessary to the tool working as designed.
Consent — where required, such as when you choose to send content to a third-party AI provider (Gemini) using your own key, or where local law requires the consent of a person you record.
Legal obligation — where we must retain or disclose information to comply with applicable law.
Where a call you record includes another person's voice or data, YOU are responsible for establishing a lawful basis — typically their consent — for recording and processing it; see section 7, "Call recording is your responsibility".
The App relies on: Google Firebase (authentication, database, storage, analytics, crash reporting); Google Gemini API (only when you enable a cloud AI feature, using your own key — see 3(h)); Google Drive (only when you enable cloud backup, using your own account — see 3(i)); Truecaller (only during phone verification on Android, and only if Truecaller is installed — see 3(b)); and Agora (to carry your live call audio for internet calls between Orgmee users — see 3(c)). Your use of those services is also governed by their own privacy policies — for the Gemini API specifically, see its terms linked above, which also cover how Google may use data submitted through the API depending on which plan your own key is on. We are not responsible for their handling of data within those services.
For calls recorded using your device's own built-in call-recording feature — rather than Orgmee's internet-calling feature — Orgmee does not create, initiate, or have live access to that recording. Your device's operating system or manufacturer performs the recording using a capability it provides independently of Orgmee; the App only reads the finished file after your call has ended, to organize, transcribe and summarize it for you. Orgmee has no way to know, control, or influence whether or how your device's own recording feature notifies the other party to a call.
Laws about recording phone calls differ by country and region. In many places all parties to a call must consent to being recorded, and recording without required consent can be a criminal offence. YOU are solely responsible for knowing and following the laws that apply to you, and for obtaining any consent required before recording. The App is a tool; how you use it is your responsibility. See the Terms of Service for more.
Your on-device data stays until you delete it or uninstall the App — and because most of what you write now lives only there (see section 2), uninstalling is itself a deletion you cannot undo. Your cloud data stays in your account until you delete it. You can delete individual items in the App at any time.
If you never delete individual items or your account, we retain your cloud metadata (call records, and note/chat/plan metadata as described in section 3) for as long as your account stays active. We do not currently apply an automatic retention limit beyond this — metadata for an active account is kept until you delete it, delete individual items, or delete your account as described below. The one thing that does expire on its own is a note sent to another Orgmee user: its encrypted content is deleted the moment their phone collects it, and any note never collected is deleted automatically 30 days after it was sent (section 3(o)).
When you use "Delete Account" in Settings, your account is signed out and hidden immediately, and everything held on that device — recordings, transcripts, summaries, Orgmee Notes, chat messages and Plan My Day content — is deleted right away and cannot be recovered, including by reactivating. Your phone-directory entry (see 3(e)) is removed immediately too, so other Orgmee users can no longer find you. What the 30-day window protects is your cloud data — your profile and the metadata records for your calls, Orgmee Notes, voice memos and chats — which is kept for 30 days from your deletion request, during which you can undo the deletion by signing back into the App and choosing "Reactivate". If you do not reactivate within 30 days, that remaining cloud data and your account itself are then permanently and irreversibly deleted.
If you no longer have the App installed, you can request deletion the same way at www.orgmee.com/delete-account.html by signing in with the Google account linked to your Orgmee account, then entering the phone number on it. We use those to locate and confirm the matching account — signing in proves you control that account, and the request only takes effect if the phone number also matches it; nothing happens otherwise. If they match, we send a one-time confirmation email to that account's address with the deletion date and how to undo it. The same 30-day undo window applies — you can still cancel by reinstalling the App and signing back in.
Submitted diagnostic logs and Contact Us messages are the exception: as explained in 3(j) and 3(k), we keep those as a record of what was reported to us, and they are not removed by deleting your account.
API keys you enter are stored in your device's encrypted storage and are never uploaded to us. Your cloud data is protected by access rules that restrict it to your authenticated account. No method of storage or transmission is 100% secure, and we cannot guarantee absolute security.
Locking your account. If your phone is lost or stolen, you can lock your account at www.orgmee.com/lock-account.html by signing in with the Google account linked to your Orgmee account. Locking disables sign-in to your account across your devices — it can take up to 1–2 hours to take full effect — and freezes your phone number so it cannot be moved to another account. Locking does NOT delete any of your data; it is kept and restored when the account is unlocked. Because locking is a security measure, unlocking is not automatic: you must contact us at support@adaptosolutions.in and verify your identity to our reasonable satisfaction (which may include control of your linked Google account and/or your phone number) before we restore access. We also recommend you change your Google password and sign out of all devices, as we cannot do that for you.
The App is not directed to children under the age required for consent in your jurisdiction (for example, under 13, or the higher age required locally). We do not knowingly collect data from such children.
Orgmee's cloud database and server functions run in India (Google Cloud's Mumbai region). This means that wherever you are, the information described in section 3 that reaches our servers — your account details, your call metadata, and the counts and labels for your notes, chats and day plans — is stored and processed in India, on infrastructure operated by Google on our behalf. The content that stays on your device (recordings, transcripts, summary text, note text, chat messages) does not go there at all.
If you are in the UK, the EU/EEA, Canada, Australia or the United States, this means your data is transferred outside your own country or region. We rely on Google Cloud as our processor and on the data-protection terms in Google's Cloud Data Processing Addendum, including the standard contractual clauses it incorporates, as the basis for that transfer. Some other services described in section 6 (for example Google Drive backup under your own account, or the Gemini API under your own key) may store or process data in other countries under their own terms.
If you would prefer your data not to be processed in India, the practical options are not to use the App, or to delete your account as described in section 8.
These are in addition to the controls the App already gives you: most of what you create never leaves your phone in the first place (section 2), you can delete individual items at any time, and you can delete your whole account (section 8). To exercise any right below, or ask a question about it, write to support@adaptosolutions.in from the email address on your account, so we can tell it is you.
United States. If you are a California resident, the CCPA/CPRA gives you the right to know what personal information we collect and why, to receive a copy of it, to have it corrected or deleted, and not to be treated differently for asking. We do not sell your personal information, and we do not share it for cross-context behavioural advertising — there is no opt-out for us to offer because there is nothing to opt out of. Several other states now give broadly similar rights; rather than asking which state you are in, we apply the same process to every request. Separately and importantly: US call-recording law is set state by state, and a number of states require every party to a call to consent rather than just you. That obligation is yours — see section 7.
Canada. Under PIPEDA you may ask what personal information we hold about you, ask for access to it, and challenge its accuracy and have it corrected. We rely on the consent you give when you create an account and choose which features to switch on. If a security breach created a real risk of significant harm to you, we would report it to the Office of the Privacy Commissioner of Canada and tell you about it. You can also complain to that office directly if our answer does not satisfy you.
Australia. Under the Australian Privacy Principles you may ask what personal information we hold, ask for access to it, and have it corrected if it is wrong. Because our servers are in India (section 11), using the App necessarily involves disclosing your information overseas, which APP 8 requires us to be plain about. If a data breach were likely to cause you serious harm, we would notify you and the Office of the Australian Information Commissioner under the Notifiable Data Breaches scheme, and you may complain to that office if you are not satisfied with how we responded.
We may update this Policy from time to time. The "Effective date" above shows when it last changed. Continued use of the App after a change means you accept the updated Policy.
You may not be an Orgmee user yourself, and this Policy is otherwise addressed to our account holders. If you spoke with someone who uses Orgmee, the only information about you that can reach our servers is your name and number, attached to that person's record of the call.
We never receive the audio of your call, or any transcript or summary of it. Those are held on that person's own device, not by us. And where their phone's own call-recording feature made the recording, we did not create it at all — see section 7.
You can contact us at support@adaptosolutions.in to ask what we hold that identifies you and to request its removal, and we will take reasonable steps to remove it on a verified request. If you want the recording itself deleted, it belongs to the person you spoke to rather than to us, so you would need to ask them.
Questions about this Policy: support@adaptosolutions.in.