Privacy policy
This is a courtesy translation provided for information only. In case of any discrepancy, the Spanish version prevails.
This policy explains which personal data we process in the Klendar app and on klendar.app, why, on what legal basis, for how long, and what your rights are. It complies with Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD).
1. Data controller
- Controller: Iván Hijano Pérez
- Data protection contact: info@klendar.app
2. What we process and why
| Processing | Data | Purpose | Legal basis | Retention |
|---|---|---|---|---|
| User account | Email, display name, password (hashed), date of birth, language, profile photo (optional), date and version of the terms you accepted | Create and manage your account; verify the minimum age (14) and access to 18+ content; and, if one of your favourite businesses offers a birthday gift and you don't turn it off in Settings → Notifications, give it to you on your birthday (the business never sees your date: it only gets the code when you redeem it) | Performance of a contract (art. 6(1)(b) GDPR); legal obligation for age (art. 6(1)(c); art. 7 LOPDGDD) | While the account is active. If you don't use it for 24 months (you don't log in or open the app or the website), we email you that it will be deleted when it reaches 36 months and remind you 30 days before; logging in is enough to keep it. If you own a business, we don't delete it automatically: we review it first and get in touch with you. When it is deleted (by you, or by us for inactivity), it is erased immediately (within 30 days at most if you ask by email) and backups are overwritten within 7 days. Businesses' invoicing data (6 years) and resolved reports (2 years) are kept, no longer linked to you |
| Sign in with Google / Apple | Provider identifier, email, name. With Apple, also an Apple code (token) that can only be used to remove Klendar's access to your Apple account | Passwordless authentication; with Apple, asking Apple to remove Klendar's access when you delete your account, as Apple requires | Performance of a contract | Same as the account. The Apple code is deleted when you delete your account, as soon as Apple confirms the removal (if Apple doesn't answer, within a couple of days at most) |
| Location | Approximate or precise device coordinates (depending on the permission you grant) or the city you pick manually | Sort the feed and the map by distance; "deals near you" if you enable it; knowing what’s nearby for your “Tell me when…” keywords (with the location we already keep for “near you”, your city or your last known location from the past 7 days; we don’t keep any other); check that you're at the venue when you scan its QR code to get a visit stamp (it's compared with the venue's address and not stored); if you've already allowed it, also when accepting something a business gives you with “Give on the spot”, to check that you're at the venue (we don't ask for it for this or store it); order today's plans according to the weather in your area (see “Based on the weather”); and, in aggregate and without identifying anyone, the distance figures in each business's “Report” (how far its customers come from). If you've chosen your city, compare where you are with it at that moment to tell you about today's best when you're travelling (more than 50 km away); we don't store where you were, only the date you closed the notice. On klendar.app, when you tap “Near me” or “Use my location”, your browser keeps your position for 6 hours to show you distances and sends it, rounded to about 100 m, in the address of the page you request (we don't store it and it doesn't go through the visit counter). If Klendar isn't in your area yet, we check it there and then with your position (without storing it) and, if you ask us to tell you, we only store the rounded area (see “Tell me when Klendar arrives”). To name that area, the app and the website ask Mapbox for the name of the town using the rounded point. Work out which town you are in when you choose “Use my location” in “Your city” or to let you know you are travelling (your position is sent —rounded to about 100 m in the app—, matched to a town and not stored) | Consent (art. 6(1)(a)), revocable in your device and app settings | No history is kept. Only the last known location is stored (for "near you") and discarded after 7 days. On the website, your browser deletes it after 6 hours |
| Approximate location from your connection (klendar.app only) | The city and an approximate point that Cloudflare infers from your connection's IP address when you request the page (rounded to about 10 km); never your exact position | If you haven't shared your location or picked a city, show you what's near that area first (“Approximate location · 5 km”), as the app does. With no data, “All cities”. You can change it under Where? (pick a city or “Use my location”) | Legitimate interest (Art. 6(1)(f) GDPR) in showing something useful from the first visit, with these safeguards: we don't ask for permission because we don't access your device, it isn't your position, we don't store it or put it in the page address, and the page built with it isn't cached for other people | Not stored: used when the page is requested and discarded |
| Buzzing tonight (busy areas on the map) | No new data: every 5 minutes we count, by areas of about 300 m, how many different people have redeemed something, stamped a visit or shown their customer QR code at a business in the last 2 hours. We only keep the area and a level (a bit, busy or buzzing) | Showing on the map where it's busy right now | Legitimate interest (art. 6(1)(f) GDPR) in offering the feature, with these safeguards: only areas with 10 or more different people, never a number, a name or a business, the point is the centre of the area and not the venue, and it's rebuilt from scratch every 5 minutes | The areas, until the next calculation (5 minutes). The redemptions, stamps and QR readings used already have their own row and retention |
| Based on the weather | An area of about 10 km around where you're looking (your position or the city you picked, rounded to 0.1°), never your exact position | If it's raining today, show indoor plans first; if the weather is nice, terraces and outdoor plans. Nothing is removed, it only reorders today's plans. Our server asks MET Norway (the Norwegian Meteorological Institute, in the European Economic Area) for the forecast using only the centre of that area: it doesn't receive your IP address, your account or your position. Turn it off in Filters (☰) → “Sort by” → “Based on the weather” | Legitimate interest (art. 6(1)(f) GDPR) in ordering what you see in a useful way; your position, with the location consent you have already given | We don't keep anything of yours: each area's forecast, for 2 days at most |
| Favourites, reviews, redemptions and stamps | Businesses saved to your favourites, publications saved to your plans, ratings and comments, redemption codes and place reservations (with how many places) and whether the ticket is named and their status and, if the business enters it, the receipt total (see “Receipt total”), your place on the waiting list and the notices we've sent you from it, deal views, stamp cards (stamps, rewards and their codes) and whether a validation was undone | Provide the service: your favourites, your public reviews, your redemption history, businesses' stamp cards and aggregate statistics for businesses. When it validates one of your codes (also at the door for a promoter's list), the business sees your public name, your profile photo only if you have one and how many times you've redeemed something at that business, including this one (“5th time here”): we work it out at that moment from your validated redemptions there and don't store it separately. For a named ticket, it's used to check that you're the person who booked. If the business has turned on “Thank your regulars”, once a month it sees its 10 customers who came most the previous month: their display name and how many visits and redemptions they had at its venue. This is information it already sees when validating, just counted; never your email, phone number or date of birth. It uses it to send you a gift with a message, if it wants. “First visit only” offers are checked by Klendar: the business only knows you couldn't get that code | Performance of a contract; the monthly list of regulars, legitimate interest (art. 6(1)(f) GDPR) of the business and of Klendar in thanking its customers, with data the business already has | While the account exists. Reviews are shown with your display name and, if you have redeemed something at that business with Klendar, with the “Verified customer” label (without saying what or when) |
| Review reminders (“How was it?”) | That you used something at a venue (what and the day), whether we sent you the reminder and whether it was to write or to update your review | Asking you the next day, if you want, to review the place (or to update your review if it’s old), without repeating it. Everyone is asked the same way, without knowing how it went | Legitimate interest (Art. 6(1)(f) GDPR) in reviews coming from real visits. You can turn it off in Settings → Notifications (“How was it? the next day”) | 200 days. Deleted when you delete your account |
| Questions to businesses | The questions you ask on a business's page, when, whether they've been answered, hidden (and why) or reported, and which questions you've marked “Helpful to me too” | To get your question to the business and publish it, without your name, with its answer; to show you yours and their status; to put the most helpful first; to apply the limits (3 a day, one unanswered per business) and to handle reports. The business and other people never see who asks or who marks “helpful” | Performance of the contract; legal obligation for reports (Regulation (EU) 2022/2065) | Answered ones, while they stay published (until you delete them, the business hides them or you delete your account); hidden ones, 30 days; unanswered ones, 180 days. They're deleted when you delete your account, answered ones included |
| It was closed | That you reported a venue as closed when its opening hours said open, which venue and when. If your phone or browser already lets us see your location, we use it at that moment to check you’re nearby (within 2 km): we don’t store it | Letting the business know so it checks its opening hours and, if 3 different people find it closed within 14 days and it doesn’t check them, showing “Opening hours not confirmed” on its page. The business only knows the day and time, never who reported it | Legitimate interest (Art. 6(1)(f) GDPR) of people looking for a place in accurate opening hours, and of Klendar and the business in keeping them up to date | 30 days. Deleted when you delete your account |
| Tell me when there's room | That you asked us to tell you when there was room at a venue: which one, when you asked, how it was (“Full” or “Nearly full”), until when it's valid and whether we told you | To tell you once when there's room again. The business only sees how many people are waiting, never who. If the venue stops showing whether there's room, we remove it and let you know with a notification | Performance of what you ask for (Art. 6(1)(b) GDPR); the notification, with your notification permission (turn it off in Settings → Notifications, “When there's room”) | Active for 3 hours at most (or until the venue closes); deleted 24 hours after we notify you, it expires or you remove it. Deleted when you delete your account and included in “Download my data” |
| Receipt total | If the business enters it when validating your code (or within the next 24 hours): how much you paid in total on that visit, in euros (only the total; never what you bought or how you paid), linked to that redemption | So the business knows how much Klendar has brought it (“What Klendar has brought you”, “at least X €”) and so you can see it in “Download my data”. If it isn't entered, the offer's price is used | Legitimate interest (art. 6(1)(f) GDPR) of the business and of Klendar in measuring what the service brings; it's optional for the business, it's only a total and it isn't used for anything else (not to choose what you see, not for profiles) | While your account exists, with the redemption. The business sees the total with your name only in “Recently validated” (24 hours, to correct it); after that, in its stats, without your name. If you delete your account, the validated redemption stays in the business's stats with no one behind it (“Deleted account”) |
| Passes and customer QR code | The passes you buy from a business (name, uses, price set by the business, what it includes, expiry and conditions), each use (when, whether it was manual and whether it was undone) and who on the business's team added the pass or recorded each use; the key of your customer QR code (which your phone also uses to sign the QR code of your named tickets); each time a business reads your QR code (which business and when) | Keeping count of your passes, showing them to you and telling you when you have few uses left or they're about to expire; preventing fraud (a QR code that changes every 30 seconds, limits on uses per minute, a record of who did what). What the business sees: when it reads your QR code, your public name, your photo if you have one, how many times you've redeemed something there and your passes from that business, nothing else (not your email, phone or passes from other places). The owner and managers also see the list of passes sold with that data and each use | Performance of the contract (art. 6(1)(b) GDPR); fraud prevention, legitimate interest (art. 6(1)(f)) | Passes and their uses, while you have the account (if you delete it, they're erased; the business only keeps what it has downloaded before). Each reading of your QR code, 30 days. The QR key is also stored on your phone, in the app's secure storage; on the web only while the page is open |
| Give on the spot | What a business has given you with a QR code of its own (what: stamps, one use of your pass or the text of “something on the spot”; which business; when and on what day; who on the team opened the QR code); that you've scanned a QR code but not accepted it yet; on the business side, the QR code (a key, a secret, who opened it and when it was closed). Your location, if you already let us use it: only to compare it at that moment with the venue's; it isn't stored | Giving you what you accept, showing it to you in “Your codes”, on your stamp cards or on your pass, and letting the business see right away that you've received it; preventing fraud (a QR code that changes every 30 seconds, which is valid for one minute and closes by itself after 10 minutes without use or once the number of people chosen by the business is reached, once per person and QR code, 5 a day per business, a record of who gave it and, if you already let us use your location, checking that you're near the venue); counting it in the business's stats as a visit and towards “Verified customer”. What the business sees: at the time, your public name (“Lucía has received it”); afterwards, in “Recently validated”, “Validated redemptions” and its data download, your public name, what it gave you, when and who on its team. Nothing else (not your email, phone or what you get elsewhere). An employee doesn't see which colleague gave it | Performance of the contract (art. 6(1)(b) GDPR), which you request by tapping “Accept”; fraud prevention and the business's stats, legitimate interest (art. 6(1)(f)) | What you were given, 400 days; after that it stays in the business's stats without your name. That you scanned without accepting, 1 day. The business's QR code, 30 days after it's closed. If you delete your account, what you were given is no longer linked to you (the business only keeps the count). Your location isn't stored |
| Virtual queue | If you get a number in a venue's queue: the number, how many of you there are, when you joined, when you were called and how long you had to get there, and how it ended (served, didn't come, you left or the venue removed you). If the venue's team adds someone without the app, only the name they type. To prevent abuse, how many times you try per minute (per account and per connection; the connection as a fingerprint that doesn't store your IP) | Giving you your turn, telling you how many people are ahead and an approximate wait (based on how fast the venue calls people), telling you when it's your turn and running the venue's queue; preventing abuse (one entry per person and queue, limits per minute). What the venue sees: your public name, your photo, your number, how many of you there are and the state of your turn. Nothing else (not your email or phone) | Performance of the contract (art. 6(1)(b) GDPR); the abuse limits, legitimate interest (art. 6(1)(f)) | Everything is deleted at the end of the day (at 6:00 venue time) or when the venue ends the queue, whichever comes first. The per-connection attempts, after 24 hours. The notifications you received stay in your Notifications like the rest |
| Ready alert | If you ask a venue to tell you when your order is ready: the venue, your number, when you asked, when it was ready and how it ended (picked up, removed by the venue, “I'm not waiting any more” or closed by itself after 2 hours). To prevent abuse, how many times you try per minute (per account and per connection; the connection as a fingerprint that doesn't store your IP) | Giving you your number and telling you when the venue marks it as ready; preventing abuse (one active order per person and venue, limits per minute). What the venue sees: your number, the first word of your profile name (if you have one) and since when you've been waiting. Nothing else (not your email, phone or photo). The figures it sees afterwards (how many orders it alerted and the average wait) are numbers only | Performance of the contract (art. 6(1)(b) GDPR); the abuse limits, legitimate interest (art. 6(1)(f)) | Everything is deleted at 6:00 (venue time), or earlier if the venue finishes for the day or turns it off. The per-connection attempts, after 24 hours. The notifications you received stay in your Notifications like the rest. Deleted when you delete your account and included in “Download my data” |
| Group requests (Groups and companies) | What you ask for (what it's for, date, number of people, approximate budget per person and note), which places (up to 3), what each one replies (proposal, indicative price, conditions or that it can't) and, if you accept a proposal, the contact details you choose to share with that place: your account email or the phone number you enter | Getting your request to the places you choose, showing you their replies, notifying you and, when you accept one, giving that place your contact details so it can confirm the booking with you; preventing abuse (3 requests every 24 hours). What the place sees: what you ask for, without your name or contact details, until you accept its proposal; then your public name and the contact details you chose, that place only. The other places only know you chose another proposal. From then on, the place is responsible for what it does with your contact details (it uses them to confirm the plan with you) | Performance of the contract (art. 6(1)(b) GDPR): you ask for it; sharing your contact details, at your request when you accept | Shared contact details, until 30 days after the date of the plan (then they're deleted from Klendar; the place keeps whatever it has noted down itself). The request and the replies, 12 months after the date. If a business reports your request, we keep a copy of what was reported with the report for up to 2 years after it is closed (legal obligation, Regulation (EU) 2022/2065), even if the request is deleted earlier |
| Giveaways | That you've entered a giveaway, your entry number, when you entered or left, whether you already had the business in your favourites and, if you win, your prize (whether you accepted it, when, and whether it was handed over). To check your age we use the date of birth in your profile | Managing your entry, checking you meet the requirements (18 or over, not on the business's team, having it in your favourites if required), running the draw in a verifiable way, telling you the result and letting the organiser hand over the prize. Who runs it: the business running the giveaway, which is responsible for the giveaway and for handing over the prize (its details are in the rules); Klendar processes your data to run the giveaway in the app. What the organiser sees: how many people have entered and how many are new favourites; of the winner, their public name and photo (and, if the prize is over €300, the tax details that person gives them, to comply with the tax authority). Nobody else sees who has entered | Performance of the contract (art. 6(1)(b) GDPR): you enter, under the giveaway's rules | Entries, 6 months after the draw; the winners' details, 12 months. The number, the seed and the numbers drawn remain (no one's data: they're the proof of the draw) |
| Coupons, gifts and what you've saved | The next-visit coupons and thank-you gifts businesses give you: what it is, which business, the message, when it arrived, when it's valid and whether it was used. “What you've saved” is a figure worked out from your validated redemptions (previous price − what you paid) | To give them to you and let the business validate them; to show you what you've saved in “Your account” | Performance of the contract (art. 6(1)(b) GDPR) | Coupons and gifts, 400 days from when they reach you (that's what you see in the app). After that, and also if you delete your account sooner, unused ones are deleted and used ones stay in the business's figures without your name, like redemptions. “What you've saved” isn't stored: it's worked out each time you open it |
| Promoter lists | If you come in through a venue promoter's link or QR code: which promoter and which night (6:00 to 6:00, venue time), the offer you get, the number of places, when you signed up and whether and when you got in | Put you on that promoter's list, give you the offers on their list (with their places and time limit) and let the venue know who comes with each promoter. Before you get anything, we tell you: “You're joining Marta's list (Sala X). Marta will see your name and whether you got in.” The promoter sees your display name and photo, when you signed up, which offer, how many places and whether and when you got in; never your email, phone number or date of birth. The venue sees the same in its dashboard and can download it. If you don't come in through a link, you don't count for any promoter | Performance of a contract (you choose to come in through that link and get the offer, after the notice) | Which promoter you're with that night, 7 days. Which promoter each code was obtained with, while the redemption exists (anonymised if you delete your account) |
| Being a venue promoter | The invitation (the email the venue invited and when it expires), whether you accept it, your status (active, paused), your links and QR codes (name, expiry, pause and how many times they've been opened, without knowing who), the offers and places the venue assigns you and your figures (signed up, got in, conversion, by night) | Let you be a promoter for one or more venues with your Klendar account, give you your link and your list, and let the venue see your figures. The venue sees your display name and photo, your status, your links and your figures; it can't edit your account and you can't change anything of the venue's. You're not part of its team | Performance of a contract (you accept the invitation); you must be 16 (18 if the venue is 18+) | While you are that venue's promoter. If the venue removes you or you leave, your links disappear; the email of an invitation you don't accept is deleted when it expires (14 days). The venue's past figures stay, without your contact details |
| Photos and videos in reviews | The photos and videos you add to a review (up to 6), with their order, size and length | Publish them with your review, in the app and on klendar.app, with your name and profile photo visible. Before uploading them we remove the data inside them: for photos, the location, date and phone model (EXIF); for videos, the location and phone model. What can be seen in the image or heard in the video is published, so don't include other people without their permission. A review that goes to review because of its text isn't published, with its photos and videos, until someone at Klendar has reviewed it. Anyone can report a photo or a video; if it breaks the Community guidelines we take it down and tell you why. In the future we may analyse photos and videos automatically (Google Cloud Vision) to detect nudity or violence before they're published; we'll let you know before turning it on | Performance of a contract (publishing what you choose to publish); legal obligation for reports (Regulation (EU) 2022/2065) | Until you remove them, delete the review or delete your account; the files disappear from our servers within a few days. If someone has reported them, we keep a copy as evidence for as long as the report and the time to appeal last |
| Friends and plans | Your friend link (and its QR code), your friends and since when, the publications you mark as “I'm going”, the invitations you send and receive (and your answers), your “Let my friends see my plans” and “Show the plans I've been to with each friend” settings and the people you block and, if you block whoever asked a question, that block and which business they asked (you'll never find out who they are; it's in your data download and is deleted with your account) | Let you become friends with people who have your link, see which plans your friends are going to, invite them and let them see what you're going to. If “Let my friends see my plans” is on, your friends see which upcoming publications you're going to (because you've marked “I'm going”, have a reserved place or a code): on each publication, on your friend page and, if they've asked for it, in a notification. Things that have already happened don't appear on your page, with one exception: a friend's page can show “You've been to N plans together”, the number of publications where you both have a validated redemption; only that friend sees it, it doesn't say which or when and it isn't stored separately (it's worked out on the spot from the redemptions we already keep). It only shows if you both have both settings on; if either of you turns it off, neither of you sees it. It's never shown with people you've blocked or suspended accounts, and when you delete your account your redemptions are anonymised and stop counting. The people you block can't be your friends or invite you (they aren't told). There is no people search: only people with your link or your QR code can find you | Performance of a contract. Showing your plans and the plans you've been to together can be turned off in Settings → Privacy and data; invitations and notifications about your friends' plans, in Settings → Notifications | While the account exists. If you remove someone from your friends, they stop seeing your plans straight away (we don't tell them) |
| Series you follow | The series you follow (“Open mic on Thursdays”), since when, whether you've asked to “Add each date to my plans” and which dates we've already told you about | Tell you about each new date of a series you follow (one notification per date, and none if another one about that publication has already reached you), save it to your plans if you ask, and tell you if the business ends or cancels it. We only tell you about things you can see (18+, exclusives) and never if you've blocked whoever runs the business. The business only sees how many people follow each series, never who | Performance of a contract (you ask for it by tapping “Follow the series”); notifications, with your notification permission (turn them off in Settings → Notifications → “Series you follow”) | Until you unfollow it, the business ends or cancels it, or you delete your account; the record of dates notified, the same |
| Teams and athletes you follow | The teams, athletes and competitions you follow (“Real Madrid”, “Fernando Alonso”, “Formula 1”), since when, which matches or races we've already told you about and, while you follow any, your filters' area (the distance and, if you pick one, the city) | Let you know a few hours before a match, race or fight night of what you follow which bars in your area are showing it (two notifications a day at most, one per event even if you follow both the team or athlete and its competition, and never if your quiet hours would deliver it after it has started). To know which bars are in your area we use your filters' distance around the city you picked or, otherwise, your last location (from the last 7 days) or your city; if there's none, we don't notify you. Bars don't know who follows what | Performance of a contract (you ask for it by tapping “Follow…”); notifications, with your notification permission (turn them off in Settings → Notifications → “Teams and athletes you follow”); location, with the location consent you have already given | Until you unfollow it or delete your account (the area, until you unfollow them all); the record of notifications, 30 days |
| Artists you follow | If you tap “Follow” on an artist's page: that you follow them and since when, and the alerts we've sent you about their dates; to know which dates are near you, the same area as for “Teams and athletes you follow” (your filters' distance and the chosen city or your last location) | Let you know when they have a new date near you (two alerts a day at most, and never about something you can't see: 18+, exclusives). It's private: neither the artist, nor businesses, nor anyone else can see that you follow them; only Klendar's team sees how many people follow each artist, without names; businesses don't see even that | Performance of a contract (art. 6(1)(b) GDPR): you ask for it by following them; notifications, with your notification permission (turn them off in Settings → Notifications → “Artists you follow”) | Until you unfollow them (Account → Artists you follow) or delete your account; the alerts sent, 120 days. When you stop following all artists and teams, we delete your area |
| Places you ask for | The name of the place you ask for, the city or area you type and, if you add them, the venue's approximate address or the map point you set; the date; if the venue joins Klendar, when we told you | Grouping your request with other people's requests for the same place (by name and area), so we know which venues people want and can suggest it to those businesses; telling you if the place is already on Klendar; and letting you know when it joins (at most two notifications of this kind a day; switch it off in Settings → Notifications → “Places you've asked for”). To prevent abuse, at most 5 requests a day and 30 open at once, and no offensive text. Nobody sees who asked: the Klendar team sees the place, how many people ask for it and the names, addresses and areas they typed; the business is only told the number (“X people have asked to see you on Klendar”), never who | Performance of the contract (art. 6(1)(b) GDPR): you ask for it; the notification, with your notification permission | Until you withdraw it (in “What you've asked for”) or delete your account; if the venue joins and we tell you, or we dismiss it, 90 more days; if it doesn't join, 24 months. For places that join Klendar or that we dismiss, only the number of people who asked is kept, with nobody's data |
| Tell me when Klendar arrives | The area where you ask: the name of the town and a point rounded to about 10 km (never your exact position); your language; your account or, if you don't have one, your email; when you signed up, when you confirmed and when we told you. To confirm and to unsubscribe, single-use links, which we don't store: only a digest (hash) | Telling you once only when Klendar reaches your area: by email and, if you have an account, also with a notification; and knowing, by counting how many people ask in each area, which cities to go to first (the Klendar team only sees how many people per area). Without an account, we first send you an email so you can confirm the address is yours (double opt-in): until you confirm, you're not on the list. To prevent abuse, without an account it first goes, when enabled, through Cloudflare Turnstile's anti-bot check (as with reports without an account) and there's a cap on requests per connection, worked out without storing the IP address | Consent (art. 6(1)(a) GDPR), which you give by tapping “Tell me when it arrives” and, without an account, by confirming in the email. Withdraw it whenever you like with the link in the confirmation email or, with an account, in “What you've asked for” | Unconfirmed, 7 days. Once we've told you, 30 days. If Klendar doesn't arrive, 24 months. When you delete your account it's deleted, including anything you signed up for without an account with the same email |
| Your plans in your calendar | If you turn it on (Settings → “Your plans in your calendar”, in the app or in “Your account”): a secret random link and when your calendar last checked it. Through that link your calendar (Google Calendar, Apple, Outlook…) receives what you have in Plans: title, date and time, place and link of the events you're going to, your reservations (and how many places), codes with a time and the dates added by the series you follow | So your plans appear in your calendar and update themselves | Performance of the contract (art. 6(1)(b)): it's a feature you ask for | Until you turn it off, change it (the old link stops working straight away) or delete your account. Whatever your calendar stores is handled by whoever provides that calendar (for example Google or Apple) under their own terms. Anyone with the link can see those plans: don't share it; if it gets out, change it |
| Push notifications | Device token, preferences (favourites, nearby, messages from your favourites, friend invitations and plans, series you follow, matches of the teams and athletes you follow, artists you follow, your passes, stamps and rewards, coupons and gifts, birthday, groups and companies, giveaways, places you've asked for, “Tell me when…” (by keyword), “How was it?” the next day, when there's room, replies to your questions, questions on your page, quiet hours) | Tell you about news and messages from your favourites (at most one a week per business), nearby offers, new things nearby that contain one of your “Tell me when…” keywords (at most 3 a day; during your quiet hours, a single one when they end), your friends' invitations and plans, new dates of the series you follow, matches of the teams and athletes you follow (with the bars in your area that are showing them), new dates near you of the artists you follow, your passes (few uses left, expiry and manual uses), the coupons and gifts businesses give you, replies to your group requests and, if you have a business, new requests, giveaway results (if you win, we always tell you), the day after you use something at a venue, whether you’d like to review it (at most one a day, never during your quiet hours); that there's room at a venue where you asked for it (once per request); that a business has answered or hidden your question (with the reason); if you have a business, that there's a new question on your page (at most one an hour); if you have a business, that a code your team scanned offline turned out not to be valid when it was checked (so you can review whether anything was given); if you have a business, that someone found your place closed, a few days before each public holiday, whether you open that day (at most twice per holiday, to whoever manages the business, between 10:00 and 21:00 local time and never in your quiet hours), a free place from the waiting list, changes to or cancellations of what you've booked, the stamps and rewards on your cards, your birthday gift and places you asked for, when they join Klendar. Each kind can be turned off separately in Settings → Notifications (notices about your bookings and the waiting list are always sent, because they're about something you asked for). Also your turn in a virtual queue (it's your turn, you missed your turn, the queue has finished, the venue removed you) and your “Ready alert” order (it's ready, the venue removed it or finished for the day); these are service notifications, with no switch, like those for a code. The same goes for the notice that Klendar has reached your area, if you asked (once only; remove it in “What you've asked for”). “It's your turn!” arrives even during your quiet hours: you asked for it and you only have a few minutes to get there. The same goes for “There's room now”: you asked for it that same night and it expires in 3 hours, so it doesn't wait for your quiet hours to end either (turn it off with “When there's room”); so does the notification that we've removed your request because the venue stopped showing whether there's room. And “Your order is ready”: you've just asked for it at the counter, so it doesn't wait for your quiet hours to end either | Consent, revocable at any time | Until you revoke the permission, log out or delete the account |
| Widget, lock screen and watch | A copy of today's plans (title, business and times) and of your pending codes (the code, its publication, the business, the places and when it expires or starts), stored on your phone and, if you have Klendar on a Wear OS watch, the code that's due at that moment also on your watch | Showing today's plans in the widget if you add it, and your code with its countdown on the lock screen and on your watch so you can use it without looking for the app | Performance of the contract (art. 6(1)(b) GDPR): it's an app feature you choose to use; it can be turned off in Settings → Notifications → “Lock screen” (for the watch too) | On your phone and watch, until your plans or codes next change; it's deleted when the code is used or expires, when you log out or when you uninstall the app. It isn't sent to Klendar. It reaches a Wear OS watch through Google Play services on your phone (see “3. Recipients and processors”); on Apple Watch, iOS shows it from the iPhone's Live Activity |
| Business account | Business details (name, address, tax ID, phone, contact email, opening hours), team members (email and role) and what each of them does in the business tools (who validated, undid a validation made by mistake, sold or recorded a use, added someone to the queue or gave something on the spot) and, if you take groups or run giveaways, what you reply to each request (and who on your team did it) and who handed over each prize; the queue settings (limit and minutes to turn up) and its code; plan and payments and, if it is an organisation, its type (what we ask to check it is under “Organisation account (the request)”), and, if it sets them, its kitchen hours and the name and password of its customer Wi-Fi (shown on its table QR page), and, if it uses live capacity, its maximum capacity and each night's figures (numbers only: never who comes in); if someone on the team answers “Are you open today?”, who answered and what (deleted after 7 days); what it lists under “What to order here” (name, line and photo of each item), its times of day, the days it opens with other hours and its answer to each public holiday question (and who on its team answered), and, if it uses “Ready alert”, its poster code and how many orders it alerted each day and the average wait (numbers only); the questions it receives on its page (without who asks them), its answers, who on its team answered and the ones it hides, with the reason; and, in “Where to watch”, which team member set “Always show” for a team, an athlete or a competition; if it is an organisation and connects its calendar, the address of each calendar (which we never show in full), who connected it, when we read it, how many events it brought and the last error, and for each imported event its identifier in the calendar and the written place (from calendars we do not read invitees or private events). It is deleted when the calendar is disconnected or the business is deleted. For the launch free period, the province of the venue, worked out from its point on the map | Register, verify and manage the business; invoice the subscription | Performance of a contract; legal obligation (invoicing) | During the relationship and afterwards for the statutory period (tax: 4 years; commercial: 6 years). If the business is handed over, the new holder gets access to its data, including billing data. When the subscription is cancelled we keep the request and its reason, if given. When a business is deleted we keep a minimal record (business name, date, who deleted it and figures without personal data) for 6 years |
| Business terms | If you register a business: which version of the business terms you accepted, when and with which account, and, when they change, when we sent you the notice by email and when you saw it or marked it as read in the app or in the dashboard | To be able to show that the business accepted the terms and was notified of each change with the notice period required by Regulation (EU) 2019/1150. The notice of a change to the business terms goes to the owner of each business; it is mandatory and cannot be turned off. If your address bounces our emails, we don't send it and the notice stays in the app and the dashboard | Performance of the contract with the business (art. 6(1)(b) GDPR) and compliance with a legal obligation (art. 6(1)(c) GDPR; Regulation (EU) 2019/1150, art. 3) | While the business exists on Klendar; it is deleted when the business is deleted. You can download it in “Download the business data”; “Download my data” shows which versions you accepted |
| Plan billing: notices, pause and VAT (businesses) | The VAT region (mainland Spain and Balearic Islands, Canary Islands, Ceuta or Melilla), which we work out from the venue's address; seasonal pauses (dates, who asked for it, paid days kept and how it ended); any manual unblocking we do (until which day); and the billing notices (which notice, for which day and whether the email was sent) | To apply the right VAT; to give notice before blocking a business and when its “Launch, free” period gets an end date; to run the pause. Billing notices (end of “Launch, free”, 7 days and 1 day before blocking, blocking and the end of a pause) go by email to the owner and in the app to the owner and managers; they're part of the service and can't be turned off | Performance of the contract with the business (art. 6(1)(b) GDPR) and compliance with a legal obligation (VAT, art. 6(1)(c) GDPR) | Notices, 400 days; the rest, like the business account |
| Claiming a business (“Is this your business?”) | Your account, the role you say you have, the business phone number or email you give us, the evidence you upload (a photo or a document) or what you tell us, your declaration that it is true, the date and what we decide (and why) | Check that you run that business and, if so, make you its owner; tell whoever was its owner that it has changed; prevent someone from taking over a business that isn't theirs. Only the Klendar team sees it, and the evidence is kept in private storage | Performance of a contract (art. 6(1)(b) GDPR: you ask for it) and legitimate interest (art. 6(1)(f)) in preventing impersonation and protecting businesses | The evidence, up to 6 months after the claim is resolved; the claim (who, when and what was decided), 2 years |
| Organisation account (the request) | Your account; the type of organisation, its official name, its tax ID (CIF), its official website and the area where it operates; your full name and your role; the document you upload to prove it (for example, your appointment, a certificate from the secretary, the board minutes or the entry in a register), your declaration that it is true, the date and what we decided (and why) | Checking that you represent that organisation before giving it the organisation badge and, if you signed up as an organisation, before its page and what it publishes are visible; preventing anyone from impersonating a council, an association or an NGO. The Klendar team and the business's team members can see it; the document, only you and Klendar, in private storage. If you sign up as an organisation, the official name and website appear on the public page; the CIF, your name, your role and the document do not | Performance of the contract (art. 6(1)(b) GDPR: you ask for it) and legitimate interest (art. 6(1)(f)) in preventing impersonation and in people knowing who publishes | The document, until 6 months after we decide (if you withdraw the request, a few days); the request (who, when and what was decided), 2 years |
| Content reports (also without an account) | If you report without an account: your name, your email (optional if it concerns child sexual abuse) and your language; if you report with your account, the account. In both cases: the reason, the text of the report, a copy of the reported content and the date. To stop abuse of reports made without an account, a digest of the connection calculated with a key that changes every day; never the IP address | Handle the report and reply to you: confirm we've received it and tell you what we've decided and why. The person who posted the content doesn't know who reported it | Legal obligation (art. 6(1)(c) GDPR; Regulation (EU) 2022/2065, art. 16) | Up to 2 years after the report is closed. The connection digest is deleted within 24 hours |
| Crash reports | Installation identifier, device model and OS, app version, technical crash report (without your name or email) | Detect and fix app crashes (Firebase Crashlytics) | Legitimate interest (art. 6(1)(f)): keeping the app working | 90 days |
| App usage statistics (optional) | Installation identifier, screens and actions (viewing a deal, saving, redeeming, sharing, searching —without what you type—), device model and OS | Know what is used in order to improve the app (Firebase Analytics) | Consent (art. 6(1)(a)): unticked box at sign-up or in Settings → Privacy and data; withdrawn the same way | 14 months |
| Marketing emails | Send you Klendar news (never from third parties) | Specific consent ticked at sign-up; revocable in every email or in your profile | Until you withdraw it | |
| “Tell me when…” alerts | The area you choose (point and radius), categories and maximum price; the keywords you type (“karaoke”, “sushi”, up to 10) and, so as not to repeat ourselves or send more than 3 a day, which post we told you about and for which keyword | Telling you when something matching appears nearby. With keywords, “nearby” means your “Flash offers near you” distance, your city or, if you have neither, 5 km from your last known location. Keywords are only used for this: we don’t use them to sort what you see or for advertising, and nobody sees them, businesses included | Performance of a contract (you ask for it) | Alerts and keywords, until you delete them or your account; what we told you about, 30 days |
| Email summaries | Email, language, city, your favourites and plans | Send you the weekly summary with deals and plans from businesses (if you turn it on in Settings → Notifications; it starts off) | Consent; one-click unsubscribe in every email | Until you turn it off |
| Emails that bounce and changing your email | Your email (or, if you don't have an account, the address we write to), the date, the reason (bounce or marked as spam) and the technical details our email provider (Resend) gives us; when you change your email, the old and the new address | Stop sending you summaries and other non-essential emails while your address keeps bouncing our messages (account access emails are always sent) and let you know in the app and on the web; confirm an email change with a code to your current address and another to the new one. If we change it for you because you've lost access to your email, our admin log keeps the old address, the new one and how we verified your identity | Legitimate interest in not sending emails that don't arrive or that you don't want (Art. 6(1)(f) GDPR); performance of a contract for the email change | Until you change your email (when you do, the mark on the previous address is deleted), tell us it works again or delete your account. If the address isn't linked to any Klendar account (for example, if you report something without an account, you're invited to a team or you ask ‘Let me know when Klendar arrives’ without an account), 12 months from the last email that bounced or was marked as spam. The admin log, 2 years |
| Messages from your favourites | That you have the business in your favourites or stamps on one of its cards | Let the business send you an alert (at most one a week per venue), reviewed by Klendar; the business doesn't see who receives it | Consent (notifications); turn it off in Settings → Notifications | Inbox, 90 days |
| “You might like” suggestions | Your interests (see “Your interests and your city”), your latest searches and the categories you look at most, stored on your phone | Suggest something when there's nothing nearby; they're sent with that request and not stored on our servers | Performance of a contract | On your phone, until you delete them or the account |
| Your interests and your city | 3 to 5 categories you choose (“Bars”, “Live music”…) and, if you like, your home town: a town in Spain, with its name and its point (the town's, never your address or your position). When you chose them or whether you said “Not now” | Show you plans in those categories first in Discover and Explore, without hiding anything (only with the “Recommended” order, the default one, where they count as if they were two days newer; with “Nearest”, “Starts soonest” or “Newest” they don't count, and you can turn this off in Filters (☰) → “Sort by”, with the “Take your interests into account” box); take them into account in “You might like”; and, with your city, tell you about today's best when you open Klendar more than 50 km away from it. Without an account they're stored only on your phone; with an account, in it too, so they also work on the web and on another phone | Performance of a contract (you ask for it by choosing them; the step can be skipped) | Until you change or clear them (Settings → What you see → Your interests) or delete your account. On the web, the browser copy is deleted when you log out |
| If you're an adult (without an account) | Your answer to “Are you 18 or over?” (yes or no), on your phone or browser | Show you 18+ content or not without an account | Legitimate interest and the legal duty not to target alcohol advertising at minors | On your device until you clear the app's or the browser's data (on the web, one year); we don't store it |
| Searches | What you searched for: your last 10 searches, stored only on your phone or in your browser; they never reach us. Most searched: each search (the text, lower-case and without accents) is added to a counter for its city and day. We don't store who searched or your IP address: so that the same person counts once a day we use a digest with a secret key that changes and is thrown away every day, and that digest is deleted the next day. We don't count text that looks like personal data (emails, links, numbers of 4 digits or more) or offensive words | Show your recent searches when you tap the search box; and show everyone “Most searched in (city)”: only terms that at least 5 different people searched on some day, never today's, and without numbers | What you searched for: we don't process it (it's on your device). Most searched: legitimate interest (art. 6(1)(f) GDPR) in suggesting useful searches; what's stored is anonymous | What you searched for: until you clear it (one or all, in the search box) or uninstall the app / clear your browser data. Most searched: 30 days; the digest used to avoid counting twice, until the next day |
| What you've already seen in Discover | Which publications in Discover (and, on the website, in the Explore list) you've had on screen for at least 1.5 seconds, when, and a fingerprint (a short code) of their price, date and places. It's stored only on your phone or in your browser; it never reaches us | So that when you reload Discover you see first what you haven't seen yet and, at the end, what you've already seen, without hiding anything. If something drops in price, changes its date or time, has few places left or becomes available again, it shows as new again. You can turn it off in Settings › What you see (on the website, also without logging in): then nothing is stored and what was stored is deleted | We don't process it (it's on your device) | 7 days from when you saw each publication (at most the last 2,000); it's deleted when you uninstall the app or clear your browser data |
| Automatic translation | What you ask to translate (by tapping “Translate” under a business's text that is in another language), without storing who asked; and, if you turn it on, the “Always translate automatically” preference (with an account, in your profile; without one, on your phone or browser) | Show you in your language (the app's or the page's), only when you ask or if you have “Always translate automatically” on, the title, description and conditions of publications, news, the business description, “What to order here” and its menu; next to the translated text it says that Google translated it, and you can always see the original. Reviews, questions and names are never translated. Our server translates them with Google Cloud Translation, which only receives the businesses' text (not your data or your account); we keep the translation so we don't have to ask for it again | Performance of a contract (you ask for it; “Always translate automatically” starts off) | The preference, until you change it or delete your account. Translations, up to 60 days after they were last used; those of a business that is deleted, at that moment |
| Share to stories | Nothing of yours: the image (1080 × 1920, with the photo, design and a QR code of the publication, business or collection) is made on your phone, or your browser downloads it from klendar.app. Whoever opens that QR code or link (?ref=stories, or ?ref=whatsapp for the WhatsApp status image) leaves a counted visit, as does anyone arriving from the QR code on a venue's TV, from the venue poster's QR code or from a promoter's link: what was opened and when, with a key that changes every day and only serves to avoid counting the same person twice within 30 minutes (never the IP address or the account) | Let you share something on Instagram, in your WhatsApp status or on another network and let the business see how many visits come from there, and how many of those from WhatsApp (only the number) | Legitimate interest (art. 6(1)(f)) in counting, without identifying anyone, whether sharing works | The counted visit, 14 months. Whatever you post on another network is handled by that network (for example Meta, for Instagram and WhatsApp) under its own terms |
| Taps on a business page's links | Which link on a business page was tapped (type, domain and time); a temporary key so it isn't counted twice, made with a secret that changes every day and deleted after 30 minutes | Telling the business how often its links and menu are opened. When you tap “Book”, “Order delivery” or another link on a business page you leave Klendar: whatever you do there is handled by that service under its own privacy policy | Legitimate interest (art. 6(1)(f) GDPR) in giving the business figures, without knowing who taps | 14 months; the temporary key, 30 minutes. Neither the account nor the IP is stored |
| Table QR scans | How many times a venue's table QR code is scanned each day (just the number); so the same connection isn't counted twice within 30 minutes, an encrypted summary of your connection made with a secret that changes every day (never the IP address or your account) | Giving the business the number of scans of its cards. The network and password you see are entered by the business | Legitimate interest (art. 6(1)(f) GDPR) in giving the business figures, without knowing who scans | The figure, 14 months; the summary, 24 hours. Neither the account nor the IP address is stored |
| Anti-bot check | Your IP address and technical browser or phone data, processed by Cloudflare (Turnstile) to give us a yes or no | Preventing fake accounts, automated reports or “Tell me when it arrives” sign-ups, and abuse of email or SMS codes | Legitimate interest (art. 6.1.f GDPR) in the security of the service | We don't store anything: Cloudflare processes that data under its processor agreement |
| Security | Encrypted digest of your connection (changes daily, never the IP address), trusted devices for fingerprint or Face ID login, codes to confirm it's you, technical website errors (no personal data) | Stop abuse, log in without a password on your devices, protect password changes and account deletion, detect failures | Legitimate interest (art. 6(1)(f)) | Digest 24 h; devices 90 days unused; codes 1 h; errors 30 days |
| Consent history | What you have accepted or withdrawn and when | Being able to prove it (art. 7(1) GDPR) | Legal obligation (art. 6(1)(c)) | While the account exists |
| Support | Email and the content of your message | Answer your enquiries | Performance of a contract / legitimate interest | 1 year after closure |
To create an account you must give your email (or use your Google or Apple account), your name (the one businesses and your friends will see; it can be a nickname), your date of birth and accept the terms; without them the account can't be used. Everything else is optional.
About the lock screen: while your code is showing, anyone holding your phone can read it without unlocking it. If your phone hides notification content on the lock screen, on Android you'll only see “You have a code ready” and the countdown; on iPhone the code number is hidden while the phone is locked if you've set it up that way.
Artist pages. So people can follow an artist, we publish their stage name (the one they use publicly and which appears on posters), their upcoming dates and, where we have them, a photo, a short description and links to their public profiles (Spotify, Instagram…). We do this on the basis of legitimate interest (art. 6(1)(f) GDPR: informing about public events the artist announces), using data that is already public and no contact or personal details beyond their stage name. We only use photos we have the right to use (provided by the artist or their representative, or under a licence that allows it) and credit the author where required. If you are the artist (or represent them) and want us to change something, remove the photo or the page, or exercise your rights (access, rectification, objection, erasure), email info@klendar.app: we'll review it within one month at most. A removed page stops being shown and won't come back even if a business types the name again (it stays hidden).
3. Recipients and processors
We never sell or share your data. To provide the service we rely on providers acting as processors under contracts compliant with art. 28 GDPR:
- Supabase (database, authentication and storage; servers in Ireland (European Union)).
- Google Firebase (push notifications, crash reports and, only if you agree, app usage statistics; Google Ireland Ltd.; international transfers covered by the EU-US Data Privacy Framework and standard contractual clauses).
- Mapbox (Mapbox, Inc., USA: maps, walking directions and place names; it receives the coordinates of the area you look at in order to render the map; if you ask for walking directions to a venue, your position and the venue's; to name an area or find a place, the rounded point or what you type (the place in “Ask for a place” or a business's address in the dashboard); on the website, your browser also requests from it the library that draws the maps; never your name or email; international transfer covered by the EU-US Data Privacy Framework, to which Mapbox has self-certified, and by standard contractual clauses).
- Cloudflare (Cloudflare, Inc.: hosting and content delivery for klendar.app; it processes visitors' IP addresses to serve and protect the website, counts visits in aggregate with Cloudflare Web Analytics, without cookies or identifying you, and, when enabled, runs the anti-bot check (Turnstile) when you create an account, log in, request a code or reset your password, on the website and in the app, and on what is sent without an account (reporting content on the website, or “Tell me when it arrives”); and, without storing it, the approximate city and area of your connection when you haven't shared your location (see “Approximate location from your connection”); international transfers covered by the EU-US Data Privacy Framework and standard contractual clauses).
- Google Cloud Translation (Google Cloud EMEA Ltd., Ireland: automatic translation of the text businesses publish, only when someone has asked for it; it receives no data about users; international transfers covered by the EU-US Data Privacy Framework and standard contractual clauses).
- IONOS (IONOS SE, Germany: our mailbox; it receives what you write to us).
- Resend (sending emails: your account emails, alerts, email summaries and replies to people who report without an account; it receives your email address and the content of the message; Plus Five Five, Inc., USA; international transfer covered by the EU-US Data Privacy Framework, to which Resend has self-certified, and by the European Commission's standard contractual clauses included in its data processing agreement).
If you log in with your Apple account (“Continue with Apple”), Apple (Apple Distribution International Ltd., Ireland) verifies your identity and gives us an identifier, your name and your email, or a private Apple relay address if you choose to hide yours. Apple processes that data as an independent controller, under its own privacy policy; we only receive what is listed here. The same applies to Google if you log in with your Google account (see below). If you delete your account, we ask Apple to remove Klendar's access to your Apple account; to do that we only send Apple the Apple code from the “Sign in with Google / Apple” row.
If you add a redemption to Google Wallet, Google receives the pass data (deal, business and code) as an independent controller. The website's icons, fonts and libraries are served from klendar.app: your browser does not request them from Google Fonts or any other service, except the map library (Mapbox GL JS), which it downloads from Mapbox (api.mapbox.com) when you open a map (more detail in the cookie policy).
Google (only if you use Klendar on a Wear OS watch): the code that's due (title, business, code, places and times) goes from your phone to your watch through Google Play services, encrypted; if the watch isn't near the phone it may go through Google's servers. Google acts under its own Wear OS terms, which you accepted when pairing the watch.
For “Based on the weather”, our server asks MET Norway (the Norwegian Meteorological Institute) for the forecast using only the centre of an area of about 10 km: none of your data reaches it. If you share something on Instagram, WhatsApp or another network from “Share to stories”, your phone hands the image to that app and from then on that network handles it as an independent controller, under its own terms.
Klendar on social media. We have profiles on Instagram, TikTok and LinkedIn. The website and the app only contain ordinary links to them: we don't load anything from those networks (no buttons, videos or pixels) and none of your data reaches them unless you tap the link. If you do, or if you follow, comment on or message us there, each network handles your data under its own terms (Meta Platforms Ireland Limited for Instagram, TikTok Technology Limited for TikTok and LinkedIn Ireland Unlimited Company for LinkedIn). The statistics those networks give us about our profiles are always aggregated (how many people, from which area, never who): for Instagram's we are joint controllers with Meta under its joint controller addendum, and likewise with TikTok and LinkedIn for their own. To exercise your rights over that data, the quickest way is to contact the network, but you can also email us at info@klendar.app. Whatever you tell us in a direct message we use only to reply to you (legitimate interest, art. 6(1)(f) GDPR) and we don't link it to your Klendar account.
Reports are only seen by the Klendar team. We never give them to the person who posted the reported content; we only pass them on to the authorities if there are signs of a criminal offence (art. 18 of Regulation (EU) 2022/2065) or if a court or the competent authority requires it.
Businesses see your display name and profile photo when you get a code or reserve a place in one of their publications (on their attendee list, which they can download, with the number of places, the time and whether you got in), when you have stamps on one of their cards, when they read your customer QR code (your passes from that business), when you get a number in their queue (your turn), when you win one of their giveaways, when you're among their 10 customers who came most the previous month (if they have “Thank your regulars” on) and when you post a review, as well as aggregate statistics. Never your email, phone number, date of birth or location, except the contact details you choose to give them when accepting their proposal in “Groups and companies”. When you ask a question on a business's page, the business sees the question, never who asked it.
Promoters (a venue's PR people) only see the people who came in through their link or QR code: their display name and photo, when they signed up, which offer, how many places and whether and when they got in. Never their email, phone number or date of birth. Whatever the venue pays its promoters is handled by the venue, outside Klendar.
Your friends on Klendar (only the people you have become friends with through a friend link) see your display name and photo and, unless you turn it off, which plans you're going to (“I'm going”, a reserved place or a code). Nobody else sees it: not other people and not businesses, who don't know who is friends with whom either.
If you log in with your Google account
If you choose “Continue with Google”, Google shares with us, with your permission, only the basics of your account: your name, your email address and your profile picture (the openid, email and profile scopes). We do not ask for access to your contacts, calendar, Gmail, Drive or any other Google data.
- What for: only to create your Klendar account and identify you when you log in. Your name and picture become your profile name and picture (you can change them at any time) and your email is used for account emails.
- Who with: nobody. We do not sell this data, we do not use it for advertising or advertising profiles and we do not pass it on to third parties, except Supabase, which stores accounts on our behalf as a processor.
- How long: for as long as you have the account. If you delete it, they are deleted with it.
- How to remove access: at any time from myaccount.google.com/permissions. Your Klendar account keeps working if you set a password.
Klendar's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. Minors
The minimum age to use Klendar is 14. Content marked "18+" (nightlife venues, alcohol) is only shown to people over 18: with an account, based on the date of birth you gave; without an account, if you answer “I'm 18 or over” to the question we ask once. That answer is stored only on your phone or in your browser; it is sent with each request so we know what to show you, but we don't store it or link it to you. With an account, your date of birth always applies: if you're under 18 you won't see anything 18+ even if a different answer was given on that device. If we detect an account belonging to someone under 14, we will delete it.
5. Your rights
You may exercise your rights of access, rectification, erasure, objection, restriction and portability, and withdraw consent at any time, by writing to info@klendar.app from your account email. From the app or from “Your account” on the website (Account → Settings → Privacy and data) you can also see what you have consented to and when, withdraw location, push, usage statistics and marketing consent separately, stop showing your plans to your friends, see and unblock the people you have blocked, download all your data as a file, including your passes and each use, today's turn in a queue, your group requests (with each place's reply and the contact details you shared), your giveaway entries and prizes, the artists you follow, your coupons and gifts, what you've been given on the spot, the places you've asked for and your “Tell me when Klendar arrives” sign-ups (including any made without an account with your account's email) (access and portability), and delete your account entirely. If you believe we have not handled your request properly, you may lodge a complaint with the Spanish Data Protection Agency (www.aepd.es).
6. Security
Data is transmitted encrypted (TLS), passwords are stored hashed, database access is restricted by row-level security policies (each person only reaches their own data), and the providers listed hold recognised security certifications.
7. Changes
If we change this policy in a material way we will let you know in the app. The current version is always at klendar.app/privacidad (Spanish, governing) and klendar.app/en/privacy.
Change history
- 5 November 2026: The “Friends and plans” row now also says that, if you block whoever asked a question, we keep that block and which business they asked.
- 4 November 2026: The “Favourites, reviews, redemptions and stamps” row now also says we keep whether a validation was undone.
- 4 November 2026: The “Business account” row now also mentions who in the team undoes a validation made by mistake.
- 4 November 2026: The “Business account” row now explains what we keep when an organisation connects its calendar.
- 4 November 2026: The “Business account” row now also names athletes in “Always show” in “Where to watch”: a team, an athlete or a competition. What data we process and why doesn't change.
- 4 November 2026: In “Teams and athletes you follow” you can now also follow whole competitions (such as Formula 1) and athletes from any sport; we let you know before each match, race or fight night. What data we process and why doesn't change.
- 4 November 2026: The “Emails that bounce and changing your email” row now says how long we keep the mark on an address that isn't linked to any account (12 months from the last bounce or complaint) and that the mark on your previous address is deleted when you change your email.
- 4 November 2026: Data is now stored on Supabase servers in Ireland (European Union).
- 4 November 2026: The anti-bot check (Cloudflare Turnstile) is switched on: when it runs (creating an account, logging in, requesting a code, resetting your password and what is sent without an account) and its row in the table.
- 3 November 2026: The “Business account” row also covers which team member set “Always show” for a team or a competition in “Where to watch” and the venue's province, worked out from its point on the map, for the launch free period. In “Friends and plans”, the screen is called Settings → Privacy and data, as in the app.
- 3 November 2026: “Teams you follow” is now called “Teams and athletes you follow”, as in the app (you can also follow athletes, such as Fernando Alonso), and so is its switch in Settings → Notifications. What data we process and why doesn't change.
- 3 November 2026: Your city can be any town in Spain: we store its name and its point (the town's, never yours). For “Use my location” in “Your city” and to let you know you are travelling, your position is sent (rounded to about 100 m in the app) to work out which town you are in, and it isn't stored.
- 3 November 2026: Live capacity: if a venue stops showing whether there's room, we remove your “Tell me when there's room” and let you know with a notification (which doesn't wait for your quiet hours); in the business account, who on the team answered “Are you open today?” and what (7 days).
- 2 November 2026: What you've already seen in Discover: stored only on your phone or browser (7 days) to show you what's new first, without hiding anything; turn it off in Settings › What you see.
- 29 October 2026: Klendar's page on LinkedIn: just a link, without loading anything from LinkedIn; its statistics, aggregated and under joint controllership with LinkedIn.
- 28 October 2026: Automatic translation: next to the translated text it says that Google translated it (without quoting the exact label, which may change).
- 28 October 2026: Klendar's profiles on Instagram and TikTok: links only, without loading anything from those networks; profile statistics, aggregated and under joint controllership with Meta and with TikTok.
- 28 October 2026: Automatic translation is on request (tapping “Translate”) or with “Always translate automatically”, and it also translates “What to order here”.
- 28 October 2026: Automatic translation: what is translated, that Google Cloud Translation does it (it only receives the businesses' text) and how long it is kept; Mapbox, also place names and the map library; on klendar.app, without your location, your connection's approximate area to show you what's near first, without storing it.
- 28 October 2026: The location used for “Tell me when…” and for your teams' match alerts is the one from the last 7 days (it said 30, but it's deleted after 7); the website's map library is downloaded from Mapbox when you open a map.
- 27 October 2026: Where to turn off “Based on the weather” and “Take your interests into account”: now in Filters (☰) → “Sort by”.
- 27 October 2026: 18+ content without an account: your answer to “Are you 18 or over?” stays on your device and we don't store it; with an account, your date of birth applies.
- 27 October 2026: Your interests: they only count with the “Recommended” order (the default one) and can be turned off with the “Take your interests into account” box.
- 27 October 2026: Sign in with Apple: we keep an Apple code that can only be used to ask Apple to remove Klendar's access to your Apple account when you delete your account; it's deleted as soon as Apple confirms it.
- 27 October 2026: When validating, the business sees your photo if you have one and how many times you've redeemed there; named tickets; “Give on the spot” can check, without storing it, that you're near the venue if you already allow location.
- 26 October 2026: In notifications, if you have a business, that a code your team scanned offline turned out not to be valid when it was checked.
- 20 October 2026: Questions to businesses: what we keep, what for and for how long; the business never knows who asks. In notifications, that a business has answered or hidden your question and, if you have a business, new questions on your page, each with its own switch; in the business account, the questions it receives (without who asks them), its answers and who on its team answered.
- 20 October 2026: “Ready alert”: what we keep, what the venue sees (your number and the first word of your name) and that it's deleted at 6:00; in notifications, the alerts about your order and that “Your order is ready” arrives even during your quiet hours; in the business account, its poster code and its daily figures (numbers only).
- 20 October 2026: In the business account, what it lists under “What to order here”, its times of day, the days it opens with other hours and its answer to each public holiday question (and who on its team answered); in notifications, the public holiday question to whoever manages a business (at most twice per holiday and never in their quiet hours).
- 19 October 2026: “Tell me when there's room”: what we keep, what for and for how long (active for 3 hours, deleted after 24 hours); its switch in notifications and that “There's room now” arrives even during your quiet hours, because you asked for it; in the business account, live capacity and each night's figures (numbers only, never who comes in).
- 19 October 2026: “Tell me when…” by keyword: the keywords you type (up to 10) and which post we told you about (30 days), what they’re for and what counts as “nearby”; its switch in notifications (at most 3 a day) and, under location, that we don’t keep any new location for this.
- 17 October 2026: “How was it?”: the next-day reminder to review a place where you used something (what we keep, what for and for how long) and its switch in notifications. “It was closed”: what we keep when you report that a venue was closed; the business never knows who it was and your location is only used to check you're nearby, without storing it.
- 16 October 2026: Give on the spot: what a business gives you with a QR code of its own (what we keep, what for, what the business sees and for how long), also in the business account and in “Download my data”. Scans of a venue's table QR code: we only count how many, without knowing who (14 months); in the business account, kitchen hours and the customer Wi-Fi.
- 15 October 2026: Group requests (“Groups and companies”): if a business reports your request, we keep a copy of what was reported with the report for up to 2 years after it is closed, even if the request is deleted earlier.
- 14 October 2026: Business plan billing: the VAT region, seasonal pauses and billing notices (what we keep, what for and for how long).
- 14 October 2026: Places you ask for and “Tell me when Klendar arrives” (what we keep, who sees it and for how long), also in location, notifications and “Download my data”; the terms a business accepts and the notices of changes to them; the organisation account request (the document, who sees it and how long it is kept).
- 13 October 2026: Widget, lock screen and watch (the copy of your plans and codes stays on your phone and your watch; Google passes it to a Wear OS watch); artists you follow and artist pages; virtual queue; group requests (“Groups and companies”); giveaways; “Buzzing tonight”; taps on a business page's links; coupons, gifts and what you've saved (coupons and gifts, 400 days); the monthly list of regulars a business sees; what the business sees, “Download my data”, notifications and the business account, brought up to date.
- 7 October 2026: Teams you follow and notifications about their matches; passes paid for at the venue and the customer QR code (what the business sees and how long each reading is kept), also in “Download my data” and in notifications; counted visits can also come from a venue's TV or poster or from a promoter's link; in the business account, the request to be an organisation and what each team member does.
- 6 October 2026: Receipt total: if the business enters how much you paid when validating your code, what we keep, what for, who sees it and for how long.
- 6 October 2026: Your interests and your city (and the notice when you're travelling); recent searches and “Most searched”, without storing who searched; your plans in your calendar through a secret link; WhatsApp status in “Share to stories”; “You might like” takes your interests into account; “Based on the weather” is turned off in the sort menu.
- 5 October 2026: Series you follow; “Based on the weather” (MET Norway receives none of your data); promoter lists and being a venue promoter; sharing to stories and the visits that come from them; the automatic translation preference. Location is also used for the visit stamp with the venue's QR code and for the weather in your area, and on klendar.app “Near me” puts it in the address rounded to about 100 m. What the business sees (your name and photo on its attendee list), bookings, waiting list and saved plans, notifications about series and the waiting list, and your name is required to create an account.
- 2 October 2026: Photos and videos in reviews: what is published, what data we remove, reports and how long they are kept.
- 2 October 2026: Your friends' plans: what your friends see of your upcoming plans, the optional notification and “You've been to N plans together”.
- 2 October 2026: Emails that bounce and changing your account email; what we keep when a business is handed over, cancelled or deleted.
- 2 October 2026: Accounts that are not used: email warning at 24 months and deletion at 36, with a reminder 30 days before; new processing “Claiming a business” (data, evidence and retention periods); the “Verified customer” label on reviews.
- 1 October 2026: Reports without an account; app usage statistics, based on consent and separate from crash reports; processing for “Tell me when…” alerts, email summaries, messages from your favourites, suggestions, security and consent history; processors, transfers and retention periods brought up to date; icons and libraries for the website, served from klendar.app.
- 29 September 2026: Current version of the terms (2026-09-29).