This policy applies to the LoopBright Android app (app.loopbright.android) and this website.
Contact & feedback
Questions, bugs or ideas for LoopBright? Reach us using the contact details in the legal notice. For a bug, briefly describe what happened. Please do not send passwords or payment details.
1. Controller
The controller is Martin Nahrwold. The postal address and contact details are in the legal notice.
2. Data in the app
LoopBright keeps the screen on at your request and offers a timer, dimming, widgets and games. It has no separate app account, advertising or usage analytics of its own. It does not access the camera, microphone, contacts or location.
Local storage holds keep-awake state, settings, timers, trial progress, game progress, best scores, Pro status and the last purchase-status check. Dimming saves the previous brightness and automatic mode for restoration. Protected activation also stores local activation and security data. These app data are not sent to a server of our own.
Notifications and a foreground service support the keep-awake mode you start. Optional Pro dimming needs Android permission to modify system settings. Any personal data processed for these requested functions are covered by Article 6(1)(b) GDPR.
Data stay in protected app storage until changed or deleted; cloud backup and device transfer are disabled. Android app settings or uninstalling remove local data. Turn keep-awake off first so brightness can be restored. A Play purchase and Google's purchase history remain unaffected.
3. Google Play: purchases and diagnostics
The optional Pro activation is a one-time Google Play purchase. Google processes account and payment data; LoopBright does not receive credit card details or banking credentials. To check, acknowledge and restore purchases, the app processes product identifiers, purchase status and purchase tokens. Our app logic does not store purchase tokens persistently or use a purchase-verification server of our own.
Purchase status can be checked when the app starts.
The Google Play billing library can send technical diagnostics to Google, even without a new purchase:
- app, library and Android versions, plus device, hardware and memory characteristics;
- language, region, time zone, network type and mobile network operator code, where available;
- billing events, error codes and random session and operation identifiers.
Connections also transmit the IP address. Diagnostics support operation and troubleshooting of billing. LoopBright has no separate switch to disable them, and they can be buffered locally until transmission or cleanup.
Where we process personal data for these purposes, purchases and activation are based on Article 6(1)(b) GDPR; necessary technical troubleshooting is based on our legitimate interest in reliable billing under Article 6(1)(f). For Google's processing and retention periods, see Google's privacy policy and data retention information.
4. Website and hosting
This website uses Google's Firebase Hosting. When a page is requested, the service processes connection data, particularly IP addresses, to deliver the website, detect abuse and analyse service usage. Google states that IP data is retained for a few months.
The website itself uses no cookies or browser storage and contains no analytics or advertising scripts, external fonts or embedded social-media content. Connections use HTTPS. Firebase Hosting for this website does not receive local app game progress.
The legal basis is our legitimate interest in a secure, accessible website under Article 6(1)(f) GDPR. See Firebase privacy information and the data processing terms.
5. Contact enquiries
When you email us, we process your sender address, message and any attachments through our email provider to handle the enquiry. The basis is Article 6(1)(b) GDPR for contractual matters, or our legitimate interest in responding under Article 6(1)(f) for other enquiries.
Correspondence is retained for as long as needed to handle and document resolution of the enquiry. Statutory retention duties remain applicable under Article 6(1)(c) GDPR.
6. Service providers and international processing
Recipients are the Google services described above and our email provider. Google can use affiliated companies and other service providers. The linked data processing terms apply to Firebase.
Google may process data outside the European Economic Area, particularly in the United States. Google describes safeguards including the EU-US Data Privacy Framework and, where applicable, Standard Contractual Clauses. Details are available in Google's data transfer information and the Firebase terms.
7. Your rights
Subject to the applicable legal conditions, you have rights of access, rectification, erasure, restriction of processing and data portability.
Right to object: You can object to processing based on legitimate interests on grounds relating to your particular situation.
You can complain to a data protection supervisory authority, for example where you live or work. For privacy enquiries, use the contact details in the legal notice.