What’s changed since the version of 2 October.
- The app is being tested by real people, so we no longer describe it in the future tense.
- The Android test has its own section (section 3).
- What the app handles since October: the date of birth, which is checked and not stored; what you’re here for; fixed sessions; invite codes; “Play again?”; “Shows up” and “Who didn’t show up?”; and the new-session notice.
- If you signed in with Apple, when you delete your account we ask Apple to remove its access.
- IONOS, which runs our email, joins the list of who handles your data.
- Since 9 October, invite codes delete themselves 30 days after they expire or are cancelled, and deleting your account deletes them straight away; your identifier no longer stays in other people’s closed sessions either.
- Since 11 October, the app no longer shows game covers, so RAWG no longer receives your phone’s IP address. There’s nothing for you to accept: this policy informs you, and less is handled than before.
- Since 11 October, this website’s forms go through our server before they’re saved: it counts the submissions from each IP address for an hour, to stop anyone filling them in on a loop, and doesn’t store it (section 5).
- Since 12 October, the app keeps the requests you decline and the conversations you delete, for you alone: whoever said hi isn’t told (section 6).
- A report for “Looks under 16” or “Explicit sexual content” takes something out of view straight away up to three times a day per person; after that it waits for three different people (section 9).
- Since 13 October you can share your personal link. Whoever opens it sees your username and nothing else about you, and can only send you a request (section 6 and section 7).
- Since 13 October, if you report a message from a chat between the two of you, the report keeps its text and time, only to review it and so we can defend ourselves if there’s a claim. It’s deleted with the report after two years, even if whoever wrote it deletes their account sooner (section 6 and section 12).
- Since 13 October, the founder number goes to the first hundred verified accounts, and if you sign up with email we send you one to confirm it (section 6).
The short version.
- If you’ve only joined the waitlist, we keep your email, the date, and the fact that it came from this site. Nothing else.
- If you’ve signed up for the Android test, we keep your Google account email, the language and the date, and it’s deleted after sixty days.
- This site uses no cookies, stores nothing on your device and has no analytics. That’s why there’s no banner.
- The app is in testing: the people we invite are using it, and everything we describe about it already applies.
- We don’t sell your data, we don’t pass it to advertisers and we don’t build advertising profiles.
- There’s no voice in GAMERLY: we don’t transmit or record audio.
- For anything about your data: contacto@gamerly.es.
1. Who the controller is
The controller of your data is Rafael Ruiz Moreno, who develops GAMERLY as a personal project. It isn’t yet a registered business, so there’s no tax ID or address to publish; the channel for everything, including exercising your rights, is contacto@gamerly.es, and it’s read by a person.
2. The waitlist
This is the section that applies to you if you’ve left your email on gamerly.es. It’s a separate use of data from the app’s.
What we keep
Your email, the date and time you sent it, the origin — which page of this site you came from — and, if you tell us, what you’re going to play: one of the games on the list or, if you pick “Something else”, whatever you type there, 40 characters at most. And nothing else: our server rejects any other field, so it doesn’t depend on the website behaving itself.
What for
To write to you once, on the day the app is available, before we announce it anywhere else. We won’t send you newsletters, news, surveys or offers.
Being on the list doesn’t reserve any founder number: those numbers are handed out inside the app, to the first hundred verified accounts (the terms explain how).
On what legal basis
Your consent (Article 6(1)(a) GDPR), which you give by ticking the box on the form. The box isn’t ticked in advance, and the form won’t send without it.
For how long
Until we tell you about the launch or until you ask to be taken off, whichever comes first; after that it’s deleted. If the project never launched, we’d delete the whole list.
Emails that were already on it
Anyone who signed up through the previous version of this website is still on the list, for the same purpose and period they consented to: one notice, once, when the app is released.
How to come off it
Write to contacto@gamerly.es and ask. You don’t have to give a reason. Withdrawing consent is as easy as giving it.
3. If you sign up for the Android test
This is the section that applies to you if you’ve left your email on gamerly.es/en/beta to try the app before it comes out. It’s a separate use of data from the waitlist’s and from the app’s.
What we keep
Your Google account email, the language of the page you signed up from, that you ticked the box, and the date. And nothing else: our server rejects any other field.
What for
To give you access to the Google Play closed test and to write to you about it: the link to get in and, if needed, the odd notice while it lasts, such as a new version being out or the test having ended. We won’t send you newsletters, news or offers, and this email doesn’t go on the waitlist.
Who else sees it
To give you access, we add your email to the app’s tester list in Google Play Console: that’s how Google lets you into the test, and it handles it under its own privacy policy. We send you the email with the link from contacto@gamerly.es, which is run by IONOS (section 10).
On what legal basis
Your consent (Article 6(1)(a) GDPR), which you give by ticking the box on the form. The box isn’t ticked in advance, and the form won’t send without it.
For how long
Your email deletes itself sixty days after you sign up, which covers the whole test. It doesn’t depend on anyone remembering: the database has an expiry set on each email, and the deletion can take up to a day longer because the service does it in batches. When the test ends, we also empty the tester list in Google Play Console. If you create an account in the app, that account is separate and covered by section 6.
How to come off it
Write to contacto@gamerly.es and we’ll delete your email. To leave the test on Google Play, open the test link again and leave from there. Withdrawing consent is as easy as giving it.
4. The guild list, closed
Until 17 October 2026, the WoW Forever page had a list of guilds and a form to add yours. We closed it that day, and since then we don’t collect any guild data. There were no submissions left in storage, and the entries that were published came off the website with the list.
If you sent us one and want to ask us anything about it, email contacto@gamerly.es.
5. This website
gamerly.es doesn’t set cookies, doesn’t use browser storage, and has no analytics or resources from other domains. The fonts are hosted here.
As with any website, your browser connects to the servers that deliver it (Firebase Hosting, from Google), and those servers receive your IP address so they can send you the page. We don’t keep visit logs. The waitlist and Android test forms, and the page of an invite link (gamerly.es/i/…), are the only requests that go to another server, also Google’s: the forms, only when you send them, to a function on our server that counts the submissions from each IP address for an hour — to stop anyone filling them in on a loop — and doesn’t store it; the invite page asks our server for that code’s details, with the code and nothing else. In both cases the IP address stays in the technical log of each request that Google Cloud keeps, and it deletes itself after thirty days.
6. What data the app handles
The app is in testing: until it’s in the stores, it’s used by the people we invite to try it, and everything below already applies.
Account
Your email and password, or signing in with Apple or Google. With Apple we receive an identifier and your email, which may be the private relay address Apple creates for you. With Google we receive an identifier, your email and your Google account name, which the app suggests as your username and you can change. We don’t use your Google account photo: GAMERLY has no profile photos. We don’t receive Apple or Google passwords, or access to anything else in those accounts. There’s no sign-in by phone number. If you sign up with email, we send you one to confirm the address — Firebase sends it, like the password-reset one — and we keep whether you’ve confirmed it.
Age and acceptance
To sign up we ask for your date of birth. The app sends it to our server only to check that you’re 16 or older, and we don’t store it anywhere, not even the year. What’s kept is that you confirmed you’re 16 or older, only as a yes, that you confirmed it with the date, and a mark on your sign-in account saying the check passed. If you’re under the age, no account is created and we keep nothing from the attempt. We also keep the version of the terms you accepted, the date, and the screen where you did it, so we can show what you saw.
Profile
Your username; the avatar from GAMERLY’s collection that you wear, which is what others see (we assign you one when you sign up and you can change it); your game region, one of six continental ones, which the app suggests from your phone’s time zone and you can change in settings; your time zone, languages, and the time slots, days and hours you usually play; your games, with the rank you declare, your roles and your class in the ones that have them; how you talk while you play (I don’t use a mic, I talk a little, I talk a lot or I call the shots); what you’re here for, if you say (chill, to win or learning); a line of up to 90 characters about what you’re looking for; the language you want the app in; which notifications you want; and, if you add them, Discord invite links (yours, a group’s or a squad’s). If you signed up from a group’s link, also which group you came from and from which page.
Your in-game name or code (for example, your Riot ID or your CS2 Friend Code) is optional: the app asks for it when you join a session in that game, and you can leave it blank.
Public profile
If you turn it on, a copy of part of your profile goes into the queue of people others can see (see section 7). It’s off by default, you’re the one who turns it on, and when you turn it off you leave the queue at once.
What you do in the app
- Passes and greetings: who you pass and who you say hi to, with the greeting message (up to 240 characters) and, if you invite them to one of your sessions, which one. It’s used so we don’t show you people you’ve already seen: someone you pass, for 30 days or until you ask for another round; someone you say hi to, for good.
- Messages in one-to-one and group chats (text and invitations; images can’t be sent), and in the text room the app opens when a session closes, for the people who were inside. In that room, your vote on “Staying together as a group?”.
- Requests you decline and conversations you delete: that you declined or deleted it, and when, so we don’t show it to you again or notify you about it (a deleted conversation comes back if someone writes again). It’s kept under your account and not in the conversation, so whoever said hi isn’t told and can’t find out.
- Groups you create or join: name, description, game, languages, schedule, members, requests, whether it’s recruiting and when there was last activity, which the server records.
- Game sessions you post or join: game, mode, roles, declared rank, languages, time slot, what you’re all there for and who joins. If you post a fixed session (“every Tuesday at 22:00”), the days, the time, your time zone and the length of the series, and for each date who’s going and who said “Not this one”.
- Invite codes: the code, who created it, which session or group it leads to, when it expires, whether it was cancelled and how many times it was used; and how many codes you create and try each day, against spam and against anyone trying to guess them. Your personal link carries one of these codes, which leads to you instead of to a session: we keep the same, and the times it’s been used are the requests it has brought you. It expires after seven days.
- Games played: when a closed session ends, the game with who was inside; your answer to “Did you play?” and, if you want, to “Who didn’t show up?”.
- “Play again?”: who from a game you’d bring along again, and with whom it was mutual.
- Ratings: the positive tags you choose for your teammates or receive from them.
- “Shows up”: a figure the server works out from the games played (section 9).
- Reports and blocks: the reason, whatever you write, the context and a copy, made by the server when the report arrives, of what was reported as it was at that moment: the person’s username, avatar and what they’re looking for, or the group’s name and description; and if you report a message from a chat between the two of you, its text and time. That text is kept inside the report, only to review it and so we can defend ourselves if there’s a claim, and it’s deleted along with it. And who you’ve blocked.
- Notices: a copy of each notice we send you (the same text, where it takes you and who caused it), so you can see in the app what’s happened even if notifications are off. It deletes itself after 30 days. And the day we told you about a new session, so we don’t do it more than once a day.
Presence
Whether you have the app open right now and when you last opened it (“1 h ago”). It’s what lets us show who’s around instead of how many people there are. The app doesn’t record what you’re playing.
Founder, frames and titles
If you’re one of the first hundred verified accounts, your founder number and the date. And the frames and titles you’ve unlocked, and which ones you’re wearing.
Technical data
- Your device’s notification token, if you turn notifications on.
- Error reports: what failed, on which screen, with which version, device model and operating system. They don’t include your email or your name, and we strip identifiers before sending them.
- The installation identifier the app sends to Expo when it checks for updates (see section 10).
- Daily counts of greetings, new conversations, reports, groups created and invite codes created and tried. The greetings, reports, groups and codes ones apply their limits (section 9); the new conversations one only orders the review queue.
- Weekly aggregate figures on use of the service, which don’t identify anyone.
There’s no third-party advertising or analytics SDK in the app.
If you report illegal content
If you tell us about content you consider illegal, through gamerly.es/report-illegal-content or by email, we handle your name, your email, what you tell us, any screenshots you attach and the decision we take. You don’t need an account. If it concerns child sexual abuse, you can do it without giving your name or email. We don’t reveal your identity to the person reported unless it’s strictly necessary.
7. Who sees what
| Data | Who sees it |
|---|---|
| Your email, your account and your reports | Only you (and us, to run the service). |
| Your public profile: name, avatar, languages, region, schedule, your games with the rank you declare in the ones that have one and your class, genres, how you talk, what you’re here for, “what you’re looking for”, founder number, the frame and title you’re wearing, the titles you’ve earned, the tags that already show, “Shows up” if it’s shown, and the day you were last online | Anyone with an account, while you have it switched on. |
| A session you post: the game, the mode, the roles you’re looking for, your declared rank, your languages, your region, the time slot or time, your username, how you talk, what you’re all there for and who has joined | Anyone with an account, while the session is open. The dates of a group’s fixed session, only its members. |
| Your in-game name or code and your Discord link | Only the people inside your session at the moment it closes, and nobody with whom there’s a block. Never in a list or on your profile. |
| An invite code you create | Anyone with the link, even without an account: the game, the time and the free spots of the session, or the group’s name, its languages and its next fixed session; and your username as the person inviting. Nothing else: not who’s inside, not how many. |
| Your personal link | Anyone with the link, even without an account: your username, and nothing else about you. From the app, all they can do is send you a request, which reaches you like a hi. |
| Whether you’re online and when you last were | People with an account. |
| Your messages | The people in that conversation, that group or that room. |
| That you declined a request or deleted a conversation | Only you. Whoever said hi isn’t told and can’t find out. |
| The names and avatars of a group’s members | Only the other members. Someone outside sees the group’s name, game, languages, schedule and description, whether it’s recruiting and how many of its people are online. |
| Your name and avatar in a session’s room | The people in that room, even if your profile is private. |
| Your vote on “Staying together as a group?” and your “Play again?” list | Only you. Nobody knows who said no or who you didn’t pick; if you both pick each other, you both know it was mutual. |
| Your answers to “Did you play?” and “Who didn’t show up?” | Only you. People in the game see who answered that it wasn’t played, and who was marked absent by two or more different people, but not who said it. |
| Rating tags | A tag only appears on your profile once three different people have given it to you. Nobody sees who gave which. |
Anyone you block stops showing up for you in the deck and in sessions, silently; your conversation with that person is closed and you don’t see their new messages. In a group or a session’s room you share, that person can still read what you write: hiding it would tell them you’ve blocked them. If you’d rather they didn’t, leave the group or the room — for groups, the app offers that when you block. The app has no people search: you reach people through the queue.
8. What for, and on what legal basis
| Use | Purpose | Legal basis | Retention |
|---|---|---|---|
| Waitlist | Telling you once about the launch. | Consent (6(1)(a)). | Until the notice or until you come off it. |
| Android test | Giving you access to the test and writing to you about it. | Consent (6(1)(a)). | Sixty days from when you sign up. |
| Account, profile and acceptance | Giving you access and being able to show what you accepted. | Performance of the contract (6(1)(b)). | While you have the account. |
| Age check | Making sure only people aged 16 or over get in. | Performance of the contract (6(1)(b)) and legitimate interest in protecting minors (6(1)(f)). | The date of birth, none: it’s used and thrown away. The mark that you’re old enough, while you have the account. |
| Public profile | Letting other people get to know you in the queue. | Performance of the contract (6(1)(b)), at your request when you turn it on. | Until you turn it off or delete the account. |
| Queue, greetings, chats, groups, sessions, fixed sessions and games played | Meeting people, talking and playing. | Performance of the contract (6(1)(b)). | While you have the account. |
| Session rooms | Talking with the people who were in the session. | Performance of the contract (6(1)(b)). | Each room, until three days after its session’s time slot ends, or that of the last one you close together. After that, a daily task deletes it with all its messages. |
| Invite codes and your personal link | Letting you bring people to a session or a group, or to write to you. | Performance of the contract (6(1)(b)). | They stop working when they expire or are cancelled, and the record deletes itself 30 days later (it can take up to a day longer). If you delete your account, they’re deleted straight away. |
| Presence | Showing who’s around. | Performance of the contract (6(1)(b)). | While you have the account. |
| Ratings, “Play again?” and “Shows up” | Showing what each person does well as a teammate and who usually shows up, and letting you play together again. | Performance of the contract (6(1)(b)). | While you have the account. |
| Reports, blocks, limits and moderation | Protecting the people who use the service, meeting the app stores’ rules and being able to defend ourselves if there’s a claim. | Legitimate interest in safety (6(1)(f)). | Reports, two years from the report, including the text of any reported message inside them. The summary that orders the review queue, while the account exists, and anonymised after that. |
| Notifications | Telling you what’s happening with your sessions, your messages and your groups, about a new session in your games at most once a day, and asking whether you played after a game. | Consent, when you turn them on (6(1)(a)). | While you have them switched on on your phone. |
| Notices inside the app | Letting you see what’s happened even if notifications are off. | Performance of the contract (6(1)(b)). | 30 days. |
| App updates | Letting the app get fixes without going through the store. | Legitimate interest in the app working (6(1)(f)). | We don’t keep it: Expo receives it to serve the update. |
| Error reports | Knowing what fails so we can fix it. | Legitimate interest in the app working (6(1)(f)). | Up to 90 days. |
| Emailing us | Replying and dealing with what you ask. | Legitimate interest in helping you (6(1)(f)), or legal obligation if you’re exercising a right (6(1)(c)). | As long as it takes to deal with what you ask and, after that, only what the law requires us to keep. |
| Illegal content notices and communications with authorities | Handling notices, deciding, telling the people affected and complying with orders. | Legal obligation (6(1)(c)): Regulation (EU) 2022/2065, Articles 16 to 18. | One year from the decision, or as long as an open procedure lasts. |
| Deletion requests made without the app | Checking the account is yours and deleting it. | Legal obligation (6(1)(c)): handling your right to erasure. | 14 days from the request; your email address comes out sooner, when it’s handled. The email you send to ask, a month after it’s handled. |
9. What’s decided automatically
No automated decision has legal effects on you, and we don’t build advertising profiles. But there are things the system does on its own, and we want you to know about them:
- The order of the queue. People are ordered by what you have in common: games first, then genres, languages, what you’re here for, how you talk, region and recent activity. Never by reputation, frame or “Shows up”. No compatibility score is calculated or shown.
- “Shows up”. The server counts how many of your games you turned up to: a game counts if someone in it was new to you, and an absence only counts if two different people mark you absent. It shows on your card and profile, as “9 of 10”, only with five games or more and eight in ten or more. A lower figure isn’t shown to anyone, you included, and it doesn’t order or decide anything.
- The new-session notice. We tell you about a new session only if your game, your language and your time slot match and there’s a spot left; at most once a day, never between 00:00 and 09:00 your time and never with someone where there’s a block. You can switch it off in Settings › Notifications.
- Daily limits. There’s a maximum number of greetings, reports, groups created and invite codes created and tried a day, and of messages in a row to someone who hasn’t replied yet. They slow down anyone writing to people in bulk or trying to guess codes.
- Precautionary withdrawal. When three different people report a profile or a group, it stops being shown until a person reviews it. If the reason is “Looks under 16” or “Explicit sexual content”, one report is enough, up to three a day from each person: from the fourth on, their report waits for three different people like any other. It isn’t a penalty: it’s taking it out of view while it’s looked at.
- Text filter. Names, greetings, messages and descriptions containing hate speech or explicit sexual content aren’t saved. The filter doesn’t apply to reports.
- Behaviour signals. Hitting those limits again and again moves someone up the review queue, so that what’s most worrying gets looked at first. Any measure is decided by a person.
If one of these affects you and you disagree, write to us and a person will review it.
10. Who else handles your data
Processors, who handle data on our behalf
| Who | What for | Where |
|---|---|---|
| Google Ireland Limited (Firebase and Google Cloud) | This website, the forms, the database, account sign-in and its emails for confirming your address and resetting your password, the server functions and presence. | European Union, with account sign-in as a global service (section 11). |
| Functional Software, Inc. (Sentry) | The app’s error reports. | Germany region. |
| 650 Industries, Inc. (Expo) | Getting notifications to your device: it receives the token, the title, the text and a technical identifier for the notification. And serving the app updates that don’t go through the store: when the app checks for them, it receives your phone’s IP address and an installation identifier. | United States (section 11). |
| IONOS | The contacto@gamerly.es mailbox: it receives what you write to us and what we reply, including the Android test link. | European Union. |
Each of them handles your data only for what we ask, under a data processing agreement that requires them to protect it with the same safeguards as this policy.
Others involved
- Apple and Google deliver notifications to your phone (APNs and Firebase Cloud Messaging) and, if you choose them, handle signing in with their account, under their own policies. If you sign up for the Android test, Google receives your email in Google Play’s tester list (section 3).
- GitHub serves the fonts for Japanese and Korean, which the app only downloads if it has to display those scripts. It receives your IP address and nothing else.
- Discord isn’t one of our processors. If you add an invite link, you’re the one adding it; when you open it, you leave GAMERLY. We don’t share any data with Discord.
We don’t sell your data, we don’t pass it to advertisers and we’re not part of any advertising network. If this list changes, this page will say so before the change happens.
11. Where it’s handled
- The database, in Google’s eur3 multi-region (Belgium and the Netherlands).
- Presence and the server functions, in europe-west1 (Belgium).
- Error reports, in Sentry’s German region.
Data being hosted in the European Union doesn’t mean nobody outside it can access it. Account sign-in (Firebase Authentication) is a global Google service, and Google may use staff and sub-processors outside the European Economic Area. Expo operates from the United States. Those transfers rely on the European Commission’s standard contractual clauses included in their data processing agreements and, where it applies, on the EU-US Data Privacy Framework. You can ask us for a copy of the safeguards at contacto@gamerly.es.
12. What happens when you delete your account
You can delete your account from the app’s settings, in a few taps and without giving a reason. Deletion is real and immediate: there’s no grace period and no way to get it back. If you don’t have the app any more, ask us by email; the steps are at gamerly.es/delete-account, and the same things get deleted.
If you signed in with Apple, before deleting the app asks Apple to remove GAMERLY’s access to your Apple ID. If that isn’t possible, it tells you and explains how to remove it yourself from your iPhone’s settings. From that attempt we only keep how it ended, with nothing that identifies you.
Deleted
- Your account, your profile, your public profile, your presence and your preferences.
- Your sessions and fixed sessions, your passes and greetings, your blocks and your in-game name or code.
- Your messages. In their place there’s the line “This account has been deleted”, so the other person’s conversation still makes sense.
- Your answers to “Did you play?” and “Who didn’t show up?”, your “Play again?” list —and your name from other people’s lists— and your votes in rooms.
- The ratings you received, “Shows up” and the notification identifiers of your devices.
- The invite codes you created, and your identifier in other people’s sessions: in the list of who was inside when they closed and in the fixed-session dates where you said “Not this one”.
Not deleted, and why
- Reports other people made about your account, with the text of the message of yours they reported, if any, are kept, anonymised, for two years from each report, only to review them and so we can defend ourselves if there’s a claim. That way there’s a record of what happened and of who spoke up, even though the account is gone.
- The reports you made stay without your name, with the text you wrote: they’re what you told moderation about someone else.
- If we ever withheld your profile or a group, the message explaining why is kept for a year from the decision, with your email address. The Digital Services Act requires it.
- If you ask for deletion without the app, we keep the request for 14 days; after that it deletes itself, though it can take up to a day longer, because the database does it in batches. Your email address comes out of it as soon as we handle it, and until it expires a fingerprint of it stays, which is what makes asking twice count as a single request. The email you send us to ask, we delete from our inbox a month after handling the request.
- The ratings you gave stay without your name, because they’re part of other people’s profiles.
- In other people’s chats and games, an anonymous participant stays in your place, so their history doesn’t change shape. You leave other people’s groups and sessions as if you’d gone, and a group with nobody left in it is deleted.
- Your founder number goes with your account and is never handed out again.
13. Your rights
You can exercise them whenever you want, free of charge:
- Access: knowing what data we hold and asking for a copy.
- Rectification: correcting what’s wrong.
- Erasure: having it deleted, within the limits of section 12.
- Objection to what we do on the basis of legitimate interest.
- Restriction: freezing a use of your data while a disagreement is resolved.
- Portability: taking your data with you in a reusable format.
- Withdrawing consent, without affecting what was done before.
Write to contacto@gamerly.es from your account’s email, saying which right you want to exercise. If you write from another address, we may ask you for something that shows it’s you, and only for that. We reply within a month at most; if we need longer, we’ll tell you within that month, and why.
14. Minimum age
To use GAMERLY you have to be 16 or older, and we check it with your date of birth when you sign up, without storing it (section 6). We don’t knowingly handle data of anyone under 16: if we find an account that doesn’t meet the requirement, we close it and delete its data, with the same exceptions as deleting it yourself (section 12). If you’re a parent or guardian and think someone under 16 has an account, write to us. What we do against child abuse is on the child safety page.
15. Security
All traffic is encrypted, the data is stored encrypted on Google’s servers, and access to it is restricted by rules that stop anyone reading what isn’t theirs. One example you can check: the waitlist lets you add an email, through our server, and doesn’t let anyone read it, not even whoever wrote theirs. That’s why the form never says whether your email was already there.
No system is infallible. If a breach meant a high risk to you, we’d tell you without delay, and the Spanish Data Protection Agency within 72 hours at most.
16. Changes
If we change this policy, the date at the top will change. If the change is substantial (a new processor, a new purpose, a new transfer), we’ll let you know before it comes into force: by email if you have an account, and with a notice in the app. If your consent is needed, we’ll ask for it; we won’t take it for granted because you keep using the service.
17. How to complain
First, write to us at contacto@gamerly.es: we’d rather sort it out directly. But you don’t have to go through us. You can complain to the data protection authority of the country where you live. Ours is the Spanish Data Protection Agency (Agencia Española de Protección de Datos), C/ Jorge Juan, 6, 28001 Madrid, at www.aepd.es.