IMAGO

Privacy policy

In effect since November 18, 2026.

In short. Your photos are processed on your device and don’t pass through our servers. Your Immich server’s key and address stay on the device. If you create an IMAGO account — which is optional — we keep your email and your edits to sync them between devices, and we delete everything when you delete the account. There are no ads and no analytics tools.

  1. Who is responsible
  2. What stays only on the device
  3. The IMAGO account
  4. Where the data is kept
  5. For how long
  6. Your Immich server
  7. Android permissions
  8. What we don’t do
  9. Your rights
  10. The forum
  11. Supporters programme
  12. This website
  13. Changes

Who is responsible

IMAGO is published by 742 Studio, which is the controller of the data described here. For any privacy question, or to exercise your rights, write to hello@742studio.eu.

What stays only on the device

Without an account, nothing you do in IMAGO leaves the device. With an account, these still stay only on the device:

Android’s automatic backup is turned off for the app, so these keys don’t leave the device that way.

The IMAGO account

The account is for one thing: finding the same work on all your devices. For that, we keep:

DataWhat for
Email and passwordSigning in. The authentication service keeps only a hash of the password, which can’t be turned back into it. The email is used to confirm the account and recover the password; we send nothing else.
Your devices: name, system, registration and last-use datesKnowing where each edit comes from. The name is the device model by default, and you can change it.
Edit recipesThe adjustment values of each photo — exposure, color, curves, masks, crop. They don’t contain the photo.
The fingerprint (SHA-1) of each edited photoRecognizing the same photo on another device, by its content. The fingerprint can’t be used to rebuild the photo.
For device photos you edited or used in a composition: file name, size, date taken and dimensionsFinding that photo on another device while its fingerprint hasn’t been computed yet.
For Immich photos: the photo’s identifier on your serverPointing to the same photo from another device connected to the same server. The server’s address is not sent.
Your libraries: the type, the name you gave them and a fingerprint of the Immich account (HMAC, keyed with your IMAGO account’s identity)Recognizing that two devices are connected to the same library, without knowing where it is or who you are on Immich.
The export recordKnowing that a photo exported to Immich came from an original, so they can be grouped.
Presets, templates, brand kit and composition projectsHaving them on all your devices. They refer to the photos they use, but don’t contain them.
Earlier versions of the records above, up to 20 per recordNot losing an edit when two devices change the same record offline.

The legal basis is the performance of the service you asked for when you created the account (Article 6(1)(b) of the GDPR). The technical security logs described below rely on the legitimate interest in keeping the service secure (point (f)).

Account data is not end-to-end encrypted: it is readable on the server, protected by rules that only let each account read and write its own records. That’s why we keep only what sync needs — never credentials, server addresses, pixels, GPS location or the photos’ full metadata.

Where the data is kept

The account and sync run on Supabase, a database and authentication service from Supabase, Inc., in a project hosted in a European Union region. Supabase processes this data as a processor, on our behalf. Confirmation and password recovery emails are sent through it.

As with any server, the provider logs technical request data — such as the IP address and time — for operation and security.

Communication between the app and the account is always encrypted (HTTPS).

For how long

What is on each device stays there until you uninstall the app or clear its data.

Your Immich server

When you connect IMAGO to an Immich server, the app talks directly to that server, with the key you gave it. We don’t see that traffic and have no access to the server. The photos you export there stay on your server, under its rules. If the address you set up is HTTP rather than HTTPS, the connection to the server isn’t encrypted — that depends on how the server is configured.

IMAGO works with Immich servers, but is not affiliated with the Immich project.

Android permissions

PermissionWhy
Photos and videosShowing the device’s gallery in the library, editing photos, and using photos and videos in compositions. You can give access only to the photos you choose.
Internet and network stateTalking to your Immich server and, if you have an account, syncing when there’s a network.
Foreground service (data sync)Letting two tasks you start finish after you leave the app, with a visible notification while they last: exporting a composition, and sending to your Immich server the photos and videos you share to IMAGO from another app.
NotificationsShowing the progress of those two tasks, and how a send to Immich ended. Asked for the first time you send something shared from another app; without it, the tasks run the same, just without the notification.
Run at startup and keep awakeUsed by Android’s background task system, to resume a pending sync or export.

What we don’t do

IMAGO is not directed at children.

Your rights

At any time, you can:

If you believe your data hasn’t been handled as it should, you can lodge a complaint with the Portuguese data protection authority, the Comissão Nacional de Proteção de Dados (CNPD).

The forum

The forum on this website is public and needs no account. When you post there, we keep:

DataWhat for
The name you choose, the text, the date and, in bug reports, the app version and device you typedShowing the post to everyone who visits the forum. All of it is public.
The screenshots you attach, reduced in size and re-encoded in your browser before they’re sent, which removes their metadata (such as a photo’s location)Showing them with the post. All of it is public. They are deleted together with the post.
A key to delete the post. The server keeps only a hash of it; the key itself stays only in your browser’s local storageLetting you delete what you posted, from the same browser.
A hash of your IP address, made with a secret value, and the time of the postLimiting how much one person can post and upload in a short time, against spam. It is deleted after 24 hours, and the address itself is never stored.

Signing in to the forum with your IMAGO account is optional. If you do, what you post is also linked to the account, so you can edit and delete it from any device, and we keep the name you last posted with, to fill it in next time. The session lasts only while the browser tab is open.

The legal basis is the legitimate interest in running a forum about the app and keeping it free of abuse (Article 6(1)(f) of the GDPR). The forum is kept on the same Supabase project as the account, described above.

Posts stay until you delete them or we do. Deleting your IMAGO account deletes the saved name and the link between the account and your posts, but not the posts themselves — delete them first, or ask us to. We delete posts that are spam, abusive or illegal, or that expose someone’s personal data. To report a post, or to have one deleted that you can no longer delete from your browser, use Report on the post or write to hello@742studio.eu.

If you create a link to a recipe, we keep a copy of that recipe on our servers: its name, its collection and its settings, tied to your account. The recipe itself never includes a photo. Anyone who has the link can see the recipe, without an account, on this website or in the app.

We keep it until you stop sharing it, which removes the copy at once and makes the link stop working, or until you delete your IMAGO account. The legal basis is the performance of the service you asked for (Article 6(1)(b) of the GDPR).

Supporters can also add two images to a link, the same photo before and after the recipe, reduced to a small size and stripped of its metadata (location and camera details). Anyone who has the link sees those images. They are removed when you take them off or stop sharing the link. Anyone can report them from the recipe’s page, without an account: we keep the reason, and a code made from the reporter’s address that cannot be turned back into it, to count one report per person and to limit abuse. Reports are deleted with the link or when the images are changed. Three different reports hide the images until we review them; we remove images that are sexual, violent, hateful or illegal, or that show someone without their consent.

Supporters programme

Supporting IMAGO is optional and unlocks nothing in the app. Supporters can vote on the roadmap, publish recipes to the gallery and enter recipes in the rounds. For that, we keep:

DataWhat for
For support through Buy Me a Coffee: the email you paid with, the amount, the currency, the date, the kind of support (monthly or one-off) and the identifier Buy Me a Coffee gives the paymentKnowing how long you are a supporter, and linking the payment to the IMAGO account with the same email. The payment itself happens on Buy Me a Coffee, which sends us this data; we never receive card details.
For support through the app: the purchase code Google Play gives, tied to your accountChecking with Google Play that the subscription is paid and until when. The payment happens on Google Play; we never receive card details.
The points you give each roadmap item and your votes in the roundsCounting the votes. Each item’s total is public; who voted is not.
Your likes on gallery recipesShowing how many likes each recipe has. The count is public; who liked it is not.
What you publish to the gallery: the title, the author name you choose, the recipe and two images, before and after, reduced and re-encoded, which strips their metadata (such as location)Showing the post. All of this is public.

The legal basis is the performance of the service you asked for (Article 6(1)(b) of the GDPR). This data is kept in the same Supabase project as the account, described above.

Deleting your IMAGO account deletes the link between the payment email and the account, the Google Play purchase codes, your votes, your likes and your gallery posts. Payment records are kept for as long as they are needed to count support and to meet legal obligations. A recipe accepted in a round stays under the CC0 licence you accepted when entering it, and remains available with its author name, even after you delete your account.

This website

This website uses no cookies or analytics tools, and the fonts are served by the website itself. It is hosted on Firebase Hosting, a Google service: Google processes the IP address of each request as a processor, on our behalf, to detect abuse and produce usage statistics, and keeps it for a few months. Firebase Hosting runs on Google’s global infrastructure, so this data may be processed outside the European Union. On the Delete your account page, the email and password you type are sent directly to the account service, only to confirm that you are the account holder, and are not stored in the browser. If you close the language suggestion at the top of the page, that choice is remembered in your browser’s local storage, and nowhere else. On the forum, your name, the keys to edit and delete your posts and the fact that you’ve already seen the forum’s introduction are kept there too, and, if you sign in, the session, in the tab’s session storage until you close it.

Changes

If this policy changes, the new version is published on this page, with the date it takes effect.