Privacy Policy
Effective: September 29, 2026
LoFi Studio does not sell personal data, serve behavioral ads, or track you across other companies' apps and websites. Current iOS versions and Android release builds collect limited, pseudonymous product events to keep playback reliable and improve the app. Those events can be associated with the same app installation over time.
LoFi Studio is operated by Calexis Labs OÜ. For privacy questions, use the in-app Feedback screen or email hello@calexislabs.com.
Data collected by the mobile apps
- Product interaction: app opens, catalog loading, playlist views, playback starts and failures, completed focus sessions, favorites, sleep timer use, and purchase-flow status.
- Device identifier: a random installation UUID created by LoFi Studio on each device. It is not an Apple or Google advertising identifier or hardware serial number, is not tied to an account, and is removed when the app is deleted.
- Diagnostics: normalized error categories such as offline, timeout, or playback failure. We do not transmit free-form error messages or signed media URLs.
- Support purchase activity: on iOS, the StoreKit product identifier and whether a purchase was verified, cancelled, pending, or failed; on Android, the Google Play product identifier and whether a purchase was started, completed, cancelled, pending, or failed. The Android supporter badge is stored on the device. Apple and Google Play process payments; LoFi Studio does not receive payment-card information.
- Feedback you choose to send: the message and email address entered in the in-app Feedback screen. This information is used only to respond to and resolve your request.
- Context: app version, build number, platform, locale, and event time.
Data we intentionally do not collect
The app has no user account. Analytics events do not contain your name, email address, contacts, precise location, raw search terms, listening URLs, advertising identifier, or the content of feedback messages. If you submit feedback, its email and message are stored separately from pseudonymous analytics.
On Android, favorites, focus-session state, sleep-timer state, and time-of-day listening preferences are kept on your device. The listening preferences are not sent as a listening-history list to Supabase; the app separately sends the limited playback events described above. Android debug builds do not send product analytics.
How we use data
We use this limited data for app analytics and functionality: measuring activation and retention, finding broken catalog or playback flows, understanding which features are useful, and confirming that voluntary support purchases work.
Service providers
Analytics and application data are processed using Supabase infrastructure; public artwork and private, time-limited audio delivery use Cloudflare. iOS purchases are processed by Apple through StoreKit; Android support purchases are processed by Google Play Billing. The website uses Cloudflare for delivery, security, uptime, and aggregate Web Analytics. These providers process data under their own terms and privacy commitments.
Retention and security
Product analytics are retained only as long as reasonably needed for trend and reliability analysis. Access to raw analytics is restricted to LoFi Studio administrators. The public app can submit validated events but cannot read the analytics table.
Your choices
You may stop analytics collection by deleting the app. This removes the random installation identifier stored on the device. You may request deletion of feedback you submitted by contacting us through the in-app Feedback screen or at hello@calexislabs.com. Because analytics are not linked to an account or contact detail, we may be unable to identify a specific installation's records from a name or email address alone.
Children
LoFi Studio is not designed to collect personal information from children. We do not knowingly collect names, contact details, or precise location from children.
Changes
We may update this policy when the product or its data practices change. The effective date above will be revised when we do.