Privacy policy
This translation is for information only. The Spanish text is the binding one: if the versions differ, the Spanish version prevails. Read the Spanish version
menumentos is a free audio guide for walking around Spanish towns and cities, with an app for iOS and Android and a website (menumentos.com). This policy explains what personal data we process, why, on what legal basis, who we share it with, how long we keep it and how you can exercise your rights, in accordance with Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 on the Protection of Personal Data and the guarantee of digital rights (LOPDGDD).
In short:
- You can use the app without an account. What you listen to and save stays on your phone.
- Your exact location never leaves your phone for our servers. The app uses it on the phone itself to let you know when you pass near a point with a story; we do not store any position or any route you walk.
- We ask for the minimum: if you create an account, your email, your language, your approximate country and your consents. We do not ask for your date of birth. If you take part in the community (you contribute, validate or have a public profile), we also store what you provide: what you write and vote, your profile, whom you follow and your «likes».
- What you do in the community can be public, and you decide. Your profile is private until you make it public. Your reputation as a validator, your votes and whom you follow are seen by nobody but you and, in part, our team.
- Analytics and personalised ads only if you accept them, and you can change your mind whenever you like.
- You can download all your data and delete your account from the app or from menumentos.com/en/account.
1. Who the controller is
| Controller | CLAUDIA TECH, S.L. (trade name ClaudIA Tech) |
| Tax ID (NIF) | B93811149 |
| Address | Calle Gumersindo Azcárate, 8, 45200 Illescas (Toledo), Spain |
| Privacy email | info@menumentos.com |
| Phone | +34 623 79 71 10 |
| Data protection officer | Not appointed: we are not required to (Article 37 GDPR and Article 34 LOPDGDD). For any privacy matter, write to info@menumentos.com |
2. What data we process and where it comes from
You give us all the data, or it is generated when you use menumentos. We do not buy data or obtain it from other sources, except your identifier and email if you sign in with Apple or Google.
2.1. If you use the app without an account
- Progress, mementos and preferences: stored only on your phone.
- Anonymous session: only when needed (buying, redeeming a code, reporting an error, reporting content or syncing) an anonymous identifier is created on our server, without email or name. Your purchases, error reports and content reports are linked to that identifier.
- Technical data: app version, operating system and device model, needed for the service to work and to fix errors (see 2.4).
2.2. If you create an account
You can sign up with Apple, with Google, with a link sent to your email or with email and password.
| Data | Purpose |
|---|---|
| Email address (with Apple it may be a relay address) | Identify you, send you the sign-in link and service notices |
| Apple or Google identifier | Sign in |
| Language and approximate country | Show you content in your language and compile aggregate statistics. The country is a two-letter code taken from your device’s language and region settings or from what you choose; never from your location or your IP address |
| Consents | Remember what you have and have not accepted: personalised ads and marketing communications |
| What you have listened to and saved (mementos) and your progress on routes | So you can get it back on another phone or on the website. A memento says which point you listened to and when, never where you were |
| Route ratings and their comment | Improve the routes. Only the team and you read the comment; publicly only the average is shown, when there are three ratings or more |
| Passes, purchased routes and redeemed codes | Give you access to what you have bought or earned |
| Questions to «ask the guide» and their answers | Answer you; we keep them for 30 days |
| Error reports and content reports you send | Fix the content and handle the report |
| Who you have hidden | Not show you what that person publishes |
| Your «likes» and what you mark as useful | So that the counter of each point, route, list, story or tip is accurate and you cannot vote twice for the same thing. Others only see the counter, not who gave it |
| Whom you follow | Show you «From people you follow» with the latest from those people. Nobody sees whom you follow; the person followed only sees how many people follow them |
| Your saved lists | So you have them in your account and on another phone |
| Your invitation code and, if someone invited you, the code you created your account with | Give you the welcome pass and give the person who invited you what they are due (see 2.3). You do not see who signed up with your code and nobody sees who invited you |
| Your email notice preferences: which notices you want to receive and, if you choose them, the cities of the weekly summary | Send you only the notices you want (see 3) |
| Your voice requests («I want to hear it read aloud» on a text that has no audio yet) | Know which texts people want to hear, so that we give them a voice first. You need an account to ask for a voice: we keep which text and when, with your account; never your location or your device |
2.3. If you take part in the community: you contribute, validate or have a profile
- Public name you choose (it can be a pseudonym), handle and whether you want your profile to be public.
- What you send: text, links, the location of the place that you mark on the map (not your own) and up to 3 of your own photos. Before uploading them we remove the photos’ metadata (including the GPS position stored by the camera). Photos are kept in private storage until they are published. This includes the tips and lists you write, public or private.
- Declarations: that you are 14 or older, and the version of the community terms you accepted, with its date. And, only if you want to put links to your social networks, apply for the creator mark or validate a place on site, that you are 18 or older, with the date you declared it. We do not ask for your date of birth or documents.
- History of your contribution: statuses, messages from the team and reasons for rejection or removal.
- Points, level and badges, and any warnings or sanctions the team imposes on you for breaching the terms.
Your profile. If you wish, you can complete your profile with an introduction (up to 160 characters), an avatar (one from a collection of our own illustrations: we do not upload profile photos), a home city (a short, optional text) and, only if you have declared that you are 18 or older, links to your social networks: your Instagram, TikTok and YouTube user names and a website. Everything is optional and you write it yourself: we do not obtain it from anywhere else. You can change or delete it whenever you like. We recommend that you do not put personal data (address, phone number, school) in the introduction or the home city. While your profile is private, only you and our team see it.
What is public. If you make your profile public, the following are seen on menumentos.com and in the app: your public name, your handle, your avatar, your introduction, your home city, your links, your level, your badges, the creator mark if you have it, what you have published (places, routes, anecdotes, lists and tips) and how many people follow you. Never shown are your user identifier, your email, your reputation, your votes, whom you follow or who invited you. Your public profile and your public lists are indexed by search engines, and other websites or search engines may copy them; if you make it private or delete it, we remove it from our pages, but we cannot withdraw copies that other websites or search engines have already made (a search engine cache takes time to update). The public profile of a person aged 14 to 17 shows the same as an adult’s, except the links to social networks, which require being 18.
Your links. The links lead to third-party pages that we do not control: what is done there is governed by their terms and privacy policy, and you are responsible for them. On the website they carry the user-link mark (rel="ugc nofollow") and noreferrer, so those websites do not know which page you come from. Before you open a link on another person’s profile, the app warns you that you are leaving menumentos. We do not pass anything of yours to those websites when you open them beyond what any link passes in a browser (for example, the IP address).
If you validate what other people contribute. When other users propose a place, an anecdote, a route, a tip or a list, people with an account who meet certain requirements (those in the community terms) can see it before it is published and vote on whether it is published. We store, with your account, each vote you cast: what you voted, for or against, the reason, the weight it had, its date and, for a place, whether you voted it «on site». And we store your reputation as a validator, a number that goes up and down depending on whether your votes match the final decision and on what you publish, and that determines the weight of your vote and, together with your seniority and your published contributions, whether you earn validator trust, which is granted automatically or given by the team.
- What the validator sees of what is being validated is the data of the contribution (text, location of the place and whatever else was sent), without the author’s public name and without unpublished photos. The validator must not copy it or use it for anything other than validating, as the terms say.
- Who sees your votes and your reputation: you (also the history of your reputation) and our team. The author of what is voted sees the decision and, if it is rejected, the reason; they do not see who voted. Other users do not see your reputation or your votes.
- «On site» validation. To validate a place while you are there, the app checks on your phone, with your location permission, that you are within the radius of the proposed place. Only people who have declared that they are 18 or older can do it. Your position does not reach our servers: only the fact that the validation is «on site» and your three answers arrive. You should know that, because the proposed place has a known location, that mark indicates that you were near that place when you voted, to the precision of the place’s radius. It is the only thing we know about where you were: we do not receive your position or your route, only that mark and the date of the vote. The phone’s location is used only while you have the app open, for this check. «Validate near you» orders the proposals by their distance on your phone, with data from the proposals that the app can already read: it does not send us your position.
- We do not use artificial intelligence to validate: decisions are taken by people (validators or our team) and fixed rules (limits, links, banned words, duplicates).
Invitations. Each registered user has an invitation code and a link. Whoever creates their account with that code receives a 24-hour pass once. We store the code they used and, so that we can give the rewards and detect fraud, who invited whom. The person who invites sees how many people have arrived with their code and how many are active (have listened to their first point), never who; the invited person does not see who invited them. To give the reward, we know that the invited person has listened to their first point («point listened»), as with any other account: never where they were. If you open an invitation link on the website, your browser stores the code and the date for 7 days to redeem it if you create your account within that period (see 8): it is not sent to our servers until the account exists.
Points, reputation and challenges. We calculate your points, your level, your badges and your reputation from what you do in the community (what you publish, your votes and your invitations) and from the rules in the community terms. With each month’s points per city we make a leaderboard and the monthly challenges; if you turn on your public profile, you appear in it with your public name. Your figures («how many people have listened to or read what you contribute, and how many “likes” and saves it has») are seen only by you, in aggregate, without knowing who.
If we publish your contribution, your public name appears as a credit on screen (never in the audio) and, if you turn on your public profile, also on your profile page on menumentos.com and in the community leaderboard. What you publish signed appears with your public name as you wrote it.
2.4. Usage data, errors and ads
- Analytics (PostHog, EU region): events such as «route started», «story completed», «walk finished» (with its duration and number of points, never the route walked) or «offer opened» (when you open a ticket offer or the travel insurance card in the app, only with the provider’s name). They are only sent if you accept them. No session recording.
- Errors (Sentry): when the app fails, a technical report of the failure. We configure it not to store your IP address or user data and to strip any coordinates before sending it.
- Anonymous technical notices: if something fails (a download, an audio, a purchase, the website), the app and the website send us the type of failure, the platform, the versions and a code, with a random identifier used only to limit the number of notices (on the website it lives only while the tab is open). Never a position or an advertising identifier, and we do not store who sent it.
- Operation logs: what our processes do (a download completed, a payment applied, a failure sending an email, the deletion of an account), with the version of the app or the website and, if you are signed in, the identifier of your account (or of your anonymous session), so that we can help you if you write to us and for the security of the service. Never your position, your email, your IP or what you write. Those of normal use of the app (that it was opened, that a pack was installed) only with your analytics consent.
- Ads (Google AdMob): in the European Economic Area, Switzerland and the United Kingdom we ask for your consent with Google’s message (IAB TCF framework) before requesting ads and, on iOS, afterwards, for Apple’s tracking permission (ATT). If you accept, Google may use your device’s advertising identifier to show you personalised ads; if not, you will see non-personalised or limited ads. For our audio spots and sponsored stops we only keep daily counters (impressions, plays and clicks), without knowing who saw them.
- Security check (Cloudflare Turnstile): when it is active, when you sign in to your account or ask for a new link (in the app and on menumentos.com) and when the app creates a session without an account, Cloudflare checks that you are a person and not an automated program. To do so it receives your IP address, technical data about your browser or device (such as the type, version and language) and about how you interact with the check. It sets no tracking cookies and does not use this data for advertising; we only receive whether the check succeeded.
- Notifications: the app’s notices (download finished, route left half done, text to read) are local: your own phone schedules them. We use no notification identifier and send nothing to any server to show them.
2.5. Your location
With your permission, the app uses your phone’s location to let you know when you pass near a point and to guide you along a route, also in the background while a walk lasts, and, if you validate a place on site, to check on the phone itself that you are near it. That calculation happens on the phone itself: we do not send your position or the routes you walk to our servers, and we do not store them in any database. We are responsible for how the app uses your location even though it does not leave your phone, and the basis for that use is your consent, which you give by granting the permission. You can withdraw it in your phone settings; the app will keep working without proximity alerts.
The app’s map is Google Maps. When it loads, Google receives the technical data inherent to downloading the map (such as your IP address). When the map shows your position, it is drawn by the Google Maps component installed in the app, and Google may process usage and location data from that component under its own privacy policy.
2.6. If you write to us, report content from the website or are a sponsor
- Report from the website without an account: your email and the reason and details of the report. Your IP address is only used to limit abuse: it is not stored with the report and is deleted within 30 days at most.
- Emails with us: what you tell us and your address.
- Sponsors: contact details of the person who manages the business account and billing details (payment data is processed by Stripe).
2.7. If you listen in a group
If you create a group to listen to a guided route at the same time or join one (only with a registered account), we store which account is in which group, which route it is for, when it joined and left, which stop the person leading it has started and the failed attempts when typing the code (only when, not the code). The other people in the group see your handle only if your profile is public and you have no sanction in force (otherwise, «Person» and a number), and they see whether you have said «I’m here»; never your location, which does not leave your phone. To alert the group’s phones at the same time we use Supabase’s real-time service, which already processes your account data. Legal basis: performance of the service you ask for (Article 6(1)(b) GDPR). Period: it is deleted a day after the group expires (12 hours after it was created) or is closed, and always when you delete your account.
3. Purposes and legal bases
| Purpose | Legal basis (Article 6 GDPR) |
|---|---|
| Providing the service: account, sync, passes and purchases, codes, «ask the guide» | Performance of a contract (6.1.b): the terms of use |
| Receiving, reviewing, validating, editing, translating, voicing and publishing your contributions, with their credit; giving you points and rewards | Performance of a contract (6.1.b): the community terms |
| Publishing your signed contributions (tips, lists, places, anecdotes and routes) with your public name | Performance of a contract (6.1.b): the community terms |
| Showing your public profile (introduction, home city, links) and having it indexed by search engines | Consent (6.1.a), which you give by making your profile public and by entering each item and which you can withdraw at any time by making it private or deleting it |
| Validating with other users what is proposed: recording your votes, calculating your reputation and the weight of your vote, earning validator trust, hiding or publishing according to votes and reports | Performance of a contract (6.1.b) for the community service you use, and legitimate interest (6.1.f) in what is published being reliable and in being able to explain and review each decision. You can object by writing to us |
| «On site» validation: your phone checks that you are near and tells us only that you were | Consent (6.1.a), which you give by granting the location permission, and performance of a contract (6.1.b) for this feature |
| Security and fraud prevention in the community: limits, fake accounts, agreed votes, fake invitations | Legitimate interest (6.1.f) in protecting the service, other people and the rewards system |
| Invitations: giving the welcome pass and the rewards of the person who invites | Performance of a contract (6.1.b) |
| Listening in a group: knowing who is in each group and alerting the group’s phones at the same time | Performance of a contract (6.1.b) |
| Points, levels, badges, leaderboard, challenges and reward passes | Performance of a contract (6.1.b): the community terms |
| «Likes», following, saved items and «From people you follow» | Performance of a contract (6.1.b) |
| Declaration of being 18 or older to put links, be a creator or validate on site | Performance of a contract (6.1.b) and protection of minors (legitimate interest, 6.1.f). It is not an age verification |
| Checking that a creator’s network account is theirs and giving them the mark | Performance of a contract (6.1.b) and consent (6.1.a) of the person who requests it |
| Editing and translating with artificial intelligence a contribution that a partner adopts for the guide | Performance of a contract (6.1.b): the community terms |
| Automated screening of contributions with artificial intelligence, when active (spam, insults, third-party data, copied text, dangerous sites or duplicates). It only leaves notes for the team: it never decides, validates or publishes | Legitimate interest (6.1.f) in keeping the service safe and lawful and in protecting people who may appear in contributions. You can object by writing to us |
| Handling reports, giving reasons for rejections and removals, and applying sanctions | Legal obligation (6.1.c): Regulation (EU) 2022/2065 on digital services; and performance of a contract |
| Security and fraud prevention: limits on attempts to redeem codes, on reports and on submissions; anonymous technical notices; operation logs of the processes; log of the team’s activity | Legitimate interest (6.1.f) |
| Security check against automated abuse (Cloudflare Turnstile) | Legitimate interest (6.1.f) in preventing abuse and the costs of accounts and sessions created by programs |
| Error reports (Sentry) | Legitimate interest (6.1.f) in the app working and being secure. Technical data only, without IP or user identifiers. You can object by writing to us |
| Usage analytics (PostHog) | Consent (6.1.a) |
| Personalised ads (AdMob) and tracking on iOS (ATT) | Consent (6.1.a) |
| Non-personalised ads | Consent (6.1.a) for Google’s use of device storage, collected in the same message. If you do not give it, Google only serves limited ads, without that use, based on our legitimate interest (6.1.f) in funding a free service |
| Marketing communications (news, offers) | Consent (6.1.a), and Article 21 LSSI |
| Service notices: in the app, such as download finished; by email, when something of yours is published, when your appeal has an answer, when you are asked for changes to a contribution and when you earn validator trust | Performance of a contract (6.1.b): the service you ask for when you contribute |
| Weekly email summary with the proposals waiting for validation in your cities, if you can validate | Legitimate interest (6.1.f) in the community working. You turn it off in your account or with the unsubscribe link in each email |
| Voice requests: deciding which texts we voice first | Performance of a contract (6.1.b): the service you ask for when you tap «I want to hear it read aloud» |
| Billing sponsors and tax and accounting obligations | Legal obligation (6.1.c) |
Where the basis is legitimate interest, we have weighed that the processing is minimal and expected and does not override your rights. You can object at any time by writing to info@menumentos.com.
You can withdraw your consent at any time from the settings of the app or your account, without affecting processing carried out before.
Service notices by email. We let you know when something of yours is published, when your appeal has an answer, when you are asked for changes to a contribution and when you earn validator trust (to provide the service you ask for when you contribute) and, if you can validate, we send you a weekly summary with the proposals waiting in your cities (on the basis of our legitimate interest in the community working): the ones you choose in your account or, if you choose none, those where you have contributed or voted in the last six months; never based on where you are. They are not advertising: each type can be turned off in your account, in the app or at menumentos.com/en/account, and each email carries a link to unsubscribe with one tap.
Automated decisions and reputation. A signed contribution is published when it adds up the approval points required by its type with the votes of other users, and is hidden provisionally when the validators’ reports add up to the corresponding threshold; a partner reviews what has been hidden within 7 days at most. An automatic system applies those rules without a member of the team reading the contribution first, but each vote is cast by a person, our team can review and undo any decision at any time (and always does so when there is an appeal), and sanctions, removals and bans are always decided by a person from the team. We calculate a reputation for each validator and, when they reach it, we give them validator trust automatically on the basis of their reputation, their seniority and their published contributions: these are not an automated decision with legal or similarly significant effects on you (Article 22 GDPR), because they only serve to weight your vote and to let you validate within menumentos, we do not use them outside the community and the team reviews them afterwards and can undo them. Even so, you can ask for a person to review your case, express your point of view and challenge a decision by writing to info@menumentos.com or through the appeal procedure in the community terms. We do not use artificial intelligence to validate or to decide.
4. Who we share data with
We do not sell your data. It is processed with us only by the providers we need to deliver the service, as processors, under a contract requiring them to process it only on our instructions and with security measures (Article 28 GDPR).
| Provider | Purpose | Data |
|---|---|---|
| Supabase, Inc. | Database, accounts and storage of contribution photos | The data in sections 2.1 to 2.3 |
| Vercel, Inc. | Hosting of the website and server functions | Technical data of visits; contribution and report data passing through its functions |
| Cloudflare, Inc. (R2 and content delivery network) | City packs, audio and published photos | Published contribution photos; technical data of downloads |
| Cloudflare, Inc. (Turnstile) | Security check when signing in, asking for a new link and creating the session without an account | IP address and technical data of the browser or device |
| BunnyWay d.o.o. (bunny.net, Slovenia), once active | Backup copy of the city packs, to download them when the main server does not respond | Technical data of the downloads (such as the IP address) |
| Anthropic, PBC (Claude API) | Editing and translating contributions that a partner adopts for the guide, automated screening while active (it only leaves notes for the team) and «ask the guide» | Text of contributions and questions. Under its commercial terms, it does not use this data to train its models |
| ElevenLabs or Google Cloud (synthetic voice) | Voicing the stories | Only the final edited text, without personal data |
| PostHog (EU region) | Analytics, with your consent | Usage events and pseudonymous identifier |
| Functional Software, Inc. (Sentry) | Error reports | Technical data of the failure, without IP |
| RevenueCat, Inc. | Managing in-app purchases | User identifier, products purchased and store receipts. If deleting a customer record fails (for anonymous sessions, after several attempts), the team deletes it by hand |
| Don Dominio (Spain) and, if we use it, Resend (EU region) | Sending emails (sign-in and notices) and the info@menumentos.com mailbox | Email address and message content |
| Stripe Payments Europe, Ltd. (Ireland) | Payments from sponsors | Sponsors’ billing and payment data. Stripe acts as a processor to process the payment and as an independent controller for fraud prevention and its legal obligations |
| Expo (650 Industries, Inc.) | App updates without going through the stores | Technical data of the update request (such as the IP address, the platform and the app version). No notification identifier: the app’s notices are local |
Other users. What you make public (your public profile, what you publish signed) is seen by all users and visitors to the website, and by search engines. Validators also see what is being voted on before it is published (without your email, your identifier, your public name or your unpublished photos) and undertake, as the community terms say, not to use it for anything other than validating, but they are not our employees or processors: they are other users, with the limitations of those terms.
Third parties acting as controllers in their own right, with their own policies:
- Apple and Google (App Store and Google Play): they sell and charge for in-app purchases. We never see your card details. Also if you sign in with Apple or Google.
- Google (AdMob): ads, according to your consent. Google acts as an independent controller of the data it processes to serve and measure ads. More information: how Google uses data.
- Google Maps: the app’s map (see 2.5).
- OpenFreeMap: the website’s map tiles; your browser downloads them directly from their servers, which receive your IP address.
- Social networks and websites on profiles: if you open a link on someone’s profile (Instagram, TikTok, YouTube or a website), you leave menumentos for that page, which belongs to a third party acting as a controller in its own right, with its own cookies, and which will know, like any website, your IP address. The website also uses
noreferrerso that it does not know which page you come from, and the app warns you before opening it. We do not pass anything of yours. - Civitatis, GetYourGuide, Tiqets and other ticket providers: if you open a ticket offer (on the website or in the app, always marked «Affiliate link»), you go to the provider’s website with our affiliate ID and a campaign tag for the place or route, nothing of yours. That website belongs to a third party: it sets its own cookies (including the one that credits us with the booking) and what you do there is governed by its terms and privacy policy. If you book through these links, menumentos earns a commission; it costs you nothing extra. On our side we add one to that offer’s click count for the day, without storing who clicked, from where or with what device; and, in the app, if you accept analytics, the «offer opened» event is also sent, only with the provider’s name.
- IATI (travel insurance): if you open the travel insurance card (marked «Affiliate link · IATI»), which appears in «Before your trip» and on the city pages, on the website and in the app, you go to IATI’s website with our affiliate ID and a tag that only says in which of those places the card was, nothing of yours: we do not pass on your account, your email, the city you are looking at or what you have ticked on the list. That website is IATI’s: it sets its own cookies (including the one that credits us with the purchase) and what you do there, including taking out insurance, is governed by its terms and privacy policy. If you take out insurance through this link, menumentos earns a commission; it costs you nothing extra. On our side, at most we add one to that link’s click count for the day, without knowing who clicked, and, in the app, if you accept analytics, the «offer opened» event is sent, as with ticket offers.
International transfers: several of these providers are US companies or may access data from there, even if they store it in Europe. We only transfer data with a safeguard under Chapter V of the GDPR: the provider’s participation in the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023) or, if it does not participate, the standard contractual clauses approved by the Commission, with any supplementary measures needed. You can ask us for the details of each provider and a copy of those safeguards at info@menumentos.com.
Authorities: we disclose data to judges, law enforcement or authorities when the law requires us to.
5. How long we keep it
| Data | Period |
|---|---|
| Account and everything linked to it (profile, extended profile, mementos, progress, ratings, entitlements, points, reputation, email notice preferences) | As long as you have the account. If you delete it, it is deleted immediately, except for what this table says |
| Anonymous session without an account | Up to 12 months without use; then it is deleted together with what is linked to it. If it holds a route or a pass still in force, it is kept while they last, and if it made a report or has a sanction, until their period ends (below). Purchases can always be recovered with «Restore purchases». When it is deleted, we ask RevenueCat to delete its customer record; if we do not manage it within 30 days, we stop trying, and what stays there is the store purchase history linked to a random identifier that no longer belongs to any session |
| Extended profile (introduction, avatar, home city, links) | As long as you have the account; you change or delete them whenever you like. If you make it private, they stop being shown immediately. If you delete the account, they are deleted immediately |
| Declaration of being 18 or older (and its date) | As long as you have the account. If you withdraw it, the links and the creator mark are removed. If you delete the account, it is deleted with it |
| Unpublished contributions and their photos | Until you withdraw them or delete your account. A withdrawn contribution is deleted, with its photos, within two days at most, and disappears from the backups at most 7 days later |
| Published contributions, including public tips and lists | As long as they are published; you can withdraw your tips and lists whenever you like. If you delete your account, the published text stays without your name and your photos are deleted (see the community terms). Private lists are deleted with the account |
| Your «likes», what you mark as useful, whom you follow and your saved lists | As long as you have the account. If you delete it, they are deleted immediately (the public counters are recalculated) |
| Your validation votes (with their reason, weight, date and whether they were «on site») | As long as the content voted on exists. If you delete your account, they are deleted with it |
| Your reputation and the history of its changes | As long as you have the account; they are deleted when you delete it |
| Your invitation code and who invited whom | As long as you have the account; it is deleted when you delete it (the link with the invited person or with whoever invited disappears; passes already given are kept) |
| Invitation code stored in your browser | 7 days from when you open the link, or until you create the account |
| Request for the creator mark and its decision | As long as you have the account and the mark. It is deleted with the account |
| Questions to «ask the guide» | 30 days |
| Email notices already sent or discarded | 30 days. If you delete your account, they are deleted with it |
| Unsubscribe link in each email | It works for one year; after that you can unsubscribe in your account settings. If you delete your account, it is deleted with it |
| Voice requests | Until the text has audio or, at most, one year. If you delete your account, they are deleted with it |
| Reports and the decision on each one | 3 years from the decision; until it is decided, it is kept. The reasons for rejecting or removing a contribution go with it (above) |
| Reports of mistakes in the content that you send | 2 years from when you send them. If you delete your account, they stay without it until that period ends |
| Sanctions | While in force and 3 more years. If you delete your account, they stay without it (type, reason, dates and who decided it), and one still in force ends when you delete it |
| The team’s activity log (what the team did, with which account and the details of each action, such as what it searched for, which may be an email address, the reason for a sanction or why a deletion at RevenueCat failed) | 3 years |
| Code redemption attempts | 30 days |
| Groups to listen together (who is in each one, for which route and which stop) and failed attempts when typing a code | Deleted in the daily clean-up, once a day has passed since the group expired (12 hours after it was created) or was closed; failed attempts, one day. Always when you delete your account |
| IP address of reports from the website | Not stored with the report; 30 days at most |
| Anonymous technical notices | 90 days |
| Operation logs | 7 days for debugging ones, 30 for informational ones, 90 for warnings, 180 for errors and 2 years for those that prove an action (such as the deletion of an account). When you delete your account they are kept without it |
| Analytics (PostHog) | 12 months. The app never links your events to your account: they carry a pseudonymous device identifier, so when you delete your account nothing in them identifies it |
| Errors (Sentry) | 90 days |
| Emails you send us | As long as needed to deal with them and then up to 1 year |
| Sponsor billing | 6 years (Article 30 of the Spanish Commercial Code) and whatever tax law requires |
| Consents | While they remain valid and then 3 years so we can prove them. If you delete your account, we keep what you accepted, with its version and date, without the account for those 3 years |
When data is no longer needed but the law requires us to keep it, we block it (Article 32 LOPDGDD): it remains available only to judges and authorities during the limitation period for any liabilities, and is then deleted.
6. Your rights
You have the right to access your data, rectify it, erase it, object to its processing, restrict it, to portability, to withdraw your consent and not to be subject to automated decisions.
From your account, without writing to us:
- Download your data: in the account settings of the app or at menumentos.com/en/account, you get a JSON file with everything we hold linked to your account, including your profile, your tips and lists, your votes and your reputation, whom you follow and your «likes», your invitation code, the groups you have listened in, your email notice preferences, the notices we have sent you and your voice requests (access and portability, Articles 15 and 20 GDPR).
- Correct it: your public name, handle, introduction, avatar, home city, links, language, consents and email notices can be changed in the settings.
- Delete your account: in the account settings of the app or at menumentos.com/en/account. Your profile (with its introduction, avatar and links), progress, mementos, entitlements, unpublished contributions, private lists, your «likes», whom you follow, your reputation, your votes, your invitation code, your email notices, your voice requests and all your photos are deleted immediately; what was published, including public tips and lists, stays without your name, which disappears from the website immediately and from the downloadable packs that same night. The app never links your analytics events to your account, so nothing in them identifies it. We also delete your customer record at RevenueCat. Your reports, mistake reports, sanctions and consents, and the operation logs, are kept without your account for the periods in section 5.
- Withdraw consents: personalised ads, analytics and marketing communications, in the privacy settings of the app or your account; the public profile and the declaration of being 18 or older, in the profile settings (when you withdraw them, the profile stops being public and the links are removed). The location permission and the tracking permission (iOS), in your phone settings.
By email: write to info@menumentos.com from your account’s email or telling us how we can check it is you. We reply within one month at most (extendable by two more months in complex cases, letting you know). It is free. By email you can also ask for a person to review a validation decision, an automatic hiding, your reputation or your validator trust (see section 3), or object to processing based on legitimate interest.
Without an account: what the app stores without an account is on your phone and is deleted when you uninstall it. If you have an anonymous session (for example, because you bought without signing up), write to info@menumentos.com with the order number or the receipt of your App Store or Google Play purchase: it lets us find your session without asking you for other data.
If you believe we have not handled your rights properly, you can complain to the Spanish Data Protection Agency (www.aepd.es, C/ Jorge Juan 6, 28001 Madrid, Spain).
7. Minors
menumentos is a service for all audiences, but it is not aimed at children under 14. The app and the website do not ask for your date of birth. To create an account, to contribute content to the community, to validate and to have a public profile you must be 14 or older (Article 7 LOPDGDD), and you declare so when you do.
Children under 14 can listen to the audio guides without an account, but should not accept analytics or personalised ads: if a child uses the phone, we ask parents or guardians to reject those options in the consent message or in the settings. If we learn that an account belongs to a child under 14, we delete it.
What people under 18 cannot do. Links to social networks and websites on the profile, the creator mark and validating a place on site are only for people who declare that they are 18 or older. It is a declaration, not a verification: we do not ask for documents or a date of birth. If we learn that whoever made it is a minor, we remove their links and the mark. The rest of the community (public profile, validating, following, challenges with a reward) is open from age 14, and the public profile of a person aged 14 to 17 shows the same as an adult’s, except the links; that is why we recommend they do not put personal data in the introduction.
If you are a parent or guardian and believe that a child under 14 has given us data without your consent, write to info@menumentos.com and we will delete it.
8. Cookies and similar technologies
- On the website: we do not use analytics or advertising cookies, or third-party scripts, except the Cloudflare Turnstile security check when you sign in to your account (see 2.4), which sets no tracking cookies. The user area stores your session in the browser’s storage, which is strictly necessary for you to sign in, and, if you use «Before your trip», the boxes you tick on that list: they stay in that browser, never reach us, and you remove them with «Untick all» or by clearing your browser data. If you open an invitation link (
?i=), the website stores the code and the date in your browser for 7 days to redeem it when you create the account: it is not sent to our servers until the account exists, it is deleted when redeemed or after 7 days, and whoever invites only sees how many people have arrived and how many are active, never who. This is storage necessary for a feature you ask for, with no separate consent. More detail in the cookie policy. - In the app: the AdMob component and, with your consent, the PostHog one access information on your device (such as the advertising identifier). We ask you first with the consent message and you can change your choice in the app’s privacy settings. The Cloudflare Turnstile security check (see 2.4) is loaded in a web view inside the app, without tracking cookies.
9. Security
We encrypt communications, limit access to data to the team members who need it (every access to a user’s record is logged) and each user can only read their own data. If we suffer a security breach that poses a risk to you, we will notify the AEPD within 72 hours and, if the risk is high, you too.
10. Changes to this policy
If we change anything important, we will let you know in the app or by email before it applies. The current version is always at menumentos.com/en/privacy, with its date.