LinkedGames Privacy Policy
This is the English version of the LinkedGames privacy policy. The Spanish version (linkedgames.fukitifu.com/privacy/) is the governing version in the event of any discrepancy. This English version is published at linkedgames.fukitifu.com/privacy/en/.
1. Who processes your data
The data controller is Javier Blanco, a natural person established in Spain.
- Contact for any privacy matter: metalbemba@hotmail.com
This is the only channel enabled for exercising your rights and for any question about this policy. No postal address is published. No data protection officer is appointed; if one is appointed in the future, it will be stated on this same page.
2. What this policy covers
This policy applies to:
- the LinkedGames mobile application for Android and iOS, in any officially distributed version;
- the website https://linkedgames.fukitifu.com.
It does not apply to Google, Apple, Google AdMob or any other third-party page you may reach from the application or from this website. Each of those pages has its own privacy policy.
3. The essentials
- You do not need to create an account or give us your email address to play.
- If you play without signing in, we only store technical data about your installation and your games, and we do not know who you are. That data is deleted automatically 12 months after your last activity.
- If you sign in with Google, we receive only an internal identifier of your Google account. We do not receive your email address, your name, your photo or your language, and we do not store them.
- We do not sell your data. When Google serves an ad, Google AdMob collects advertising data (the advertising identifier, technical device data and ad-request data) and processes it as an independent advertising provider under its own policies, as explained in sections 4.5 and 6. We do not send Google your identity.
- Before requesting any ad, the application shows you Google's consent form (UMP); depending on what you decide there, Google may show you personalised or non-personalised ads. We do not build advertising profiles and we do not send Google your identity.
- Usage analytics and crash reports are optional and turned off until you authorise them.
- You can delete your account and all your data yourself from the application or, if you no longer have it installed, by writing to metalbemba@hotmail.com.
4. What data we process
4.1 If you play without an account (guest)
When you first open the application, a random installation identifier is created on your device and stored in the application's private storage. That identifier:
- is not your name, your email address or any personal detail;
- identifies only that specific installation of the application;
- is sent to our server, where we store only an irreversible fingerprint (a cryptographic digest) and never the original value;
- is never displayed on screen and never logged in the clear on our servers.
Linked to that identifier we store:
| Data | Why |
|---|---|
| Games played (puzzle, difficulty, Daily or Unlimited mode, date) | To resume your game and avoid showing you puzzles you have already seen |
| Result (time, errors, hints used, whether you used help) | To show you your results and statistics |
| Coin balance and movements | So your balance is the same across the devices of that installation |
4.2 If you sign in with Google
When you tap "Sign in with Google", Google shows you its own screen and gives us an identity token. Our server validates it and extracts only an internal identifier of your Google account, which becomes an opaque LinkedGames code (your "account identifier").
We do not receive or store:
- your Google email address;
- your first or last name;
- your profile picture;
- your language, country or date of birth from your Google account;
- your contacts or any other data from your Google account.
The application shows that account identifier on your profile, so you can quote it when you exercise a right or request deletion. That identifier is a code for your account, not a piece of your Google account data.
In addition, to keep your session:
| Data | Why |
|---|---|
| Access token (expires in 15 minutes) | So the application can talk to our server |
| Refresh token (stored only as an irreversible fingerprint) | So you do not have to sign in every time |
| Session creation date and last use | Security: to be able to close and expire sessions |
| Account status (active or disabled) | To be able to block accounts for abuse |
On your phone, these tokens are kept in the operating system's secure storage (Keystore on Android, Keychain on iOS), never in plain text and never in the game database.
4.3 Your games and your coins
We store your games, results, hints used and coin movements on our server, always calculated and verified by the server. Coins are earned by playing; they cannot be bought with money and cannot be transferred to another person (the only possible transfer is from your guest balance to your own account the first time you sign in).
We also store your public alias and the friendships you create, and the Daily results you publish on the leaderboard. When you delete your account, that whole history, your coins, your transactions, your alias and your friendships are deleted too.
4.4 Analytics and application stability
LinkedGames uses Google Firebase Analytics and Google Firebase Crashlytics. Analytics data retention is configured at 14 months.
- Firebase Analytics tells us how many people play, in which mode, at which difficulty, whether they complete or abandon, and how long they take. We send it no identifier of yours: not the installation identifier, not the account identifier, not your email address, not the puzzle identifier, not the board contents. As with any service of this kind, Google's own SDK generates and uses technical identifiers for the application installation (for example a Firebase installation instance identifier) to group data and calculate statistics; we do not use them to identify you. Google also infers the country you play from using the IP address at the moment the data is collected.
- Firebase Crashlytics sends us a report when the application crashes, with the device model, the system and application versions, the error trace and the application state at the moment of the crash, so we can fix it.
Firebase Analytics data is processed with the Europe location selected in our configuration, and Google may process data outside the European Economic Area under its own policies. Firebase Crashlytics offers no equivalent location option, so its data may be processed outside the European Economic Area. In every case Google acts as the provider and applies the transfer mechanisms described in section 7.
We do not receive or store the IP address: Google uses it at the moment of collection to derive the country. We neither request nor use city or more precise location reporting, and the application requests no location permission.
Usage Analytics and Crash Reports are optional, initially off, and independently controlled in Settings → Data and diagnostics. Nothing is preselected on first use. An explicit grant enables the selected service in the same application session. Analytics consent is not inferred from sign-in, notifications, advertising consent or crash-report consent.
Without Analytics authorization the application does not forward usage events. Withdrawal blocks new application-managed events immediately and requests that Analytics collection be disabled; requests already sent cannot be recalled.
Crashlytics follows Google's standard opt-in lifecycle. While automatic crash reporting is disabled, its native SDK may retain crash information locally on the device. Pending reports may be uploaded after a subsequent authorization. Withdrawing Crash Reports consent immediately stops new application-managed error submissions and requests that automatic collection be disabled. Native changes may become fully effective on the next application launch; previously transmitted reports cannot be retroactively cancelled. We do not promise synchronous deletion of locally pending reports.
You can change either choice at any time in Settings → Data and diagnostics. These controls are separate from notification permission and advertising privacy options.
4.5 Ads and consent
LinkedGames shows Google AdMob ads:
- a voluntary rewarded video ad: it is shown only if you ask for it, in exchange for in-game coins;
- a full-screen ad between one puzzle and the next in Unlimited mode.
Before requesting any ad, the application shows you Google's consent form (UMP), in accordance with Spanish and European law. Your choices in that form determine which advertising data Google may process and whether the ads are personalised or non-personalised. With your consent, Google AdMob may collect and process the device's advertising identifier, technical device data (such as the model, the system version and the language) and ad-request technical data (such as the IP address, the application version and the ad unit), and may use data derived from your activity to select the ads. That identifier and that data never reach our servers and we do not use them. We do not build or use advertising profiles of our own and we do not use your LinkedGames activity to target ads. Google processes that data as an independent advertising provider, under its own policies. We do not send Google your account identifier, your installation identifier, your email address or any application token: for the rewarded video, the only value that travels to Google is an anonymous single-use token, and the coin is granted by our server only when Google confirms in a signed message that the video was completed.
You can review or withdraw your advertising choices at any time in Settings → Data and diagnostics → Advertising privacy options. If you refuse consent you can keep playing normally and no game feature changes; Google may show you non-personalised ads or, if no inventory is available, no ad at all. Withdrawing consent does not remove ads, but it prevents advertising that requires that consent.
4.6 Functional notifications
For signed-in accounts, LinkedGames uses Firebase Cloud Messaging (FCM) for neutral notices about friend requests and acceptances, optional Daily reminders and operational communications about the service. The three account preferences — friendship, Daily reminders, news and announcements — default to enabled and can be changed independently in Settings. Those communications are not advertising. Device notification permission is separate; enabling a preference does not authorize the operating system to show a notification. The news preference alone does not authorize promotional messages, which require their separately approved authorization.
Our backend associates an installation with the current account/session and stores an encrypted routing token, keyed continuity proof, current notification language, permission and app/build version. The application keeps its random installation continuity secret in secure local storage; we do not use hardware identifiers. Firebase uses its own installation identifiers and routing tokens and processes technical service data to provide Messaging. The messages contain neutral text, random message/audience references and expiry information, never private aliases, invitation tokens, account identifiers or puzzle solutions. Firebase receives no LinkedGames account or session identifier from this notification integration.
You can disable each category in Settings or withdraw device permission in system settings. Signing out, changing accounts or deleting the account invalidates local notification access immediately when safely completed. With no connection, server cleanup waits for reconnection through an authorized new binding or lease expiry; we do not retain signed-out credentials to retry it. Already accepted messages cannot be recalled from the provider, and delivery/background execution is not guaranteed. Token deletion, Firebase Installation deletion and backend account deletion are different operations; provider deletion is best-effort and preserves any other independently authorized Firebase purpose. Notification permission grants no analytics, crash-report or advertising consent.
4.7 Invitations and sharing links
If you are a signed-in account, you can create LinkedGames invitations and sharing links. The application generates a single-use random token with an expiry and only its irreversible fingerprint is stored on the server. The link you share contains that token: someone who opens it in the application sees the inviter's public alias, but not your account identifier or the state of your games, and the friendship is created only if that person expressly accepts it. A link you share yourself is not a communication from us: you choose the messaging application and the recipient. Links expire and you can revoke them; their expiry is not treated as activity.
5. Why we use your data and on what legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the game: games, results, statistics and coins | Game data, installation identifier, account identifier | Performance of a contract (the application's terms of use) |
| Identifying you when you sign in with Google and keeping your session | Google internal identifier, session tokens | Performance of a contract |
| Not showing you puzzles you have already seen | History of puzzles shown | Performance of a contract |
| Social features: alias, friendships, invitations and the Daily leaderboard | Alias, friendships, invitation tokens, ranked results | Performance of a contract |
| Security: preventing abuse, cheating and automated use | IP address (transiently), technical request data, account status | Legitimate interest in protecting the service |
| Functional friendship notices, Daily reminders and operational communications | Installation routing/continuity, notification preferences and language, neutral message data | Performance of a contract |
| Usage analytics | Game events without identifiers, approximate country, technical device data | Your consent |
| Crash reports | Technical crash and device data | Your consent |
| Showing ads and managing your advertising consent | Consent, advertising identifier and technical data processed by Google | Your consent |
| Answering your rights requests | The data needed to handle the request | Legal obligation |
6. Who we share data with
We do not sell your data. We do not share it with third parties for advertising or commercial purposes, except for the advertising data that Google AdMob collects when it serves an ad and processes as an independent advertising provider under its own policies (sections 4.5 and 7). We send Google no identity. The following providers take part:
| Provider | Service | Role and what it processes |
|---|---|---|
| Google Sign-In | Google provides the sign-in service with its own account, acting as an independent provider in relation to your Google account. We receive only the validation of the identity token and the account's internal identifier | |
| AdMob and the consent form (UMP) | Google acts as an independent advertising provider: it serves the ads and decides how it processes the data it collects for that purpose, including the advertising identifier, technical device data and ad-request data, under its own policies. We only manage your consent and send it no identity | |
| Firebase Analytics and Crashlytics | Here Google acts on our behalf and following our instructions, as our data processor: it receives usage events without identifiers, the approximate country, technical data and crash reports from our application | |
| Firebase Cloud Messaging and Firebase Installations | Processes notification routing, provider-generated installation identifiers, neutral message data and technical service data. Google acts on our behalf for customer Messaging data; service data is handled under its applicable terms | |
| Ionos | Server and database hosting (Spain) | Acts on our behalf: it hosts all the data described in this policy |
For sign-in and for ads, Google also processes data as an independent controller under its own privacy policy, which you can read at policies.google.com/privacy.
We may also disclose data where there is a legal obligation (for example, a request from a competent authority) or for the exercise or defence of claims.
7. International transfers
Our server and database are hosted by Ionos in Spain, within the European Economic Area, and we make no international transfers of game, account, social or coin data.
The Google services (Sign-In, AdMob, Firebase Analytics, Crashlytics and Cloud Messaging) are provided by Google, which may process data outside the European Economic Area. For Firebase Analytics we have selected the Europe location in the configuration, and Firebase Crashlytics offers no equivalent location option, so its data may be processed outside the EEA. Where Google processes data outside the EEA, it relies on the transfer mechanisms provided for by the GDPR (adequacy decisions, such as the EU-US Data Privacy Framework, or standard contractual clauses). You can find the details in Google's privacy policy.
FCM uses global infrastructure; no EU-only processing location or Analytics retention setting is promised for Messaging. Its technical routing data is distinct from the game/account/coin records held on our server.
8. How long we keep your data
| Data | Period |
|---|---|
| Account, sessions and session tokens | While the account exists. Without activity they are deleted after 180 days. When the account is deleted, they are erased immediately |
| Games, results, statistics, puzzle history | While the account exists. Deleted with the account |
| Coins and movements | While the account exists. Deleted with the account |
| Alias, friendships and invitations | While the account or the relationship exists. Deleted with the account |
| Guest data (no account) | 12 months from the last verifiable activity. Local device data is deleted when you uninstall the application or clear its data |
| Rewarded ad tokens | 15 minutes (their designed lifetime) |
| Advertising data processed by Google (advertising identifier, ad-request data) | Google keeps it under its own policies and periods; we do not store it |
| Technical server logs (including the originating IP address) | Maximum 12 months |
| Database backups | Maximum 45 days, with the exceptions described below |
| Notification routing/binding | Renewable 30-day active lease; routing removed on teardown, revocation, invalid token or maintenance retirement |
| Notification continuity tombstones | 30 days after retirement, without account/session association |
| Notification events, device work and Daily claims | 30 days after absolute event expiry, removed with applicable account deletion |
| Analytics (Firebase) | 14 months |
The automated cleanup processes run on a fixed cadence: the inactive-session and guest cleanup runs at least once every 24 hours, and rewarded-ad token cleanup every 15 minutes. Actual deletion may therefore happen shortly after the stated period, and a service interruption can delay the next attempt.
Backups. Backups are a security and recovery measure, not a historical archive. When we delete data from the live system, the deletion is immediate in that system, but the data may remain in a backup until that backup expires and is destroyed on a rotating basis, within a maximum of 45 days. That period has three qualifications you should know about:
- the newest backup is not deleted automatically even when it is older than 45 days, so that the system is never left without any available backup; the system records that situation instead of presenting it as strict compliance;
- a limited number of archival copies created manually before automatic rotation existed fall outside automatic deletion and are preserved as a recovery copy; they contain no data different from any other backup;
- the removal of a backup is not simultaneous with the deletion of the data in the live system, and no backup is restored in a way that reintroduces a deleted account into the live system.
We check that backups are readable, and a restore test with a quarterly cadence is planned against a disposable database.
Firebase provider identifiers follow separate provider deletion rules: Firebase documents installation-ID removal from live and backup systems within 180 days after its deletion API is called. Backend account deletion does not itself make that provider call, guarantee immediate provider erasure or recall accepted pushes.
Deleting your account also deletes the records of the rewards you obtained by watching ads. To prevent the same reward from being credited twice, the system keeps the identifier of the transaction that was already credited as a single-use record: it is a code for the ad transaction, it is not linked to your account or your installation, and it cannot be used to identify you. Our server still checks on every reward notification that the transaction has not been used before.
9. Your rights
You can exercise the following rights by writing to metalbemba@hotmail.com:
- Access: to know what data we process about you.
- Rectification: to correct inaccurate data.
- Erasure: to delete your account and your data.
- Objection: to object to processing based on legitimate interest.
- Restriction: to ask us to suspend processing while a complaint is resolved.
- Portability: to receive the data you gave us in a reusable format.
- Not to be subject to automated decisions: we make no automated decisions and build no profiles that significantly affect you.
- Withdraw your consent at any time, without affecting the lawfulness of prior processing, for analytics, crash reports and ads.
To exercise portability, write to us stating that you want a copy of the data you gave us, and we will provide it in a reusable format.
How to delete your account. You can do it yourself from the application, on your profile screen: the "Delete my account" option explains what is erased and asks you to confirm before running the deletion. On confirmation we delete your account and all associated data (games, results, statistics, coins, transactions, alias, friendships and sessions), and your open sessions become invalid immediately. A network or session failure deletes nothing: you can try again.
If you no longer have the application installed, or you cannot sign in, you can request deletion without reinstalling it and without an active session from linkedgames.fukitifu.com/account-deletion/ or by writing to metalbemba@hotmail.com. In that case, tell us the account identifier the application shows on your profile screen, or the information that lets us locate your account. The maximum response time is 30 days from the moment we can identify the account.
The identifier alone is not enough to verify a request: we ask that the request be attributable to the holder of the account, and if we cannot attribute it to a specific account we will tell you and explain what is missing instead of deleting another person's data.
If you never signed in, there is no account to delete: your data is linked to an installation of the application. In that case, uninstalling the application or clearing its data from the system settings deletes the local information, and data already sent to our server is deleted automatically 12 months after the last activity. The application neither displays nor communicates the installation identifier, so we cannot locate a specific installation from an email; if you write to us for this reason, we will tell you plainly what we can do.
How to complain. If you believe we have not handled your request correctly, you can complain to the Spanish Data Protection Agency (www.aepd.es). We ask you to write to us first so we can try to resolve it.
10. Security
- The server is the authority: coins, results and rewards are calculated and verified on the server, never on the phone.
- Session tokens are stored as irreversible fingerprints and are rotated on every use; if we detect misuse, the session is closed.
- The installation identifier is never stored or logged in the clear on our server.
- Invitation tokens are stored only as irreversible fingerprints, expire and can be revoked.
- We do not log session tokens, your email address, your board contents or the puzzle solutions in our server logs.
No system is infallible, but we protect your data with the technical and organisational measures appropriate to the risk.
11. Minors
LinkedGames is intended exclusively for people over 18 years of age. It is not directed at minors and we do not knowingly collect data from minors. If we detect that an account belongs to a person under 18, we will delete it together with its data. If you are a parent or guardian and believe a minor has used the application, write to metalbemba@hotmail.com and we will delete that data.
12. Your data on your own phone
The application stores the installation identifier, your games in progress, your preferences and the local notification state on your device. If you uninstall the application or clear its data from the system settings, that local information is deleted. Data already sent to our server is not deleted by uninstalling the application: for that you must request deletion as explained in section 9.
13. Data we do not process
To avoid any doubt, LinkedGames does not:
- ask for your email address, your name or your phone number;
- use your Google account for any purpose other than identifying you;
- sell or rent personal data;
- ask for payment details, because there are no in-app purchases;
- access your contacts, photos, microphone, camera or precise location;
- send your data to social networks on its own: when you share an invitation, you choose the messaging application and the recipient.
14. Changes to this policy
If we change this policy in a relevant way, we will publish the new version at this same address with its version number and effective date. If the change affects processing that requires your consent, we will ask for it again before applying the change.
15. Language
This policy is published in Spanish and in English. In the event of any discrepancy between the two versions, the Spanish version prevails. You can read the Spanish version at linkedgames.fukitifu.com/privacy/.