Privacy policy

for the Remika apps for Android and for iOS (iPhone and iPad) and the website remika.app · Last updated: 17 October 2026

1. Controller

A data protection officer has not been appointed and is not required by law.

2. What stays on your device

Reminders, birthdays, notes, the photos and voice recordings you attach, and all settings are stored only locally on your device, in the app's own storage. We have no access to them. Uninstalling the app deletes them, with these exceptions: backup files you saved outside the app, photos you take with the camera inside the app (they are also saved to the device's photo gallery and stay there), and, on iOS, the two small items that Remika keeps in the iOS Keychain (sections 3.3 and 3.8).

Backups. A backup is made only when you ask for one in the settings. It is a single file, and we do not upload it anywhere. The backup file is not encrypted: the titles of your reminders, the text of your notes, your settings and your attachments are inside it in the clear, so keep it where you keep documents.

• On Android: the app writes the file into a folder you choose. If that folder is synced by a cloud service, that service's terms apply. You can also send a backup on through Android's share menu.
• On iOS: the app opens the iOS share sheet; you choose where the file goes (for example "Save to Files", including iCloud Drive, or mail). If you save it to a cloud service, that service's terms apply.
• On both: when you export or send a backup through the share menu, a temporary copy of the file stays in the app's temporary storage until the next export replaces it or the system clears it. To restore, you pick a file with the system file picker.

Device backups. Remika has no synchronisation of its own and does not use iCloud. If your device's own backup is switched on, the backup may also contain the data of apps, Remika included: on iOS the iCloud Backup or a backup to a computer, unless you exclude Remika in the iPhone's settings; on Android Android's automatic backup, where it is switched on. That happens between your device and Apple or Google under their terms; we have no access to it.

Calendar files (.ics) you open with Remika are read on the device only.

The device's calendar. If you choose "Import from the phone's calendar" in the settings, Remika asks for permission to read the calendar and reads the events of the calendars you select (from 60 days back to one year ahead: title, notes, times, alerts and repeat rules), once, on the device only. During this import and ordinary editing of the resulting reminder, no calendar data is sent to our server or to third parties. Remika never changes the calendar. The events become ordinary reminders in the app.

• On Android: the app asks for the permission to read the calendar only.
• On iOS: iOS offers reading events only as "Full Access"; Remika uses it solely to read. It does not read the Reminders app.

Widgets. Remika's home-screen widgets (shortcuts, notes and a calendar) do not connect to our server or to anything else.

• On Android: the widgets show data read from the app's own local storage on the device.
• On iOS: the app places a prepared display snapshot in storage shared between the app and its widgets (an iOS App Group). For the calendar widget the snapshot holds the month grids: day numbers, the colour of the category of reminders on a day, holiday markers, labels in your language and the theme colours. It contains no reminder titles, notes, attachments or settings.

Receiving shared content. When you share text, a web address, an image or a file with Remika from another app, the app makes a note from it and copies a file or image into its own storage.

• On Android: this goes through Android's share menu.
• On iOS: the "Share → Remika" extension copies the item into the shared storage (the same App Group) so that the app can pick it up. The extension makes no network connection.

Sharing and opening in other apps: when you pass a note on through the system share menu or open an attachment in another app, you do so on your own initiative; the receiving app's terms apply.

3. What leaves your device

3.1 Voice input

For dictation Remika uses the speech recognition service of your device. Remika only receives the recognised text; we neither receive nor store dictation audio. The microphone is used only when you start dictation or a recording yourself. To recognise times better, when you dictate a reminder the app gives the recognition service a list of hint words: fixed words such as weekdays, and words you corrected in the app before. For dictation into notes and comments no hint words are given.

• On Android: this is Android's speech recognition service (usually provided by Google). The audio is processed by that service, on the phone or on Google's servers depending on the device, under Google's privacy policy. Language packs for offline recognition are downloaded by Android itself.
• On iOS: this is the speech recognition built into iOS (Apple's Speech framework). Remika asks for two permissions: Microphone and Speech Recognition. Remika does not require the recognition to happen on the device: according to Apple, depending on the language and the iPhone, the audio is processed on the iPhone or sent to Apple's servers, under Apple's privacy policy. Dictation in Remika on iOS needs an internet connection; the app does not start it when it knows the device is offline.

3.2 Text interpretation by our server (AI)

By default Remika first tries to understand a reminder on the device itself. Text is sent to our server

• when the app finds no date and no time in a reminder, or cannot reliably understand a time or a word (for example whether "7:30" means morning or evening),
• for notes: the text just dictated, to add punctuation, suggest a title or split it into list items; if the device was offline, this is retried the next time the note is opened. If you ask the app to split a list item yourself, that item (possibly typed) is sent too.

For reminders we send the text, the current time with time-zone offset, the input language and your default reminder time; for notes only the text and the language. The installation identifier from section 3.3 is sent as well. Our server runs on Cloudflare (Cloudflare, Inc., USA) and passes the text to Google's Gemini API (Google LLC, USA), which produces the result. Our server does not store the text. While a request is being handled, our server writes a short line to Cloudflare's live log view: which function was called and how long it took; if a request fails, the error details appear there as well, which may include the error response from Gemini. This view can be watched only live, while someone is connected to it. We have not set up any storage for these lines, so they are not kept by us. So that a request repeated over a poor connection is not counted against the daily limit twice, our server remembers each request for 10 minutes by its fingerprints: a hash (SHA-256) of the installation identifier together with a random request key, a hash of the identifier itself, a hash of the function name and the request text, the start time, the state (in progress, done, failed), whether the request was counted against the limit and how many times the model was called for it. The server stores neither the text, nor the answer, nor the key itself. The hash of the text is derived from your words, so we treat it as pseudonymous rather than anonymous data. After 10 minutes the record is no longer used and is deleted with the next request or by the nightly clean-up, at the latest within a day. Google processes the text under the Gemini API terms (paid tier) and does not use it to improve its products; however, Google retains the request and the response for up to 55 days solely to detect and prevent abuse (Gemini API usage policies).

Legal basis: Art. 6(1)(b) GDPR: interpreting the text is the function you request by entering it.

3.3 Installation identifier and usage limit

When the app first starts (see section 3.8) it contacts our server and receives a random identifier. It contains no information about you or your device. The app keeps it in the device's secure storage. On the server we keep the identifier itself, its creation date and the date it was last used (updated at most once a day); all three are deleted 400 days after the last use. In addition we keep daily counters of AI requests for 2 days, one in total and one for notes and lists, to enforce the daily limit: 10 requests without Remika Plus and 20 with Remika Plus, of which at most 7 and 15 respectively for notes and lists. So that a program stuck in a loop cannot overload the service, we also count each installation's requests per minute (at most 10); this counter is kept for 2 minutes. Next to the identifier we keep the trial pseudonym from section 3.8 (the same hash), so that the server knows whether the installation is in its trial period; it is deleted together with the identifier.

On iOS: the identifier is kept in the iOS Keychain. According to Apple's documented behaviour, items in the Keychain may remain on the iPhone after an app is deleted, and items that are not marked as limited to this device are part of encrypted device backups and can move with such a backup to a new iPhone. The identifier may therefore be used again after a reinstall.

3.4 IP address

Every connection to our server involves your IP address, processed technically by Cloudflare. To prevent abuse we count requests per IP address (the counters are stored together with the IP address): at most 300 requests per calendar minute from one address (this counter expires after two minutes and is removed by a nightly clean-up) and at most 20 newly issued identifiers per day per IPv4 address or 10 per IPv6 /64 network; for IPv6 only the first 64 bits of the address are stored. Issuing an identifier again to a device that is already known does not count. This counter is deleted after 2 days. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is a working service that cannot be abused.

3.5 Public holidays and school holidays

While showing public holidays or school holidays is switched on, the app requests the chosen country, region (if any) and year from the public services OpenHolidays API (openholidaysapi.org) and Nager.Date (date.nager.at). Your IP address is visible to these services; no other data is sent. Results are cached on the device, and a year that is already stored is requested again only when it is older than 90 days, when you change the country or region, or when the calendar shows a year that is not stored yet. The lists of countries and regions offered in the region picker are requested when you use the picker and are kept for 180 days. With both switched off, nothing is requested. Legal basis: Art. 6(1)(b) GDPR.

3.6 Link previews

When you share a link into Remika, the app creates a note with a preview card. To do so it requests the linked page itself (for YouTube, YouTube's oEmbed service, www.youtube.com, Google LLC, USA, with the full video address) and then the preview image named by the page. In addition, the component that receives shared items on your device contacts the shared web address once, to find out what kind of content it points to; for a YouTube link this is the video page itself. These sites see your IP address and the address of the link; no other data is sent. The preview is stored on the device only. Legal basis: Art. 6(1)(b) GDPR: the preview is part of the note you create by sharing the link.

3.7 Remika Plus and payments

We do not receive your card or bank account details. The app asks the store whether you have bought Remika Plus, so that it can enable it. Remika processes the store's answer only on your device and does not send purchase information to our server. With each AI request (section 3.2) the app tells the server one thing: whether Remika Plus is currently active (a purchase or the trial period), so that the right daily limit applies (section 3.3). The server receives no purchase type, token or dates, and does not store this flag separately. Legal basis: Art. 6(1)(b) GDPR: performance of the contract for access to the purchased Plus features.

• On Android: payments are handled by Google Play. To enable Plus, the app receives purchase information from Google Play: the product, the purchase status and a purchase token used to acknowledge the purchase. Remika sends the token back to Google Play to acknowledge the purchase. The local cache stores only the purchase type and the date of the last check. Google Play handles the payment under Google's privacy policy.
• On iOS: payments are handled by Apple through the App Store. We do not receive your Apple Account details. The app asks the App Store (StoreKit) on your iPhone about your purchases of Remika Plus: the product, the purchase status, the expiry or cancellation date and whether the purchase is a test purchase. The app checks the answer on the iPhone with StoreKit's own verification. The local cache stores only the purchase type, the expiry date of a subscription, the store environment and the date of the last check; no receipt or transaction code is stored. When you tap "Restore purchases", the app asks the App Store to synchronise your purchases. Apple handles the payment under Apple's privacy policy and the Apple Standard EULA.

3.8 Protecting the trial period

When the app starts, it sends a device code, the trial start date and the installation token described in section 3.3 to our server. The server turns the device code into a pseudonymous hash (HMAC-SHA-256 with a server secret); this is not anonymous data. The trial record stores only this hash, the start date and the expiry date calculated from it: no raw device code, IP address or content from your reminders or notes.

• On Android: the device code is the Android device identifier (ANDROID_ID).
• On iOS: the device code is a random code that the app creates itself and keeps in the iOS Keychain. It is not derived from your iPhone, your Apple Account, the advertising identifier or the vendor identifier. The Keychain remark in section 3.3 applies to it as well.

You cannot delete this record from inside the app. You can ask us to delete it by writing to privacy@remika.app; section 9 explains what we can and cannot find.

The purpose is to prevent a reinstall from restarting the trial. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest in preventing abuse of the trial. The record is kept for the 60-day trial and a further 365 days, then removed by the nightly clean-up. It is not shared with third parties for their own purposes; our hosting provider Cloudflare processes it on our behalf. The technical processing of IP addresses described in section 3.4 also applies to this connection.

4. App permissions

On Android:

• Microphone: for dictation and voice notes, only when you tap.
• Camera: to attach a photo to a reminder or note, only when you tap. Photos stay on the device.
• Photos and media: so that a photo taken with the camera is also saved to the gallery.
• Calendar (read only): only if you start the import from the phone's calendar (section 2).
• Notifications and exact alarms: so reminders arrive on time. No data is transmitted.

On iOS:

• Microphone: for dictation and voice notes, only when you tap.
• Speech Recognition: so that iOS can turn your dictation into text (section 3.1).
• Camera: to attach a photo to a reminder or note, only when you tap. Photos stay on the device.
• Photos: Remika asks only for permission to add to your Photos library, so that a photo taken with the camera is also saved there. Choosing a photo from your library uses the iOS photo picker and gives Remika only the photo you choose.
• Calendars: only if you start the import from the iPhone's calendar (section 2).
• Notifications: so reminders arrive on time. No data is transmitted.

On both: reminders are scheduled on the device as local notifications, and Remika does not use push notifications from a server. Remika does not ask for your location, your contacts or the advertising identifier, and it does not track you across other companies' apps or websites.

5. Transfers outside the EU

Cloudflare, Inc. and Google LLC are based in the USA. Both are certified under the EU-US Data Privacy Framework; transfers rely on the European Commission's adequacy decision (Art. 45 GDPR). On iOS, Apple processes dictation (section 3.1) and payments (section 3.7) under its own privacy policy.

6. Emailing us

If you write to us, we process your address and message to reply. Mail to remika.app addresses is forwarded via Cloudflare Email Routing to our mailbox at WEB.DE (1&1 Mail & Media GmbH, Germany). We delete correspondence once it is resolved and no legal retention duty applies. Legal basis: Art. 6(1)(b) or (f) GDPR.

7. This website

remika.app is served by Cloudflare (Cloudflare, Inc., USA), which processes technically necessary connection data such as the IP address. The website sets no cookies, loads no external fonts and uses no analytics.

8. Children

Remika is intended for adults aged 18 and over, in Google Play and in the App Store. The AI interpretation described in section 3.2 is provided by Google under terms that require its users to be at least 18 years old and that do not permit services directed at people under 18.

9. Your rights

You have the right of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR). These rights also apply to the pseudonymous trial record described in section 3.8. Because we keep no accounts, we cannot identify the installation record in section 3.3 or the trial record from your name or email address alone; the data on your device is under your own control. Questions: privacy@remika.app.

In practice. Write to privacy@remika.app. What our server keeps is tied only to codes: the installation identifier (section 3.3), the counters described in section 3.4 and the hash of the device code in the trial record (section 3.8). The app does not show any of these codes anywhere, neither in the settings nor on an about page nor in a prepared email, and you cannot read them yourself; the Android device identifier from which the trial record is derived is, in addition, specific to Remika's signing key, so other tools do not show it either. For that reason we generally cannot find your records from your name or email address. In that situation Art. 11 GDPR applies: we are not obliged to collect further data merely to identify you, and Art. 15–20 GDPR apply only if you provide additional information that enables us to identify the records (Art. 11(2) GDPR); if you have such information, send it to us and we will use it to find and delete the records. Regardless of requests, nothing on our server is kept indefinitely: the installation record is deleted 400 days after its last use, the request counters after 2 minutes to 2 days, and the trial record 60 + 365 days after the start of the trial; the deletion runs in the nightly clean-up (sections 3.3, 3.4, 3.8). The data on your device you can delete yourself by uninstalling the app (with the exceptions in section 2).

You may lodge a complaint with a data protection supervisory authority, for example the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (ldi.nrw.de).

10. Changes

When the app changes, we update this policy. The version published here applies. In case of doubt the German version (Datenschutzerklärung) prevails.