When you configure a personalized deck, you upload photos from which we create card artwork. We use Google's Gemini API (processing also in the USA) and Microsoft Azure services (West Europe region, Netherlands) for this. Before card creation starts we obtain your explicit consent to this processing via a separate checkbox; you can withdraw it at any time with effect for the future (email to hello@keepsakedeck.com or an erasure request via /en/datenschutz/anfrage).
5.1 Face detection on your device
On the photo step, our site finds the faces in your photos directly on your device, in your browser. Your browser loads the detection model (MediaPipe BlazeFace) from our own server; your photos do not leave your device for this. For a group photo, your browser cuts out one crop per face. Nothing is uploaded until you start card creation on the consent step, and then only the photos or crops you assigned to the figures. Faces and photos you do not assign to a figure stay on your device. If we cannot start card creation after that (for example because of a daily limit), the photos already uploaded stay stored until they are deleted automatically after 7 days at the latest.
Azure Face API (older parts of the configurator only): The Azure Face API is used only for face localization. Technically, we call the service with the parameters `returnFaceId=false` and the detection model `detection_03`. The service returns only rectangle coordinates (`faceRectangle`) indicating where a face is located in the image. No biometric template, no FaceID and no persistent identifier is created or stored at Azure. The image transits Azure West Europe solely for this localization.
Legal basis: Art. 6(1)(b) GDPR (performance of the contract: producing the ordered deck) and your explicit consent (Art. 6(1)(a) GDPR, as a precaution Art. 9(2)(a) GDPR), which we obtain via a separate checkbox because the legal classification of facial images sits at the border of biometric data. In fact, no biometric templates are generated on our side.
Group photo in the earlier version of the photo step: if you use "Upload a group photo" there, we send the chosen photo to Azure West Europe for face localization right there, i.e. before the consent step. We say so immediately before you choose the photo. We do not store this photo; only the face crops come back, and until you confirm them they stay in your browser only. The legal basis is Art. 6(1)(b) GDPR (steps taken at your request prior to entering into a contract). No identification takes place, so in our assessment Art. 9 GDPR does not apply. Further processing to create the cards only happens after your consent in the consent step.
5.2 Image generation via Google Gemini and Azure OpenAI
To generate the court cards (King, Queen, Jack, Joker) we transmit your photos or the face crops located in them together with a prompt and style references to Google's Gemini API (Google LLC, USA; EU contracting entity: Google Ireland Ltd.). Under the paid API Google processes these contents solely to provide the service and does not use them to train its models; processing may take place on servers in the USA (third-country transfer based on the EU-U.S. Data Privacy Framework and standard contractual clauses, see section 6). For image analysis (e.g. pet detection) we use Azure OpenAI (`gpt-4o`) in the West Europe region; Microsoft does not use your content for training. Number cards and aces contain no personal data and are produced without AI.
Legal basis: Art. 6(1)(b) GDPR (performance of the contract) and your consent under section 5.1.
5.3 Automated decision-making (Art. 13(2)(f), Art. 22 GDPR)
The card artwork is generated automatically from your uploads and your inputs. This automated processing does not produce any decision with legal effect and has no similarly significant impact on you within the meaning of Art. 22(1) GDPR. It merely produces the graphical output of the service you ordered. You review each figure before ordering and can reject it or have it regenerated.