Cookie Policy
Last updated: 18 August 2026
Why there is no cookie banner. PintaMinis sets no analytics, advertising or tracking cookies — none at all. Everything listed below is strictly necessary to sign you in and to keep the service from being abused. Under the ePrivacy Directive and Spain's LSSI (Art. 22.2), strictly necessary storage does not require consent, so asking for it would be theatre. If tracking is ever added, a real consent banner will come with it.
What is actually stored
The list below was produced by auditing the running application, not copied from a template. "Cookies" here covers the equivalent browser storage technologies too, since the law treats them the same way.
Cookies
| Name | Set by | Purpose | Lifetime |
|---|---|---|---|
_GRECAPTCHA |
Google (www.google.com) |
Anti-abuse. Lets reCAPTCHA Enterprise tell a genuine app apart from an automated script, which is what stops someone scraping the recipe database or running up the hosting bill | Up to 6 months |
That is the only cookie. There are no others, first-party or third-party.
Local storage
| Key | Purpose |
|---|---|
FlutterFire-[DEFAULT]-recaptchaSiteKeyFlutterFire-[DEFAULT]-recaptchaType |
Remembers which anti-abuse provider is configured, so the check does not have to be renegotiated on every page load |
_grecaptcha |
Working data for the reCAPTCHA library |
Session storage
| Key | Purpose |
|---|---|
flutterfire-flutter-fire-* |
Version markers for the Firebase libraries in use. Cleared when you close the tab |
IndexedDB
| Database | Purpose |
|---|---|
firebaseLocalStorageDb |
Keeps you signed in between visits. Without it you would have to enter your password every time you opened the app |
firebase-app-check-database |
Caches the anti-abuse token so a fresh check is not needed on every request |
firebase-heartbeat-database |
Records that the Firebase libraries were used, for Google's own service diagnostics |
Cloud Firestore also keeps an offline cache of your own data in the browser, so the app keeps working without a connection and syncs when the network returns. That cache holds only data your account already has access to.
What is not there
- No Google Analytics, and no analytics of any other kind.
- No advertising or remarketing cookies. The AdMob integration in the source code is disabled and not compiled into the published build.
- No social network pixels, no cross-site tracking, no fingerprinting for profiling.
- No cookies from Cloudflare, which fronts the site as a CDN and firewall without setting any.
Controlling it
You can clear or block this storage from your browser's settings at any time. Be aware of what that costs: clearing it signs you out, and blocking it outright will prevent sign-in from working at all, because the session cannot be remembered and the anti-abuse check cannot complete.
Google publishes its own information about reCAPTCHA in its Privacy Policy and Terms of Service.
Related
For what happens to your data once it reaches the server, see the Privacy Policy.