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. WiseCloq does not operate a server, and none of this information is transmitted to us or to anyone else by the app itself. 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).

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 7.

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. What we don't do

WiseCloq's code contains no advertising SDK, no analytics or crash-reporting SDK, and no account or sign-in system of any kind. The only network requests the app makes are the QR Check lookups described in section 4, to APCOA's own servers — WiseCloq itself does not operate a server. Concretely, the app does not:

• Create a user account or ask you to sign in;
• Send your entries, reports, or settings (the data described in section 3) to any WiseCloq server (none exists) or to any third party;
• Show ads or share data with advertising networks;
• Use analytics, tracking pixels, or crash-reporting tools that phone home;
• 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.

6. Third-party components

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 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.

7. 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.

8. 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.

9. Legal basis for processing (GDPR)

Because WiseCloq processes your entries entirely on your own device, for your own purposes, and never transmits them to us, in most respects we are not "processing" your 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. To the extent GDPR principles are treated as applying to this local processing, the legal bases we rely on are: your own decision to use the app for a purpose you choose (Article 6(1)(a)/(b)), and our legitimate interest in providing a functioning, useful tool (Article 6(1)(f)), balanced by minimizing what the app collects in the first place — namely, nothing beyond what you type in, plus the minimal QR Check lookup described in section 4.

10. How long information is kept

Your 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 8).

11. 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. Because your data lives on your own device and not on any server we control, the most direct way to exercise these rights is usually 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.

If you'd still like to contact us — for example, to ask a question about how the app handles a particular field, or to raise a 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.

12. International data transfers

Since WiseCloq has no server and does not transmit your entries anywhere, there is no cross-border transfer of your data by the app itself to disclose, beyond the QR Check lookup described in section 4 (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 7) is governed by that app's own policies and by wherever its servers happen to be.

13. 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 don't collect data at all, so we have no way to knowingly collect data "from" a child in the first place — but if you believe a child has used the app and you'd like help clearing local data from a device, you're welcome to contact us, or simply clear the app's data or uninstall it from that device directly.

14. Security

Your 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. Because there's no WiseCloq account or server, the security of your data mostly comes down to the security of your device itself — for example, using a device lock screen and keeping your phone's software up to date.

15. Regional notices

WiseCloq is offered to users in many countries through Google Play. Because the app doesn't collect personal information in the first place, the analysis above — nothing collected, nothing sold, nothing shared except at your own initiative — 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.

16. Changes to this policy

If WiseCloq's data practices change in the future — for example, if a later version adds an optional cloud-sync feature, analytics, or ads — 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.

17. Contact

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

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