Privacy

Practice is personal.

KalaPanion is built to support a music practice, not to turn that practice into content. This notice explains what the current beta stores on your device, what leaves it, and when you make that choice.

Effective August 30, 2026KalaPanion 1.0 beta

The short version

Your practice stays local

Recordings, reflections, marked moments, and musical context are stored on your device. They are not uploaded to KalaPanion analytics.

Beta analytics is bounded

Amplitude receives a random installation identifier and a small set of product events used to understand whether the core Practice flow works.

Sharing is your action

Audio leaves the app only when you use an export or share action and choose a destination through your operating system.

Information the beta handles

Google sign-in

Google sign-in is required. After you sign in, KalaPanion stores the Google user identifier, name, email address, and available profile photo in local app storage so it can restore your access. KalaPanion does not use your Google password.

Practice data on your device

Your SQLite practice history, audio recordings, reflections and Journal text, Sankalp, musical selections, zones, marker details, and related settings are local-first. KalaPanion does not currently provide cloud backup or cross-device sync for this material.

Beta usage analytics

On approved TestFlight and Google Play beta builds, Amplitude analytics is on by default. It uses a random identifier created for that app installation. The identifier is not derived from your Google account, email address, advertising ID, or hardware identity.

The allowed events cover a bounded core Practice funnel: app session, intentional Practice start, Aumkaar exit, recording start, Practice finish and save, playback start, and curated recoverable errors. They may include app version, build, release channel, coarse platform and operating-system major version, coarse duration buckets, and bounded outcome codes.

Not sent to analytics

Names, email addresses, Google identifiers, audio, recordings, reflections, Journal text, Sankalp text, Raag, Taal, zones, markers, filenames, file paths, precise location, advertising identifiers, contacts, notifications, credentials, screen replay, and free-form logs are excluded.

KalaPanion does not use Firebase Analytics or a second product analytics service. Analytics is used for aggregate beta reliability and core-flow learning, not advertising, scoring your music, or building a profile of your musical practice.

When you choose to send something

Share and export

If you choose Export Full Recording or Trim & Share, KalaPanion prepares the selected audio and opens the operating system share interface. The destination you choose—such as Files, AirDrop, or another app—then handles that file under its own privacy terms.

Optional MKSM submission

MKSM submission is a separate, optional feature. If you enable it, enter the requested details, and choose to submit after Practice, KalaPanion sends a Google Form response containing your MKSM number, first and last name, email address, batch name, practice date, minutes practiced, available Raag/Taal/practice context, and the optional one-word close.

This Google Form flow is not analytics. Google and the form owner handle a submitted response under their own access and retention practices. No MKSM submission is sent unless the feature is configured and you invoke the submission action.

Retention and your controls

Signing out removes the cached Google sign-in profile from KalaPanion. It does not delete your device-local practice history.
Device-local practice data remains in the app sandbox until it is removed through an available app or device control, or the app is removed. Operating-system backups or previously exported copies may follow separate retention rules.
Raw Amplitude beta events are retained for no more than 90 days under KalaPanion's operating policy. Aggregate, non-raw beta summaries may be retained for up to 13 months.
A Google Form response submitted to MKSM follows Google's and the form owner's retention practices. KalaPanion has not verified a fixed deletion period for that external destination.

You can review or remove KalaPanion's connection from your Google Account settings. Removing that connection does not erase data already stored locally in the app or previously submitted to another destination.

You may contact us to ask about access, correction, or deletion. The analytics identifier is deliberately not linked to your email or Google profile, so an email address alone cannot reliably locate an individual installation's anonymous events. This is a current beta limitation; the 90-day raw-event limit still applies.

Providers and security

KalaPanion uses Google for sign-in and the optional MKSM Google Form, and Amplitude as the beta analytics processor. External connections use HTTPS. The Amplitude beta project is hosted in the United States. These providers may process information under their own terms and in the locations described in their notices.

KalaPanion does not sell personal information, serve advertising, or use these beta analytics events for cross-company tracking. No storage or transmission method is perfectly secure, but the beta is designed to minimize what leaves the device in the first place.

Contact and changes

Questions or privacy requests can be sent to [email protected]. Depending on where you live, applicable law may provide privacy rights; requests will be handled according to the law that applies.

This notice may change as KalaPanion changes. Material changes will be reflected on this page with a new effective date. Future features are not covered as current behavior until they are actually released and this notice is updated.