Privacy policy

This Privacy Policy explains how the Android app Loop and its related support and privacy website handle information. Loop is an interval timer for workouts, study sessions, focus sessions, and everyday routines.

The short version is: Loop works offline, does not require an account, and does not send timer data, presets, settings, or usage analytics to the developer or to analytics services. Information leaves the device only when a user chooses to contact the developer, opens an external website, uses Google Play’s rating and review functions, or uses another device-level function controlled by Android.

1. Controller and contact details

The controller responsible for processing personal data described in this Privacy Policy is:

Tom Vogel
Am Silberberg 47
01454 Radeberg
Germany

Email: tom.vogel.dev@gmail.com

No data protection officer has been appointed because there is currently no legal requirement to appoint one.

2. Information processed locally by the app

Loop stores and processes the following information locally on the user’s device so that the app can provide its timer and customization features:

the selected active duration and rest duration;
the selected number of sets;
user-created presets, including the preset name, selected icon, active duration, rest duration, and number of sets;
a locally generated technical identifier for each preset;
whether onboarding has been completed;
preferences for keeping the display active, picture-in-picture mode, haptic feedback, and sounds;
theme, accent color, custom color, timer visualization, app icon, and app language selections;
a completed-loop counter and the dates of the first completed loop and the most recent review-request attempt, used only to limit how often Loop may request a Google Play review;
local storage schema versions used to read saved settings safely; and
the notification permission status and a local record indicating whether the notification permission has previously been requested.

While a timer is active, Loop also temporarily processes:

the current timer phase;
remaining and elapsed time;
the current set and completed intervals;
whether the timer is running, paused, or complete; and
elapsed active and rest time.

The live timer state is kept in memory by the app and its Android foreground service. It is not uploaded to a server. Temporary copies of the built-in timer sounds may be created in the app cache for playback. These sound files do not contain user information and may be removed automatically by Android.

Preset names are free text. Users should avoid entering personal or sensitive information in a preset name if they do not want that information stored on their device.

All processing in this section is performed on the user’s device to provide the app functions requested by the user. Where a legal basis is required, the processing is necessary to provide Loop and its requested functions under Article 6(1)(b) GDPR.

3. No collection by the developer or analytics services

Loop does not operate developer-controlled servers and does not transmit its locally stored timer data, presets, settings, or review-eligibility records to the developer or to analytics services. Except for the user-initiated Google Play review process described in Section 8, Loop does not collect or share the following through the app:

names, postal addresses, phone numbers, or dates of birth;
precise or approximate location;
contacts, calendar entries, photos, videos, or documents;
camera or microphone data;
health or fitness records;
advertising identifiers or persistent device identifiers;
app interaction statistics for analytics or profiling;
search history;
crash reports, diagnostics, or performance telemetry; or
browsing history.

The release version of Loop does not request the Android Internet permission for its own network operation. Opening a help page, this Privacy Policy, an email draft, or the Play Store transfers control to an external app or system function. The in-app review interface is provided and controlled by Google Play.

4. Local storage and cloud backups

Loop has no built-in cloud backup or cloud synchronization. Android cloud backup for Loop is disabled in the release build. The developer therefore does not use Google Drive or any other cloud service to back up presets, settings, or timer information.

On some Android versions or devices, Android may still offer a direct, user-initiated device-to-device transfer during device setup. Such a transfer is controlled by Android and the user, does not use Loop servers, and is not accessible to the developer.

Locally stored settings and presets remain on the device until the user resets them, clears Loop’s app storage, or uninstalls the app.

5. Android permissions and device features

Loop uses only Android permissions and device features needed for its visible functionality:

Notifications: to show the status of a timer that the user started;
Foreground service: to keep a user-started timer running in the background;
Wake lock: to help an active timer run reliably while the device would otherwise sleep;
Vibration: to provide optional haptic timer cues; and
Picture-in-picture: to keep the timer visible over other apps when the user enables this feature.

These permissions and features are not used for advertising, tracking, or profiling. Loop does not request access to location, contacts, external storage, the camera, or the microphone.

6. Accounts and synchronization

Loop does not provide:

user accounts or registration;
sign-in or social login;
developer-operated cloud storage;
cloud synchronization; or
developer-operated cross-device profiles.

Because no Loop account exists, there is no account data held by the developer and no account deletion process is required.

7. Analytics, crash reporting, advertising, and payments

The current version of Loop does not use Firebase, Firebase Analytics, Firebase Crashlytics, Google Analytics, Sentry, advertising SDKs, social media SDKs, or other telemetry services.

Loop currently contains no advertising, personalized advertising, in-app purchases, subscriptions, payment processing, or Loop Pro product.

Loop integrates the Google Play In-App Review interface described in Section 8. This interface is used only for voluntary Play Store ratings and reviews; it is not an analytics, advertising, or behavioral tracking service.

If a future version introduces accounts, cloud features, analytics, crash reporting, advertising, purchases, subscriptions, or other processing that changes the practices described here, this Privacy Policy will be updated before that functionality is made available.

8. Google Play ratings and reviews

After a user has completed at least three Loops and at least three days have passed since the first completed Loop, Loop may ask Google Play to display its standard in-app review interface. Loop limits its own requests to no more than one attempt every 30 days. Google Play applies an additional quota and decides whether the interface is actually displayed. Users may dismiss the interface without submitting anything.

Loop stores only the following review-eligibility information in its private local app storage:

the number of completed Loops;
the date and time of the first completed Loop; and
the date and time of the most recent review-request attempt.

These local records are used only to avoid excessive review requests. They are not sent to the developer, Google Analytics, or any other analytics service. The Google Play review API does not tell Loop whether a user has already submitted a review, how many stars were selected, whether the prompt was dismissed, or whether it was displayed. Consequently, Loop cannot reliably stop future requests based on whether a review was submitted; it can only apply the local 30-day interval.

Users may also select Rate Loop in the app settings. This opens Loop’s Google Play listing and does not use the quota-limited in-app review prompt.

If a user voluntarily submits a review, Google Play processes the selected star rating and any optional review text. Google states that this information is encrypted and is used to publish a review on Google Play. In a closed testing track, the submitted feedback is instead shared privately with the developer through Google Play. The developer may use submitted reviews to understand feedback, improve Loop, and respond where Google Play provides that functionality. The legal basis for the local request-limiting process and the developer’s use of received feedback is Article 6(1)(f) GDPR, based on the legitimate interests of improving Loop and communicating with users. The user decides whether to submit a rating or review.

Review content and related Google Play account or technical information are processed by Google under Google’s own terms and privacy policy. Google may process information outside the European Economic Area using the safeguards described in its privacy documentation. Loop does not create a separate copy of reviews outside the facilities provided by Google Play.

Google controls the retention of submitted reviews. Users can manage or delete their reviews using Google Play or their Google Account. More information is available in the Google Play In-App Reviews documentation and the Google Privacy Policy.

9. Voluntary bug reports and support emails

When a user selects Report a bug, Loop prepares an editable email draft in the user’s external email app. The draft includes:

the Loop version and build number;
the device’s Android version; and
a space for the user to describe the issue.

Loop does not send the email automatically. The user can edit or remove any information, add attachments, or cancel the message. Information is sent only after the user deliberately sends the email using the external email app.

If the user contacts the developer, the following information may be processed:

the sender’s email address and any name shown by the email service;
the subject, message, attachments, and other information the user chooses to provide;
the Loop version and build number; and
the Android version, if it remains in the message.

This information is used only to respond to the request, provide support, investigate reported problems, and protect or establish legal rights. The legal basis is Article 6(1)(b) GDPR when the communication concerns use of the app, and Article 6(1)(f) GDPR for the legitimate interests of responding to users, fixing problems, and securing the app. If retention is required by law, Article 6(1)(c) GDPR also applies.

Support and bug-report emails are deleted no later than 12 months after the matter has been closed, unless a longer period is required by law or is necessary to establish, exercise, or defend legal claims.

The receiving mailbox is a standard Gmail account provided by Google. The user’s own email provider and Google process the email and related technical data when the message is sent and delivered. Google may process information outside the European Economic Area. Information about Google’s processing, retention, and international transfer safeguards is available in the Google Privacy Policy.

10. Website hosting through Cloudflare Pages

The website on which this Privacy Policy and Loop support information are published is a static Astro website hosted through Cloudflare Pages. Cloudflare Web Analytics is disabled. The website operator does not use analytics scripts, advertising trackers, contact forms, or analytics and advertising cookies.

When a visitor opens the website, Cloudflare must process technical connection information to deliver and protect the site. Depending on the request, this may include:

the visitor’s IP address;
the requested hostname, path, and URL;
date and time of the request;
browser, operating system, language, and system configuration information;
routing and traffic information; and
information needed to detect and prevent malicious traffic.

This processing is necessary for the legitimate interests of providing a secure, reliable, and globally available website under Article 6(1)(f) GDPR. The website operator does not create or export separate visitor profiles from these connection records.

Cloudflare may set strictly necessary security cookies when a security, rate-limiting, or challenge function is triggered. These cookies are used to deliver and protect the website, not for advertising or cross-site tracking. Their use and duration depend on the security function involved. The website itself does not set optional cookies.

Cloudflare retains personal information for as long as needed for the service, security, and legal purposes described in its policy. The exact period depends on the type, purpose, sensitivity, and legal requirements of the information. The website operator does not determine a longer independent retention period for Cloudflare’s technical records.

Cloudflare may process data in the United States and other countries. For transfers from the European Economic Area, Cloudflare states that it relies on the EU-U.S. Data Privacy Framework and, where necessary, the European Commission’s Standard Contractual Clauses.

Cloudflare provider details:

Cloudflare, Inc.
101 Townsend Street
San Francisco, CA 94107
United States

More information is available in the Cloudflare Privacy Policy and the Cloudflare Cookie documentation.

11. Distribution through Google Play

Loop is distributed through Google Play. Google may independently process information relating to a user’s Google account, device, store activity, download, installation, security checks, ratings and reviews, and use of Google Play. This processing is controlled by Google and is not part of developer-operated analytics or server collection. The specific review process initiated from Loop is described in Section 8. More information is available in the Google Privacy Policy.

12. Retention and deletion of local information

Users can remove their user-created information in the following ways:

In Loop: Open Settings > Data > Reset local data. This removes all user-created presets, restores timer inputs and app settings to their defaults, deletes the locally stored review-eligibility records, restores the standard app icon, and causes onboarding to be shown again.
In Android: Open the Android app settings for Loop and select the option to clear storage or app data. The exact name and location of this option varies by device. This removes the app’s local preferences, cache, and other local app data.
Uninstall Loop: Uninstalling the app removes its local app storage from the device.

Android controls notification permissions and related system settings. Resetting data inside Loop does not necessarily reset the permission decision stored by Android. Users can review or change notification permissions in the Android system settings.

An active timer state is removed when the timer is stopped or the applicable app process and service end. Temporary cache files may also be removed by Android automatically.

Because the developer does not receive the local timer data, presets, or settings, the developer cannot view or remotely delete them.

Submitted Google Play reviews are not deleted by resetting or uninstalling Loop. Users can manage or delete those reviews through Google Play or their Google Account as described in Section 8.

13. Security

Local information is stored in Loop’s private app storage, which is protected by Android’s application sandbox under normal operating conditions. Loop does not separately encrypt its local preferences. Users should protect their device with a PIN, password, or comparable screen lock and install operating system security updates.

Connections to the support and privacy website use HTTPS. Email transport and storage security depend on the email providers used by the sender and the developer. No method of storage or transmission can be guaranteed to be completely secure.

14. No automated decision-making or profiling

Loop does not use personal data for profiling or automated decisions that produce legal or similarly significant effects.

15. Children

Loop is intended for users aged 13 and older and is not directed to children under 13. Loop does not ask for a user’s age or date of birth and does not perform age verification because the app does not require an account or automatically collect personal data.

Children under 13 should not send support emails without the involvement of a parent or legal guardian. A parent or guardian who believes that a child has sent personal information to the developer may request its deletion using the contact details above.

16. Privacy rights

Depending on applicable law, individuals may have the right to:

request access to their personal data;
request correction or deletion;
request restriction of processing;
receive data they provided in a portable format;
object to processing based on legitimate interests; and
lodge a complaint with a data protection authority.

Loop does not sell personal information and does not share personal information for targeted or cross-context behavioral advertising.

Requests may be sent to tom.vogel.dev@gmail.com. These rights apply to information actually available to the developer, such as support correspondence. The developer cannot identify or retrieve information that exists only in the app’s local storage.

The supervisory authority responsible for the controller in Germany is:

Saxon Data Protection and Transparency Commissioner
(Sächsische Datenschutz- und Transparenzbeauftragte)
Maternistraße 17
01067 Dresden
Germany

Email: post@sdtb.sachsen.de
Website: www.datenschutz.sachsen.de

Individuals may also contact the data protection authority in the country or region where they live or work.

17. Changes to this Privacy Policy

This Privacy Policy may be updated when Loop, the support website, legal requirements, or the services used by the developer change. The updated version will be published at the same public URL and will show a revised effective date.

Material changes will be disclosed before the related functionality is made available. In particular, this Policy will be updated before introducing accounts, cloud synchronization, analytics, crash reporting, advertising, in-app purchases, subscriptions, or other processing not described above.