Privacy Policy

1. Who we are

WiseCloq is developed and published by Marius Mocanu, an individual (sole) developer operating without a registered company. For the purposes of data protection law, Marius Mocanu is the party responsible for this policy and can be reached at support@wisecloq.com.

This is not a corporate app built by a team with a dedicated legal or privacy department — it's an independently published tool. We've written this policy as carefully and transparently as we can, but it is a template informed by the app's actual code as of the date above, not a substitute for professional legal advice.

2. Scope

This policy explains how the WiseCloq Android application (distributed through Google Play) handles information. It does not cover any other product, any third-party app you use to open a file WiseCloq creates, or any website other than a page hosting this policy itself.

3. What the app processes, and where it lives

WiseCloq is a personal work-log and shift-report tool. Everything it processes is information you type into the app yourself, for your own record-keeping. Depending on how you use the app, that can include:

• A name and employee/badge identifier you enter for your own reports;
• Shift start and end times, and daily work metrics you log (for example, units handled, hours worked, overtime, holiday or bank-holiday time);
• An hourly pay rate and bonus-scheme settings you configure, used only to calculate estimates shown back to you;
• Free-text remarks you choose to add to a daily entry.

All of this is stored locally on your device, in a private app database (SQLite) and in plain-text report files the app generates, both inside WiseCloq's private app storage — this hasn't changed. Just logging your daily entries never sends any of it off your device, and we — the developer — have no access to it, no copy of it, and no way to see it unless you choose to send it to us directly (for example, by attaching a report to a support email).

The one exception is generating a Monthly Report, a paid feature (section 6) that needs connectivity: to calculate the bonus/pay formula, the app sends your relevant entries and settings for that month — including the fields listed above — to a server function we operate (see section 9), over an encrypted (HTTPS) connection, together with your own sign-in token (section 5) so we can confirm your subscription is active. That server function calculates the report and returns it to your device; it does not write your entries to any database, and we don't keep a copy after the calculation finishes. Nothing else in the app triggers this — QR Check (section 4) is separate and unrelated.

4. The QR Check feature (camera, network requests, and location)

WiseCloq includes QR Check, an optional tool for scanning a QR code posted at an APCOA car park gate, to look up an audit code for that site. This feature works differently from the rest of the app described in section 3, so it's covered separately here. When you scan a QR code, the app:

• Uses your device's camera to read the code directly on-screen, entirely on your device. The camera feed is processed locally to detect the code; no photo or video is captured, stored, or sent anywhere.
• Sends a lookup request over the internet to APCOA's own servers (scanpay.apcoa.ie or scanvisit.apcoa.ie, depending on which scan type you use) — these are APCOA's servers, not ours; we don't operate them and don't receive a copy of what's sent. The only information sent is the site/carpark identifier encoded in the QR code itself, and a fixed placeholder value (AUDITVRN) used to run the lookup — never your own vehicle registration, name, or any other personal data you've entered elsewhere in the app.
• Reads your device's GPS location, if you've granted the location permission, and attaches it, in coordinate form, to that scan's entry in a local log kept on your device — the same local-only storage model described in section 3. This location is not sent to APCOA or to us; it stays on your device.
• Lets you export that log as a PDF, using Android's own file-save picker (Storage Access Framework) — the same "you choose the destination" principle as sharing a report, described in section 10.

Using QR Check requires the app to request the Camera, Internet, and Location permissions from Android, in addition to the permissions already covered elsewhere in this policy.

5. Accounts & sign-in

Using WiseCloq's main features now requires signing in to a WiseCloq account. There is no self-service sign-up screen in the app — we set up accounts individually, currently by request at support@wisecloq.com or as otherwise arranged directly with you. We don't ask for your name, phone number, or any identity document to do this.

An account consists of an email address and a password, authenticated through Supabase Auth, an authentication infrastructure service we use (see section 9 for the full list of providers we rely on). Your email address and password are stored on that provider's servers, not ours directly — we don't operate our own server hardware. Passwords are handled by Supabase's own authentication system; we never see or store your password in plain text ourselves.

Once you're signed in, the app keeps you signed in by storing a session token on your device. That token is encrypted (AES/GCM, using Android's own Keystore) before being saved in the app's private settings storage, rather than kept as plain text.

6. Subscriptions & payments

Generating a Monthly Report (section 3) is a paid feature that requires an active WiseCloq subscription. Subscriptions are sold and billed through Google Play Billing — WiseCloq itself never sees, receives, or stores your payment method, card number, or billing address. That entire relationship is between you and Google, governed by Google Play's own terms and privacy policy.

To know whether your subscription is currently active, we use RevenueCat, a third-party subscription-management service (section 9). RevenueCat receives purchase, renewal, and cancellation events from Google Play on our behalf, and tells our server your subscription's status. We store a minimal record linked to your account: a RevenueCat-assigned identifier for you, your subscription's expiry date/time, and the type of the last subscription event (for example, a renewal or a cancellation) — nothing about the price you paid, your card, or any other transaction detail, because we never receive that.

This record exists only so the Monthly Report server function (section 3) can check that your account is currently entitled to use it. It's tied directly to your account and is deleted automatically if your account is deleted (section 14). If you need to cancel a subscription or have a billing issue, that's handled entirely through Google Play (Play Store app → Subscriptions), not through us.

7. App check-in, devices & usage records

Whenever you open WiseCloq while signed in, the app makes a short "check-in" request to our server (Supabase, section 9). Along with it, we record the following, linked to your account:

• The version of the app you're running;
• Your device's manufacturer and model, and its Android version;
• A pseudonymous device identifier: a one-way cryptographic hash (SHA-256) of the identifier Android provides to WiseCloq for your device (ANDROID_ID). It can't be turned back into the original identifier, it's specific to WiseCloq, and it can't be used to follow you across other apps;
• The date and time of each check-in, a count of how many times you opened the app each day, and a record each time your account signs in (identified by our sign-in system's own session identifier) — all taken from our server's clock, not your phone's.

We don't record your location, your IP address, your contacts, or anything from your daily entries as part of this. We use these records to:

• Make sure you're on a version of the app we still support, and ask you to update when that's no longer the case;
• Protect your account and enforce that WiseCloq accounts are personal (see our EULA, sections 2–3): we look at how many devices an account is used on and how often it signs in, and may show you a notice, or limit the account to its registered device(s) — normally one. On a device that isn't allowed, the app shows a message instead of its normal screens and can't generate Monthly Reports; and
• Understand, in aggregate, how many people actively use the app.

These decisions are made by us, individually — not by an automated system acting on its own. If you think your account was limited by mistake (for example, after changing your phone), contact support@wisecloq.com and we'll move it to your new device. How long these records are kept is described in section 13.

8. What we don't do

Beyond the account, subscription and check-in system described in sections 5–7, WiseCloq's code contains no advertising SDK and no analytics or crash-reporting SDK. The only network requests the app makes are: signing in (section 5), the check-in (section 7), generating a Monthly Report and checking your subscription (sections 3 and 6), and the QR Check lookups (section 4), each to the specific servers named in those sections. Concretely, the app does not:

• Ask for any personal information beyond an email address and password to set up your account;
• Send your daily entries anywhere, except transiently when you choose to generate a Monthly Report (section 3);
• See, receive, or store your payment details — that's handled entirely by Google Play (section 6);
• Show ads or share data with advertising networks;
• Use third-party analytics, tracking pixels, or crash-reporting tools that phone home — the check-in (section 7) goes only to our own server, for the purposes listed there;
• Sell or rent your information to anyone, for any reason.

If a future version of WiseCloq adds any of the above, this policy will be updated first, and the update will be reflected in the app's Google Play store listing.

9. Third-party components & service providers

WiseCloq uses MPAndroidChart, an open-source charting library (Apache License 2.0), purely to draw the bar chart on the app's main screen from data that is already on your device. It renders locally and does not transmit any data anywhere.

For accounts, sign-in, the check-in, and Monthly Report generation (sections 3, 5, 6, and 7), WiseCloq uses Supabase (authentication, the server-side report calculation, the minimal subscription record described in section 6, and the check-in records described in section 7) and RevenueCat (subscription-status tracking from Google Play). Both act as service providers processing data on our behalf — sometimes called "data processors" or "subprocessors" under the GDPR — under their own security commitments, and don't use your data for their own purposes. See Supabase's and RevenueCat's own privacy policies for how they handle infrastructure-level data.

For QR Check (section 4), the app also uses: CameraX (Apache License 2.0) to run the camera; ML Kit Barcode Scanning, Google's on-device code-reading model bundled with the app — it runs locally and is governed by Google's own terms rather than an independent open-source license; OkHttp (Apache License 2.0) and Jsoup (MIT License) to make and parse the lookup request described in section 4; Guava (Apache License 2.0), a supporting library for those; and Google Play services Location, used to read your device's GPS position for that feature, governed by Google's own terms.

Standard AndroidX/Jetpack libraries used to build the app's interface work the same way as MPAndroidChart — they run entirely on your device.

10. Sharing & exporting reports

WiseCloq lets you tap "Share" on a report to send it wherever you choose, using Android's standard share sheet (technically, via a FileProvider and an Android ACTION_SEND intent). When you do this, you are choosing the destination — email, a messaging app, cloud storage, printing, and so on — and the file is handed directly to that app. That app's own privacy policy, not this one, governs what happens to the file from that point forward. WiseCloq itself is not a party to that transfer and does not see where the file goes.

QR Check's scan log (section 4) works on the same principle: you can export it as a PDF using Android's own file-save picker, and you choose where it's saved — WiseCloq doesn't upload or share it automatically.

11. Device backups

On Android 12 and later, the operating system offers a built-in backup feature that can back up an app's private storage to the device owner's own Google Account, if that device owner has backups turned on. WiseCloq does not disable this OS-level feature, so if you have Android backup enabled on your phone, your locally stored WiseCloq data (including the database) may be included in your own device backup, in the same way as most other apps on your phone. This is controlled entirely by your device and Google Account settings — WiseCloq has no separate access to that backup, and neither do we.

12. Legal basis for processing (GDPR)

Your daily entries never leave your device just from logging them, so in most respects we are not "processing" that personal data under the EU General Data Protection Regulation (GDPR) at all — you are the one processing it, on hardware you control, using a tool we provide.

For the parts that do involve our own infrastructure — your account (section 5), your subscription record (section 6), and the transient Monthly Report calculation (section 3) — the legal bases we rely on are: performance of a contract (Article 6(1)(b)), since creating an account and subscribing is how you obtain the Monthly Report feature you've asked for; and our legitimate interest in running a functioning, fraud-resistant service (Article 6(1)(f)), which is also why the bonus/pay calculation now runs on our server rather than inside the app itself. In both cases we minimize what's involved to an email address, a subscription status, and a report calculation that isn't stored afterward. The check-in records described in section 7 rely on the same two bases: keeping you on a supported version is part of providing the service you signed up for, and we have a legitimate interest in keeping accounts secure and personal to the person they were set up for, and in preventing misuse of the paid features — which we balance by recording only the device and usage details listed in section 7, pseudonymizing the device identifier, and keeping these records for a limited time (section 13).

13. How long information is kept

Your daily entries stay on your device for as long as you keep them there — there is no automatic deletion, and no retention period set by us, because we don't hold a copy to retain. You can delete an entry, clear the app's data from Android's app settings, or uninstall WiseCloq at any time, which removes the local database and report files from your device (subject to any backup copy your own device may already have made, per section 11).

Your account (email address) and subscription record (section 6) are kept on our infrastructure for as long as your account exists, and are deleted when you ask us to delete your account — see our Data Deletion page for exactly what that removes and how to request it.

The check-in records described in section 7 are kept for 12 months: a device record is deleted automatically 12 months after that device was last used, and sign-in and daily-use records 12 months after they were created. A single "last seen" summary for your account (time of the last check-in, app version, and device model) is kept for as long as your account exists. All of them are deleted when your account is deleted.

Data sent to generate a Monthly Report (section 3) is processed in memory by our server function and discarded immediately after the calculated report is returned to your device — it is never written to a database.

14. Your rights over your data

Data protection laws — including the GDPR, the UK GDPR, and similar laws elsewhere — give you rights such as access, correction, deletion, restriction, portability, and objection. For your daily entries, which live only on your own device, the most direct way to exercise these rights is to use the app itself: view, edit, or delete any entry directly, export/share a copy whenever you like, or uninstall the app to remove everything at once.

For your account, subscription and check-in records (sections 5–7), see our Data Deletion page — in short, email support@wisecloq.com and we'll delete your account, which cascades to your subscription and check-in records, within the timeframe described there.

For anything else covered by this policy — a question about how the app handles a particular field, or any other concern — email support@wisecloq.com and we will respond as promptly as we reasonably can. If you're in the EU or EEA, you also have the right to lodge a complaint with your local data protection supervisory authority.

15. International data transfers

Your daily entries never leave your device, so there is no cross-border transfer of that data by the app itself to disclose. Your account, sign-in, subscription and check-in records (sections 5–7) are processed on infrastructure operated by our service providers, Supabase and RevenueCat (section 9), which may be located outside your own country, including outside the EU/EEA depending on the provider — see each provider's own privacy policy for the safeguards it applies to international transfers.

The QR Check lookup (section 4) is sent directly to APCOA's own servers, not routed through us. Any transfer that happens because you shared a file with a third-party app (section 10) is governed by that app's own policies and by wherever its servers happen to be.

16. Children's privacy

WiseCloq is a work-shift and pay-estimate tool aimed at adults in employment; it is not directed at children, and we do not knowingly design it for use by children under 16 (or the minimum age that applies in your country). We set up accounts individually and don't knowingly create one for a child. If you believe a child has used the app or has a WiseCloq account, contact us at support@wisecloq.com and we'll help delete the account, or you're welcome to simply clear the app's local data or uninstall it from that device directly.

17. Security

Your locally stored entries are protected the same way any Android app's private storage is protected: by the operating system's app sandboxing, which keeps one app's data inaccessible to other apps on the same device. WiseCloq does not add its own password or biometric lock on top of this for that local data.

Your sign-in session token (section 5) is encrypted on your device (AES/GCM, via Android's Keystore) before being stored, rather than kept in plain text. On our side, your account, subscription and check-in records (sections 5–7) sit behind Supabase's Row Level Security, which restricts every request so an account can only ever read its own record (the check-in records can't be read through the app at all), and all traffic between the app and our servers travels over HTTPS/TLS.

18. Regional notices

WiseCloq is offered to users in many countries through Google Play. The analysis above — your daily entries stay on your device, the only personal data we hold on our own infrastructure is your account email, a minimal subscription-status record, and the check-in records described in section 7, and none of it is sold or shared for advertising — applies equally under other regional frameworks, including the UK GDPR and the California Consumer Privacy Act / CPRA. Users anywhere can reach us at support@wisecloq.com with questions specific to their own region's law.

19. Changes to this policy

If WiseCloq's data practices change further in the future, we will update this policy first, change the "Last updated" date above, and reflect the change in the app's Google Play listing before the new version is released.

20. Contact

Questions, requests, or feedback about this policy or about WiseCloq generally: support@wisecloq.com.

This Privacy Policy works together with our Terms & Conditions, End User License Agreement, and Data Deletion page, all linked at the top of this page.