Skip to content
pperk. eats
How it worksFeaturesWith friendsPrivacyCities
Sign inStart rolling
DeutschEnglish
Contents1. Controller2. In short3. What we process and why4. Recipients and processors5. Transfers outside the EU6. How long we keep data7. Your rights8. No automated decisions9. Children10. Changes

Privacy policy

Last updated: 12 October 2026 · Deutsche Fassung

1. Controller

The controller for heyperk.app and Perk Eats (eats.heyperk.app) under the GDPR is:

Hrishikesh Jadhav
Postal address to follow
Germany
Email: hello@heyperk.app

No data protection officer is appointed. For privacy questions, write to hello@heyperk.app.

2. In short

  • Perk Eats shows you places nearby. That needs your location, which stays saved in your browser and only goes to our server to search.
  • With a heyperk account, Perk Eats remembers your swipes (the place's id and what kind of place it is, not its name or address), the places you pick and your group rolls.
  • Analytics cookies only with your consent: with “Accept”, PostHog (servers in the EU) counts how Perk is used. Without consent we only count anonymously and store nothing on your device. No ads; we don't sell data.
  • AI providers only get facts about places and, if you type one, your mood text. They may not train on it.
  • Paid plans go through Stripe. We never see card details; all we keep is ids, the plan and its term.

3. What we process and why

Visiting the website and app

What
IP address, time, address requested, browser identifier (server logs).
Why
To serve the pages and spot errors and abuse.
Legal basis
Legitimate interest in running the service securely (Art. 6(1)(f) GDPR).

heyperk account (sign-in)

What
Email address, single-use 6-digit sign-in codes, sign-in times, your follow-up email setting.
Why
So you can sign in without a password and your data is the same across heyperk apps.
Legal basis
Contract or steps before one (Art. 6(1)(b) GDPR).

Location and place search

What
Your device's coordinates when you use “Use my exact location” and allow it in your browser, or a place you type. The location is saved in your browser and sent to our server with each search. Our server uses it to look up places at Google Places and OpenStreetMap, the country at OpenStreetMap Nominatim (rounded to about 10 km) and the weather at MET Norway (rounded to about 10 km). A place you type goes to Nominatim.
Why
To show places near you, distances, walking times, the right delivery apps and weather-based dice.
Legal basis
Contract (Art. 6(1)(b) GDPR). Your browser only shares the device location with your permission, which you can withdraw in your browser settings at any time.

Swipes and taste (with an account)

What
For each swipe, linked to your account: the place's id (for example the Google place id), yes or no, vibe, cuisine, price level, and whether the place has a terrace, live music, cocktails or is a chain. Not the place's name or address, and not your location.
Why
So Perk Eats shows you places that suit you more often and can show you your taste.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Picked places, passport and “Did you make it?” (with an account)

What
The place you picked (id, name, vibe, cuisine), the mode, the label of your location, the time, and your answers (did you go, would you go back). Partner restaurants see monthly counts for their own place (picked, went), never who.
Why
For your passport, the next-day question, and so places you wouldn't go back to don't come up again.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Next-morning email (with an account)

What
Your email address, the name of the place you picked, a link to answer.
Why
To ask once per picked place whether you went.
Legal basis
Legitimate interest in following up on your own choice (Art. 6(1)(f) GDPR). Turn it off any time under “You” or with the link in every email.

Group rolls (with an account)

What
The name you show in the group, your membership, your votes and the five places in the roll.
Why
So everyone in the group swipes the same places and sees what matches. Other members see your name and votes.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Diet needs and allergies

What
What you choose under “Diet & allergies” (vegetarian, vegan, gluten-free, lactose-free, halal, kosher). It stays in your browser. Only when you tap “Add my needs” in a group roll do we store it with your membership; the others then see which needs there are in the room, not whose.
Why
So Perk shows places whose listing fits, and a group takes everyone into account. Perk only repeats what a listing says and never says a place is safe for an allergy.
Legal basis
In your browser: contract (Art. 6(1)(b) GDPR). In a group roll: your explicit consent (Art. 9(2)(a) GDPR), because such details can reveal health or religion. Withdraw any time with “Stop sharing my needs” or by leaving the room.

Places from TikTok and Instagram links

What
The link you paste goes to our server. It asks TikTok or Meta (Instagram) for the post's caption and account name, and uses them and your coordinates to search Google Places for the place. With an account we store only the id of the place you choose and whether it came from TikTok or Instagram. We don't store the link or the caption.
Why
So you can keep places you've seen and roll from them later.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Founders in Regensburg and Berlin (with an account)

What
When you roll in Regensburg or Berlin while signed in, our server checks which of the two cities the coordinates are in and compares them with the approximate location of your IP address from Vercel's request headers (country, latitude and longitude); it stores neither. It stores the city, your founder number there (1 to 100 in each city, one stamp per person), your account and the time. Some of the first testers get a “Day one” stamp from us by hand; for that we store your account, the time and a place we type in ourselves (such as “USA”), never a location from the app.
Why
For the numbered stamp in your passport and Perk Plus at no cost. First come, first served; there is no draw.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Offers from partner restaurants (with an account)

What
An offer has rules: days, hours (Berlin time), a pause per guest (30 to 365 days) and optionally “first visit only”. When you pick a partner restaurant on your own and have a Plus account, we store for that pick, linked to your account: the id of your visit, the offer shown, a code for staff (PERK-XXXX), and when the code was shown and when it was marked used (by tapping “Used it” or in your answer at the next check-in). Only Plus accounts get a code; with a free account you see the offer locked and nothing is stored for it. Whether the pause is running or this is your first visit is checked by the database from those stored codes and your picked places (when you last got a code from this restaurant; whether you have picked the place before). Partners see only monthly counts from this, never who. For restaurants we show counts from the swipes and picks of guests signed in with a heyperk ID, only as totals; values under 5 are not shown exactly.
Why
To show you the offer after you have picked, to keep to its rules (pause per guest, first visit) and to count how often it was shown and used. And, for restaurants (also before they join): totals showing how often signed-in guests saw, liked, picked and visited their place. The offer only appears after your pick and doesn't change which places you are shown.
Legal basis
Contract (Art. 6(1)(b) GDPR), to provide the offer. For the totals shown to restaurants: legitimate interest (Art. 6(1)(f) GDPR) in showing restaurants aggregate, non-identifying counts; values under 5 are not shown exactly.

Contact details of partner restaurants

What
Name and email address of the contact person of a partner restaurant or of a place we approach, the place's business address and Kiez, the status (prospect, live, paused, ended) and a secret link to the report. The report shows counts only, no individual guests. The restaurant's offer with its rules (text, days, hours, pause, first visit), whether it came from us or from the restaurant, who at our end reviewed it, when, and our note to the restaurant. When a restaurant proposes its offer through the link, we store only the time of each attempt (no content, no IP address) to limit abuse (at most 10 attempts in 24 hours), and delete it after 30 days. We delete the contact details of a prospect if no partnership starts within 12 months.
Why
Getting in touch, running the partnership and the offer: setting up and reviewing the offer, giving access to the report, staying in touch.
Legal basis
Partners: contract or pre-contractual steps (Art. 6(1)(b) GDPR); prospects we approach: legitimate interest (Art. 6(1)(f) GDPR).

Teams (with an account)

What
When you create a team or join one: the team's name, the office label and coordinates as the team admin picks them in the address search (not your device's location), the lunch weekday and time, the invite code, the email domain of the person who creates the team (for example “company.de”; a work address only, not Gmail, GMX and the like) and, if an admin adds one, the webhook address for Slack or Microsoft Teams. When you join, we check that your account's email address is at that domain; other members never see your address, only the team's domain. For each member we store the team, your account, your display name and your role (admin or member). Members of your team see your name and role; only admins see the invite code and the webhook address. Team rooms are group rolls for team members only.
Why
To provide the team feature and keep each team to colleagues at the same company: opening a group roll with places around the office on lunch day (in the morning) and, if set up, posting its link to Slack or Teams. An admin can also send a test message to the webhook.
Legal basis
Contract (Art. 6(1)(b) GDPR).

Invites (with an account)

What
Your invite link: a random code, the name you choose for the link, and two settings (“Let friends start with my picks” and “Taste twins”). Anyone who opens your link sees that name and your most common vibe (from your swipes, once you have three yeses). If you sign up through an invite link or a group roll’s link, we store who invited you, which way, your display name and when you first picked a place. The person who invited you sees your display name and whether you’ve picked a place yet; you see the name on their link. Only if both of you turn on “Taste twins” does our server compare your swipes, showing both of you a percentage and up to three things you share, never the swipes themselves. With “Let friends start with my picks”, friends you invited see up to 10 places from your saves until their first pick, never when or whether you went.
Why
To provide invites: showing your link, matching invites, and after the first pick adding the Plus one stamp and 30 days of Perk Plus for both of you (for an inviter, for up to 12 friends a year).
Legal basis
Contract (Art. 6(1)(b) GDPR).

Plus codes (with an account)

What
When you redeem a Plus code, we store the code, your account, the days it gave you and the time. When a code didn’t work (it doesn’t exist or can’t be used any more), we store the failed attempt with your account and the time, never the text you typed. A code belongs to a campaign of ours or to a partner restaurant. The partner restaurant’s report shows only how many times its code was used in the last six months, as a number (values under 5 not exact), never by whom. Your analytics events never contain the code, only a rough band of days or the reason it was refused.
Why
To credit you the Plus days, to let each code be used once per account and at most three times in 365 days, and to stop people guessing codes (at most 10 failed attempts an hour).
Legal basis
Contract (Art. 6(1)(b) GDPR); protection against guessing codes: legitimate interests (Art. 6(1)(f) GDPR).

Traffic measurement (DataFast)

What
Only with your consent and only on the public pages (home page, city pages, the pages for restaurants and teams, legal texts), not in the app, on sign-in, on partner pages or on invite links: page views and where you came from (referrer, campaign), browser, device type, the approximate region from your IP address and a random id in a cookie. Without consent the script isn't loaded. If you withdraw, the page reloads so the script stops running.
Why
To understand which pages and channels bring people to Perk.
Legal basis
Your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which you can withdraw any time in the app under “You” → “Analytics cookies”.

Describing your mood, and AI

What
The text you type into “Tell Perk your mood”. Our server reads short texts itself; longer ones go to TypeSafe AI (the “Jev” model). To describe cards, AI providers only get facts about the place (name, cuisine, price, features), nothing about you.
Why
To turn your description into dice and filters, and to describe cards.
Legal basis
Contract (Art. 6(1)(b) GDPR). Please don't type personal details about yourself or others there.

Usage analytics and error reports (PostHog)

What
What you do in the app, as events: for example rolled, swiped (with the place's vibe, cuisine and price level), picked a place (directions, call, delivery app), changed filters, signed in. Also page views (the address without group codes or other ids), browser, device type, the approximate region from your IP address, load times and error messages. Our server reports its own events (such as how many places were found, or that a follow-up email was sent) and errors. Never your email address, your exact location, restaurant names or your mood text.
With consent: a random id in a cookie and local storage, linked to your heyperk account id once you sign in, and recordings of your sessions with all text and inputs masked.
Without consent, or after “Decline”: nothing on your device. PostHog makes a hash from your IP address and browser identifier that changes daily, so events can't be tied to one person across days.
Why
To understand what works in Perk and where it gets stuck, and to fix errors.
Legal basis
Cookie, local storage and session recordings: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which you can withdraw any time in the app under “You” → “Analytics cookies”. Anonymous counting without consent and server error reports: legitimate interest in usage and error analysis (Art. 6(1)(f) GDPR); nothing is stored on or read from your device for it.

In your browser

What
In local storage: your sign-in, filters, preferred delivery app, a name you choose, your location, saved picks, the places shown to you in the last 14 days (only their ids), the ids of your last picks with a Plus offer (at most 5, so the offer appears if you switch to Plus), how often and when we offered to add Perk to your home screen (so we don't ask more often) and your diet needs; without an account also places from links (only their ids). In a cookie for heyperk.app and eats.heyperk.app: your choice about analytics cookies. Analytics cookies only with your consent (see above).
Why
So the app works and remembers your settings.
Legal basis
Strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG); further processing as above.

Paying (Perk Plus, Teams)

What
When you subscribe, checkout opens at Stripe (Stripe Payments Europe Ltd., Dublin). There you enter your payment method, billing address and, as a business, your VAT ID. That stays with Stripe, not with us; we never see card details. Stripe records your tick for the terms (for Perk Plus, also your request to start straight away) with the order. What we keep: the id of your Stripe customer and subscription, the plan (Perk Plus monthly or yearly, Team), the end of the paid period, for Perk Plus also whether it is set to end at the end of the term, and the time of the latest Stripe event. For Teams these belong to the team. We also remember only the id, type and arrival time of each Stripe event we process, so none is booked twice; that holds no details about people.
Why
To start, bill, renew and end the subscription, switch on the paid features, and meet invoicing and tax duties.
Legal basis
Contract (Art. 6(1)(b) GDPR) and legal obligations, mainly invoicing and tax (Art. 6(1)(c) GDPR).

Cancelling a contract (the “Cancel contracts here” form)

What
No sign-in needed: your email address, the contract you want to end, optionally a team name and a reason (free text), and the time we received it. Our server looks up customers with that address at Stripe and sets matching subscriptions to end at the end of the term. By email through Resend, a confirmation goes to the address you gave (contract, time, address; never your free text) and a message goes to us (hello@heyperk.app) with everything, including the reference and reason, followed shortly by one with the result. We don't put the entries in the database; they stay as emails. Against abuse, the server counts for up to an hour in memory how often an IP address and an email address use the form.
Why
So you can cancel a contract without an account (§ 312k BGB), to confirm, document and carry out the cancellation.
Legal basis
Contract (Art. 6(1)(b) GDPR) and the legal duty to offer a cancellation button and confirm the cancellation (Art. 6(1)(c) GDPR).

When you write to us

What
Your email address and your message.
Why
To answer you.
Legal basis
Contract or legitimate interest in answering (Art. 6(1)(b) or (f) GDPR).

4. Recipients and processors

Vercel Inc. (USA)Hosting, server logs, and the AI gateway that requests to AI providers go through.
Supabase Inc. (database in Frankfurt)heyperk accounts and account data (swipes, picked places, group rolls, places from links, founder number, day-one stamp, offers from partners, teams with name, office, lunch time, invite code, email domain, webhook address and membership, invites, Plus codes, Plus with Stripe ids, plan and term) and the contact details of partner restaurants.
Resend Inc. (USA)Sending sign-in emails and the follow-up email, and the emails of the cancel form.
Stripe Payments Europe, Ltd. (Dublin, Ireland), with Stripe, Inc. (USA)Payment processing as payment service provider: checkout, payment methods, billing address, VAT ID, payments, invoices and the calculation of VAT (Stripe Tax). We also give Stripe your email address, to match your subscription and to cancel it when you ask.
Google LLC (USA)Google Places: places nearby from the coordinates, and finding the place from a link. For a team, the office location its admin entered is also sent, to find places near the office. Photos are fetched by our server, not your browser.
TikTok (TikTok Pte. Ltd.) and Meta Platforms Ireland Ltd. (Instagram)Only when you paste a link: our server sends that link to their oEmbed endpoint to read the caption. Your IP address and other data about you aren't sent.
OpenStreetMapOverpass servers (including overpass-api.de, FOSSGIS e.V., Germany) for places, alongside Google (to add places Google doesn't list) or instead of it; Nominatim (OpenStreetMap Foundation, United Kingdom) for the country and place search. For a team, the office location entered is also sent to Overpass, to find places near the office.
MET Norway (Norway)Weather, with coordinates rounded to about 10 km.
TypeSafe AI, Inc. and Anthropic PBC (USA), via VercelAI: mood text (TypeSafe AI) and facts about places (both). The gateway is set to use only providers that don't train on requests.
PostHog Inc. (EU cloud, servers in Frankfurt)Usage analytics and error reports; with consent, session recordings too.
DataFast (datafa.st)Traffic measurement, only with consent and only on the public pages.
Slack Technologies (Salesforce) or Microsoft (Teams)Only if a team admin adds a webhook: our server then sends one message a week, on lunch day, to that address, and a test message when an admin triggers one. The weekly message contains only the link to the team room and the times, the test message only a short greeting; no names and no data about members. Your use of Slack or Teams is governed by their terms.

When you open a link (directions in Google Maps, a delivery app, a restaurant's website), their own privacy terms apply. Members of a group roll see your name and votes in that roll.

5. Transfers outside the EU

Some providers are in the USA or the United Kingdom. The basis for each transfer:

Google LLC, Vercel Inc.EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR).
Supabase Inc.Standard contractual clauses in the data processing agreement (Art. 46(2)(c) GDPR); the database itself is in Frankfurt.
United Kingdom (Nominatim)Adequacy decision (Art. 45 GDPR).
Norway (MET Norway)EEA, no third-country transfer.
PostHog Inc.The data is stored in the EU (Frankfurt). For access from the USA: standard contractual clauses in the data processing agreement (Art. 46(2)(c) GDPR).
Stripe Payments Europe, Ltd.Based in Ireland (EEA). Stripe passes data to Stripe, Inc. and other group companies outside the EU, on the basis of Stripe's standard contractual clauses and, where certified, the EU-US Data Privacy Framework (Art. 45 and 46 GDPR).
Resend, TypeSafe AI, AnthropicStandard contractual clauses of the providers or of Vercel as the gateway operator; we are confirming the exact basis for the AI providers with Vercel and will add it here.

6. How long we keep data

Server logsAbout one hour (current Vercel plan).
heyperk accountUntil you ask us to delete it.
SwipesUntil you choose “Forget my taste” or have your account deleted.
Picked places and passportUntil you have your account deleted.
Group rollsA roll is open for 24 hours and deleted 7 days after it expires, with its members, votes and shared diet needs.
Places from linksUntil you remove the place or have your account deleted. Captions up to a day in the server's memory, by link (not by person).
Founder number and day-one stampUntil you have your account deleted.
Offers from partners (code, shown, used)Deleted with the picked place, at the latest when you have your account deleted.
Contact details of partner restaurantsUntil 3 years after the partnership ends; for prospects, 12 months if no partnership starts.
Attempts in the restaurants' offer form (time only)30 days, then deleted.
Paid plans (Stripe ids, plan, term)Until you have your account deleted; for teams as there. We and Stripe keep invoices and bookkeeping records for as long as tax and commercial law require (currently up to 10 years; § 147 AO, § 14b UStG); deleting them on request is excluded for that time (Art. 17(3)(b) GDPR). Payment methods and billing address are with Stripe, under its retention periods.
Cancellations through the form (emails to us)3 years, then deleted. The emails are also with Resend, under its retention periods. The counters against abuse: up to an hour in memory.
Teams (name, office, lunch time, invite code, email domain, webhook, membership)The team is deleted when the last person leaves it; your membership ends when you leave, are removed or have your account deleted. If the person who created the team deletes their account, the whole team is deleted, for everyone. Team rooms follow the group-roll retention.
Invites (link, name, settings, who invited whom)Until you have your account deleted. If either person deletes their account, the link between you is deleted.
Plus codes (redeemed codes with account and time)Until you have your account deleted.
Failed attempts with a Plus code (account and time)30 days, then deleted.
Failed look-ups of room, team and invite codes (account, kind and time; at most 20 an hour)30 days, then deleted.
Places and weather foundUp to 30 minutes in the server's memory, by area (not by person).
AI results about placesUp to 30 days, not linked to you.
Your mood textNot stored; only processed for the request.
Usage analytics (PostHog)Events up to 12 months, session recordings up to 30 days. The analytics cookie up to 12 months, or until you decline or delete it.
In your browserUntil you sign out, clear it in the app, or remove the site's data in your browser.

7. Your rights

You have the right to

  • access your data (Art. 15 GDPR),
  • have incorrect data corrected (Art. 16 GDPR),
  • erasure (Art. 17 GDPR),
  • restriction of processing (Art. 18 GDPR),
  • data portability, receiving your data in a common format (Art. 20 GDPR),
  • object to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation (Art. 21 GDPR); you can object to the follow-up email at any time without giving a reason,
  • withdraw consent with effect for the future (Art. 7(3) GDPR), such as analytics cookies (in the app under “You” → “Analytics cookies”) or location access in your browser.

You can do some of this yourself in the app under “You”: “Forget my taste” deletes your swipes, and you can turn off follow-up emails. For anything else, including deleting your account, please write to hello@heyperk.app from your account's email address.

You can also complain to a data protection authority (Art. 77 GDPR), for example where you live. Ours is:

Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18
91522 Ansbach
poststelle@lda.bayern.de · www.lda.bayern.de

8. No automated decisions

Perk Eats makes no decisions that have legal effects on you or similarly significantly affect you (Art. 22 GDPR). It suggests places; where you go is up to you.

9. Children

Perk Eats isn't meant for children under 16. If you think a child has created an account, write to hello@heyperk.app and we'll delete it.

10. Changes

When the way heyperk processes data changes, we update this policy. The current version is always on this page; the date at the top shows the last change.

pperk. eats

Small, honest tools for everyday decisions. Made for indecisive eaters.

hello@heyperk.app
Perk EatsOpen the appHow it worksWith friendsCities
heyperkHomeSign inThe next app
For businessFor teamsFor restaurants
LegalLegal noticeDatenschutz (DE)PrivacyTermsVerträge hier kündigen
© 2026 heyperk · No ads. No ad trackers.Places from Google or © OpenStreetMap contributors · Weather: MET Norway