Privacy Policy

Your practice journal, cycles and goals are stored on your device. File exports and restores use the system file picker, at your request. GrooveLog does not send practice records to a developer server. On iOS, purchases are managed by Apple.

Android: Google Play purchases and diagnostics

On Android, Google Play processes purchases and restoration. When you choose Restore purchases or complete a purchase, GrooveLog verifies the signed subscription receipt through its shared verification service hosted on Cloudflare, which checks it with Google Play. The receipt contains the app identity, product, purchase token and transaction attributes, such as the order reference, time and state when provided by Google Play; practice records are not included. Opening or returning to the app does not send this receipt to the developer. A lifetime purchase is verified locally; its token is sent to Google Play when confirming the transaction. The developer does not receive your payment card details. A private copy of a production verification response can be reused on your device for at most one minute to handle an immediate restart, within the subscription’s expiry. An expired copy is discarded when checked again; it can remain in local app storage until then or until you remove the app’s data. The raw receipt and token are not stored in this copy. Test responses stay in memory. The verification service does not store receipts in an application database; the hosting provider can process connection metadata, including the source IP address.

The Google Play Billing library also sends technical diagnostics to Google over HTTPS when Billing is used, including at app startup. These diagnostics concern billing operations, response codes and durations, together with Android and app versions, device model and system build, language, network context and timestamps. They help assess billing reliability. There is no GrooveLog setting to disable this SDK diagnostic flow, which can operate even when purchases are unavailable. Practice journal entries are not sent through this flow. Google can see the source IP address of the connection; its server-side use and retention are governed by Google.

GrooveLog cannot delete purchase records or SDK diagnostics held by Google from inside the app. These Android Billing flows do not apply to the iOS app. The support form below is a separate, optional web service.

The optional support form sends the app name, support subject, chosen category, reply email address, any app and operating-system versions you enter, your message, and an anti-spam field to Cloudflare Workers for validation. The request is then forwarded to the developer’s support inbox. Grok Bot, an automated assistant used by the publisher, reads inbox messages to sort requests and prepare or send replies. This information is used to respond to your request and maintain the app, not for advertising.

The developer uses a support submission only to route, investigate and answer your request, handle a privacy request, and protect the support channel against abuse. The developer does not sell the submission, use it for advertising, or build a profile about you.

The developer keeps a support submission only as long as reasonably necessary to resolve and follow up on the request and to meet applicable legal or security obligations, then deletes it or removes information that identifies you. There is no single fixed period because those needs differ by request. You may request access to, correction of, or deletion of a support submission by using the same form and choosing the Privacy category. A request may be limited where retention is required by law or needed to establish, exercise, or defend legal claims.