RecallMap Privacy Policy

Last updated: 9 November 2026

This Privacy Policy explains how RecallMap handles personal information through its native apps, website and cloud service, including automatically managed local copies.

1 Who is responsible for your information

Ali Efe Yigiter, trading as RecallMap ("RecallMap", "we", "us" or "our"), is the controller of personal information processed to operate RecallMap. We are based in Başakşehir, Türkiye. Contact billing@recallmap.app about privacy, your account or a request concerning your information.

This Policy covers information handled through RecallMap and related support. Providers such as Apple and Google also process information under their own notices when you use their accounts or services. Their independent processing is distinct from processing they perform for us.

2 Your cloud notebook and local copies

Ordinary account notebook use requires an account and an active cloud plan or eligible active free trial. Notes, places and supported attachments belong to that account and synchronise while the app is running, connected and able to complete the upload. Cloud processing is part of providing the notebook. Refer to the live app for the features and storage options available on your device.

Before account activation, introductory screens may keep a first note, selected place, attachments or photo-import selections on your device. These are not uploaded as an account notebook until an activated account claims them. Onboarding preferences, such as your selected profile, remain device preferences rather than a cloud identity label.

The app automatically manages account-specific local copies for performance, synchronisation and available offline features. This includes notebook records, downloaded attachments, pending changes and recoverable recordings. Uploaded copies may be removed from the local cache to make space; unsynchronised content may remain only on your device until an upload succeeds. An offline access allowance belongs to one account and expires independently of whether copies remain stored. The Terms explain when online verification is required again. Keeping a local copy does not extend a plan or trial.

Using online maps and place search also sends requests to the relevant providers, independently of uploading notebook content.

Your operating system or a backup service you enable may also back up device files under its own settings. Such backups are separate from RecallMap cloud sync. Signing out is not a request to delete your cloud account or every locally stored copy.

3 Information you provide

Account information. We process your email address, account identifier, chosen sign-in method and the identity or profile information returned through that method. When you choose Apple or Google sign-in, the provider supplies information needed to authenticate you. Apple may supply a relay email address if you select Hide My Email. These methods do not give us your Apple or Google password or access to your mailbox. An email sign-in flow processes your address, verification and session information through our authentication service.

Waitlist information. The waitlist is closed to new signups. If you previously requested a launch notification, we process your email address and a record of that request, including its date and the consent wording. Joining the waitlist did not create an app account.

Notebook information. We process notes and checklists, titles, dates, place and folder names, coordinates, building identifiers, photographs, recordings, favourites, trip collections and related notebook records. Trip information includes the name, selected note references, dates, time zone and cover selection. Coordinates may describe places you manually select rather than your physical position. Attachment records include identifiers, names, sizes, formats, image dimensions or recording duration, and integrity checksums.

Selected images. The image importer resizes and re-encodes selected images and removes original GPS and EXIF metadata from the resulting image file. Information visible in the picture, retained filenames and separately saved dates or coordinates can still identify people or places. Selecting an image through the system picker does not itself give RecallMap access to your entire library.

Photo-library suggestions. If you choose Find moments on iPhone, RecallMap requests Photos access and reads dates, locations and asset information from the library you permit. It groups possible moments on your device. After an explicit scan, Daily suggestions can check that day’s photos when you open the app; you can turn these suggestions off. Scanning does not upload the whole photo library. Moments you keep can add a reduced cover image, original date, place and import information to your notebook. Saved notebook information can then synchronise with your account.

Raw device photo identifiers and skipped-photo decisions remain in a local import record. Saved notes may include source hashes and portable iCloud photo identifiers so another device with access to the same Photos library can resolve the source. These identifiers travel with the saved note; they do not grant us access to your iCloud Photos account. Photo access can be limited or withdrawn in device settings. Removing access does not delete images or metadata already saved to RecallMap.

Voice recordings. When you use recording, the app requests microphone permission and captures audio until you pause, end or cancel the recording. Audio and its metadata are stored with the account notebook; completed recordings may be retained locally for recovery if saving or uploading fails. Where cloud audio is available in the live app, saved recordings use the account’s attachment storage and allowance. The app does not transcribe recordings or request speech-recognition access. You can remove a recording from its note or discard a recoverable recording through the available controls.

Support information. If you contact us, we receive your contact details and whatever you include in your message or attachments. Send only what is needed to explain the problem; avoid passwords, sign-in codes, payment-card information and unnecessary private notebook content.

4 Information from using the service

Location features. My Location, quick capture and the camera viewfinder use location readings with your device permission. Readings include coordinates and accuracy and may be refreshed while a feature is in use. RecallMap does not continuously track movements in the background or automatically record a history of your movements. A location saved to a note becomes part of the notebook and can synchronise to the cloud. You can withdraw location permission in device settings and continue selecting places manually. Withdrawing permission does not erase saved coordinates.

Camera and motion. The iPhone viewfinder uses a live camera preview, location and device direction to help you select a mapped building. Camera frames are not recorded or uploaded. Motion and direction readings support the viewfinder on your device; the place you confirm can become part of the notebook.

Arrival reminders. When you arm an arrival reminder on iPhone, the app gives iOS a saved geographic region and a generic notification to deliver. iOS handles the location trigger without continuous location tracking by RecallMap. The app stores the reminder’s account, note and place references, region and scheduling state locally. It can observe notification state and interactions, but does not store a visit history or send arrival events to our server. Manage or cancel reminders in the app. A request already scheduled with iOS may remain until your device processes a change or cancellation.

Memories, notifications and widgets. The app selects memories and prepares widget information from the notebook on your device. Local scheduling records include selected note references, timing and interactions used to avoid repeated notices and adjust frequency. Memory notifications use the device notification system rather than a RecallMap push-notification service. Widgets and notifications can display note text, places, dates or images according to the feature and your privacy settings, including on the Lock Screen. Widget snapshots are stored locally for the app’s extension. Review notification-content settings and remove widgets if you do not want this information visible there. Arrival notifications use generic text without note content.

Maps and search. Loading or moving the map causes requests for the displayed map area to OpenFreeMap. The provider receives network information, including the requesting IP address, and requests identifying map areas. Native destination search sends the query and, where supplied, the current map region through Apple MapKit. These requests can reveal areas or places of interest even without access to your notebook text.

Purchases. Apple supplies transaction and product identifiers, purchase and expiry dates, subscription status, revocation or refund information, the purchase environment and an identifier binding the purchase to a RecallMap account. We use this information to verify cloud access, restore purchases and prevent the same purchase being assigned to another account. Apple collects payment information; RecallMap does not receive your full payment-card details.

Technical and security information. Our hosting, authentication, email and storage providers process information needed to handle requests, such as IP addresses, request times, delivery results, session identifiers and security events. Cloudflare Turnstile is used in supported email sign-in flows to help distinguish legitimate requests from abuse; it processes browser, device and network signals for that purpose.

Website error reports. When enabled, Sentry receives a limited error report containing the app version, environment, error category, time and selected source-file locations. Our reporting code removes notebook text, email addresses, credentials, original error messages, URL query strings and other fields outside its permitted set. Sentry also receives network information associated with delivering the report. This configuration does not enable session replay or behavioural advertising. Native notebook content is not sent to Sentry by this reporting feature.

App analytics (optional, iPhone). RecallMap 1.1 and later send usage analytics to Google Analytics for Firebase only after you turn on Settings → Share analytics. It is off until you choose it and is not used in the Mac app. When it is on, the app sends a limited set of events: features and steps you use (for example opening the editor, saving a note, place or trip, searching, starting sign-in, viewing plans or starting a purchase), result counts grouped as none, one, few or many, map loading time in broad ranges, failure categories such as offline or timeout, and the plan and price when a new subscription is activated in the app. Events never contain note, title, place or search text, coordinates, photos, recordings, email addresses or account identifiers. Google Analytics also receives an app-install identifier it generates, device and app details such as model, operating-system version, language and app version, and network information from which it derives approximate location such as country or city. The app does not access the advertising identifier (IDFA) or collect the identifier for vendors.

We collect information electronically through the app, website, sign-in and purchase providers, and your support messages. The legal grounds below apply where the relevant data-protection law governs our processing, including Türkiye’s law and UK or EEA law where applicable.

We use account, identity and session information to register and authenticate you and deliver sign-in messages. We use notebook records, trips, attachments and saved locations to store, organise, display, synchronise and export your notebook. We use purchase and account-binding records to verify your plan. These activities are necessary to perform our contract with you or take steps you request before entering it.

Optional capture, photo suggestions, reminders and widgets use the device readings, content, settings and scheduling records needed to provide the feature you choose. We rely on providing the requested service and obtain consent where the law requires it for device access or other processing. A device permission controls access to the relevant sensor or library; it does not authorise unrelated uses of the resulting information.

For earlier waitlist requests, we use the recorded information with your consent for the requested launch notification. You can withdraw that consent through an unsubscribe link or by contacting us.

We use correspondence and relevant account records to answer support requests and resolve account problems, relying on our contract or our legitimate interest in answering other enquiries. Security events, network information, limited diagnostics and subscription checks support our legitimate interests in preventing abuse, protecting accounts and keeping the service reliable. We weigh those interests against your rights.

With your consent, we use app analytics to understand which features are used, find failures and slow loading, and count how many people subscribe after installing, including in aggregate after an app promotion through Google Ads. We tell Google Analytics that advertising storage, advertising user data and ad personalisation are not permitted, and we do not use analytics to track you across other companies’ apps or websites. You can withdraw consent at any time; withdrawal does not affect processing before it.

We process records required to comply with legal obligations and respond to lawful requests. Where necessary to establish, exercise or defend a legal claim, we process the relevant account, transaction and correspondence records on that basis under Turkish law, or on the applicable legitimate-interest or legal-obligation basis under UK or EEA law.

We will request consent separately where it is required, including for any non-essential storage or access technology that requires it. An operating-system permission is a technical control and is not, by itself, a substitute for every legal consent requirement.

An account and cloud processing of your notebook are necessary for RecallMap’s notebook service. If you do not provide the required account information or permit the processing needed to deliver that service, you cannot use its notebook features. We also need to verify an active plan or eligible trial. This does not prevent you from viewing public information, contacting support or exercising your data-protection rights. Photos, recordings, location access, camera use, suggestions, reminders and widgets are optional. Refusing a permission prevents the dependent feature from working but does not prevent ordinary manual note-taking or place selection.

We do not ask you to provide health information, religious beliefs or other specially protected information to create an account. Information you choose to include in notes, images, recordings or saved places may nevertheless reveal these details. Accepting the Terms, granting a device permission or uploading content does not by itself provide explicit consent to process specially protected information. Where the law requires explicit consent, we will request it separately for the stated purpose.

6 Who receives information

We disclose information only as needed for the purposes above, subject to applicable law and appropriate contractual arrangements.

Supabase provides authentication, the account database and cloud attachment storage. It processes account details, uploaded notebook records and attachments, and associated service and security information.

Resend delivers account emails and launch notifications and manages the launch subscriber list. It processes email addresses, subscription preferences, consent records, message content and delivery information.

Cloudflare provides website delivery and security and processes network and request information. Its Turnstile service handles checks in supported sign-in flows.

Apple processes App Store purchases, subscription verification and Apple sign-in. MapKit receives native search queries and map-region context. Apple’s device services also support the Photos, location, notification, widget and optional system-backup functions you use.

Google processes authentication information when you choose Google sign-in.

Google also provides Google Analytics for Firebase, which receives the app analytics described above only while Share analytics is on.

OpenFreeMap receives map resource and area requests and the network information accompanying them.

Sentry receives the limited website error reports described above when reporting is enabled, together with network information associated with those requests.

These recipients do not all receive the same information. For example, the map provider does not need your notebook text to serve map tiles, and our error-reporting payload excludes notebook content. Independent provider functions, such as Apple billing and Google account management, are also governed by those providers’ own privacy notices.

People providing support, maintenance or professional advice may access information where necessary for their role and subject to confidentiality obligations. Information may also be disclosed to comply with law or protect lawful rights and safety. If the business is transferred or reorganised, relevant information may be transferred with it under appropriate safeguards and applicable notice requirements; it is not made public merely because ownership changes.

We will not use your stored data to train or fine-tune any artificial intelligence models, and we do not permit our service providers to do so. We do not sell personal information or share it for cross-context behavioural advertising. We do not make private notebooks available to other users as a social or public publishing feature.

7 Local storage and similar technologies

The native apps use local files and preferences for notebook copies, pending onboarding content, capture recovery, photo-import records, reminder configuration, widget snapshots and display settings. Apple Keychain stores session credentials and account-bound access allowances. Local device processing does not mean that all of these records are uploaded to our servers. Website account and security features may use browser storage for authentication, preferences and related operation.

When Share analytics is on, the Google Analytics for Firebase SDK keeps an app-install identifier and queued analytics events on your iPhone. Turning Share analytics off stops collection, deletes queued events and resets that identifier.

Removing native app data can erase unsynchronised notes, recordings and recovery copies. Clearing browser storage affects website sessions and settings; the website does not provide a browser notebook. Some device records remain until you discard them, remove the relevant app data or the app replaces or clears them. Device backups and saved exports are separate copies under your control.

Where consent is required for non-essential storage or similar technologies, we will ask for it separately. You can use your browser or device settings to control storage, although disabling storage needed for sign-in or security may prevent those features from working.

8 Storage locations and international transfers

The account database and cloud attachment service use a Supabase project in the London region of the United Kingdom. RecallMap is operated from Türkiye. Providers and their subprocessors, support teams and network services may process information in other countries; selecting the London region does not restrict all processing to that region.

Contact billing@recallmap.app for information about processing locations and the transfer safeguards applicable to your information, including how to obtain a copy of relevant safeguards.

9 How long information is kept

We retain information for the purposes described in this Policy. The criteria include whether your account exists, whether you have requested deletion, outstanding support or purchase disputes, security needs, recovery requirements and legal obligations.

Local notebook copies support account use, synchronisation and recovery. Replaceable uploaded attachments may be evicted automatically. Pending changes and recoverable recordings remain until saved, explicitly discarded or the relevant app data is removed. Signing out or losing access does not necessarily erase these files.

Photo-import, reminder and widget records remain on the device while needed to resolve source photos, avoid duplicate imports, manage reminders or supply widgets. Cancelling a reminder or disabling notifications changes scheduled delivery; it does not necessarily erase every local configuration record. App-data removal and backup settings affect retained copies.

Cloud notebook data is kept to provide your account while access is active, unless you request deletion. It is retained for 30 days after plan or trial access ends and may be deleted afterward. This does not mean deletion occurs automatically on that date or that the account itself is immediately closed. You may request access or earlier deletion without renewing. Continued storage after this period is not a guarantee of recovery.

Completing account deletion removes the cloud account and its associated notebook and attachments from active systems. A failed request can leave cleanup incomplete. When no note uses a cloud photo or recording any more, for example after you delete its note or remove it from a note, we keep it for 30 days so the change can be undone, then permanently delete it from cloud storage and stop counting it toward your storage allowance. Deletion waits while an account is suspended or under a recovery or deletion hold. Provider backup copies remain until their recovery cycle overwrites or expires them.

Account-linked subscription verification records are deleted with the account. Separate records may be retained where required by law or necessary to resolve a dispute. Apple retains its own purchase records under its policies.

Support correspondence is kept for the enquiry, necessary follow-up and related legal claims. Whether an issue is resolved and the applicable legal retention or limitation period determine how long it is needed. Operational records are kept for delivery, security and diagnostic purposes, including resolving failures, investigating incidents and preventing repeated abuse, subject to provider retention settings and applicable legal requirements.

Google Analytics keeps event-level app analytics for 2 months and information linked to an app-install identifier for up to 14 months after that install’s last activity. Aggregated reports that no longer identify an app install may be kept longer.

Information retained for a legal obligation or claim is limited to what is necessary for that purpose. Copies on an offline device, in your saved exports or in device backups cannot all be erased by a cloud account-deletion request. Deletion from active systems does not imply immediate erasure from every provider backup. Contact billing@recallmap.app to ask about retention of your information or to request deletion.

10 Deletion and your choices

You can edit or remove notebook content through the available app controls. Contact billing@recallmap.app to request deletion of the cloud account, or use account-deletion controls where available. We may ask for information needed to verify the request. If deletion fails or remains pending, contact us; a failed request is not confirmation that deletion finished.

Signing out, deleting the app and cancelling renewal have different effects. Cancelling a subscription does not itself delete cloud content. Deleting a RecallMap account does not cancel an Apple subscription. Manage Apple renewal separately in Apple’s subscription settings.

Device settings control permissions for location, Photos, microphone, camera and notifications. The app provides controls for photo suggestions, reminder cancellation and notification content. Disabling a feature or withdrawing permission stops its future use of that permission; it does not erase information already saved.

You can turn Share analytics on or off at any time in the app’s Settings.

The app’s notebook export requires active notebook access and can include saved changes on that device, together with attachments it can retrieve. Refer to the live app for supported export formats and limits. You can also request a copy of information held in the cloud, or account deletion, by email without an active plan or trial. A cloud-data request cannot retrieve changes held only on an offline device. Save an accessible copy before requesting deletion; we do not promise recovery after deletion.

11 Your data-protection rights

Depending on the law that applies, you may have rights to access your information, correct inaccuracies, request erasure, restrict processing, and receive or transfer certain information in a portable form. You may withdraw consent for processing that relies on consent without affecting earlier lawful processing.

You may object to processing based on legitimate interests on grounds relating to your situation. You may also object to direct marketing at any time.

Contact billing@recallmap.app to exercise a right. We will respond within the applicable legal time limit and explain any lawful restriction, extension or refusal. We may need to verify your identity, but will request only information proportionate to the request.

Under Türkiye’s Personal Data Protection Law, you may ask whether we process your data, how and why it is used, and who receives it; request correction or deletion where applicable and notification to recipients; object to adverse outcomes from exclusively automated analysis; and seek compensation for unlawful processing. Submit your request to us first. We respond within the applicable period, no later than 30 days for requests under that law. If necessary, you may then complain to the Turkish Personal Data Protection Board through the applicable procedure.

In the United Kingdom, you may complain to the Information Commissioner’s Office. In the EEA, you may contact the competent national supervisory authority. These complaint rights do not require you to obtain our permission.

12 Security and automated checks

We use account and session checks and access restrictions intended to keep notebooks separated, together with secure transport for cloud requests. Native session credentials are stored in Keychain. No system can guarantee absolute security.

Cloud notebooks are not end-to-end encrypted. Our service and infrastructure providers must process uploaded content to operate storage and sync. Protect your devices and avoid sending credentials in support messages.

Automated checks validate transactions, account access, subscription status, quotas and potential abuse. A failed check may delay sign-in, restrict notebook access or block cloud writes. Contact us if you believe a restriction is mistaken. These checks do not use the meaning of your notebook to create advertising profiles. Optional photo suggestions and memory selection organise information for you on your device; they are separate from purchase and access checks.

13 Children

RecallMap is not intended for children under 13 or anyone below a higher minimum age required where they live. If you believe a child has provided information in breach of those requirements, contact us so we can investigate and take appropriate action. Where the Terms allow a guardian to agree for a younger user, the minimum age still applies. An App Store age rating is a content rating and does not replace these eligibility requirements.

14 Updates and contact

We will update the date above when this Policy changes and provide appropriate advance notice of material changes. Before using information for a materially different purpose, we will explain that purpose and obtain consent where required.

Ali Efe Yigiter, trading as RecallMap
Başakşehir, Türkiye
billing@recallmap.app

Terms of Service