Launch draft · version 1.3 · effective date to be set before launch
Rekallme is an app for saving things you want to remember — notes, photos, documents, dates — and finding them again later. Because that means you are handing us things that matter to you, this page sets out exactly what we collect, where it goes, how long we keep it, and what you can do about it.
It is written to be read. If anything here is unclear, write to [email protected] and we will explain it.
Rekallme is operated by:
Manusinh Thakor (sole trader)
ABN 59 110 869 973
Greenacres SA 5086, Australia
[email protected]
We are the data controller for the information described here. Australian privacy law and the Australian Privacy Principles are the framework we build against.
When you save a memory we store:
Dates we find in what you save, and the folders you organise things into, including any rules you set for what a folder should keep.
Your plan, remaining balance, usage, and records of any purchases, promotions or referrals. If you buy through an app store, we and our billing provider receive purchase and entitlement information so we can give you what you bought. Apple or Google processes your payment card; we do not receive its full details.
If you send feedback or a feature request in the app, we keep your message, its type, your account identifier, the app version and when you sent it. We also receive technical information needed to diagnose crashes, such as the app version, device and operating system, the error type and code location. Our crash-reporting code removes the original error message because it could contain something you saved. A diagnostic report can still contain technical identifiers and should not be assumed anonymous.
With analytics enabled, we record limited events such as a screen or feature being used, a save succeeding, or a paywall being shown. These events may be linked to your account identifier. We do not intentionally send the text of memories, questions, file names, photos or documents to analytics. Session replay is not enabled.
For each memory and event we also record where it was saved from (the phone app, the web app or a connected AI app) and when, and when and from where it was last opened. We also record which of these you use and when you first and last used each one. This helps us show recent items and understand how Rekallme is used. It is stored with your account and deleted with it.
When you visit this website, its hosting provider may receive ordinary technical request data such as your IP address, browser and requested page to deliver and secure the site. If you email us, we keep your message and contact details to respond. This website does not receive the memories you save in the app.
If you choose Accept in the cookie banner, this website also uses PostHog to record which pages are visited and which links and buttons are clicked, with the browser, device type and approximate location worked out from your IP address. PostHog stores an identifier in a cookie and in your browser's storage so repeat visits can be counted. If you choose Decline, or make no choice, none of this is loaded and no analytics cookie is set. You can change your answer at any time from Cookie settings at the bottom of every page; declining after accepting removes what PostHog stored in your browser.
Your consent decisions, an audit log of significant account actions, which version of this policy you agreed to, and any account deletion request.
If you connect Rekallme to ChatGPT or Claude through MCP, the app can use only the access you choose on the connection page. Read allows searching folders, reading saved information and reading events. Write allows saving information and creating folders or events. Each choice is stored separately for your account and the connected app. Neither choice is selected automatically.
The connected app receives the tool results needed for your request. MCP activity records the app, your account, the tool, the outcome, the time and affected record IDs for security and support. The audit record does not copy the saved text. Detailed MCP activity and consent-change history is removed by a daily cleanup after 90 days, or sooner if you delete your account. Your current Read and Write choices remain until you change or revoke them. You can revoke an app's access, and revocation stops new MCP requests immediately. MCP does not provide delete, Ask AI, file or image tools.
The MCP Server is part of Rekallme Pro. You connect an app by signing in to your Rekallme account on our connection page and choosing Read, Write or both. If you connect the same app again, the new connection replaces the older one. You can see and disconnect every connected app in Settings, under MCP Server, or in the connected app itself.
Once a connected app receives a result, such as a saved note or an event, what happens to it there is decided by that app's provider and your settings with them. For example, Claude or ChatGPT may keep it in your chat history or use it to improve their models, depending on your settings and their own privacy policies. We do not control that. Connect only the apps you trust with your information, and choose Read or Write to match what you want them to do.
This is the most important section on this page, so it is not buried.
Rekallme sends what you save to AI companies outside Australia so they can process it. There is no way to provide the product without this. The providers are:
| Provider | What it does | Where |
|---|---|---|
| Anthropic (Claude) | Reads what you save to write the title and summary, pull out dates and structured values, and answer your questions when you search | United States |
| OpenAI | Creates meaning-based search representations for saved memories and search questions | United States |
When you dictate, your phone's own speech recognition converts what you say into text — Google's on Android, Apple's on iOS. Depending on your device and your settings, that conversion may happen on the phone or on their servers. That part is the platform's, governed by Google's and Apple's privacy terms.
Rekallme itself never receives, records or stores audio. Only the resulting text reaches us, and only the text is saved or sent to the AI providers above.
We do not permit your content to be used to train general-purpose AI models, and we are finalising the contractual terms with each provider that put this beyond doubt. We will update this policy, and tell you, once those terms are in force. We would rather say this plainly than imply a protection we have not yet signed.
Both providers are outside Australia, so using Rekallme involves disclosing your information overseas. We take reasonable steps to ensure they handle it appropriately, and we remain accountable to you for it. The current list of everyone who processes your data is at rekallme.com/sub-processors.
Supabase stores account details, saved content and files, feedback, and operational records. Google Firebase helps us receive crash reports and deliver push messages. A push token identifies an app installation for delivery; message content can pass through the push service. RevenueCat helps us verify app-store purchases and manage subscription entitlements. PostHog processes the limited app analytics described above, and website analytics if you accept cookies, in the United States. Cloudflare runs a security check (Turnstile) on email sign-in, sign-up and password reset to stop automated abuse. It receives technical signals from your browser or device, never what you save. Cloudflare also hosts this website. Stripe processes card payments for subscriptions and credits bought on the web, and Resend sends billing emails such as receipts and invoices. Apple and Google also process sign-in, payments, speech recognition or push delivery where you use those platform features. The sub-processor list explains each service's role in more detail.
Crash reporting begins when a release build starts. Push delivery depends on your device permission. Analytics requires an analytics-enabled build and your acceptance of the app's data-processing consent. The current app does not offer a separate analytics switch: withdrawing data-processing consent stops analytics and also stops new saves. We will not describe analytics as separately optional unless the app offers that choice.
Push messages may include service information and, where permitted, product news or offers. You can turn off push notifications in your device settings. Before sending promotional messages at launch, we will provide a simple way to opt out of those messages without losing reminders.
Your memories, files and account are stored with Supabase in Sydney, Australia. Some processing required to run the app, including AI, analytics, billing and push delivery, takes place outside Australia. The sub-processor list identifies those services and their known locations. This website does not receive the memories you save.
| What | How long |
|---|---|
| Memories, events, folders and files | Until you delete them, or delete your account |
| Your original input, word for word | Exactly as long as the memory it belongs to. Delete the memory and it goes with it |
| Search representations | Stored with the memory; deleted with it |
| Feedback and feature requests | Until you delete your account, unless a longer period is required to resolve a legal obligation |
| Push token | Until it is removed when you sign out or delete your account, or replaced by your device |
| Purchase and subscription records | While your account exists; app stores and billing providers may keep their own records under their policies |
| Detailed MCP activity and consent-change history | Removed by a daily cleanup after 90 days, or sooner when you delete your account. Current app access choices remain until changed or revoked. |
| General audit log of significant account actions | Kept after your account is deleted, so we can show your data was handled lawfully. It records that things happened, never what you saved. This is separate from MCP activity. Your consent records and subscription records are attached to your account and are deleted with it. |
Our providers may retain operational records, backups, crash reports or AI requests under their own service terms. Deleting your account removes the data we control as described below, apart from the general account audit log; it does not necessarily erase a provider's already processed request or a purchase record held by Apple or Google. We will confirm the remaining retention periods before launch and publish them here.
If we stop running Rekallme, you get 60 days' notice by email and in the app. Export works for the whole 60 days, so you can take everything out. Any paid time you have not used is refunded pro-rata. The app content and account data we control are deleted 30 days after we close, on a date we state in the notice, subject to the audit-log and provider exceptions above.
The same commitment is written into the Terms of Service.
Settings → Data and Privacy → Export. You get your memories, events, folders and file details in a portable format.
Anything Rekallme wrote about what you saved — the title, the summary, the dates it found — can be edited in the app. Extracted dates in particular are the AI's reading of what you wrote, not a fact, which is why you are always asked to confirm one before it becomes an event.
Delete a single memory at any time. To delete everything, Settings → Account → Delete account. What happens then is described at rekallme.com/delete-account. In short: the request is held for 7 days so you can change your mind, and after that your files and account records are removed, except the general account audit log and third-party records described here.
Settings → Data and Privacy. Withdrawing consent to data processing means new memories can no longer be saved, because AI processing is how saving works. It also stops app analytics under the current consent design. You can change notification permission in your phone's settings.
Write to [email protected] first — we would rather fix it. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Your data is encrypted in transit and at rest. Every record is bound to its owner at the database level, so one account's search cannot reach another account's memories. Our own operational logs are designed to record events, identifiers and errors rather than what you wrote. Crash reports and service providers' logs are described above.
No system is beyond compromise, and we will not claim otherwise. If a breach occurs that is likely to cause you serious harm, we will notify you and the Office of the Australian Information Commissioner as the law requires.
Two things here are not ours to secure. The first is your way in — the Google or Apple account you sign in with — and the device you unlock. Anyone who has either reaches your memories exactly as you do, and nothing we build at our end changes that. Because there is no Rekallme password, the security of that account is the security of your memories: protect it there, and if you think someone has reached it, secure it with Google or Apple first, then write to us.
The second is the ground your data rests on. We do not own it: the providers named above run it. We choose them for their security record and hold them to it in contract, but a failure inside one of them is something we can detect, disclose and act on rather than something we can prevent.
To report a security problem, write to [email protected].
Rekallme is for people aged 18 and over. We do not knowingly collect information from anyone under 18. If you believe a child has created an account, write to [email protected] and we will remove it.
Every version of this policy has a version number and a date. When we change it in a way that affects how your information is handled, the app will show you the new version and ask you to agree to it before you continue. Your agreement is recorded against the specific version you saw, so there is always a clear record of what you were told and when.