Privacy Policy — Cookie Approval Plus
- Effective date: 12 August 2026
- Applies to: Cookie Approval Plus for Android, package
com.cookie.approval.plus, version 1.1.1 and later - Published by: Casinos Custom, LLC (“Casinos Custom”, “we”, “us”)
- Contact: app.dev@casinoscustom.com
- Data controller for the purposes of the UK/EU GDPR: Casinos Custom, LLC
1. The short version
Cookie Approval Plus is assistive technology for people who cannot reliably perform precise, repeated touch gestures. To do its job it must read what is on your screen and tap a button for you.
It does not collect, store off-device, transmit, sell, or share any personal data. It has no user accounts, no analytics, no advertising, no crash reporting, and no network access of any kind.
The app does not request the INTERNET permission. Android will not grant an
app network access it has not declared, so the app is technically incapable of
sending your information anywhere, regardless of what any policy document
claims. You can verify this yourself — see §11.
Everything the app remembers stays in its own private storage on your device and is deleted when you uninstall it.
2. Who this policy is for
This policy covers the Cookie Approval Plus Android application only. It does not cover the websites or apps you use the app alongside; those have their own privacy policies, and this app has no influence over them.
3. What the app is, and why it needs access to your screen
Cookie Approval Plus is an accessibility tool. It is built for users with limited or no use of their hands, arms, or fingers, for whom the small, imprecise buttons on cookie consent banners and similar prompts are a genuine physical barrier encountered many times a day.
To stand in for a tap that the user cannot easily perform, the app uses Android's Accessibility Service API — the same platform capability that screen readers, switch access, and voice control are built on. That API is the only mechanism Android provides for one app to read on-screen content and perform a gesture on the user's behalf. There is no narrower permission that would accomplish the same task.
What the Accessibility Service can access while it is enabled:
| Accessed | Purpose |
|---|---|
| Text and content descriptions of on-screen elements in the foreground app | To recognise a consent prompt and identify which button is “Accept”, “Reject”, and so on |
| The on-screen position and size of those elements | To aim the synthetic tap at the correct button, and to reject targets that are the wrong shape to be a real button |
| Which app is currently on screen | To skip apps where automation must never act (system settings, the Play Store, the package installer, the permission manager, the dialer, messaging apps), and to record what happened in the on-device activity log |
What happens to that content: it is examined in memory, on your device, at the moment it appears, and then discarded. Screen text is not written to storage, not indexed, not profiled, and not sent anywhere. The only trace kept is the activity-log entry described in §5.
What the app deliberately does not do, even though the Accessibility Service would technically permit it: it does not read or record passwords, form fields, messages, keystrokes, page contents, browsing history, or the contents of any screen beyond what is needed to identify a consent prompt and its buttons; it takes no screenshots; it records no audio, video, or location; it reads no contacts, files, photos, calendar, or call logs; and it does not act inside system settings, app stores, package installers, permission dialogs, dialers, or messaging apps at all.
4. Personal data we collect
None.
Casinos Custom, LLC receives nothing. There is no server, no account, no usage tracking, and no code from any other company in this app. We cannot see how many times you have used the app, which sites you visit, or whether the app is installed at all.
Google Play may provide us with aggregate, anonymous install and crash statistics as it does for every app on the store. That is Google's processing under Google's privacy policy, not ours, and it is not linked to you as an individual.
Your purchase. Cookie Approval Plus is a paid app. Google takes and processes the payment; Casinos Custom, LLC receives an aggregated payout and sales reporting from Google. We never see or hold your card number, billing address, or any other payment detail — that is between you and Google, under Google's privacy policy. The app itself contains no payment code and contacts no payment service, because it has no network access at all.
5. Data stored on your device
All of the following lives in the app's own private storage on your phone, which no other app can read. None of it is transmitted.
| Stored | What it is | How long |
|---|---|---|
| Risk-acknowledgement flag | Whether you completed the first-run disclosure screen | Until uninstall or app-data clear |
| Service on/off state | Your master enable toggle | Until uninstall or app-data clear |
| Per-category policy | Your Approve / Reject / Ignore choice for each of the eight prompt categories | Until uninstall or app-data clear |
| “Guess the button” setting | Whether you turned on the option that guesses which control to press when it recognises none of them (off by default) | Until uninstall or app-data clear |
| Counters | How many prompts have been handled, per category | Until uninstall, app-data clear, or reinstall |
| Activity log | See below | Newest 200 entries; older entries are automatically discarded |
The activity log
The app writes one entry every time it presses a button, and every time a safety guard stopped it from pressing one. This exists for your benefit: the service acts without asking, sometimes on screens you are not looking at, so “what did it just tap?” must always be answerable.
Each entry contains, and only contains:
- a timestamp;
- which app was on screen at the time, recorded by its internal name (for
example
com.android.chrome, which is Chrome); - which category was recognised (for example
COOKIES); - the outcome (the action taken, or the reason a guard refused);
- the visible text label of the button involved, truncated to 120 characters.
The log therefore contains a partial record of which apps you used and what consent prompts appeared in them. Treat it as personal information. It never leaves your device on its own, it is capped at 200 entries, and you can erase it at any time with Clear log on the app's main screen.
Backups
The app excludes all of its stored data from Android Auto Backup and from
device-to-device transfer (backup_rules.xml, data_extraction_rules.xml).
Your activity log and settings are not copied to your Google Drive backup
and do not follow you to a new device.
6. The one way data can leave your device — and only if you choose it
The app's main screen has a Send report button. It exists so testers and users can report a problem with enough context to diagnose it.
Pressing it opens Android's standard share sheet with a plain-text report that contains: your app version, your device manufacturer and model, your Android version, whether the service is active, your current settings, and your activity log (up to 200 entries — including the app package names and button labels described in §5).
Nothing is sent until you choose a destination app (email, messaging, notes) and send it yourself. The app has no network access and no default recipient; it cannot transmit the report on its own. Once you send it, the report is subject to the privacy policy of whichever app and recipient you chose.
Please read the report before sending it, and clear the log first if you do not wish to share the record of which apps you used.
If you send a report to Casinos Custom, LLC at app.dev@casinoscustom.com or support@casinoscustom.com, we hold it only for as long as it takes to investigate the issue you reported, use it for no other purpose, and delete it afterwards. You may ask us to delete it sooner at any time.
7. Permissions the app requests
The app declares exactly one permission:
BIND_ACCESSIBILITY_SERVICE— required by Android for any accessibility service. It is not granted by installing the app. You must turn the service on yourself, in Android's own Settings → Accessibility screen, after passing Android's own warning dialog. You can turn it off there at any time, and the app stops acting immediately.
It also declares a <queries> element so it can ask Android which app is your
home launcher — used solely to exclude the home screen from scanning. It reads
no other information about your installed apps.
The app requests no other permission. It has no access to the internet, camera, microphone, location, contacts, storage, SMS, phone, calendar, or your list of installed applications.
8. Advertising, analytics, and tracking
There is none. No advertising identifier is read. No tracking or advertising code from any other company is built into the app. No profiling or automated decision-making about you is performed.
The app does not improve your privacy, and we make no such claim. Its default setting is to accept cookie banners, which means consenting to those sites' tracking. That is a deliberate accessibility trade-off, it is disclosed on first run, and you can change it to Reject at any time. See the Terms of Service, §4.
9. Children
The app is not directed to children and is not designed for or marketed to anyone under 13 (or under 16 in jurisdictions where that is the applicable age of digital consent). We knowingly collect no data from anyone, of any age.
10. Your rights
Because we hold no personal data about you, there is nothing for us to disclose, correct, export, or delete on request — there is no record of you to act on.
You retain full and immediate control of everything the app stores, without needing to contact anyone:
- See it: the activity log is displayed in the app.
- Erase it: Clear log in the app, or Android Settings → Apps → Cookie Approval Plus → Storage → Clear storage.
- Stop the processing: turn the service off in Android Settings → Accessibility, or use the master toggle in the app.
- Erase everything: uninstall the app. No residue remains.
If you are in the UK or EEA, the UK GDPR / GDPR still gives you the right to lodge a complaint with your supervisory authority (in the UK, the Information Commissioner's Office, ico.org.uk). If you are a California resident, we sell and share no personal information as those terms are defined by the CCPA/CPRA, and we have no personal information to which a request to know or delete could attach.
Legal basis (UK/EU GDPR): the on-device processing described in §3 and §5 is carried out on your device, under your control, at your instruction, in order to provide the accessibility function you asked for — Article 6(1)(b), performance of a contract with you. Casinos Custom, LLC is not a recipient of that data.
11. How to verify these claims
We would rather you check than take our word for it:
- Confirm there is no network access. Android Settings → Apps →
Cookie Approval Plus → Mobile data & Wi-Fi. There is no permission to revoke and the
data-usage figures stay at zero, because the app never declares
INTERNET. - Watch what it does. The in-app activity log records every tap it made and every one a guard refused.
12. Security
Data is stored in the app's private, OS-sandboxed storage, readable only by this app on a device that has not been rooted. Because nothing is transmitted, there is no data in transit to intercept and no server to breach. The app ships with code minification enabled and is signed with a key held only by Casinos Custom, LLC and Google Play App Signing.
The main residual risk is not to your data but to your device: any accessibility service can, in principle, be tricked into tapping the wrong thing. The safeguards built to prevent that — a list of button labels it refuses outright, apps it never acts in at all, a refusal to press anything too large to be a real button, a limit on how often it will act, and the activity log — are described in the Terms of Service, §5, and in the app's onboarding.
13. Changes to this policy
If this policy changes materially, the revised version will be published at the policy URL before the corresponding app update is released, with the effective date updated. Because the app cannot reach the network, it cannot notify you in-app of a change; please check the policy URL if this matters to you.
Revision history
| Date | Version | Change |
|---|---|---|
| 12 August 2026 | 1.0 | First published. |
14. Contact
Questions, concerns, or a privacy complaint:
Casinos Custom, LLC
- app.dev@casinoscustom.com — general and privacy enquiries
- support@casinoscustom.com — app support
We aim to respond within 30 days.