Rymind app icon
Rymind Premium reminders and tasks for Android
Privacy Policy

Privacy Policy

Rymind is built around dependable reminders, calm task follow-through, and respectful data handling. This page explains what the app stores, what optional services are involved, and the choices you keep.

Last updated: April 27, 2026
Package: com.avora.planner
Optional Android sync
Optional Remove ads purchase
1

Information the app handles

Rymind stores reminder titles, notes, task names, checklist items, reminder dates and times, repeat settings, completion state, app appearance settings, and app language settings on the device so the app can function.

If you use the optional "Call someone" reminder feature, Rymind opens Android's system contact picker. Rymind does not request broad contacts access. Rymind only receives the contact name and phone number that you explicitly choose through the picker.

If you share text or an image into Rymind, the app handles only the content you explicitly share. Shared images may be processed on-device with text recognition so Rymind can extract text and prepare a reminder draft. Shared content is used only to create or prefill reminder or task content for you.

Rymind does not require account sign-in for normal use.

If you choose optional Google sign-in and sync, signing in remains optional. On first connection, Rymind may ask how you want to link the local data already on this phone with the data already stored in your Google account. Signed-in phones may sync reminders, tasks, checklist items, repeat and completion state, deletion state, and limited sync metadata such as stable item IDs, ordering timestamps, install identifiers, and sync enrollment state needed to keep changes ordered and reduce unintended overwrites. Device-local delivery diagnostics, widget prompt state, engagement streaks and milestone state, theme and language preferences, and Android permission state remain local to the device.

If you choose the optional Remove ads purchase, Rymind may handle Google Play purchase status, purchase tokens, order IDs, product IDs, verification timestamps, cached entitlement state, and a hashed purchase-token reference needed to restore the purchase and confirm whether ads should stay removed. This flow does not include your reminder, task, checklist, contact-selection, or shared-content text.

2

How information is used

Rymind uses your reminder, task, checklist, contact-selection, and shared-content data only to provide core app features such as:

  • Showing reminders and tasks inside the app
  • Scheduling alerts and lock-screen alarm experiences
  • Reopening the phone dialer for call reminders
  • Restoring your information after device reboot
  • Applying your selected theme and language preferences
  • Preparing reminder drafts from text or images you explicitly share with the app
  • Exporting or importing backup files of reminders, tasks, and checklist items
  • Syncing signed-in reminder and task data across your Android devices when sync is enabled
3

Data sharing and third-party services

Rymind does not sell your personal information.

Rymind does not sell your reminders, tasks, checklist items, selected contact information, or shared-content payloads.

Rymind may include Google Mobile Ads SDK and Google's User Messaging Platform in builds that show ads on selected app surfaces, including Today, Upcoming, Calendar, and a footer area in Settings. These services can help request consent where required, serve ads, measure ad performance, and manage privacy options. They do not receive your reminder titles, notes, checklist text, selected contact names, phone numbers, or shared text or image payloads for ad requests from Rymind.

If you choose optional Google sign-in and sync, reminder, task, and checklist data needed for sync is stored in Firebase services under your signed-in account so it can sync across your Android devices. This data is not used for advertising.

If sync or its backend rollout controls are active, Firebase App Check and Firebase Remote Config may process app-instance, device-integrity, or rollout-configuration metadata to protect backend access and control release rollout. These systems are used for security and release control, not advertising, and do not receive your reminder, task, checklist, contact-selection, or shared-content text as configuration values.

If you choose the optional Remove ads purchase, Google Play Billing may process purchase, restore, order, and payment-state metadata needed to complete the transaction and restore it on your other Android devices that use the same Play account. Rymind may verify purchase state through Firebase Functions and the Google Play Developer API, and may keep admin-only billing audit records that do not include your reminder or task content.

Rymind may include Firebase Analytics in release builds to collect limited product-usage analytics for activation, retention, reminder follow-through, widget adoption, sync health, and share-capture measurement. These analytics are limited to operational metadata such as event names, counts, repeat usage, widget type, permission state, sync state, share-import type, and similar product-flow signals. Rymind does not send reminder titles, notes, checklist text, selected contact names, phone numbers, or shared text or image payloads through product analytics.

Rymind may include Firebase Crashlytics in release builds to collect crash reports and technical stability diagnostics, such as stack traces, app version, device and Android version, enabled reminder-delivery access state, and limited operational breadcrumbs about reminder, backup, and sync actions. Rymind does not send reminder titles, notes, checklist text, selected contact names, phone numbers, or shared text or image payloads through crash diagnostics.

If ads are enabled in a shipped build, Google ad services may process consent status, app and device metadata, advertising or app-instance identifiers, network context, and ad interaction signals needed to request, deliver, measure, or limit ads. This ad-related processing is controlled by Google services and applicable regional consent requirements, not by your reminder or task content.

Release telemetry is limited to product health and operational measurement. User-authored reminder content is intentionally excluded from analytics and crash diagnostics.
4

Data storage and retention

Your reminder and task data is stored locally on your device in the app's private storage.

If you export a backup, the backup file is written only to the device or storage location you choose through Android's file picker.

If you enable sync, a synced copy of reminders, tasks, checklist items, repeat settings, completion state, deletion state, and the limited sync-ordering metadata needed to keep signed-in devices consistent may also be stored in Firebase Cloud Firestore under your account.

Rymind does not operate a custom developer server for your reminder or task content in the current app implementation.

If crash diagnostics are enabled in a release build, technical crash-report data may be processed by Firebase Crashlytics for stability monitoring.

If product analytics are enabled in a release build, limited usage analytics may be processed by Firebase Analytics to help measure app activation, retention, follow-through, and feature adoption.

If ads are enabled in a release build, ad-request and consent-related metadata may also be processed by Google ad services to support ad delivery and privacy compliance. Those ad surfaces may still appear on their supported screens even when there is little or no reminder or task content visible.

If you use Remove ads, limited purchase-verification metadata and cached entitlement state may also be stored locally so Rymind can restore the ad-free state calmly on startup and re-check it when the app returns to the foreground. Admin-only billing verification records may also be stored in Firebase for audit and refund or revoke handling.

Data remains on your device until you edit it, delete it, clear the app's data, restore a replacement backup, or uninstall the app. If sync is enabled, synced cloud copies may remain until the corresponding items are deleted through sync or the account or provider data is removed.

5

Permissions and device capabilities

Rymind may request or rely on the following Android permissions and capabilities:

  • Notifications, to deliver reminder alerts
  • Exact alarms, to trigger reminders at the scheduled time
  • Full-screen intent, to present alarm UI when appropriate
  • Wake lock and boot completed support, to reschedule and deliver alarms reliably after restart
  • Network access and network-state detection, when optional sync and release telemetry features are available
  • Ad and consent services, when ads are enabled in the shipped build

Rymind does not request READ_CONTACTS or CALL_PHONE. Contact selection uses the Android system picker, and calling uses the system dialer.

6

Your choices

You can:

  • Use Rymind without signing in
  • Delete reminders and tasks from within the app
  • Connect Google and choose how to link local and cloud data, or cancel and stay local-only
  • Export a backup file and restore a backup after reviewing the restore preview
  • Disable or deny notification and alarm-related access in Android settings
  • Sign out of sync while keeping local device data
  • Buy Remove ads as a one-time purchase or restore it later through the same Google Play account
  • Review ad privacy options when they are required for your region and shown in the app
  • Clear app data or uninstall the app to remove locally stored data

Rymind does not currently provide a separate in-app toggle for release analytics or crash diagnostics when those services are enabled in the shipped build configuration.

7

Children's privacy

Rymind is not directed to children under the age required by applicable law in your region, and the app is not designed to knowingly collect personal information from children.

8

Changes to this policy

This policy may be updated to reflect product, legal, or platform changes. The latest version should also be published on the public privacy policy URL used for app distribution.

9

Contact

If you have questions about this policy, contact:

Rymind Support Privacy, sync, data handling, and policy questions
johjen.mathew@gmail.com