Legal

Privacy Policy

Effective 6 September 2026 · Last updated 6 September 2026

This policy explains what Re:Click does with your information. It covers Re:Click for Windows, published on the Microsoft Store by CODELEVEN ("we", "us"), the forthcoming Re:Click for Android, and this website.

The short version

• Re:Click has no account. You never give us a name, an email address or a password to use it.
• Your settings, your recorded macros and your statistics are stored on your own device. We never receive them.
• The Windows app makes one anonymous request on startup, to fetch a small configuration file. It sends no identifier of any kind.
• There are no ads, no ad networks and no third-party trackers in the app or on this site.
• We do not sell, rent or share your personal information, and we never have.
• The Android app will use Google Firebase for usage analytics. That is described in full below, before it ships.

1. What stays on your device

Nearly everything Re:Click knows about you never leaves the machine it runs on. The Windows app keeps the following in its own application data storage, which Windows removes when you uninstall it:

• Settings — your click rate, button and target choices, hotkeys, theme, window position and tray preferences.
• Macros — the clicks, key presses and mouse movement you record, together with the names, icons and shortcuts you give them.
• Statistics — lifetime counters for clicks sent, keys pressed, macros played and time spent running.
• A cached licence state — whether this installation is Free or Pro, so the app works offline.
• Housekeeping marks — such as when a theme trial started and which release notice you have already seen.

None of this is transmitted to us or to anyone else. If you export a macro, the file goes wherever you choose to put it; that copy is yours to manage.

2. Recording, and what it does not capture

Macro recording captures mouse clicks, mouse movement and key presses — but only while a recording is running, only for the duration of that take, and only into the macro you are making. Re:Click does not run a background keylogger, does not read your screen, does not read your clipboard and does not read your files. A recording is a local file on your machine, and nothing in the app uploads it.

Because a recording captures whatever you type while it runs, do not record yourself entering a password, a card number or anything else you would not want written down, and take care before exporting a macro to someone else.

3. What leaves your device — Windows

3.1 Remote configuration (Google Firebase)

Once per launch, the Windows app fetches a small JSON configuration file (roughly sixty bytes) from a Firebase Realtime Database operated by Google. It lets us adjust a few in-app behaviours — such as when the app is allowed to ask for a rating — without shipping an update.

• The request is an ordinary anonymous HTTPS GET. It carries no account, no device identifier, no advertising ID and nothing about how you use the app.
• It is a read only. The app never writes to that database.
• As with any web request, Google receives the network information needed to serve it — including your IP address — and may log it. See Firebase's privacy documentation and Google's Privacy Policy.
• If the request fails, the app carries on with its built-in defaults. It is never blocking, and you lose no functionality by firewalling it.

The Windows app contains no analytics SDK. We do not know how many times you have opened it.

3.2 The Microsoft Store

Installation, updates, purchases and ratings are handled by the Microsoft Store, not by us. When the app checks whether you own Pro, or opens the purchase or rating dialog, it is talking to Microsoft's services using the Store account already signed in on your PC.

• We never see your payment details. Cards, billing addresses and receipts are handled entirely by Microsoft.
• We receive only aggregate, anonymised sales and health reporting through Microsoft Partner Center — counts of purchases, installs, ratings and crashes. Individual customers are not identifiable to us in it.
• Microsoft's handling of that data is covered by the Microsoft Privacy Statement.

3.3 If you contact us

When you email feedback@codeleven.app, we receive your address and whatever you write. We use it to answer you and to fix what you reported, keep it no longer than we need it for that, and never add it to a mailing list.

4. What will leave your device — Android (coming soon)

Re:Click for Android is in development. When it ships it will use Google Firebase, which the Windows app largely does not. We are describing it here in advance so there are no surprises; this section takes effect for you only if and when you install the Android app.

4.1 Firebase Analytics (Google Analytics for Firebase)

The Android app will report anonymous usage events so we can see which features are used and where people get stuck — for example that a macro was recorded, that the upgrade screen was opened, or that a purchase completed. Events carry what happened, not what you did it to: we do not send the contents of your macros, the apps you automate, the text you type or anything you see on screen.

Firebase Analytics collects, on Google's side:

• A pseudonymous app instance ID generated on your device — not your name, not your Google account, and reset if you clear the app's data or reinstall it.
• Device and app information — model, operating system version, app version, language, coarse region derived from IP, and whether this install is Free or Pro.
• Event records — which in-app actions occurred and when.

Advertising identifiers are not used, and the data is not used for advertising, ad personalisation or audience selling. You will be able to turn analytics collection off from the app's settings; the app works identically with it off.

4.2 Firebase Remote Config

Same purpose as on Windows: fetching a small configuration document so a handful of behaviours can be adjusted without an update.

4.3 Firebase Crashlytics

If enabled in a given release, Crashlytics reports crashes and fatal errors: a stack trace, the app and OS version, the device model, and a pseudonymous installation identifier. It exists so we can fix the crash you just hit. It does not collect your macros or your input.

4.4 Google Play Billing

Purchases in the Android app are processed by Google Play, exactly as Microsoft processes them on Windows. We never see your payment details; we receive only the entitlement — whether this install owns Pro — and anonymised sales reporting in the Play Console.

All of the above is governed by Firebase's privacy and security documentation and Google's Privacy Policy. Where the Android app requires system permissions to do its job — such as an accessibility service to deliver taps — the app will explain what each permission is for at the point it asks, and use it for nothing else.

5. This website

This site is a set of static files hosted on GitHub Pages. It sets no cookies, runs no analytics and embeds no third-party scripts, fonts or trackers. GitHub, as the host, logs requests (including IP addresses) for security and operational purposes — see the GitHub Privacy Statement. Links to the Microsoft Store, Google Play or Google's own documentation take you to services with their own policies.

6. Who we share data with

We do not sell, rent, trade or share personal information for anyone else's marketing. The only third parties involved are the ones that make the product work:

• Google (Firebase) — remote configuration on Windows and Android; analytics and crash reporting on Android.
• Microsoft — distribution, updates, purchases, ratings and crash reporting for the Windows app.
• Google Play — distribution, updates and purchases for the Android app.
• GitHub — hosting for this website.
• Our email provider — only if you write to us.

We may also disclose information where we are legally required to, or to protect our rights or users' safety. Given how little we hold, in practice there is very little to disclose.

7. Your rights

If you are in the UK, the EEA, Switzerland, California or another region with data protection law, you have rights over your personal information — access, correction, deletion, portability, restriction, objection, and withdrawal of consent. Because Re:Click has no accounts and stores your data locally, you can exercise most of these yourself:

• Delete everything — uninstall the app. Your settings, macros and statistics go with it.
• Export your data — Settings has an export option for your macros; the file is plain and portable.
• Stop the analytics (Android) — turn it off in Settings; also removable by clearing app data.
• Stop the config request (Windows and Android) — block the app in your firewall; the app carries on with its defaults.

For anything else, or to ask what we hold, write to feedback@codeleven.app. We will respond within 30 days. Where the GDPR applies, our lawful basis is legitimate interest — running and improving the app — except for Android analytics, which rests on your consent and which you can withdraw at any time. You also have the right to complain to your local data protection authority.

California: we do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not process it for cross-context behavioural advertising.

8. Children

Re:Click is not directed at children under 13 (or under 16 where local law sets that age), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, write to us and we will delete it. The app's Store listings carry the age ratings assigned by Microsoft and Google.

9. Retention and security

Data on your device lasts until you delete it or uninstall the app. Android analytics data is retained by Firebase under our configured retention window, which will be no longer than 14 months. Support emails are kept only as long as needed to resolve the matter. Everything the app sends travels over HTTPS. No system is perfectly secure, but the surest protection here is structural: we hold almost nothing about you in the first place.

10. International transfers

Our service providers — Google, Microsoft and GitHub — operate globally and may process data outside your country, including in the United States, under the safeguards described in their own policies (such as Standard Contractual Clauses).

11. Changes to this policy

If we change how the app handles data, we will update this page and move the "Last updated" date. Material changes — a new category of data, or a new recipient — will also be noted in the app's release notes. Continuing to use Re:Click after a change means you accept the updated policy.

12. Contact

CODELEVEN — feedback@codeleven.app
Please put "Privacy" in the subject line so it reaches the right place quickly.

← Back to Re:Click · Terms of Use