Privacy Policy

Effective date: September 4, 2026
Last updated: September 9, 2026

1. Overview

This Privacy Policy explains how Rhythm Apps ("Rhythm Apps", "we", "us" or "our") handles information in Rhythm Adaptive Calendar ("Rhythm" or the "App"). It applies to Android MVP version 1.0.4 and later versions unless a later policy states otherwise.

Rhythm is a calendar and time-planning app. Its current design is local-first: calendar information and Rhythm-specific planning data are processed on the device whenever possible. The current MVP does not require a Rhythm account.

2. Information and data the App may handle

2.1 Calendar information

If you grant calendar permission, Rhythm can read calendars made available through the Android Calendar Provider and can write or update calendar events when you ask it to. Depending on the events you use, this can include event titles, dates and times, all-day status, locations, descriptions or notes, recurrence information and the calendar/account to which an event belongs.

Rhythm uses this information to display your schedule, search events, calculate free time, detect conflicts, support Adaptive Day, show NOW/NEXT information and keep edits synchronized with the calendar provider you selected.

2.2 Rhythm-specific planning data

The App may store information you enter or generate for Rhythm features, including tasks, priorities, flexible/fixed status, preparation and recovery time, travel estimates, distance and travel mode, reminders, Event Pack checklists, note fields, document names and local content references, completion status, actual start/end times when recorded, contact names or notes you choose to associate with events, Life Admin categories and expiry dates, display preferences and feature usage counters.

These data are stored locally in the App's private storage in the current MVP.

2.3 Location

Rhythm may request approximate or precise location permission when you use live Travel Intelligence. Rhythm reads the device's current location only when you request a live travel estimate. The App sends the current coordinates and event destination securely to the Rhythm serverless routing proxy, which forwards the request to Google Routes API and returns duration and distance. The proxy does not intentionally store coordinates or destinations, and Rhythm does not persist your current device coordinates.

The live route result is used to calculate travel and Leave by information for the current App session. Rhythm does not intentionally persist Google Maps Routes content as permanent calendar data. A separate manual/offline travel buffer can be stored locally when you choose to use it.

Google processes live routing requests under the Google Maps Platform Terms and Google Privacy Policy.

2.4 Notifications and alarms

If you allow notifications, Rhythm can create local notifications for events and leave-by reminders. The App may also request permission to schedule exact alarms where Android requires it so that time-sensitive reminders can be delivered more accurately. These permissions are used for reminder functionality, not for advertising or tracking.

2.5 Purchases and subscriptions

Paid plans and one-time purchases are processed through Google Play Billing. The App sends a Google Play purchase token, package name and product identifier to the Rhythm serverless service, which verifies them with Google Play Developer API. Google Play lifecycle notifications may also be processed to validate renewals, cancellations, expiry, refunds and revocations. Rhythm Apps does not receive or store your full payment card details through the App.

2.6 Technical and analytics data

MVP 1.0.4 does not include advertising SDKs or third-party analytics SDKs, and the serverless functions do not collect product analytics. We do not use the App to build advertising profiles or sell usage data.

3. Android permissions

Depending on the features you use, Rhythm may request the following Android permissions:

• Read calendar: to display and work with calendars available through Android.
• Write calendar: to create, update or delete calendar events when you request those actions.
• Notifications: to show event and leave-by reminders.
• Exact alarms: to support time-sensitive reminders where permitted by Android.
• Device location: when you request a live travel estimate. Current coordinates and the event destination are transmitted to Google Routes API for routing. Rhythm does not persist the current device coordinates.

You can deny or revoke permissions through Android settings. Some features may then become unavailable, but the rest of the App should continue to work where technically possible.

4. When information may leave your device

The Rhythm serverless service does not receive your calendar or Rhythm planning database in MVP 1.0.4. Information can leave your device in these limited situations:

• Your calendar provider: if an event belongs to a synchronized account such as Google Calendar or another provider, edits made through Android Calendar Provider can be synchronized by that provider under its own privacy terms.
• Rhythm routing proxy and Google Routes: when you request a live travel estimate, current coordinates and the event destination are transmitted through our serverless proxy to Google Maps Platform. The proxy returns only route duration and distance and is not designed to retain the request.
• Rhythm billing verification and Google Play: purchase tokens and product identifiers are transmitted to our serverless service and Google Play Developer API to verify entitlements and process subscription lifecycle events.
• Android backup and device transfer: if backup or device-transfer features are enabled on your device/account, Android may include Rhythm's local database and settings in a device backup or transfer. Rhythm Apps does not operate that backup service.
• Content you intentionally share: information leaves the App if you choose to export, copy or share it using Android or another application.

Rhythm Apps does not sell personal data and does not share personal data with advertisers in the MVP.

5. Local storage and security

Rhythm-specific data are stored in the App's private Android storage, including a local Room database and app preference storage. Android's application sandbox and the security controls of your device help protect this data from other apps.

The local Rhythm database is not separately encrypted by a Rhythm-specific encryption layer in MVP 1.0.4. You should protect your device with an appropriate screen lock and keep Android security updates current.

6. Retention and deletion

Rhythm has no cloud account and the serverless service does not hold a copy of your calendar or local planning database. Routing requests are processed transiently. Operational cloud logs may retain limited request metadata and errors for security and reliability according to the configured Google Cloud retention period; application logs are designed not to contain coordinates, destinations or purchase tokens.

• Rhythm-specific local data remain on your device until you edit/delete them, clear the App's data or uninstall the App, subject to Android backup/restore behavior.
• Calendar events written to a connected calendar remain with that calendar provider until they are deleted there, and may be synchronized across your devices by that provider.
• Android backup copies may be retained according to your device, Google account or backup-provider settings.
• Google Play retains billing and transaction records according to Google's own legal and retention obligations.

If Rhythm later introduces user accounts or a Rhythm cloud service, we will add an appropriate account and server-data deletion mechanism before launch of those features.

7. Your choices

You control whether to grant Android permissions, which calendars are visible, what information you enter into Rhythm, and whether to purchase paid features. You can change Android permissions from your device settings and can manage Google Play subscriptions through Google Play.

8. Children

Rhythm is a general productivity application and is not directed specifically to children under 13. We do not knowingly operate a service in the MVP that collects children's information into a Rhythm Apps backend.

9. International use

Rhythm can be used in different countries. Because the MVP does not operate a Rhythm cloud backend for calendar data, the main transfers relevant to the App arise from services you choose to use, such as your calendar provider, Google Play or Android backup.

10. Changes to this Privacy Policy

We may update this Privacy Policy when Rhythm's features, data practices, third-party integrations or legal requirements change. The current version will be published on this page with an updated effective or revision date. Material changes that require new permission or consent will also be presented in the App where required.

11. Contact

Rhythm Adaptive Calendar is created by Rhythm Apps.

For privacy questions or requests, contact: privacy@rhythmcalendar.com
For general support: support@rhythmcalendar.com

If these addresses change, the current contact details will be published on the Support page.