← Auto AI Agency

Privacy Policy

What we collect

24 of the 49 apps we advertise run entirely in your browser. Everything you enter or make in them — quiz answers, names, notes, drawings, your best times, a virtual pet — is processed on your own device and stays there. No account is required anywhere, and in these apps nothing you enter is kept or recorded by us. That is true of these 24 apps, a complete list rather than a sample: Chess, Solitaire, Isobath, Lexicon, Lumesweep (Minesweeper), Tilewright, Backgammon, Dominoes, Crownfall (Checkers), Fiveaside, Acecourt (Tennis), Sweepmark, Driftline, Oche, Gridmark, Bugsquash, Yearmark, Tierforge, Countmark, Tapedeck, Inkwell, Focus Fern, Handlelabel and Dewkeep. The one exception is the share card in Countmark: if your browser cannot draw the download locally, the date you picked is sent to our own stateless image renderer only to produce the PNG.

The other 25 apps send a small record to our own server, because the number they show you cannot be worked out on your device alone: a day’s tally, the crowd’s split, a percentile or a leaderboard position lives on the server side. Those apps are Baloney, Bracketday, Brainrank, Cipherday, Claymark, Daymint, Debutcover, Deskforge, Flacon, Gutcheck, Hivemind, Holdout, Loomlock, Maze of Breth, Nightword, Passportrait, Prismdrift, Pulsedrop, Rainline, Saltfire, Thornwall, Tidewords, Trailmark, Vexil and VibeCard. What leaves your device is the material of that app’s own feature — an answer, a score, the archetype you landed on, the flag or perfume you just designed, the parks you ticked off, a cipher you built to share — together with the date, and in some cases an anonymous per-play id so the same run is not counted twice. Never an account, an email address, a name you typed as identity, or an advertising identifier: nothing on our side can be tied back to you as a person, and we do not attempt to rebuild one person’s session out of the counts.

Where an app has one, we also record anonymous usage events — that a round was started, finished or shared — to see which apps are worth keeping. They carry no account and no identifier that follows you to another site.

On the catalogue site we use Google Analytics (GA4) in aggregate: which page was viewed, which site or search sent you here, and coarse information about the device and approximate location your browser reports. It may set cookies so a return visit is attributed to the same browser; it does not know who you are, and we do not combine it with anything else we hold. The tag travels with the interactive site rather than with each document, so a page served to you as a plain document — an app article, the guide, this policy — arrives without it and is counted only if you reached it through the site itself.

The aggregate counts are kept for as long as the feature that uses them keeps running — a “today’s tally” that forgot yesterday would not be one. Because they are counts rather than records, we cannot separate a single visitor’s contribution from the total; keeping nothing that identifies you is what makes that acceptable.

Advertising & cookies

Some of our pages show ads via Google AdSense — the catalogue home page in particular. The guide, article and policy pages of this site carry no ads at all. Where ads do appear, Google and its partners may use cookies (including the Google DoubleClick DART cookie) to serve ads based on your visits to our sites and others.

Consent is handled by Google’s certified consent-management platform, configured on our AdSense account and shown by the ad code where it applies. We deliberately do not run a cookie banner of our own, because a second banner on top of that one helps nobody. This catalogue site’s own build also ships Google’s consent-mode defaults, which are recorded on the page before anything else runs: ad storage, ad user data and ad personalisation aredenied by default, and analytics storage is denied by default for visitors in the EEA, the UK and Switzerland while it stays on elsewhere. That region list is the one this catalogue site ships, and it is the only build this sentence speaks for. Each app we publish is a separate build with its own analytics configuration: where an app’s own defaults differ from the catalogue’s, it is the app’s configuration that applies to you there, not this page’s. Before a choice is made, those defaults mean cookies are not being used to personalise an ad for you. Where a consent message is shown, the choice you make there updates those signals before any advertising cookie is set.

Legal basis, and how long cookies last

Why we are allowed to process this. Personalised advertising and the analytics described above are based on your consent. That is what the consent-mode defaults implement: ad storage, ad user data and ad personalisation start denied, so nothing that would personalise an ad is stored until you answer the consent message, and the choice you make there is what turns it on. Serving an ad that is not personalised and stores nothing about you rests on our legitimate interest in keeping the sites free to use, as do the anonymous counts our own apps keep — knowing whether a feature is used at all is what tells us what to keep building. We do not need your consent for the counts, because they identify nobody and no decision about you is taken from them. Nothing here rests on your entering into a contract with us: there is nothing to buy and no account to create. Nothing here is used to make an automated decision about you.

How long things last. The aggregate counts are kept for as long as the feature that uses them keeps running, as described above. The cookies that advertising and analytics rely on are set and timed by Google rather than by us — Google publishes the lifetime of each of its cookies in its own documentation — and they are stored only while your consent stands. Clearing cookies in your browser, which the list above tells you how to do, or withdrawing the choice you made in the consent message, ends them at once rather than waiting for them to expire.

Your rights (GDPR / CCPA)

If you are in the EEA, the UK or Switzerland, or in California, you have the right to ask what personal data we hold about you, to have it corrected, and to have it deleted. In our case the honest answer to “what do you hold?” is almost always nothing: in the 24 device-only apps your data never leaves your browser, and the records the other 25 do send reach us as aggregate numbers with no record of who contributed. You can clear anything an app did keep on your device by clearing your browser’s data for the site.

Those three are not the whole list. You also have the right to ask us torestrict what we do with your data while a question about it is open, to object to processing we base on our own legitimate interests — the anonymous counts described above are the only thing in that category — and to receive the data you gave us in a portable, machine-readable form or have it sent to someone else. On this site the last of those is usually the shortest possible answer, because there is no account and no profile to export; where an app did send a record, you can ask us to delete it and we will. If you think we have got any of this wrong, you have the right tolodge a complaint with a supervisory authority: ours is the Croatian Agency for Personal Data Protection (Agencija za zaštitu osobnih podataka, the AZOP), which is where the studio is established, and you may equally complain to the authority in your own country of residence, place of work, or where the problem happened. Complaining to a regulator costs you nothing and you do not need to contact us first, though we would rather you did — the address is at the bottom of this page.

We answer every request within 30 days, and we do not charge for the first one. To keep the answer honest we may ask you to show that a request is really yours, which on a site with no accounts generally means very little: because we hold no record that ties a person to a run, the usual truthful answer to “what do you hold about me?” is “nothing we can find you by”.

We do not sell personal information. Under California law, using personal information for cross-context behavioural advertising counts as “sharing” even when nothing is sold, and personalised advertising can fall into that category. Where that right applies to you, you can opt out through the consent message, through Google Ads Settings, or by blocking third-party cookies in your browser. We have no per-visitor opt-out control of our own to offer you, and we would rather say so plainly than point you at a switch that does not exist.

Children

Our apps are general-audience and not directed at children under 13.

Contact & data rights

To exercise your GDPR/CCPA rights, opt out of personalised ads, or ask a privacy question, email auto-ai-agency@quantum-solutions.hr. We respond to verified requests within 30 days.