Version 1.2 · effective 2026-09-19
init.Dither has no registration, no login and no user profile. There is no email address, no password and no identifier that links what you do in the app to you as a person. Everything below follows from that: we have no way to look up “your” data, because there is no you in our records to look it up by.
Almost everything the app holds never leaves the phone:
Two of those can travel, and only ever into storage you control:
init.Dither sends anonymous usage events to our own analytics server in the EU. It is a self-hosted instance of Aptabase: no third party receives the data, and no advertising or attribution network is involved.
An event carries the name of the thing that happened, the app version, the operating system and its version, your device’s language, and a session identifier that is derived from the time and expires after an hour of inactivity. Event details are limited to the app’s own vocabulary — identifiers and fixed option names such as halftone or pattern. Text you have written is never sent: not palette names, not gallery titles, not custom size labels.
There is no identifier in this data that persists across sessions, and none that could be used to single you out.
If you like a pattern in Discover, the app sends the pattern’s identifier and a random device identifier to our server in the EU. That identifier is generated by the app the first time it is needed and stored on the device; it is not your device’s hardware identifier, is not shared with anything else, and disappears when you delete the app. Its only purpose is to stop the same device liking the same pattern twice, which the database enforces.
Sharing a picture to Discover is entirely optional — nothing is submitted unless you fill in the share sheet and tap the button. When you do, the app sends the picture’s recipe (the settings that generate it), a signature, the engine version, and the name you type.
It does not send the picture. Every copy of the app paints it from the recipe, so no image file ever leaves your device.
The name you choose is public. It appears under your picture in Discover for anyone who opens the app, so choose something you are content to be seen — it does not need to be, and probably should not be, your real name. A random identifier for your installation is stored alongside the submission so that a picture can be traced back and removed if it has to be.
This is the one place where something you send is not anonymous, and it is the only place you are ever asked for a name.
If you report something in Discover, we receive the picture’s identifier, your installation’s random identifier and the reason. A picture reported by three different devices is hidden automatically, and we can remove anything at any time.
The feed is a set of static files served from dither.initmade.com. Requesting them leaves the ordinary trace any web request leaves — IP address, time and app version — in our web server’s access log. Those logs are kept briefly for security and troubleshooting and are not used to build a profile.
If you send feedback from inside the app, we receive what you wrote, plus the app version and platform so the report can be understood. Please do not include anything sensitive in the message — whatever you type is what we get.
On iPhone, the app asks iOS for a push token each time it starts, and sends it to our server together with the app version. Its purpose is to let us tell you about something that affects the app itself — the end of the beta, for example.
A push token names an installation, not a person. It is issued by Apple rather than read off your device, it carries no name, no account and nothing you have made, it changes if you reinstall, and it stops working the moment you delete the app. We keep nothing beside it but the version you are running. Whether a notification ever reaches your screen remains yours to decide, in iOS Settings. The Android app does not do this.
Purchases are handled entirely by Apple on iOS and Google on Android. They are the seller. We never see or store your card details, your billing address or your tax location.
We use RevenueCat to tell the app what you have bought. RevenueCat receives the store’s purchase record together with a pseudonymous identifier generated for your installation — enough to unlock what you paid for, and nothing that names you. Apple’s and Google’s own privacy policies govern the payment itself.
We do not sell personal data, we do not share it for advertising, and we do not use it for automated decision-making or profiling.
| Data | Where | Kept |
|---|---|---|
| Pictures, recipes, settings | Your device only | Until you delete them or remove the app |
| Usage events | Our server, EU | Aggregated; no per-person record to delete |
| Likes | Our server, EU | Until the pattern is retired |
| Shared pictures | Our server, EU (public — recipe and the name you chose) | Until you ask us to remove it |
| Feedback | Our server, EU | Until the issue is resolved |
| Web server logs | Our server, EU | A short period, for security |
| Purchase status | Apple / Google / RevenueCat | Per their own policies |
Our servers are located in the European Union. No personal data is transferred outside the EU by us. Apple, Google and RevenueCat are United States companies and handle purchase data under their own safeguards.
We process the small amount of data described above under legitimate interest (Article 6(1)(f) GDPR): understanding in aggregate how the app is used, keeping the service working, and preventing abuse. Where you choose to send something — feedback, or a like — the basis is your own action in sending it.
The monthly reminder, if you turn it on, is scheduled on your device by the app itself, and nothing is sent to a server to deliver it. The push token described above rests on the same legitimate interest: being able to reach you about the app you installed.
Everything that leaves the app travels over HTTPS. Our servers are kept patched, access to them is restricted, and they are backed up. No system is perfect, but the safest data is the data that was never collected — which is why this policy is as short as it is.
Under the GDPR you have the right to access, correct, delete, restrict and object to the processing of your personal data, and to data portability.
In practice, most of this is already in your hands: the data that matters is on your device, and deleting the app removes it, along with the random identifier used for likes. Because there is no account, we cannot identify which anonymous records came from you, so we cannot single them out for you either.
Pictures you shared are the exception, because they carry the name you chose. Tell us that name, or point us at the picture, and we will take it down.
For anything else, write to us at the address below. You also have the right to complain to a supervisory authority — in the Netherlands that is the Autoriteit Persoonsgegevens.
init.Dither is not directed at children and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.
The data controller for init.Dither is Vladyslav Glogus, an individual operating init.Dither from the Netherlands. For any privacy question or request, write to hello@initmade.com.
If this policy changes in a way that affects you, the version and date at the top of this page change with it, and the app points here. Material changes will be called out in the app’s release notes.