Cookie Policy
Effective 29 September 2026 · version 1.1
Language. This English text is the authoritative version. We publish it in Türkçe, Deutsch, Nederlands, Polski, Português (Brasil) and Español so that you can read it in the language you use the site in. Those translations are provided for your convenience; if a translation and this English text disagree, this English text governs. That does not take away the protection of the mandatory consumer and data protection rules of the country where you live. You may write to us in any of those languages and we will answer in the same one.
1. The short version
We store nothing on your device when you open rasterless.com. No cookie of ours, no local storage entry, no database — nothing, on any page, in any language. We checked this on the live site rather than assuming it, and the page contacted no third-party server at all while we watched. We re-checked this against the live response headers, on five separate requests, after an earlier draft of this page assumed our CDN set a bot-management cookie: it does not.
Storage only appears once you do something that requires it: change the theme or the language, or sign in. Everything listed in section 3 is there to carry out something you asked for. There is no advertising, no analytics, and no tracking of any kind.
2. What this policy covers
A cookie is a small file a site stores on your device. The same legal rules cover the equivalents — local storage, session storage and IndexedDB — so this page covers all of them and calls them "storage".
3. Everything we store, and when
| Name | Kind | Set by | Why | How long |
|---|---|---|---|---|
| *nothing* | — | — | On page load we store nothing at all. This row is the normal case. | — |
theme | local storage | rasterless.com | Remembers whether you chose light or dark. Written only when you use the theme control. | Until you clear site data |
lang | local storage | rasterless.com | Remembers your interface language. Written only when you use the language selector. | Until you clear site data |
firebase:authUser:… | local storage and IndexedDB | Firebase Authentication (Google) | Keeps you signed in so you can download, and so we can apply the signed-in quota of 60 per hour and 300 per day. The Firebase code is not even loaded until you click sign in. | Until you sign out or clear site data |
| Cloudflare Turnstile | nothing is stored | Cloudflare | Bot check on the free quota. Loaded only after you choose a file, and only if you are not signed in. Produces a single-use token sent with that one conversion. Pre-clearance is off, so no cf_clearance cookie is set. | Not applicable — nothing is stored |
Not present: no Google Analytics, no Meta pixel, no advertising identifier, no A/B testing cookie, no session recording, no cross-site identifier, and no storage set by any party other than the ones named above. When we inspected the live site, the page contacted no third-party origin at all on load.
The Turnstile bot check is live. We use a Cloudflare Turnstile challenge to protect the free quotas. It is not loaded when you open a page: nothing from challenges.cloudflare.com is requested until you choose a file to convert, and it is shown only to visitors who are not signed in. It sets no cookie. Cloudflare issues a cf_clearance cookie only when a site enables the feature Cloudflare calls pre-clearance; ours is off, which is Cloudflare's own default. What the check produces is a single-use token that travels with that one conversion request and is verified once. To run the check, Cloudflare receives your IP address and the signals its script collects in your browser; Cloudflare states that Turnstile "does not access, store, or transmit user communications, form entries, or other page inputs". Our Terms of Service and Privacy Policy say the same thing, so if you ever find them disagreeing, the more restrictive reading is the one we will hold ourselves to.
4. Why we do not show a cookie banner
Under Article 5(3) of the ePrivacy Directive (2002/58/EC), as transposed into the national law of each EU country — in the Netherlands, where we are established, article 11.7a of the Telecommunicatiewet — consent is not required for storage that is strictly necessary to provide the service the user has explicitly requested, or that is used solely to carry out a transmission. The Article 29 Working Party's Opinion 04/2012 (WP194), which the European Data Protection Board carried over, applies the same exemption and is explicit that what counts is what is strictly necessary from the user's point of view, not the provider's — which is the test everything in section 3 is written to meet. The same exemption exists in the United Kingdom under regulation 6(4) of PECR.
Everything in section 3 is in that category, and the ordinary visit is easier still: nothing is stored, so there is nothing to consent to. The theme and language entries record a choice you made by making it. Sign-in storage is necessary because downloading requires an account. Each of them exists because you asked for something: a theme, a language, or an account.
In Türkiye the KVKK sets no separate cookie-consent rule either. Storage that is necessary to deliver the service you asked for rests on KVKK art. 5/2-(c) — necessity for the performance of a contract.
In Brazil the analysis is different, because the LGPD sets no separate cookie-consent rule. There the question is only which legal basis applies: the sign-in storage rests on Art. 7, V (performing the service you asked for). The ANPD's guidance on cookies takes the same view of strictly necessary cookies.
A banner would be required if we used storage that was merely useful to us — analytics, advertising, profiling, cross-site tracking. We use none. If that ever changes we will ask you first, before setting anything, and we will change this page before we change the site.
5. What we do not do
- No advertising cookies and no ad networks.
- No third-party analytics. The site contains an inert analytics hook that is switched off and loads no script; if we ever switch it on it will be a cookieless, privacy-preserving product, and this page will say which one before it runs.
- No cross-site tracking, no profiling, no fingerprinting.
- No selling or sharing of any data, from storage or otherwise.
- No storage set by anyone other than the parties named in section 3.
6. Controlling it yourself
Every major browser lets you block or delete cookies and site data. Because we store nothing on a plain visit, blocking storage costs you very little:
- Blocked, not signed in: the site works. You can convert and preview at the anonymous quota of 10 conversions per hour. You will lose your theme and language choice on each visit.
- Blocked, signing in: sign-in will fail, and downloading needs an account, so you will not be able to download.
7. Where your data goes
What this storage means for your personal data — the legal basis, who processes it, transfers outside the EU, how long it is kept and your rights — is set out in our Privacy Policy.
8. Changes
If we change what we store on your device, we change this page and the date at the top before the change reaches the site, not after.
9. Contact
- Anything about this page, and any data protection request: [email protected]
- General enquiries: [email protected]
---
What changes when the company exists
Nothing on this page depends on the company. The one change already scheduled is a named analytics product in section 5 if we ever adopt one.