Version 1.9 · effective 2 November 2026
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 support@rekallme.com and we will explain it.
Rekallme is operated by:
Manusinh Thakor trading as Natura Apps (sole trader)
ABN 59 110 869 973
Greenacres SA 5086, Australia
support@rekallme.com
We are the data controller for the information described here. Australian privacy law and the Australian Privacy Principles are the framework we build against.
If you sign in with Google or Apple, that provider also processes information to authenticate you and keep the sign-in secure. Google Sign-In may process an account identifier and an IP address, including an approximate location inferred from it, for sign-in and fraud prevention. Google's hosted sign-in or account-verification screens may also ask you for information such as a phone number. Information you provide directly to that provider is handled under its privacy policy; it is not automatically added to your saved Rekallme information. Sign-in libraries may also process technical and usage information as described in their privacy disclosures. We disclose relevant app and SDK collection in the App Store privacy information. See Google's privacy policy and Apple's privacy policy.
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. Analytics can also include device and app details and approximate location derived from your IP address; this does not require access to your phone's GPS. We do not intentionally send the text of memories, questions, file names, photos or documents to analytics. Session replay is not enabled.
We record the source and time of saved information and significant account actions to run the service and maintain an operational audit trail. Your device may also keep recent-item information locally. These records are separate from the contents you save.
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.
How It Helps page. You can type your profession on the How It Helps page to see how Rekallme could help. We keep what you type, the answer shown, the time, your country and a code that changes every day, so we can count visitors without knowing who they are. We do not keep your IP address. If your profession is not in our list, what you typed is sent to Anthropic (Claude) to write the answer. We use these records to improve the page and delete them after 12 months. Please type only your profession, not personal details. If you accept cookies, we also count which professions you pick from the list.
App launch emails. If you ask us to tell you when the iPhone and Android apps launch, we keep your email address, which app you asked about, the time, your country and the same daily visitor code. It is stored with Supabase in Sydney, used only to send you the launch email, and deleted once that email has been sent. Ask us any time and we will remove it sooner.
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.
MCP connections are available on the eligible plans shown in the app. 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.
In the web app, Upload Files can import files from your Google Drive. Google
shows its own window, where you choose the files. Rekallme asks Google only for
access to the files you pick (Google's
drive.file permission); it cannot see or open anything else in
your Drive. Each picked file is downloaded in your browser and saved into
Rekallme like any file you upload, using one credit each. The short-lived
Google access token stays in your browser for that session; we do not store it
on our servers, and we never change or delete anything in your Drive.
Rekallme's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use it only to import the files you choose, we do not use it for advertising, and we do not use it to train AI models. You can remove Rekallme's access at any time in your Google Account, under Security, Your connections to third-party apps and services.
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; also writes the answer for professions typed on the website's How It Helps page | United States |
| OpenAI | Creates meaning-based search representations for saved information and search questions; depending on the model used, also extracts details and events and answers 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 use the commercial APIs of OpenAI and Anthropic to process your saved information and search requests. Under their standard API policies, inputs and outputs are not used to train their general-purpose models unless the customer explicitly opts in. The provider accounts we use have optional training-data sharing and model-feedback sharing disabled. We do not submit your saved information or search requests to their voluntary feedback or training programmes.
No training use does not mean no storage. The providers may retain data for service delivery, abuse prevention, security or legal obligations, as explained below. The consumer settings for ChatGPT or Claude are separate from the API services Rekallme uses.
store: false for Responses API requests to
avoid optional response-history storage. This does not turn off abuse-monitoring
retention or establish a Zero Data Retention agreement.Rekallme does not claim Zero Data Retention with either provider. Deleting information in Rekallme does not immediately erase a request already processed and retained by a provider under these rules. See OpenAI's API data controls, Anthropic's commercial training policy and Anthropic's retention policy for the applicable details and exceptions.
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, runs the human check on the How It Helps page and stores that page's records. Stripe processes card payments for subscriptions and credits bought on the web, and Resend sends transactional emails, including billing emails such as receipts and invoices, and a one-time account-deletion completion email where enabled for a verified email address. The deletion-confirmation recipient and retention limits are described in the account-deletion section below. 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. Android also provides separate notification channels for reminders, service updates and news or offers. Where available, you can disable the news and offers channel without disabling reminders. We will seek any consent required before sending promotional messages.
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.
Extra credits do not expire. An active Lite or Pro subscription is required to use them. If your subscription ends, unused extra credits remain on your account and become usable when you resubscribe. Refunds are subject to applicable law and the purchase platform’s policies. Monthly plan allowances are separate. Deleting your account removes its unused extra-credit balance along with the account records described below; deletion does not automatically issue a refund or cancel an app-store subscription.
| 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. The AI-provider retention periods and exceptions are explained above. Other service providers apply their own retention schedules; these include operational and legal records that can outlast your account.
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 → Privacy, Security and Data → 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 interpretation of what you wrote and may be wrong. Rekallme can create events from extracted dates automatically. Review the resulting dates, times and reminders, and correct or delete events that are not right.
Delete a single memory at any time. To delete everything, Settings → Privacy, Security and Data → 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 removal of your files and account records starts on the next hourly cleanup run. Temporary service failures can delay completion. This excludes the general account audit log and third-party records described here.
When deletion-completion confirmations are enabled, a verified account email is kept separately only to send that confirmation. It is removed after the email service accepts the message, delivery permanently fails, you cancel deletion, or the retention period expires. This period is at most 7 days after completion; for a request that has not completed, it expires 7 days after the grace period. Delivery status may remain with the account-deletion audit, without the email address.
In app version 1.0.0 build 9 and later, open Settings → Privacy, Security and Data → AI Processing → Withdraw AI Consent. Confirm the choice to stop new AI saves, extraction and AI searches. In older builds, or if you cannot use the app, email support@rekallme.com.
Your existing information remains available to browse, export and delete. Pending AI drafts are paused; enabling AI again does not automatically submit those drafts. You must review and retry them. To enable AI again, review the current disclosure and explicitly agree in AI Processing settings.
Requests already sent may finish. Data already sent is subject to the provider retention rules described above. App analytics follows the same consent. Notification permission is separate. Withdrawal does not delete your account, cancel a subscription or revoke a separately authorised external tool connection; manage those controls separately in Settings.
Write to support@rekallme.com 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 email and password, Google account or Apple account you sign in with — and the device you unlock. Someone with access to your sign-in credentials or an unlocked app may be able to access your saved information. Protect your device and sign-in account. If you suspect unauthorized access, reset your Rekallme password or secure the Google or Apple account you use, and contact 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 security@rekallme.com.
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 support@rekallme.com and we will remove it.
Each published policy has a version number and effective date. We will notify you of material changes and seek renewed consent where required before introducing the affected processing. Consent decisions are recorded against the version presented to you. This version explains the retention and paid-plan use of purchased extra-credit balances. It does not introduce new data collection, marketing or AI-processing permissions.