AI Act Image Tool

Privacy policy

Last updated 28 August 2026 · Leggi questa pagina in italiano

AI Act Image Tool is a Shopify app that marks products whose photos were generated or edited with artificial intelligence: it writes a metafield, a tag and alt text on the images, and — if the merchant asks for it — stamps a visible watermark on the photos. This page explains what data it handles, where that data sits, for how long, and what the people it belongs to can ask for.

Who handles the data

The data controller is Made in Evolve S.r.l., Via Rosalba Carriera 26, 41126 Modena (MO), Italy, VAT number IT03497200364. For anything concerning this policy: hello@madeinevolve.com.

No data protection officer (DPO) has been appointed: the company does not fall within the cases where the regulation requires one. Requests go to the address above.

What we do NOT handle

The app does not access the store's customer data or its orders. It doesn't even ask for permission to: the permissions requested at installation cover only products, files and the store's languages (read_products, write_products, read_files, write_files, read_locales). Names, addresses, emails, phone numbers and purchase history of the store's customers never reach us and are not kept in any form.

The languages permission serves one purpose only: knowing what language the store's storefront speaks, so that the default alt text is offered in the language of the people buying rather than in ours. It is read-only and concerns no individual.

What we keep about the store

• The store's address and the access credentials issued by Shopify, needed in order to work on the catalogue. They expire and are renewed automatically.
• The marking settings chosen by the merchant: which actions to switch on, the tag and the text to use, how and where to stamp the watermark, and the language we show the app in.
• The history of runs: which products and which library files were marked, when, and what values they had before. This is what makes it possible to undo a run, even only in part. It contains identifiers, titles and alt texts of the products and files.
• References to the images a watermark was stamped on: the identifier of the replaced image and that of the safety copy, both needed to be able to go back. If the merchant uploads a mark of their own to stamp, we keep its name, identifier and address — the file itself stays in their store's library, not with us.

All of this is data about the store and its catalogue, not about people.

The personal data the app actually handles

Two things, and they are worth stating precisely.

IP addresses in the server logs. Every request reaching the app is recorded by the server along with the IP address it came from, as on any website. An IP address is personal data, so those logs are a place where we handle people's data — in practice, the store staff who open the app.

Whatever is written in the support chat. The app includes a chat for asking for help, present on all of its pages. If it is used, the message and any replies stay with the service that provides it (Crisp, see below), together with the store's domain, which the app passes on so that whoever answers knows who they are talking to. If a name, an email or other personal data is typed into the chat, that ends up there: write only what is needed to solve the problem.

They serve to keep the service running and secure: diagnosing faults and recognising abuse. They are kept for 14 days and then deleted. We don't use them to profile anyone and we don't cross-reference them with anything else.

The app uses no cookies to sign the merchant in: access happens through Shopify's session tokens, not third-party cookies. But the support chat does: Crisp writes in the browser to recognise a conversation already under way and keep it from restarting on every page. Without that the chat cannot work.

The interface also loads two things over the network: a typography stylesheet from Shopify's content delivery network (cdn.shopify.com) and the chat script from Crisp's servers. Both, in doing so, see the browser's IP address.

How we handle photos

When the merchant asks for a watermark to be stamped on a photo, the app downloads that photo from Shopify's servers, reworks it and sends it back up. It is the only feature of the app that changes the store's files, and it starts out switched off.

• Photos are never written to disk. They stay in the server's memory for the length of the run — a few seconds per image — and are then discarded. There is no archive of merchants' images on our servers.
• The watermark rewrites the photo's content without deleting anything. The app uploads the stamped bytes to a Shopify staging area and then writes them into the file that was already there: the file keeps the same identifier and the same name, and only the version number in its address changes. No file is deleted, and the photo stays where it was in the product's gallery.
• Before rewriting it, the app uploads a copy of the original photo into the store's file library: it is that copy that makes it possible to undo the run and put the photo back as it was. On undo, the copy's bytes are written back into the original file, and the copy — having done its job — is removed.
• The copies live in the merchant's store, never on our servers. The app removes one only when it undoes the run it was there for; otherwise it does not delete them, and they stay in the file library until the merchant removes them. While the copy exists the watermark can be undone; once it is gone, it cannot.
• If the merchant uploads a mark of their own to stamp, the app holds it in memory for at most ten minutes, so as not to download it again for every photo in the same run.

Why we are allowed to handle this data

The legal basis is performance of a contract (GDPR art. 6.1.b): the merchant installs the app so that it does a job on their catalogue, and without that data the job cannot be done. For the server logs the basis is legitimate interest (art. 6.1.f) in keeping the service working and secure.

We don't handle data for marketing purposes, we don't profile, and we make no automated decisions about people. The app's automatic runs concern product pages, not individuals.

Where the data sits, and who else touches it

On a server managed by Made in Evolve S.r.l. at DigitalOcean, in the Frankfurt, Germany data centre, in a PostgreSQL database not reachable from the internet. Traffic between the merchant's browser and the app always travels over an encrypted connection, with a certificate that is renewed periodically.

Besides us, the data passes through three parties:

• Shopify, which hosts the store, the products and the images. It is both the source of the data and its destination: all the app does is read from and write to it.
• DigitalOcean, which provides the server. It is a US company: even though the data centre is in the European Union, the parent company could in principle be subject to its own country's legislation. The relationship is governed by DigitalOcean's contractual clauses for data processing.
• Crisp, which provides the support chat. It receives the IP address of the browser opening the app, the store's domain, and — if the chat is used — the content of the conversation. It receives nothing about the catalogue, the products or the images: the chat is not connected to the rest of the app.

We do not sell, transfer or share this data with anyone else.

For how long

• Access credentials: deleted immediately when the app is uninstalled. The token is worth nothing any more and keeping it would only be a risk.
• Settings and run history: kept for 48 hours after uninstall — this is the window Shopify allows so that someone reinstalling finds their things again. After that Shopify sends the deletion request and all of the store's data is permanently removed.
• Server logs: 14 days.
• Copies of original photos: they live in the store's library, not with us. The app removes a copy only when it undoes the run it was there for; the others stay until the merchant removes them.
• Support chat conversations: they stay with Crisp's service, because that is where a support history lives. They can be deleted on request by writing to the address below.

What the app writes on the store

At the merchant's request the app writes, on the chosen products: a metafield recording the marking, a tag, and alt text on the images. On library files that don't belong to any product it writes the alt text only, plus the watermark if it is on: metafield and tag live on the product, and there is no product there. If the watermark is on, it rewrites the content of the images with the stamped version, having first put a copy in the store's library. This is the store's data, not ours, and it stays there even if the app is uninstalled. Any run can be undone from the app for as long as it is installed and the safety copy is still in the library.

Security

Traffic to the app always travels encrypted. The database is not reachable from the internet: it accepts connections only from the app's server, and those over an encrypted channel too. Store credentials expire and renew themselves, so a token that happens to be exposed loses its value on its own. Notifications Shopify sends to the app are accepted only if the cryptographic signature is valid.

The rights of the people concerned

Anyone can ask us, at any time and free of charge, for:

• access to their data and a copy of it
• rectification of inaccurate data
• erasure
• restriction of processing
• portability, that is, the data in a format another service can read
• objection to processing based on legitimate interest, that is, the logs

Just write to hello@madeinevolve.com: we reply within 2 working days. Anyone who believes their data is being handled improperly may also lodge a complaint with the Italian data protection authority (www.garanteprivacy.it) or with the authority in their own country.

Requests from the store's customers

If a customer asks the merchant what data is kept, or asks for it to be deleted, Shopify forwards the request to us as well. Since we keep no data about stores' customers, there is nothing to hand over and nothing to delete: the request is confirmed back to Shopify within the required time.

Changes to this policy

If what the app does changes, this page changes with it, and the date at the top says so. When a change affects the handling of data substantially — new data, different retention, a different provider — we flag it inside the app to the merchants who have installed it, before the change takes effect.