Privacy
Privacy Policy
Last updated: 14 November 2026
This policy applies to the website stempla.at and the Stempla app (iOS and Android). We process personal data exclusively within the limits of the law (GDPR, the Austrian Data Protection Act and TKG 2021).
1. Controller
Raphael Gerhard Bogner (business name: MaYE Media)
Kramlweg 7, 5252 Aspach, Austria
Phone: +43 670 6533244
Email: support@stempla.at
Joint controllership with businesses (Art. 26 GDPR): For feedback after a visit (section 10), abuse protection when stamping (section 11) and push messages that a business sends to its guests (sections 7 and 14), we and the business concerned are joint controllers. We decide how these functions work, which data they store and for how long. The business decides whether and how it uses them, and is responsible for the content of its messages and for what it does in response to feedback and matches. The essence of our arrangement: we inform guests and team members (this policy and notices in the app), obtain consent for push messages, ensure the security of processing and report data breaches in our systems. The business informs its team as their employer and uses the data only for the agreed purposes. We are the contact point for your rights, but you can also exercise them against the business. For all other processing in the app, such as your account, stamps, rewards and billing, we are the sole controller. A business's messages to its guests (including its birthday campaign), feedback and abuse protection only run once the business has accepted our terms, including this arrangement. Our reminders about cards and rewards are not affected.
2. Website hosting & server log files
The website is hosted by Hostinger International Ltd. (registered in Cyprus, EU). When the pages are accessed, the server automatically processes server log files (IP address, time, file requested, data volume transferred, browser and operating system information, referrer URL). This ensures trouble-free operation and security. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR). A data processing agreement is in place with Hostinger; EU standard contractual clauses are used for any third-country transfers.
3. Fonts
The fonts used are served locally from our own server. There is no connection to third-party servers (e.g. Google Fonts), and no personal data is transferred to third parties.
4. Cookies & tracking on the website
The website sets no analytics or marketing cookies and includes no tracking. A cookie banner is therefore not required.
On the home page, the “Participating businesses” page and the business pages we embed a map from OpenStreetMap. Map tiles are only loaded once the map area becomes visible; your IP address is then transmitted to servers of the OpenStreetMap Foundation (see the “Recipients” section). No cookies are set in the process. The legal basis is our legitimate interest in showing the participating businesses clearly on a map (Art. 6(1)(f) GDPR).
Location feature of the map (“My location”): The map can centre on your location. This happens only when you click the “My location” button. Your browser then asks for your permission; using it is voluntary, and you can withdraw the permission in your browser settings at any time. The legal basis is your consent (Art. 6(1)(a) GDPR). Your location is processed only in your browser, to position the map and choose the area with the nearest businesses. It is not transmitted to us and not stored; it is gone once you close the page. Please note: when the map then shows your surroundings, your browser loads the map tiles for that area from the OpenStreetMap Foundation. From your IP address and the coordinates of the requested tiles, it can infer your approximate area.
5. Contacting us
When you contact us by email, the transmitted data is stored to process your request. The legal basis is Art. 6(1)(b) GDPR (pre-contractual/contractual measures) or (f) (legitimate interest). The data is deleted once it is no longer required, unless statutory retention obligations apply. How and when we clear our support mailbox is described in section 18.
On stempla.at/en/for-businesses/ we also offer WhatsApp as a way to reach us. The link only opens WhatsApp once you click it; merely loading our page establishes no connection to WhatsApp and transmits no data there. If you message us on WhatsApp, your phone number and the content of your message are transmitted to WhatsApp Ireland Ltd. and its parent company Meta Platforms, Inc. (USA). We have no influence over that processing; WhatsApp's privacy policy applies. The legal basis is Art. 6(1)(a) GDPR (consent through voluntarily contacting us) or (b). Any transfer to the USA relies on the standard contractual clauses or the EU-US Data Privacy Framework. If you would rather avoid this, please email us instead.
Support from the app: If you tap “Contact support” in the app, your email app opens with a new message to support@stempla.at. So that we do not have to ask, it already contains the app version, the platform (iOS or Android) and the app language. If businesses ask about their access, the business name is in the subject line. You see the text before sending and can edit or delete it. We only receive the message once you send it yourself. The first paragraph of this section then applies.
WhatsApp channel: In the app (business settings and the “What's new” window for owners and managers) we link to our WhatsApp channel. The link only opens WhatsApp once you tap it. Before that, no connection to WhatsApp is made. If you follow the channel, WhatsApp's privacy policy applies as above.
6. AI assistant Hazel on the website
On the “For businesses” and “Help videos” pages we offer Hazel, our AI assistant. She answers
questions about the Stempla app. For Hazel in the app, section 24 applies. The chat is only loaded when you click the chat button;
before that, your browser makes no connection to the chat server. After the click, your browser
loads a script from our chat server chat.mayemedia.at, which transmits your IP
address to that server. The script is hosted by Hostinger (see “Website hosting & server log
files”). Your messages are processed by our chat server at Supabase (server functions, Frankfurt am
Main region; Supabase acts as our processor, see section 16).
We process the messages you type into the chat and the path of the page you are on (e.g. “/de/hilfe/”) so that Hazel can answer more precisely. Please do not enter login credentials, payment details or special categories of personal data (Art. 9 GDPR). To answer, our chat server sends your messages to Anthropic PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA, which generates the reply with the AI model “Claude”. Anthropic acts as our processor (data processing agreement under Art. 28 GDPR including EU standard contractual clauses for the transfer to the USA). Under its own policy, Anthropic deletes inputs and outputs within 30 days, keeping them longer only to enforce its usage policies or where the law requires it. More information: anthropic.com/legal/privacy.
We do not store chat content ourselves: the conversation is kept only in your browser (sessionStorage) and is deleted when you close the tab. Our server logs contain technical metadata only (time, hashed session ID, number of messages, token counts, status) and technical usage events (chat opened, quick question or contact link clicked, an answer rated with thumbs up or down) — no message content, no visited pages and no IP addresses. To prevent abuse (rate limiting), we store the IP address only as a keyed hash and delete it after 24 hours. We delete the metadata after 12 months at the latest. Separately, the edge logs of the server functions at Supabase and Cloudflare contain your IP address for technical reasons; how long they are kept depends on the providers’ settings.
If Hazel mentions a way to contact us (email or WhatsApp), we create a short summary of your request from the conversation so far; this also sends the conversation to Anthropic. If you then click the email link, the summary is prefilled in the message in your email program. For the WhatsApp link, the chat first shows you the summary and asks whether to include it. Only if you choose “Open with text” is it passed to WhatsApp when it opens and inserted into the message; with “Open without text” nothing is passed on. Only you can send it, and you can edit or delete the text beforehand. For WhatsApp, section 5 applies. We do not store the summary.
The chat sets no cookies and does no tracking. The legal basis is Art. 6(1)(b) GDPR (answering your enquiry about our offer, including pre-contractual) or (f) GDPR (our legitimate interest in answering questions quickly). Hazel is an AI; her answers may contain errors. Only information from our team is binding.
7. The Stempla app — data we process
Stempla is a digital stamp card. An account is required. We process the following categories:
- Account data: email address and name (customer or business owner) — required for the account.
- Sign-in data: sign-in via email/password or via “Sign in with Apple” or “Google Sign-In”. Sign-in runs through your device’s account picker or the browser. Apple or Google sends us a sign-in token containing your name, email address and an account ID; Google may also include the link to your profile picture. With Apple, the email address may be an anonymous relay address.
- Business data (for business accounts): company name, address, geo-coordinates derived from the address, logo/images and the stamp-card configuration. After setup is complete, we publish the business’s name, logo, cover image, category, “About us”, location details (address, phone, website, opening hours) and its active stamp cards in the app under “Discover businesses” and on stempla.at. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). Businesses can object to publication at any time by emailing support@stempla.at.
- Stamp card log (for business accounts): when a stamp card is activated or archived, we record when this happened and from which account, even if it happens in the app. This lets us clarify why a card has suddenly disappeared. Only we can see the log. The entries are kept in our internal change log. We delete them after 24 months, at the latest together with the business’s data (section 18). If the acting account is deleted, the link to it is removed. The legal basis is our legitimate interest in operating the service in a traceable way (Art. 6(1)(f) GDPR).
- Loyalty & usage data (for customers): collected stamps, rewards, redemptions, welcome bonuses received, joined businesses and related timestamps. For every stamp and every redemption we store at which business and, where available, at which location it happened. For a group card, this is the venue where it was scanned or redeemed (section 14).
- Optional data (consent): date of birth (for the birthday campaign) and demographic details. These are off by default and only processed after explicit opt-in consent in the optional onboarding step.
- Push token: device token (Firebase Cloud Messaging) for sending push notifications.
- Notification history: stored in-app and push notifications. For each notification the app also stores whether and when you opened it (tapped the push message or the entry in the app’s notification bell). The business that sent a message only sees aggregated figures per message: how many people it reached, what share opened it and how many recipients collected a stamp there in the 7 days after. The business does not see names or a list of who opened it. If a message went to only very few people, these figures may still allow conclusions about individuals. The purpose is an impact statistic for the business. The legal basis is the legitimate interest of the business and our legitimate interest in measuring the success of messages in a data-minimising way (Art. 6(1)(f) GDPR). We delete the history 12 months after sending, and notifications after transferring a paper card after 90 days. We delete messages sent by a business after 24 months.
- Suggesting a business: If you suggest a business in the app, we store its name, town, address and website, your account and whether we may contact you about it. The purpose is winning new businesses (Art. 6(1)(f) GDPR); we only contact you with your consent (Art. 6(1)(a) GDPR). We delete the suggestion after 12 months. If we approach the suggested business, we do not tell it who suggested it and inform it where its data came from.
- Feedback, abuse protection, billing and groups: see sections 10 to 12 and 14.
- AI assistant Hazel (owners and managers only): see section 24.
- Stored locally on the device: session/auth tokens (in secure storage) and app settings.
8. Device permissions — clarifications
-
Camera: used to scan QR codes and, if you choose to, for a
photo of your logo when setting up a business (we then upload the photo like a selected image).
A business’s team uses it to scan guests’ QR codes. From app version 2.1.0, guests can use it to
scan a business’s counter QR code, even before signing in. The app only reacts to Stempla codes
(addresses like
app.stempla.at/b/…) and then opens the business’s page. It reads other codes but does not use them and sends nothing from them; it only shows a notice. When scanning, no images are stored or transmitted; processing happens only locally on the device. - Photos/media library: accessed only when you actively pick a logo/image (upload to Supabase storage).
- Location: When you open “Discover”, the app asks for your location to sort businesses by distance and centre the map. Your position is processed exclusively on the device, is not transmitted to us or to third parties, and is not stored. Granting access is voluntary; without it, “Discover” works fully, just without distance information. Business addresses are still entered manually and converted via geocoding (address → coordinates), see section 13.
9. Anonymous counting of welcome QR codes
When you scan a business’s welcome QR code, we count that visit so we can tell how many people actually complete the path from the web page into the app. All that is stored is:
- the business concerned,
- the stage reached (page opened, app store opened, app installed via the store link (Android only), app opened),
- the operating system in coarse form (iOS, Android or other),
- for visits from the app, the app version as well,
- the point in time.
If you scan the counter QR code with the scanner in the app, this also counts as “app opened”, with the same details.
No identifier that identifies you or your device is stored — no cookie, no device or advertising ID, no link to your account. Nothing is stored on or read from your device. Your IP address is transmitted for technical reasons, as with any web page you open, but it is not stored together with these counters. The figures are only ever evaluated as totals, so drawing conclusions about individual people is impossible.
Protection against misuse of the count. To stop anyone from inflating these numbers, we limit counts per connection. For this we derive a check value (hash) from your IP address using a random value that changes daily. We do not store the IP address itself. The check value is stored separately from the counters and is valid for 20 minutes. After that, we delete it with the next request, at the latest after one day. The legal basis is our legitimate interest in reliable figures and in preventing misuse (Art. 6(1)(f) GDPR).
The legal basis is our legitimate interest in privacy-preserving reach measurement (Art. 6(1)(f) GDPR). The counters are deleted automatically after 400 days.
10. Feedback after a visit
From app version 2.0.0, the app may ask you after a visit how you liked it at the business. The question only appears in the app, never as a push notification. The app asks at the earliest 30 minutes and at the latest three days after a stamp from the team, only from your second visit day at that business, and at most once in seven days. After an answer, it asks again at the same business after 60 days at the earliest. Answering is voluntary.
In doing so we process:
- Stars (1 to 5). We save them as soon as you tap a star. The business receives the stars even if you do not send the feedback afterwards.
- A message to the team (optional, up to 1,000 characters). The business only receives it once you send the feedback.
- Your name (optional), only if you turn on “Send with my name”. This choice is off by default. The business then sees the first name and the first letter of the last name from your account (e.g. “Lena K.”).
- Assignment: your account, the business, the location and the stamp card of the visit, and the times of the visit and of the feedback.
- Control data: when the app last asked you, your choice of “Later” or “Don’t ask again”, and the setting in your profile. This keeps the app from asking too often.
- Google click: whether and when you tapped “Review on Google” (see below).
Who sees the feedback: Within the business, only owners and managers see it. A manager assigned to specific locations only sees feedback for those locations. Staff see no feedback. Feedback goes to the business where the stamp was given; for a group card, that is the venue of the visit (section 14). The business sees stars, message, location and day, but not the time. Without your name, the feedback appears as “anonymous”. Anonymous here means: the business sees no name. We do, however, store the feedback with your account. If a business has few guests, it may be able to guess from the day and location who sent it. For 1 or 2 stars with a message, owners and the responsible managers receive a push notification with the number of stars and the location, without your message and without a name. We (Stempla) see feedback in our admin area in order to support the service. Feedback and stars are not shown publicly.
Google review: Businesses can add a link to their Google review page, for the whole business or per location. If there is such a link for the visit, the app shows a “Review on Google” button, regardless of your star rating and always in the same form. It opens Google’s page in your browser or a Google app. Stempla transmits nothing to Google, not even your stars or your message. Only on the opened page does Google process data, as a separate controller under its privacy policy. We only store that and when you tapped the button. The business sees whether Google was opened after a piece of feedback. Neither we nor the business learn whether you actually leave a review there.
Purpose and legal basis: Businesses learn how guests experienced their visit and can improve what they offer. The legal basis for asking and for stars and message is the legitimate interest of the businesses and our legitimate interest in this part of the service (Art. 6(1)(f) GDPR). The legal basis for passing on your name is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time without giving reasons. A short email to support@stempla.at is enough, ideally from your account’s email address. We will then remove your name from your feedback. The business will then see it as “anonymous”. The withdrawal applies from that point on; what the business saw before is not affected.
Not being asked any more: In your profile you can turn off “Ask for feedback after visits” (on by default). The app then stops asking altogether. “Don’t ask again” in the feedback window applies to that business until you undo it or delete your account. You can undo it in the app: right away with “Undo”, or later on the business’s page with the switch “Ask for feedback after visits”. An email to the address above also works. When you undo it, we delete the entry; the app then asks again under the usual rules. We delete feedback you have sent on request to the email address above.
Retention: A daily automated run applies the following periods:
- After 24 months we delete a piece of feedback’s message, the name sharing and the link to your account. We shorten the time to the day. For the business’s statistics, the stars, day, location, stamp card and Google click remain in pseudonymised form. Pseudonymised means: without a name and without a link to your account. In small businesses, a piece of feedback may still be attributable through the day, location and card.
- “Later” without stars is deleted after 60 days.
- “Don’t ask again” remains until you undo it or delete your account.
If you delete your account earlier, we delete your feedback and the related settings straight away. If the business’s data is deleted (section 18), we delete its feedback as well.
11. Abuse protection when stamping
Since 27 October 2026, every stamp card has a minimum interval between two stamping operations (default: 2 hours). The log and the daily check run on our server and apply regardless of which app version guests and the team use.
From app version 2.0.0, the business can change the minimum interval per card. If the team scans a guest again sooner, the scanner shows when and by which team member the last stamp was given. The team can override this with “Stamp anyway”. Until we switch the block on, nothing is blocked; stamping operations within the minimum interval are then only logged.
Log: We log every override, as well as every stamping operation within the minimum interval that was booked. We store the business, location, stamp card, guest, team member with name, time of the previous and the new stamp, and the number of stamps.
Daily check: Every morning an automated check reviews the previous day’s stamping operations for three patterns:
- three or more stamping operations for the same guest on the same card on one day,
- more than ten stamping operations by one team member for the same guest within seven days,
- a team member using “Stamp anyway” three or more times on one day.
We store a match with the guest, team member, stamp card, day and the stamping operations concerned. A match is only a prompt to take a look. It blocks no one and triggers no automated decision. Within the business only owners see matches, in the app from version 2.0.0; a push notification with the number of matches may accompany this. Managers and staff do not see them. We (Stempla) see the log and matches in our admin area. An owner can switch off the display of matches (“Unusual patterns”) for their business. The business then no longer sees matches and receives no push messages about them. The log and the check continue; only we then use the results, to support the service and check billing.
Notice to the team: From app version 2.0.0, the app shows every team member who is not an owner a one-time notice about abuse protection: after the update and the first time they open the app after joining a team. We store per person and business when the notice was shown, so that the business can prove it informed its team. The legal basis is the business’s legitimate interest and ours in this proof (Art. 6(1)(f) GDPR). The entry is deleted together with the team entry.
Group cards: For a group card (section 14), the owner of the group sets the minimum interval. It applies across the whole group. If a venue’s team scans a guest too soon, it therefore also sees the time and team member of a stamp from another venue of the group. Matches of the daily check belong to the venue where the stamp was given.
Purpose and legal basis: We want to prevent stamps and rewards from being given without a real visit. This protects businesses and keeps billing by regular guests accurate (section 12). The legal basis is the legitimate interest of the businesses and our legitimate interest in preventing fraud and abuse (Art. 6(1)(f) GDPR). Guests and team members are affected.
Retention: We delete the log and matches automatically after 12 months, at the latest together with the business’s data (section 18). The app shows matches from recent days, going back 90 days at most. If a guest deletes their account, we delete their log entries. Matches are kept, but without any link to the guest, because they often concern the team. If a team member is removed or deletes their account, we remove their name from the stamps immediately; it remains in the log and matches until these are deleted after 12 months. If the business only deactivates a team member, the name remains until we delete the team entry 12 months after deactivation.
12. Billing and location confirmations (businesses)
Counting regular guests: Businesses pay according to their number of regular guests (see the terms for businesses). To do this, we count from existing stamp data how many guests were stamped by the team on a further visit day in a month. A stamp counts for the business of the location where it was scanned, so in a group for the respective venue. This applies regardless of the app version. For the ongoing count we collect no additional data about guests; for the monthly closing, see below. Towards the business, the legal basis is the contract (Art. 6(1)(b) GDPR). For evaluating guests’ stamp data, it is our legitimate interest in correct billing (Art. 6(1)(f) GDPR).
Monthly closing: On the first of every month we record the figures of the previous month, for the first time on 1 January 2027 for December 2026. The monthly closing is the record for the invoice. After that, we only change it to correct an error or to reduce the amount after a longer outage of Stempla (waiving the minimum amount or reducing a fixed price pro rata). We store per business or group: name, month, trial or contract phase, number of regular guests and return visits, active locations, prices and amount, and for groups also these figures per venue. If a business deletes its account, we first record the current month and any previous month not yet closed.
Guest-level record: For each monthly closing we store one row per regular guest: a pseudonymous guest ID, the day on which the guest became a regular guest in that month, venue and location, and the number of the guest’s visit days and return visits in that month. It contains no names or email addresses. The guest ID is a shortened check value (HMAC-SHA256) of your account and the venue. We create it with a secret key that only we hold. The same guest has the same ID at the same venue every month, and a different one at another venue. As long as your account exists, only we can link an ID back to your account. We need this record to answer questions about an invoice and to find errors.
What the business sees: Only we see the complete guest-level record; the business has no access to it in the app. In the app, the business only sees the counting as totals, such as the number of regular guests, the number of return visits and the amount, but no names and no list of individual guests. Only owners can retrieve stored monthly closings. In a group, a venue’s managers only see the regular guests of their venue, without the amount (section 14). If a business asks us for a breakdown to check its invoice (see the terms for businesses), it only receives entries for its own business for the month concerned: day, location and a number assigned only for that breakdown, without names and without the guest ID. Because the business knows its own stamps, it may in some cases be able to attribute individual entries to a guest via day and location. The legal basis for this disclosure is the business’s legitimate interest and ours in a verifiable invoice (Art. 6(1)(f) GDPR).
The legal basis for the monthly closing is the contract (Art. 6(1)(b) GDPR); for the guest-level record it is our legitimate interest in correct and verifiable billing (Art. 6(1)(f) GDPR). Where both serve as records for an invoice, statutory retention obligations also apply (Art. 6(1)(c) GDPR). We keep the monthly closing and the guest-level record for seven years from the end of the calendar year to which the month belongs. Then we delete them automatically. This also applies if the guest’s account or the business is deleted earlier. If a guest deletes their account, closed months stay unchanged; the guest ID can then no longer be linked to any account.
Export after the trial or contract ends: Up to 30 days after the trial or the contract ends, a business can request an export of its business data. It contains stamp cards, locations, settings and the stamp history of its business. Guests appear in it only with a pseudonymous ID, without name or email address. Because the business knows its own stamps, it may in some cases be able to attribute individual entries to a guest. The legal basis is the business’s legitimate interest in its own business records (Art. 6(1)(f) GDPR).
Confirming additional locations: If a business activates an additional location and this raises the monthly maximum amount, the owner must confirm this, from app version 2.0.0 directly in the app. If a confirmation reaches us another way (e.g. by email), we enter it in our admin area. In a group, the owner of the group confirms (section 14). As evidence we store: name and email address of the confirming person, time, names of business and location, number of locations and maximum amount before and after, the version of the terms and the app version. If we enter a confirmation, we also store who entered it and, where applicable, a note. The owners of the business and we can see this evidence. Regardless of the app version, we also log when a location was activated, deactivated or deleted, and by which account. This log is also kept; the link to the acting account is removed when that account is deleted.
The legal basis is the contract (Art. 6(1)(b) GDPR) and our legitimate interest in being able to prove the agreement and to establish or defend claims (Art. 6(1)(f) GDPR). Where the confirmation serves as a record for billing, statutory retention obligations also apply (Art. 6(1)(c) GDPR). The evidence is therefore kept even after the account or the business has been deleted. We keep the evidence and the location log while the location is active and the contract runs. After that, they are kept for seven years from the end of the calendar year in which the location was deactivated or deleted or the contract ended, whichever is later. Then we delete them automatically.
Billing emails: From the launch of Stempla 2.0.0, we send the owner of the business, or in a group the owner of the group, the following emails in the language of the account:
- Location confirmed: after every confirmation of an additional location, with the business, location, number of active locations and maximum amount before and after (or fixed price), the month from which it applies, the version of the terms, the time and the name of the confirming person.
- Location deactivated or deleted: with the business, location, time, the name of the person who acted (or “Stempla” if it was us) and the maximum amount from the next month.
- “Your month at Stempla”: after every billable monthly closing, from March 2027 at the earliest, with regular guests, return visits and amount. If Stempla had an outage in the month, the email also states the outage days and the reduction. We check the monthly closing before the email goes out. Owners can switch this email off from app version 2.0.0 under “Billing”; an email to us also works.
The two location emails are evidence of the contract and cannot be switched off. We receive a blind copy of each of these emails at support@stempla.at. On set days (30, 14, 7 and 1 day before a business’s last trial day) we also send ourselves an internal overview of businesses whose trial ends soon and that have no contract yet: name of the business or group, end of trial, the owner’s email address, number of locations, regular guests and current amount. None of these emails contains guests’ names. Sending runs via SMTP through Hostinger (section 16). We keep the content, recipients and sending time of each email for 90 days as evidence and then delete them. The legal basis is the contract (Art. 6(1)(b) GDPR) and our legitimate interest in being able to prove confirmations and to look after businesses in their trial (Art. 6(1)(f) GDPR).
Notice of changed terms: If we change the terms for businesses, we notify the owner of the business, in a group the owner of the group, by email. If a business has not yet accepted the current version, we instead ask it by email to accept it in the app. We receive a blind copy of each of these emails at support@stempla.at. As evidence of the notice and its deadline we store for each business: the version, the date from which it applies, recipient addresses, sending time, subject and text of the email, a checksum of the email, the message identifier (Message-ID) and the mail server’s response. If a termination arrives, we note the date and a short note. None of these emails contains guests’ names or advertising. The legal basis is the contract (Art. 6(1)(b) GDPR) and our legitimate interest in being able to prove the notice and to establish or defend claims (Art. 6(1)(f) GDPR). Like the acceptance of the terms, we keep this evidence for seven years, even if the account or the business is deleted earlier.
13. Converting addresses into coordinates (geocoding)
Businesses enter their address in the app by hand. So that the business appears on the map, the app converts the address into coordinates:
- First, the app uses the operating system’s location service. On iOS the address goes to Apple, on Android usually to Google. This already happens while typing. Apple or Google process the address as separate controllers; a transfer to the USA is possible (section 17).
-
If that finds nothing, the app sends the address directly from the device to the
Nominatim service of the OpenStreetMap Foundation
(
nominatim.openstreetmap.org) when saving or when opening the map to set the pin. For technical reasons Nominatim also receives the device’s IP address and the app version. - When we maintain an address in our admin area, it also queries Nominatim directly.
If none of the services finds the address, the pin is set by hand. Only businesses are affected, not guests. The legal basis is the contract (Art. 6(1)(b) GDPR), as the business should appear correctly on the map. The OpenStreetMap Foundation (St John’s Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdom) processes the request as a separate controller under its privacy policy. For the transfer to the United Kingdom, see section 17.
14. Groups of businesses
From app version 2.0.0, we can combine several businesses of the same company into a group at that company’s request. Venues run by another company, for example a leaseholder, cannot belong to a group. Each business remains a separate Stempla account as a venue, with its own locations, cards and team. One person manages the group (owner of the group). This person is the owner in every venue. Whoever runs a venue usually has the role of manager there. For the group we store the display name, logo, company name for the invoice and the owner, as well as when a venue joined or left. Only the group’s display name and logo and its venues are publicly visible.
Group cards: A group card is valid at all locations of all venues in the group. You collect and redeem in every venue. For every stamp and every redemption we store venue, location, time and team member. The teams of all venues (owners, managers and staff) can see:
- that you have the group card and how many stamps it holds,
- which rewards are open or redeemed,
- when and where stamps were given or rewards redeemed, and which team member gave a stamp.
This also covers stamps and redemptions in other venues of the group. Teams therefore also see the names of team members of other venues who gave stamps. On the group card, the app names all set-up venues where it is valid, including venues not listed in the directory. The minimum interval applies across the whole group (section 11). If a venue leaves the group, the group cards no longer apply there; your stamps are kept.
Welcome bonus on two levels: The owner of the group can set a welcome bonus for the group. You receive it once for the whole group. Each venue can also set its own welcome bonus. We store which welcome bonus you received, when, and via which venue. The group’s welcome bonus is visible to the owner of the group, a venue’s welcome bonus to that venue’s team.
Message to the group: The owner of the group can send a push message to guests of all venues. It goes to guests who visited a venue of the group in the last 365 days (stamp from the team) or received a welcome bonus from the group or a venue. Each guest receives it only once. It only goes to guests for whom “Offers” is allowed for the group itself or for a venue they visited. For each business, your setting for that business counts; if you have not set anything there, your general “Offers” setting counts. If you do not want messages from the group, switch off “Offers” for the group and the venues you visited, or in general. The aggregated impact statistic of the message (section 7) is only visible to the owner of the group.
Group statistics: The owner of the group sees statistics across all venues: totals without double counting, a comparison of the venues, the group card per venue, the number of guests who visit several venues, and the number and average of stars from feedback per venue. The statistics contain only figures, no names. With very small numbers, conclusions about individuals are still possible.
Who sees what:
- Owner of the group: in every venue everything owners see, including feedback and matches of the abuse protection; in addition group cards, messages to the group, group statistics, and the group’s billing and monthly closings including the amount.
- Managers of a venue: in their venue the same as managers of a business without a group, i.e. feedback but no matches of the abuse protection; in addition the guests’ group cards (stamping and redeeming, but not editing the card) and the regular guests of their venue without the amount.
- Staff of a venue: the guests’ group cards with stamps from all venues; no feedback, no matches and no billing.
- We (Stempla) set up groups in our admin area and see their data there in order to support the service.
Splitting an existing business: If, on request, we split a business with several locations into a group, its existing cards become group cards. We assign stamps, redemptions, feedback, matches and logs to the venue of the respective location. We carry over your notification settings for the business, any “Don’t ask again” and open birthday gifts to every venue. So that we can undo the split, we record the previous state in a log that only we can see.
Legal basis: Towards the businesses, it is the contract (Art. 6(1)(b) GDPR). For guests, the group card and welcome bonus are part of the loyalty programme you use (Art. 6(1)(b) GDPR). All venues seeing your group card is necessary for this, because you can collect and redeem in every venue. Teams also seeing the time, place and team member of stamps in other venues is based on the group’s legitimate interest and ours in abuse protection and traceable rewards (Art. 6(1)(f) GDPR). Guests and team members are affected. For the group statistics, it is the group’s legitimate interest in an evaluation across all venues (Art. 6(1)(f) GDPR). For messages to the group, it is your consent (Art. 6(1)(a) GDPR), as with other push messages.
15. Purposes & legal bases
- Performance of contract (Art. 6(1)(b) GDPR): account, digital stamp cards, collecting stamps and redeeming rewards, group cards and welcome bonus (section 14), and for businesses also billing, monthly closing, location confirmations, billing emails, geocoding and groups (sections 12 to 14), offers and invoices in BusinessHub (section 16).
- Consent (Art. 6(1)(a) GDPR): push notifications, including messages to a group (section 14), birthday/marketing campaign, optional demographic data and passing on your name with a piece of feedback (section 10), follow-up on a business suggestion (section 7) and the AI assistant Hazel in the app (section 24). Consent can be withdrawn at any time with effect for the future.
- Legitimate interest (Art. 6(1)(f) GDPR): app security and fraud/abuse prevention (e.g. protection of stamp tokens, minimum interval and daily check, section 11), the aggregated impact statistic of messages for businesses, feedback after a visit (section 10), evaluating stamp data for billing including the guest-level record of the monthly closing and the evidence of billing emails (section 12), the internal “trial ending soon” overview (section 12), and the group statistics and venues’ view of stamps in other venues (section 14), proof of offer acceptance and handling reports from the app (section 16), business suggestions (section 7), the time of last use and the notice before deleting an unused account, and our internal change log, such as the stamp card log (traceability and security, sections 7 and 18), the use of aggregated figures by Hazel, the proof of consent to Hazel and reporting Hazel answers (section 24).
- Request for access (section 23): handling the request and approval under Art. 6(1)(b) GDPR; prospect list, suppression list, source, form counter and proof of consent under Art. 6(1)(f) GDPR; marketing emails and calls only with consent, Art. 6(1)(a) GDPR; email and offer at the end of the trial under Art. 6(1)(b) and (f) GDPR.
- Legal obligation (Art. 6(1)(c) GDPR): retention of invoice data and billing records, such as monthly closings and location confirmations (section 12), and entries on contracts, monthly closings and terms in our change log (section 18).
16. Recipients / processors
We separate providers by their role: some work for us, others are themselves responsible for their processing. Transfers to third countries are covered in section 17.
Providers working for us (processors)
- Supabase (Supabase Pte. Ltd., Singapore; Supabase, Inc. for support and operations) — backend (database, authentication, file storage, edge functions, requests for access and the prospect list). Data is hosted in the EU West (Paris, France) region, including the server function for Hazel in the app (section 24). Hazel on the website (section 6) and Hazel’s technical metrics are kept in a separate project in the Frankfurt am Main region. The server functions sit behind Cloudflare's network (section 23).
-
Hostinger International Ltd. (registered in Cyprus, EU) — hosting of
stempla.at,app.stempla.at(deep-link and authentication callback pages, administration), the chat widget script (chat.mayemedia.at) and BusinessHub (see below); mailboxes and email delivery via SMTP, for example authentication (e.g. password reset, confirmation), billing (section 12), requests for access (section 23) and support. Hostinger uses its own sub-processors, according to its contract including AWS EMEA, Google Cloud EMEA, Cloudflare, MailChannels, Proofpoint, Anthropic Ireland and Vonage. - Google Firebase Cloud Messaging — sending push notifications (device token and message content). Provider: Google.
- Anthropic PBC (USA) — AI model for the AI assistant Hazel on the website and in the app (see sections 6 and 24). Requests are processed by our server functions at Supabase (website: Frankfurt am Main, app: Paris); only the website’s widget script is hosted at Hostinger.
- Cloudflare, Inc. (USA) — Turnstile spam protection in the request for access: for bot detection, Cloudflare works for us according to its Turnstile privacy terms (section 23).
For Supabase, Hostinger, Google (Firebase Cloud Messaging) and Anthropic (Hazel), the data processing terms are part of the provider's contract terms.
Providers responsible for their own processing
- Cloudflare, Inc. (USA) — for improving its bot detection, Cloudflare is itself responsible according to its Turnstile privacy terms.
- Meta Platforms Ireland Ltd. — ads on Facebook and Instagram. In future our ads lead to our page stempla.at/betrieb-werden, no longer to a Meta form. We keep older contacts from Meta forms (section 23). No Meta pixel is installed on our pages.
- OpenStreetMap Foundation (United Kingdom) — geocoding via Nominatim (address → coordinates, see section 13) as well as map tiles in the app and on this website (home page, business directory and business pages). Your IP address is transmitted to the servers of the OpenStreetMap Foundation.
- Apple or Google — the operating system's location service when a business enters its address (see section 13).
- Google — “Google Sign-In”: you sign in with your Google account.
- Apple App Store / Google Play — distribution of the app.
- WhatsApp Ireland Ltd. — if you write to us on WhatsApp (section 5).
- Postal or courier service — shipping the starter pack to businesses (recipient and delivery address, section 23).
- Banks — when a business pays its invoice, the banks involved see the payment data.
Apple: sign-in and iOS push
Apple provides “Sign in with Apple” and the Apple Push Notification service under its developer terms.
Our own systems and payment
BusinessHub (businesshub.mayemedia.at) is our own software and runs at
Hostinger. There we process offers for businesses, acceptance of the terms, the chosen payment method
(SEPA direct debit or bank transfer) and invoices. The legal basis is the contract (Art. 6(1)(b) GDPR),
and legal obligation for keeping invoices (Art. 6(1)(c) GDPR). When an offer is accepted, we store the
typed name, the type of sign-in, IP address and browser identifier as proof. The IP address also appears
in the offer PDF. If you reject an offer, we store the reason, any request for a follow-up, IP address and
browser identifier. The legal basis for this is our legitimate interest in proof of the contract
(Art. 6(1)(f) GDPR).
The form you use to report a bug or request from the app is also in BusinessHub. The app passes on the type of report, app version, role and platform. In addition there are your name and email address (required), title, description and any screenshots. We process your IP address to limit attempts. We send the status of the report to your email address. The legal basis is our legitimate interest in handling reports (Art. 6(1)(f) GDPR). We delete reports 2 years after they are closed. We keep accepted offers with their proof for 7 years from the end of the year, rejected or unaccepted offers for 12 months.
No payment service provider is currently connected for Stempla, and nobody pays online on this website or in the app. Before we use a provider for direct debit, we will name it here. We reconcile incoming payments in BusinessHub with bank statements, including the payer's IBAN.
Development: GitHub and Claude
If a report becomes a development task, its content may end up as an issue at GitHub, Inc. (USA): title, text, answers from selection fields, links to screenshots and a report number. Your name and email address stay in BusinessHub. Older issues may still contain both. Please do not enter any third-party data. The links to screenshots cannot be guessed, but can be opened without signing in. We delete or clean up the issue 2 years after the report is closed. In its data protection agreement GitHub describes itself as a processor for such data and as responsible itself for account and abuse data. If we work on the issue with the AI tool Claude, this content also goes to Anthropic (USA).
Businesses
Within the app, businesses also receive data. For feedback, abuse protection and their push messages they are joint controllers with us (section 1). Businesses where you collect stamps see your name, your profile picture and your stamps, rewards and redemptions. When scanning, the team sees when the last stamp was given and by which team member (section 11). Owners and managers see feedback (section 10). Only owners see the matches of the abuse protection (section 11). Your group card is visible to the teams of all venues of the group; group statistics and messages to the group are a matter for the owner of the group (section 14).
17. Third-country transfers
Database, authentication and file storage are located in the EU (region eu-west-3, Paris). A transfer to a third country may still occur in these cases:
- Supabase: Data stays in the chosen region. Exceptions are account data, support, usage data and the CDN (delivery network). Transfers to and access from Singapore and the USA rely on EU standard contractual clauses.
- Cloudflare (Turnstile): Transfer to the USA. It relies on the EU-US Data Privacy Framework, otherwise on EU standard contractual clauses.
- Hostinger: According to its contract, EU standard contractual clauses apply to sub-processors with a third-country connection.
- Meta: Meta Platforms Ireland is based in the EU. Whether and how Meta transfers data from its services to third countries is governed by Meta as its own controller; in general, Meta refers to its own contract addenda for this. We send no contact data to Meta.
- Firebase Cloud Messaging, Apple, Google: A transfer to the USA may occur. It is safeguarded by EU standard contractual clauses and/or the EU-US Data Privacy Framework.
- Anthropic (Hazel on the website and in the app, sections 6 and 24): Transfer to the USA. It relies on EU standard contractual clauses.
- GitHub (reports from the app, section 16): Transfer to the USA. According to GitHub's contract it relies, where applicable, on the EU-US Data Privacy Framework and/or EU standard contractual clauses. If Claude works on the issue, the contents also go to Anthropic in the USA.
- WhatsApp: see section 5.
The OpenStreetMap Foundation is based in the United Kingdom (geocoding and map tiles). For the United Kingdom, an adequacy decision of the European Commission applies (Art. 45 GDPR). The Commission renewed it on 19 December 2025; it applies until 27 December 2031.
18. Retention
Account data is stored until the account is deleted; thereafter it is deleted or anonymised. A business's data (including its team, stamp cards and its guests' cards, stamps and rewards there) is deleted six months after the trial or contract ends; the owner receives an email 30 days before. Invoice data is kept for as long as the law requires (generally seven years).
Support mailbox: We delete emails to support@stempla.at, such as contact requests (section 5), by hand. Twice a year we clear the mailbox and delete every email older than six months. An email is therefore kept for about twelve months at most. Emails we need to keep longer because of statutory retention obligations are taken out beforehand and kept only as long as required.
Accounts without use: If you don't use Stempla for 24 months, we delete your account including cards, stamps and rewards. 30 days before, we send you an email to your account address. Opening the app while signed in is enough to keep the account. Use means what you do yourself: opening the app while signed in, receiving a stamp, transferring a paper card, redeeming a reward or joining a business (including a welcome stamp). We detect opening when the app signs in or renews its sign-in. Birthday stamps and gifts, notifications and campaigns by businesses do not count as use. We only store the time of your last use, no device data. Accounts that belong to an active team or own a group are excluded. The legal basis for storing the time of your last use and for the email beforehand is our legitimate interest in deleting unused accounts without surprising you (Art. 6(1)(f) GDPR). Deleting them implements data minimisation and storage limitation (Art. 5(1)(c) and (e) GDPR).
Fixed periods: notifications 12 months, messages sent by businesses 24 months, business suggestions 12 months, “Notify me at launch” for a business that does not launch 12 months, birthday gifts 24 months after expiry. We delete team members that a business has deactivated 12 months after deactivation. We delete our internal change log after 24 months, and entries on contracts, monthly closings and terms seven years after the end of the calendar year in which the entry was made. We delete technical data that prevents double stamping after 7 days and failed invitation code attempts after one day.
In addition: for feedback, we delete the message, the name sharing and the link to your account after 24 months; the rest remains in pseudonymised form. “Later” without stars is deleted after 60 days (section 10). We delete the log and matches of the abuse protection after 12 months (section 11). We delete location confirmations and the location log seven years after the end of the calendar year in which the location was deactivated or deleted or the contract ended (whichever is later), even if the account or business has already been deleted (section 12). We delete monthly closings including the guest-level record seven years after the end of the calendar year to which the month belongs, and the content and recipients of billing emails after 90 days (section 12). Like the acceptance of the terms, we keep the evidence of notices of changed terms for seven years (section 12). We delete counters for the AI assistant Hazel after 24 months and daily counters after about a week. We delete a withdrawn consent to Hazel 3 years after the withdrawal. We delete the decision to share figures with Hazel together with the business’s data. We delete reported Hazel answers 12 months after the report (section 24).
19. Deleting your account
This applies to the Stempla app by Raphael Gerhard Bogner (business name: MaYE Media), Kramlweg 7, 5252 Aspach, Austria. You can delete your account in two ways: in the app, or without the app by email.
In the app
You can delete your account at any time directly in the app: guests under Profile → Account → Delete account, businesses under Settings → Delete account (exception for groups, see below). For security, you confirm your sign-in first. Deletion takes effect immediately.
Without the app, by email
Write to support@stempla.at with the subject “Delete account”. Please write from the email address of your account. If that is not possible, state this address in your email. We will then send a request to the account’s address, and you confirm the deletion from there. This way, nobody else can have your account deleted.
We delete the account without undue delay, at the latest within one month of receiving your email or your confirmation, and confirm the deletion to you by email. Only where many or complex requests make it necessary can this period be extended by at most two further months; we will tell you so, with reasons, within the first month (Art. 12(3) GDPR). We delete your email to us like other emails in the support mailbox (section 18).
If your business account belongs to a group as owner (section 14), you do not delete it yourself in the app. Please write to us at support@stempla.at; we first sort out leaving the group.
If you only want certain data deleted and want to keep your account, also write to us at support@stempla.at (section 20).
What is deleted
Deletion removes or anonymises the associated personal data. For a guest account, this mainly means the account, profile and profile picture, stamp cards, stamps, open rewards, notifications, feedback and settings. For a business account, we also delete your access to the business and your consent to Hazel. If you are the owner and the business has no other active team members, we also delete the business with its stamp cards, images and the guests’ cards, stamps and rewards there. Otherwise the business remains and only your access is removed.
What is kept
The following data is kept after deletion, in each case until its period ends:
- Matches of the abuse protection, without any link to your account. A team member’s name remains in the log and matches. We delete both after 12 months (section 11).
- A business suggestion, without any link to your account, until 12 months after the suggestion (section 7).
- Proof of a consent to Hazel: version, times and business, without any link to your account, for 3 years (after a withdrawal: until 3 years after the withdrawal, section 24).
- Reported Hazel answers (question, answer, reason, note) without any link to your account, until 12 months after the report (section 24).
- If you requested a copy of your data: the request and how it was handled, without any link to your account, for 3 years as evidence. We delete the email we sent with the data after 30 days (section 20).
- Entries in our internal change log, for example on stamp cards and sharing figures with Hazel, without any link to your account. We delete them after 24 months, and entries on contracts, monthly closings and terms seven years after the end of the calendar year in which they were made. If the business is deleted as well, we delete its entries with it (sections 7, 18 and 24).
- Acceptance of the terms with name, email address and business as evidence of contract, for 7 years (sections 18 and 23).
- Notices of changed terms with recipient address and email text as evidence of contract, for 7 years (section 12).
- Location confirmations with the name and email address of the confirming person as evidence of the contract, and the location log without any link to your account. We delete both seven years after the end of the calendar year in which the location was deactivated or deleted or the contract ended, whichever is later (section 12).
- Closed months together with the guest-level record and its pseudonymous guest ID, until seven years after the end of the calendar year to which the month belongs. Before a business is deleted, we record the current month and any month still open (section 12).
- Content and recipients of billing emails and of the notice before deleting an unused account, until 90 days after sending (sections 12 and 18).
- Invoice data, for as long as the law requires (generally seven years, section 18).
- If you requested access for businesses: we delete the request together with the account. The periods in section 23 apply to the entry in the prospect list, the suppression list and records of consent.
20. Your rights
You have the rights to access, rectification, erasure, restriction of processing, data portability and objection, as well as the right to withdraw any consent at any time. To exercise these rights, please use the contact details above.
Access to your data: From app version 2.1.0, you can request a copy of all data about your account in the app under Profile or Settings → “Request my data”. You can also write to us. We send the data within one month as a readable page and as a machine-readable file (JSON), and only to the email address of your account, so that nobody else receives it. We delete the sent email with the data after 30 days. We keep the request and how it was handled for three years as evidence (legitimate interest in proving that we fulfilled it, Art. 6(1)(f) GDPR). You can delete your account yourself in the app or by email at any time (section 19).
Right to object (Art. 21 GDPR): Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation. We will then stop processing the data unless we can demonstrate compelling legitimate grounds or the processing serves the establishment, exercise or defence of legal claims. You can object to the questions after a visit at any time in your profile (“Ask for feedback after visits”). We must keep a monthly closing that has already been made, including its guest-level record, as a billing record (section 12).
You also have the right to lodge a complaint with the supervisory authority: Austrian Data Protection Authority, Barichgasse 40–42, 1030 Vienna, phone +43 1 52 152-0, dsb@dsb.gv.at, www.dsb.gv.at.
21. Minors
The app is not specifically directed at children; the age rating in the app stores is set accordingly.
22. Changes to this policy
We reserve the right to amend this privacy policy so that it always complies with current legal requirements. The current version is available on this page.
23. Requesting access for businesses
At stempla.at/betrieb-werden businesses can request access to Stempla. We process the business name, industry, number of locations, requested number of stands, delivery address, your name, email address, phone number, language and the details of your stamp card (card name, number of stamps, colour, symbol, reward, stamp rule, welcome stamps). We use this to check by hand that the business exists and to contact you; for this we search the business name on Google and in the Austrian Chamber of Commerce directory and, if needed, call the publicly listed number. With several locations, we sort out the setup personally if needed. We create your card from the card details when you redeem your link. The legal basis is steps prior to a contract (Art. 6(1)(b) GDPR).
Logo: A logo you choose in the form stays on your device until you submit. If you tick the separate box confirming that you may use it for your business, a smaller, re-encoded copy is sent to us on submission. We store it under a random name in non-public storage at Supabase. Only we can see it, for review. It becomes public only once a person has approved the request and you have opened the link, then like a logo from the app. We do not use it as a reference. We delete the copy after it is taken over, on rejection, when the request is deleted, and otherwise after 90 days. The logo never appears in emails. The legal basis is steps prior to a contract (Art. 6(1)(b) GDPR).
Storage in the browser: So that you can continue later, the form stores your card details, the business name, the number of locations and stands and the current step in your browser's local storage (localStorage). Contact details, address, logo and consents are never stored there. This data only leaves your device when you submit. We delete it after a successful submission; the form discards a draft older than 30 days the next time it is opened. You can also delete it with "Start over" or in your browser settings. The storage serves the service you requested (§ 165(3) Austrian Telecommunications Act). When filled in during an on-site visit, the form stores nothing in the browser.
Origin: If the address you opened contains campaign details (utm_source, utm_medium, utm_campaign, utm_content), we store them with the request, as well as your voluntary answer to "Where did you see us?"; for an on-site visit we record that without this question. This shows us which advertising leads to requests. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR). No cookies and no Meta pixel are used for this, and we do not evaluate other parameters such as click IDs.
Prospect list: We keep requests together with contacts from Meta forms, visits and referrals in an internal list with a history (Art. 6(1)(f) GDPR, legitimate interest in handling enquiries). You receive service emails about your request. If you tick the optional box for tips and offers, we store the wording, version and time with the request (Art. 6(1)(a) GDPR). You can withdraw at any time. We only send advertising once you have also confirmed your address. If you tick the optional box about phone calls, we also store the wording, version and time and may call you on the number you gave (Art. 6(1)(a) GDPR). You can withdraw this at any time too.
Start page, account and one-time link: After approval you receive a one-time link to stempla.at/betrieb-werden/start. It is valid for 14 days; we only store a hash of it. There you sign in or create an account (email and password, where offered also via Google or Apple). The sections on the app apply. The session stays in the memory of the page, the link briefly in the memory of the browser tab. When redeeming, we check the sign-in method and sign-ins on the account for security; in certain cases we replace an existing password with a random value and sign out all sessions. With an existing account we activate access only after about one hour. If the account already has a business or a sign-in method with a different address, we briefly store the account address and sign-in methods with the request until we have decided; we remove them afterwards and when the account is deleted.
Cloudflare Turnstile: To prevent spam we load Cloudflare Turnstile by Cloudflare, Inc. (USA) in the last step of the form. Your browser sends your IP address and technical browser characteristics to Cloudflare. Our server sends the check token and your IP address to Cloudflare to obtain the result. Transfers to the USA rely on the EU-US Data Privacy Framework or standard contractual clauses. The legal basis is our legitimate interest in a form free of abuse (Art. 6(1)(f) GDPR). Turnstile is not loaded before this step. For bot detection Cloudflare works for us; for improving its bot detection Cloudflare is itself responsible (section 16).
Logs: Opening the form and each step (form counter, see below), submitting, uploading a logo and redeeming each send a request through our server functions at Supabase, which sit behind Cloudflare. Their edge logs include your IP address, approximate location data such as the country and browser information. The pages themselves are hosted by Hostinger, where the server log files from section 2 apply. Supabase Auth logs sign-ins. How long these logs are kept depends on the providers' settings.
Abuse protection: To limit mass submissions we store a hash of your IP address (for IPv6 only its front part) with a secret salt and a hash of your email address. We delete these entries after 2 days. The legal basis is Art. 6(1)(f) GDPR.
Suppression list: If you request deletion from the prospect list, we keep hashes of your email address, phone number and any Meta ID so that you are not added again (Art. 6(1)(f) GDPR). These hashes are not directly readable, but can be checked by someone who already suspects the address or number. If someone requests access with a blocked value, no entry is created in the list at first. After a person has reviewed it, a blocked address only receives a confirmation without any advertising. Only someone who opens its link receives further service emails. The block on marketing stays until you consent again and confirm it, the block on the number until you give separate consent, at most until the period below ends.
Contacts from Meta forms: If you filled in a form on Facebook or Instagram in the past, we copy the details you gave there, such as name, business, email address, phone number, city and number of locations, plus Meta's ID of the entry, to the prospect list. The legal basis is handling your enquiry (Art. 6(1)(b) and (f) GDPR). In future our ads lead to stempla.at/betrieb-werden instead of a form.
Help emails: After approval we send service emails about using Stempla, such as help with the setup and notes on the first stamp (Art. 6(1)(b) GDPR). They contain no offers. If you don't want them, tap “Unsubscribe” in the email or just reply briefly. We record the unsubscribe with time and method as proof (Art. 6(1)(c) GDPR). The link carries a random token and neither your address nor your name. We only store a hash of it, for just over a year. Invalid requests are counted per IP address (for IPv6 only the network part) as a salted hash, deleted after 2 days. The emails “Your trial is now running” and “Your trial has ended” are part of the contract and still arrive after you unsubscribe. We no longer send the end-of-trial email that announces the offer once you have unsubscribed.
Directory: Once your business is set up, it appears in the app and on stempla.at. Before the start it can be listed there as “Coming soon”. Guests can then ask to be notified at the start.
Email and offer at the end of the trial: About a month before the trial ends, we send you a factual email about the end of the trial and an offer to continue Stempla. For new requests we point this out in the request. This also happens without the box for tips and offers, unless you have withdrawn, objected or unsubscribed via the link. The offer only concerns continuing Stempla, no other products. This also applies to existing businesses. The purpose is to clarify whether you continue after the trial. We rely on carrying out the trial (Art. 6(1)(b) GDPR) and our legitimate interest in continuing it (Art. 6(1)(f) GDPR). You can object at any time, a short reply is enough. If you don't accept the offer, the trial ends by itself at no cost. On the day after, businesses without a contract get one short email that the trial has ended and what that means. It contains no advertising.
Marketing emails: We only send advertising about your Stempla access with your consent (Art. 6(1)(a) GDPR, § 174 TKG 2021), for example via the optional box in the request. You first confirm your address via a link in an email without advertising. Every marketing email has an unsubscribe link, and you can withdraw informally at any time. We do not send any marketing emails yet. The email and offer at the end of the trial are described separately above. Service emails about the request and access contain no advertising.
Calls: If you tick the separate, optional box about phone calls, we may call you on the number you gave to help with the setup and to present offers (Art. 6(1)(a) GDPR, § 174 TKG 2021). You can withdraw this at any time. We do not record calls. We keep short notes in the history of the entry. If the number belongs to someone else, we end the call, delete the number and note the incident. To check a request we may call the business's publicly listed number, which is not a sales call.
Proof of consent: For each consent and channel we record a hash of the address or number, the source, wording, version and time, the confirmation, and any withdrawal with its time and route. This lets us show what you agreed to (Art. 6(1)(f) GDPR, Art. 7(1) GDPR). The proof remains after a withdrawal and after the entry is deleted, then with hashes only. They are not directly readable, but can be checked by someone who already suspects the value.
Form counter: To improve the form, we count how often each step is opened. We only store daily totals: source and campaign from the link, step, language and count. The language comes from the request header. For this we store neither your IP address nor any identifier, and nothing is stored on or read from your device. The numbers cannot be linked to a person or a request. The request itself appears in the edge logs (see "Logs"). We delete the numbers after 24 months. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR).
Recipients: Supabase (database, sign-in, server functions), Hostinger (website, email delivery, BusinessHub), Cloudflare (spam protection, Supabase's network), a postal or courier service (recipient and delivery address when shipping the starter pack). Section 16 sets out the roles. From Meta we only receive contacts from older Meta forms, and we pass no contact data on to Meta.
Terms: By submitting, you confirm the terms for businesses. We store the version and the time with the request. When you redeem the link, we record the acceptance with your name, your email address and the name of the business (Art. 6(1)(b) GDPR).
Retention: We delete requests and prospects without a deal after 12 months without activity. We delete redeemed requests and the prospect entry 12 months after the end of the trial or contract; if you delete your account before that, the request is deleted too. We delete email queues after 90 days, limit counters after 90 days and abuse-protection hashes after 2 days. We clear phone number and delivery address 12 months after the end of the trial or contract, unless a starter pack is still open. We delete suppression list entries 5 years after the last match, and a new match extends this period. We keep proof of consent for as long as the consent applies and for 3 years afterwards. We delete logos after 90 days at the latest.
24. AI assistant Hazel in the app (businesses only)
This section applies from app version 2.1.0. Owners and managers of businesses can ask Hazel, our AI assistant, questions in the app. Hazel can also translate texts into English (“Translate automatically”) and suggest messages to guests (“Suggestions from Hazel”). Staff and guests do not use Hazel. Hazel is an AI and can make mistakes. Before first use, the app shows each account a notice and asks for consent.
What we send to the AI provider: To answer, the following is sent via our server function at Supabase (section 16, Paris region) to Anthropic PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA, provider of the AI model “Claude”:
- Your question and the conversation so far, at most the last 10 messages (yours and Hazel’s) with no more than 8,000 characters in total. A single question may be at most 1,000 characters long. We automatically replace email addresses, phone numbers and IBANs beforehand. We cannot reliably detect names. Please therefore do not enter data about guests or other people.
- Your role, the app language, the screen you are asking from, today’s date, whether the figures are shared and whether you are asking in the group view.
- Only if the figures are shared: aggregated information about the business, as also shown in the app’s statistics and only from the same amount of data. These are stamps, guests and rewards in the period, stamps per weekday, hour, month and location including the location names, figures per stamp card including name, reward and stamp rule, typical intervals between visits and the number of guests who have stayed away for longer, the impact of the welcome bonus and of sent messages with their titles, the number of locations and team members, the month’s billing, and the number and average of stars from feedback. In addition, age and gender groups of guests who have consented to this, only as totals, only from 10 such guests and without groups below 5. The figures are available for the whole business, one location or one calendar month. In the group view, they are added per shared venue, together with the names of the other venues.
- If you use “Translate automatically”: the German text of the respective fields. Here too, we replace email addresses, phone numbers and IBANs beforehand and put them back afterwards.
- If you use “Suggestions from Hazel”: the business’s name and category, the occasion you chose and your note on it. These helpers do not send any of the business’s figures.
What is never sent: Hazel receives no names, email addresses or IDs of individual guests and no feedback texts. We do not state guest numbers below 5, nor weekdays and hours with fewer than 5 stamps, nor the average of stars with fewer than 5 pieces of feedback.
Signing in to the server function: With every request, your app sends its sign-in token. The server function passes it on to our database (Supabase, section 16). There we check your role, your consent, the business’s access and the limits. The server function does not store the token.
What we store: We do not store questions, answers, translations or suggestions, unless you report an answer (see below). The conversation is kept only in your app’s memory until you close it or switch account or business. We store:
- Your consent: account, version of the notice, time, business and any withdrawal with its time. The entry remains as evidence after a withdrawal; we delete a withdrawn entry 3 years after the withdrawal. If you delete your account, we keep only the version, the times and the business, without any link to your account, for another 3 years (after a withdrawal: until 3 years after the withdrawal). This lets us prove that consent was given (Art. 7(1) GDPR). The legal basis is our legitimate interest in this proof and in defending against claims (Art. 6(1)(f), Art. 17(3)(e) GDPR).
- The decision on sharing the figures: business, on or off, account and time. It remains as long as the business exists, and we delete it together with the business’s data (section 18). Each change is also recorded in our change log, which only we can see. We delete these entries after 24 months, at the latest together with the business’s data. If the account is deleted, the link to it is removed in both.
- Per business and month: number of questions, token counts, estimated costs and time of the last question. Separately, per business and month, the number of translations and suggestion rounds. If we grant a business additional questions, we store the number, month, who and when. We delete these counters after 24 months, at the latest together with the business’s data.
- Per account and day, the number of questions. We delete these counters after about a week.
- If you report an answer from Hazel: your question, the answer, the reason for the report and your comment if you write one, plus your account, the business and the time. We use this to check the quality of the answers and to detect abuse. The legal basis is our legitimate interest in this (Art. 6(1)(f) GDPR). We delete the report after 12 months, at the latest together with the business’s data. If the account is deleted, the link to it is removed.
- For messages to guests: whether you used a suggestion from Hazel for them. We delete this information together with the message (24 months, section 18).
- For each request in progress, briefly a placeholder with account, business, day and type of request (question, translation or suggestion). This way, a request without an answer does not count. We delete it with the answer, otherwise after about a day at the latest.
- Technical metrics as for the website chat (section 6), without content, for 12 months, in the database of our chat service at Supabase (Frankfurt am Main). To limit abuse, we store the IP address there only as a hash with a secret key and delete it after 24 hours. The edge logs of the server functions contain your IP address for technical reasons; how long they are kept depends on the providers’ settings.
- On your device: whether the Hazel button is shown, where it sits and whether you have already seen Hazel’s introduction.
At the AI provider: The provider processes the data as our processor and deletes inputs and outputs within 30 days. If its safety systems flag a chat as a possible violation of its usage policy, it may keep inputs and outputs for up to 2 years and classifications for up to 7 years. By default, the content is not used to train its models. The transfer to the USA relies on the EU standard contractual clauses (section 17).
Who decides about the figures: Whether Hazel may use a business’s figures is decided by the business’s owners or the group owner, and can be changed at any time under Settings → Hazel. The decision applies to the business’s whole team. In a group, each venue decides for itself. In the group view, Hazel only uses the figures of venues that have shared them.
AI label: Texts that Hazel generates may carry an invisible, machine-readable label from the model provider that marks them as AI-generated. In addition, for messages to guests we store whether a suggestion from Hazel was used (see above).
Hazel decides nothing: Hazel only provides information and suggestions. Hazel changes nothing in the app and makes no decisions about people.
Legal basis and withdrawal: The legal basis is your consent (Art. 6(1)(a) GDPR). You give it with “Agree and continue” in the notice before first use. You can withdraw it at any time in the app under Settings → Hazel with “Withdraw consent”, with effect for the future. Hazel is then no longer available to you; the rest of the app stays the same. For the use of the aggregated figures, the legal basis is the business’s legitimate interest in information about its business (Art. 6(1)(f) GDPR).