Privacy Policy

1. Who is responsible for your data (Data Controller)

The app “Posture Break” (Android package com.luxebyte.posture, the “App”) is published by Luxebyte Labs (the “Developer”, “we”, “us”).

For the limited processing described in this policy, the data controller is:

• Controller: Matteo Lamarque, trading as Luxebyte Labs
• Contact for privacy matters: luxebytecomp@gmail.com

“Luxebyte Labs” is a trading name of Matteo Lamarque, an independent developer based in Italy. This is a one-person publisher, and the email address above is the contact point for every privacy matter: it reaches the person who can act on it. If you need a postal address in order to exercise a right, write to luxebytecomp@gmail.com and it will be given to you.

2. Scope of this policy

This policy applies only to the “Posture Break” Android App distributed through the Google Play Store. It does not cover any other product, website, or third-party service except as expressly described here (in particular Google’s advertising, statistics and payment services). This policy describes version 1.0 of the App. The English text is the only version.

What the App is

The App reminds you, on a schedule you choose, to take a short break from sitting, and shows a one-minute sequence of simple moves to do in that break. It counts the breaks you finish each day.

Posture Break is a wellness app. It is not a medical device and does not diagnose, treat, cure, or prevent any medical condition.

Updates to this policy

We may update this policy, for example if the App changes or if legal requirements change. When we make a material change we update the “Last updated” date and the policy version above and publish the new version at the same web address where you found this policy, before or at the time the change takes effect. Where the change concerns advertising or statistics consent, you may be asked again through the in-app consent message (see Section 7). Your continued use of the App after an update takes effect means the updated policy applies to you; if you do not agree, you can stop using the App and uninstall it.

3. What data is processed

The App processes six separate categories of data. We keep them separate on purpose, because they behave very differently: one is kept on your device (3(a)), one is collected by Google for advertising and never reaches us (3(b)), one is a single request that carries nothing about you (3(c)), one is a small, predefined set of usage statistics (3(d)), one is the one-time Pro purchase, handled by Google Play (3(e)), and the last is a short list of what the App does not do (3(f)).

3(a). Data kept on your device

To make the App work, the App stores a small amount of information locally on your device, using Android’s standard app-private SharedPreferences storage. This is the complete list, grouped by what it is for.

Your schedule and reminder (copied by your phone’s backup, below)

• the days of the week reminders are on, the time they start and end, and how often they come (every 15 to 120 minutes);
• the sound and the vibration you chose for the reminder;
• the reminder text, if you wrote your own. It is shown in the reminder notification, which Android can display on your lock screen;
• the time reminders are paused until, when you pause them: a time later the same day, or the end of the day.

Your breaks (copied by your phone’s backup, below)

• the number of breaks you finished on each day, for the last 60 days. A break counts when you press Done on a reminder or finish a one-minute reset in the App. Nothing else is recorded about it: not the time, not the moves.

How the reminders run (never copied by the backup)

• when the last reminder was posted and when the next one is due, and whether Android lets it arrive on the minute (precise timing) or only approximately;
• how many reminders in a row went unanswered, and, after several, until when the App spaces them out; and which reminder your last Done counted for, so that one reminder never counts twice;
• a record of the last 60 reminder deliveries: for each, when it was due, how late it arrived, what the App decided to do with it, what started it, whether precise timing was in use, and the battery standby group Android had placed the App in. It is shown on a hidden reliability page in the App, so that a late or missing reminder can be explained;
• the last internal step that failed, with the time and the type of error, and no other detail;
• a number that names the App’s notification channel, the day the App last showed Android’s notification question, and the last move a break showed, so that the next break starts with the move after it.

Other records (never copied by the backup)

• whether you own Pro, and when Google Play last confirmed it (Section 3(e));
• the last copy of the advertising switch file and when it was fetched (Section 3(c));
• a copy of what Google’s consent component last told the App: whether a consent message applies to you and, if it does, whether it has been answered (not what you answered);
• when the App last asked you to rate it on Google Play, and the dates it uses to decide when it may ask again (Section 3(f)).

Google’s own components described in Sections 3(b), 3(d) and 7 keep their own records on your device, such as your consent answer and the statistics identifier; those Sections describe them.

This on-device data:

• is never transmitted to the Developer, who has no servers to receive it;
• is never sold or shared with anyone;
• contains nothing that identifies you by name: there is no account, no login, no name, no email address and no device or advertising identifier in it. The one piece of free text is the reminder text you may write yourself;
• is not sent anywhere by the App, except what Section 3(d) describes, only where usage statistics are permitted: how late a reminder arrived (as a band), whether precise timing was in use, the battery standby group, how long a pause you chose lasts (as one of four predefined lengths), and your answers to Android’s notification and precise timing questions. Your schedule, your reminder text, your count of breaks and the moves you did are never sent;
• may be included in your phone’s own backup (Android Auto Backup): if backup is switched on in your phone’s settings, Android copies the App’s schedule and reminder settings and its count of breaks to your Google account, and puts them back when you reinstall the App or move to a new phone. Nothing else the App stores is included. That copy is kept by Google under your account, under Google’s terms, and the Developer cannot see it. You can switch backup off in Android’s settings;
• is fully under your control: uninstalling the App, or clearing the App’s storage in Android Settings → Apps → Posture Break → Storage, deletes it from your phone.

Permissions

The App itself declares four permissions:

• Notifications (POST_NOTIFICATIONS), for the break reminder. On Android 13 and later Android asks you first, and the App posts nothing unless you allow it. The App shows Android’s question when you turn reminders on during setup, at most twice and the second time on a later day;
• Alarms and reminders (SCHEDULE_EXACT_ALARM), used only if you switch on Precise timing, so that a reminder arrives on the minute. Without it Android may deliver reminders some minutes late;
• Run at startup (RECEIVE_BOOT_COMPLETED), to restore your reminder schedule after the phone restarts. It sets the next reminder again and reads nothing;
• Vibration (VIBRATE), to mark each change of move during a one-minute reset.

The libraries built into the App, all named in this policy, declare these as well, and only those libraries use them:

• Internet access (INTERNET) and Network state (ACCESS_NETWORK_STATE), used by the advertising and consent components (3(b)), the single request in 3(c), the usage statistics (3(d)), Google Play’s purchase and rating services (3(e), 3(f)), and by nothing else;
• Advertising ID (com.google.android.gms.permission.AD_ID), which allows Google’s advertising component to read the resettable advertising identifier described in 3(b);
• Ad services (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION and ACCESS_ADSERVICES_TOPICS), Android’s Privacy Sandbox interfaces, declared by Google’s advertising and analytics components, which may use them for the advertising purposes in Section 3(b) under the consent described in Section 7;
• Keep awake (WAKE_LOCK), which WorkManager, a scheduling library used by Google’s components, uses to finish short pieces of background work. The App’s own reminders do not use it;
• Google Play billing (com.android.vending.BILLING), which lets the App offer the Pro purchase through Google Play (Section 3(e));
• Install referrer (com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE), which lets the App ask Google Play, when it opens, which link brought you to the App (Section 3(d));
• an internal permission named after the App (com.luxebyte.posture.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION), declared by Android’s support library so that only the App itself can send messages to its own components.

The App declares no other permission. It has no access to your camera, microphone, location, contacts, files, motion sensors or phone state, and no permission that identifies you personally.

The reminder. Reminders are scheduled on your device with Android’s alarm service; there is no push service and no server, and nothing is sent to anyone to make them arrive. A reminder never contains an ad. Tapping it opens a one-minute reset, the one screen that can show the banner described in Section 3(b). You can change or stop reminders at any time in the App’s Settings, or in Android’s notification settings for the App.

3(b). Advertising data — collected and shared by Google (AdMob)

The App can show one small banner advertisement, anchored at the bottom of the one-minute reset while its moves play. The reset is also the screen a reminder opens. The banner is never shown on the Home screen, on the screen that follows a finished break, during setup, in the schedule, the settings or the list of moves, in a five-minute routine, or in a reminder, and it never covers a button, the moving figure or the timer. It is not shown to users who own Pro (Section 3(e)), and it is not shown where advertising is switched off (Section 3(c)). In the regions where a consent message applies, no ad is requested until you have answered it, and that message never appears during a reset (Section 7).

To serve this ad we use the Google Mobile Ads SDK (Google AdMob). When an ad is requested and shown, Google and its advertising partners collect and process the following categories of data for the purposes of serving ads, measuring ad performance, and detecting and stopping fraud and abuse:

• the Android Advertising ID (AAID), a resettable advertising identifier;
• the app-set ID, an identifier scoped to apps from the same developer;
• your IP address;
• technical information about the device (such as device model, operating-system version, language and region, and similar technical data);
• your interactions with ads (such as whether an ad was shown, viewed, or clicked).

This advertising data is collected by and shared with Google and Google’s advertising partners. The Developer does not receive it. Because Google’s advertising infrastructure is global, this data may be processed on servers located outside the European Union / European Economic Area, including in the United States (see Section 6).

Nothing about your breaks is ever sent with an ad request: not your schedule, not your reminder text, not your count of breaks, not the moves you did.

3(c). One request to a static file, so ads can be switched off without an update

The App fetches a single small text file from a set address:

The file holds one line per switch, and the App reads only the line saying whether this App’s advertising is on. It exists so that ads can be turned off without publishing a new version of the App.

The App sends nothing with this request: no identifier, no advertising ID, no setting, nothing about you or your breaks. But as with any request to any web server, the server that answers it sees the IP address the request came from, together with ordinary connection information such as the time, the file requested and the type of client. That server is GitHub Pages, operated by GitHub, Inc., which hosts the file as a plain static document. We run no server for it, and we never see a log of these requests.

The App keeps the last copy of the file on your device and fetches it again from time to time while you use the App. If the App has no copy, or its copy is more than 7 days old, it keeps advertising switched off.

Separately from this file, the App asks Google’s consent component when it starts whether a consent message is required for you (Section 7), because the answer governs both the advertising in Section 3(b) and the usage statistics in Section 3(d). Outside the EEA, the UK and Switzerland that check usually shows nothing; in a US state with a privacy law it can show that state’s message.

3(d). Usage statistics (Google Analytics for Firebase)

Why this exists, plainly. Posture Break is made by one person. Android phones delay alarms in different ways, and the only way to learn whether reminders reach people on time, on phones we do not own, is a small, predefined set of facts sent by the App. The same facts show which parts of the App people use, and so whether the App is understood. This Section describes every one of them. They never decide what the App does: the schedule, the moves and the reminders follow rules that read none of this data.

We describe this data as pseudonymous, and deliberately not as “anonymous”. Each installation is identified by a random identifier generated by Google’s SDK, and Google sees the IP address the data arrives from. That is enough for the data to count as personal data, so this policy handles it as personal data throughout.

Where this is active

In the EEA, the UK and Switzerland, nothing is sent unless you say yes. The consent message described in Section 7 includes a purpose for these statistics. If you consent to that purpose, the App collects what this Section describes; if you decline it, or do not answer, nothing is sent at all: not a reduced set, nothing. You can change your answer at any time from Settings → Privacy choices; a withdrawal takes effect immediately and discards the identifier described above. Whether a consent message is required for you at all is decided by Google’s consent system, from the message we publish for those regions. The App does not work out your location itself.

Everywhere else, the statistics are on. The legal basis is our legitimate interest in knowing whether reminders arrive on time and whether the App is understood (Section 4). You have the right to object at any time (Section 9); clearing the App’s data or uninstalling the App removes the identifier and ends the collection from that installation.

What is collected — every fact, in plain words

Every item below is one of a predefined list of words chosen by the App, or a band. Nothing is free text, nothing is a precise time, and nothing describes your body or the moves you did.

• that a reminder was delivered, with how late it arrived as a band, whether precise timing was in use, and the battery standby group Android had placed the App in (one of Android’s named groups, such as “active” or “rare”);
• that you answered a reminder, and how: by tapping it, or by its Done button;
• that a reminder was swiped away without being opened;
• that a one-minute reset started, and from where: a reminder, the Home screen, the library or the end of the first-time setup. Never which move, and never whether the reset was finished;
• that “Another move” was used during a reset. Never which move;
• which step of the first-time setup you reached;
• your answer to Android’s notification and precise timing questions: which permission, and whether it is granted;
• that a setting was changed, and which one: the days, the hours, how often, the sound, the vibration, the reminder text or precise timing. Never what it was changed to;
• that reminders were paused, and for how long: one hour, two hours, four hours or the rest of the day. Never the time the pause ends;
• that a test reminder was sent from Settings;
• that the Pro screen was shown, and from where it was opened. The App itself never sends whether you bought Pro; Google’s SDK records a completed purchase by itself (below);
• where your installation came from, recorded as a property of your installation: Google Play, our app Shake Flashlight & Torch, or “other”. The App asks Google Play for it each time it opens; the link’s own text is never sent.

Collected automatically by Google. Where the statistics are active, Google’s SDK also records, on its own: the first opening after installation; each opening; the start of a session and roughly how long it lasted; an App update; an operating-system update; that the App was uninstalled, or its data cleared; a screen view when a screen of the App comes to the front; where Google Play tells the SDK that your installation came from a campaign link, that campaign’s name, source and medium; that an advert was shown, where Google’s advertising SDK reports it to the same system; that an in-app purchase was completed through Google Play (the Pro purchase in Section 3(e)), with details the SDK reads from Google Play, such as the product’s ID and name, its price, the currency and the quantity; and an approximate country or region derived by Google from the IP address. Google also records the device model, operating-system version, App version and language with each event.

Devices used for testing are left out: nothing is sent from Google’s automated test devices (Firebase Test Lab, which runs the pre-launch checks for Google Play), and nothing from our own development builds unless we are deliberately checking the statistics on that device.

What is deliberately not collected. No move or exercise, no record of whether a break was finished, no count of breaks, no streak and no percentage. No purchase event of the App’s own (the purchase record Google’s SDK makes by itself is described above). No schedule, no value of any setting, no reminder text, no free text of any kind. No precise timestamps as data fields. No advertising identifier is used for this purpose: the advertising identifier described in Section 3(b) is used by the advertising SDK alone. No contacts, no location from the device, no account.

The identifier. Google’s app-instance identifier is random, scoped to this App on this device, and resettable: withdrawing consent discards it, and clearing the App’s data or uninstalling removes it. It is not the Android advertising ID.

The provider. Google Analytics for Firebase (GA4), supplied by Google. The data is encrypted in transit by Google’s own TLS. Retention is described in Section 8, and the countries it may reach in Section 6.

3(e). Purchases (Posture Break Pro)

Pro is a one-time purchase, made through Google Play. It removes the banner in Section 3(b) and unlocks the extra routines in the App’s library. There is no subscription and no trial.

• Google Play processes the payment. You pay with the payment method in your Google account, under Google Play’s terms. The App and the Developer never see your card or bank details.
• What the App receives from Google Play: whether you own Pro, whether a payment is still waiting, and a purchase token, which the App returns to Google Play to confirm the purchase, as Google Play requires. The App keeps on your device only whether you own Pro and when Google Play last confirmed it (Section 3(a)). That record is not copied by your phone’s backup: the App asks Google Play again each time it opens, which also restores Pro when you reinstall the App or use another phone with the same Google account.
• What the Developer receives: Google Play makes a record of each order available to us in the Google Play Console (for example the order number, the date, the product and the amount), under Google Play’s terms. We use it only for accounting and tax, refunds, and to answer you if you write to us about a purchase.
• In the usage statistics (Section 3(d)): the App sends no purchase event of its own, but where the statistics are active, Google’s statistics SDK records a completed Pro purchase by itself, with the product, its price, the currency and the quantity, as Section 3(d) describes. Nothing about a purchase is sent with an ad request.

3(f). What the App does NOT do

The App contains no account or sign-in, no crash-reporting service of its own, no attribution SDK other than Google Play’s own install referrer (Section 3(d)), no social features and no server of ours. Google’s advertising SDK (3(b)) and statistics SDK (3(d)) may collect crash and diagnostic information about their own operation, which Google processes as those Sections describe. Apart from the Google advertising and consent components (3(b), 7), the single static-file request (3(c)), the statistics component (3(d)), Google Play’s billing service (3(e)), and Google Play’s rating card (below), the App makes no network requests of any kind.

Rating the App. From time to time, after you have used the App for some days, the App may ask Google Play to show its own rating card. Google Play decides whether it appears, and handles your rating and any review under its own terms. The App is not told whether you rated it, or what you wrote.

4. Why we process data, and the legal basis for each purpose (GDPR)

Where the EU or UK GDPR applies to you:

If you refuse consent, the App works in full: reminders, resets, the count of breaks and Pro are unaffected.

5. Who receives data (third parties / recipients)

• Google Ireland Limited / Google LLC, as the provider of Google AdMob and the Google User Messaging Platform (the consent tool). Google’s own privacy policy: https://policies.google.com/privacy. How Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites.
• Google Ireland Limited / Google LLC again, in a separate role: the same two companies operate Google Analytics for Firebase, which receives the usage statistics described in Section 3(d) where they are active. We decide what is collected there and why; Google acts as our analytics provider, and processes the data additionally for its own purposes as described in the policies linked above.
• Google Play (Google Ireland Limited / Google LLC), which processes the Pro purchase (Section 3(e)), tells the App where an installation came from (Section 3(d)), and shows its own rating card (Section 3(f)), each under the Google Play Terms of Service and on its own account.
• Google’s advertising partners, where you consent to personalised ads. The list of partners is presented to you inside the consent message and can be reviewed there at any time.
• GitHub, Inc., only as the host of the one static text file described in Section 3(c). It receives the IP address that request is made from, and nothing else. GitHub’s privacy statement: https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement.

The Developer discloses your data to no one else. We do not sell data (see Section 9).

6. International data transfers

The Developer receives and stores none of the data described in Sections 3(b) and 3(d), and so transfers none of it. That is not the same as saying nothing leaves your device: the App is designed to cause requests to the recipients named in Section 5, and those recipients may process what they receive outside Switzerland, the EEA and the UK.

The static file described in Section 3(c) is served by GitHub, Inc., a company based in the United States, so the IP address that request is made from is received there.

The usage statistics described in Section 3(d) are sent to Google Analytics for Firebase, and Google may process and store them outside Switzerland, the EEA and the UK, including in the United States, under the safeguards Google states below. In the EEA, the UK and Switzerland this happens only where you have consented under Section 3(d).

Google, as an independent controller for advertising and Google Play data, may transfer that data outside Switzerland, the EEA and the UK, including to the United States. Google states that it relies on the European Commission’s Standard Contractual Clauses and, for transfers to the US, on the EU-US Data Privacy Framework, its UK Extension and the Swiss-US Data Privacy Framework, where applicable. Details are in Google’s own privacy documentation linked in Section 5.

If you are in Switzerland. Swiss data protection law (the Federal Act on Data Protection, FADP) asks us to name the countries your data is sent to and the safeguard for each. From Switzerland, the data described in this policy may go to:

• Ireland, and other countries of the EU and the EEA, where Google Ireland Limited is the Google company responsible for users in Switzerland. The Swiss Federal Council recognises these countries as providing an adequate level of data protection (Annex 1 of the Swiss Data Protection Ordinance).
• The United States, where Google LLC and GitHub, Inc. are based. Both companies are certified under the Swiss-U.S. Data Privacy Framework, and the Federal Council recognises the United States as providing an adequate level of protection for certified companies (Annex 1 of the Swiss Data Protection Ordinance).
• Other countries where Google or its partners operate. Google lists its data centre locations at https://datacenters.google/locations/, and the advertising partners are listed in the consent message described in Section 7. Where no adequacy decision covers a transfer, we and Google rely on standard contractual clauses, which the Swiss Federal Data Protection and Information Commissioner (FDPIC) recognises under Art. 16(2)(d) FADP.

7. Consent and how to change or withdraw it

In the EEA, the UK, and Switzerland

Before the App requests any ad, it shows a consent message provided through the Google User Messaging Platform. No ad is requested, and no usage statistic is sent, until you have answered it. The message is never shown during a one-minute reset.

You can change or withdraw your choice at any time:

That row appears in the App where a standing consent entry point is required, which is the region where you have the right to withdraw. Opening it shows the same consent message so you can change any choice, including withdrawing consent entirely. The same message governs the usage statistics in Section 3(d): it carries a purpose for them, and withdrawing it there stops the collection at once.

In US states with a privacy law

Where Google’s consent system shows a US state privacy message, the same Settings → Privacy choices row opens it, and you can opt out there (Section 9).

Everywhere — controlling your Advertising ID at the Android level

Independently of the App, Android lets you control the advertising identifier:

There you can delete or reset your Advertising ID, and on Android 12 and later you can remove it entirely, after which apps receive a string of zeroes instead.

Children

See Section 10. The App is not directed to children.

8. Data retention — how long data is kept

• On-device data (Section 3(a)): kept on your phone until you delete it, by clearing the App’s storage or uninstalling the App. The count of breaks keeps the last 60 days and deletes older days by itself. If backup is switched on in your phone’s settings, Android also keeps a copy of the schedule, reminder settings and count of breaks in your Google account, as Section 3(a) describes; that copy is governed by Google, not by us. We have no copy and therefore no retention period of our own.
• Advertising data (Section 3(b)): retained by Google according to Google’s own retention schedules, which are described in Google’s privacy documentation. The Developer holds none of it and cannot delete it on your behalf; requests concerning it should be directed to Google, and we will help where we can.
• The static-file request (Section 3(c)): whatever server log GitHub keeps is subject to GitHub’s own retention schedule. We receive no such log and hold nothing from it.
• Usage statistics (Section 3(d)): event-level data is kept by Google for 14 months, a setting in the Google Analytics console applied to the whole property. If we ever lengthen it, this policy will say so before we do. The random app-instance identifier is discarded when you withdraw consent, when you clear the App’s data, or when you uninstall.
• Purchases (Section 3(e)): Google Play keeps its records of your purchase under its own terms. The order records Google Play gives us are kept for as long as Italian accounting and tax law requires, and then deleted.

9. Your privacy rights

If you are in the EEA or the UK (GDPR / UK GDPR)

You have the right to access, rectify, erase, restrict, and object to processing of your personal data, the right to data portability, and the right to withdraw consent at any time without affecting the lawfulness of processing before withdrawal.

Practically:

• For the on-device data, you can exercise all of these yourself, instantly, by clearing the App’s data or uninstalling it. We cannot access it, so we cannot act on it for you.
• For the advertising data, the controller in practice is Google. Requests should be addressed to Google using the contacts in Google’s privacy policy. Write to luxebytecomp@gmail.com as well and we will do what we can to assist and to point you to the right place.
• For the usage statistics, withdraw consent in Settings → Privacy choices where that row appears, or clear the App’s data. The statistics identify an installation only by Google’s random identifier, so we cannot find your data without it; if you write to us, we will explain what we can and cannot do (Art. 11 GDPR).
• For a Pro purchase, write to us with your order number and we will tell you what the order record holds.

You also have the right to lodge a complaint with a supervisory authority in your country of residence, place of work, or place of the alleged infringement. In Italy that is the Garante per la protezione dei dati personali.

If you are in Switzerland (Swiss Federal Act on Data Protection, FADP)

You have the same choices described above, and the FADP gives you these rights:

• to ask whether personal data about you is processed, and to receive the information the FADP lists, free of charge and in general within 30 days (Art. 25 FADP);
• to receive data you gave us, in a common electronic format (Art. 28 FADP);
• to have inaccurate data rectified, and to object to processing or ask for it to stop or for the data to be deleted (Art. 32 FADP);
• to withdraw your consent at any time from Settings → Privacy choices in the App.

Apart from the order records of Section 3(e), we hold none of this data on any server, so for most requests we will tell you that, and help you take the request to Google, which holds it. Write to luxebytecomp@gmail.com.

You can also report a concern to the Swiss Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern, Switzerland, https://www.edoeb.admin.ch.

The App makes no decision about you based solely on automated processing that has a legal consequence for you or a considerable adverse effect on you.

If you are in California (CCPA/CPRA) or another US state with a privacy law

We do not sell your personal information.

We do not claim that no “sharing” takes place. Showing a personalised ad means advertising data is made available to Google and its partners for cross-context behavioural advertising, and that is capable of being “sharing” as the CCPA and CPRA define it, whether or not the Developer ever holds the data. The App gives you the opt-out:

• In the App: Settings → Privacy choices, which opens a US state privacy message where you can opt out of that use. The row appears where such a message applies to you.
• On the device: the Android Advertising ID controls described in Section 7, which apply wherever you are.

You may also request access to, or deletion of, personal information we hold about you. Apart from the order records of a Pro purchase, we hold none, and we will tell you so.

10. Children’s privacy

The App is not directed to children. On Google Play it is declared for users aged 16 and over, and it is not part of the Google Play “Designed for Families” programme. 16 is the highest age of digital consent that any EU Member State sets under Art. 8 GDPR, so every user inside the declared audience can give the consent asked for in Section 7 themselves.

The declared audience describes who the App is intended for; it is not a claim that nobody younger ever installs it. We cannot verify anyone’s age and we do not try to. We do not knowingly collect personal data from children: the App asks for no age, name, email address, contacts or account. If you believe a child has used the App in a way that resulted in personal data being processed, contact luxebytecomp@gmail.com and we will help you direct the request to Google, who holds the data.

11. Security

The App stores its data using Android’s standard app-private storage, which the operating system isolates from other apps. We hold no servers, no accounts and no database. The data sent to Google and GitHub travels over encrypted connections.

No method of electronic storage or transmission is completely secure, and we cannot guarantee absolute security of data handled by third parties such as Google.

12. Changes to this policy and how you are notified

Material changes are published at the same address as this document, with an updated “Last updated” date and policy version, before or when they take effect. Where a change concerns advertising or statistics consent you may be asked again through the in-app consent message.

13. How to contact us about privacy

luxebytecomp@gmail.com

Write to us with any question, any request, or to tell us this policy is wrong about something. We would rather put it right than defend it.

Appendix. Previous versions

This appendix is the record of what each version of this policy changed, newest first. The policy in force is Sections 1 to 13 above; where an entry below says something different from those Sections, the Sections apply.

Version 1.2, dated 21 October 2026 (this version of the policy). This version:

• adds the timed pause to Section 3(a): besides pausing reminders for the rest of the day, you can pause them for one, two or four hours. The App keeps the time such a pause ends with your schedule and reminder settings, which your phone’s backup copies;
• adds the length of a pause to the statistics in Section 3(d): one hour, two hours, four hours or the rest of the day, as a predefined word, never the time the pause ends. Section 3(a) names it among the values that leave the device where the statistics are active.

Version 1.1, dated 20 October 2026. That version:

• moves the banner from the Home screen to the one-minute reset, and lists the screens that never show it (Sections 3(a) and 3(b));
• adds to the statistics in Section 3(d): a reminder swiped away, “Another move”, which setting was changed (never its value), reminders paused for the day, a test reminder, and a reset started from the end of the first-time setup;
• asks Google Play where the installation came from each time the App opens, and records it as a property of the installation (Sections 3(a) and 3(d));
• adds to Section 3(f) the information Google’s advertising and statistics SDKs may collect about their own operation.

Version 1.0, dated 17 October 2026. The first version of this policy.