ALPENDOS
Privacy Policy
Last revised: 9 November 2026
What does this policy cover?
This policy describes the account, gameplay, security and support services of Alpendos. The Android and iOS application identifier is com.ertanuzun.gi. The data controller is Ertan Uzun. Contact for privacy and support: alpendosonline@gmail.com. A sign-in, advertising or payment option on one platform does not mean it is enabled on every platform.
Accounts and optional provider sign-in
Email/password accounts use an account email address, a secure Argon2id password hash instead of the stored password, verification records and session records. An email service sends verification messages. Do not include your password or verification codes in support messages.
Where enabled, Google sign-in on Android and Apple sign-in on iOS are optional. The chosen provider authenticates you; the game server verifies the signed response, intended application, validity period and one-time request. A keyed link derived from the provider’s stable account identifier is retained to find the same game account. This transformed link is not anonymous. Matching email addresses do not automatically link accounts or give access to another existing game account.
An email address in the provider response may be processed to check sign-in and a conflict with an existing email account. Provider-created accounts do not retain the raw provider identifier, profile photo, contact list, mailbox or raw Google sign-in token as a permanent account record. Your Google or Apple password is not sent to Alpendos. Providers process their own sign-in flows under their policies: Google Privacy Policy and Apple Privacy Policy.
For Apple-created server accounts, the authorization code is verified with Apple. Apple refresh/access credentials needed to validate authorization and revoke the app’s authorization when the account is deleted are encrypted in the database. Codes and tokens are not retained as plaintext records or written to log output. One-time sign-in and reauthentication requests are short-lived security records bound to the account/session.
Gameplay, communications, transactions and security
Character names and appearance, progress, inventory, virtual currency, rewards, battles, guilds, friendships, market activity and transaction records are retained to run the game and apply actions to the correct account. Chat content is shown to the relevant participants. Reported content and support explanations may also be kept as evidence for review. Avoid including private information in chat or support text.
Session identifiers, timestamps, IP/device connection information and their derived identifiers are processed for session security, quotas, duplicate-transaction checks and abuse prevention. Technical identifiers and hashes do not automatically anonymize personal data. Authorized access is limited by purpose and role.
When payments or rewarded ads are enabled, product/transaction identifiers, signed verification results, account/character links, delivery records and refunds are used to deliver the correct entitlement once. Necessary purchase tokens are encrypted. The relevant store handles payment-card information; card numbers are not sent to the game server. A test ad or test purchase does not prove that a real payment has been verified. Stores and advertising providers process data according to the feature actually used.
Friendships represent in-game social relationships; Alpendos does not read your phone’s address book. Character/guild names, game profiles, rankings and relevant game results may be visible to other players. Clearing chat from your own view does not delete other recipients’ copies or every server-side evidence record.
Account-linked connection and security records may include your IP address and information identifying the client type. Alpendos does not use them to obtain precise GPS location. Aggregate usage measures, such as the number of players online, may be calculated from account/session records to operate and understand the audience of the service. This does not mean that private messages are used for advertising targeting.
Optional advertising, privacy choices and reward verification
When available, rewarded ads use Google AdMob (Google Mobile Ads). Google’s User Messaging Platform (UMP) manages privacy information and choices required for your region. Watching an ad is not a condition of playing the core game or requesting account deletion. Advertising and real-money diamond purchases may be disabled or unavailable depending on the platform, provider availability, configuration and testing status. The app shows the current availability of these features.
Separately from data on Alpendos’s account/game server, Google’s advertising services may process IP addresses and the approximate location inferred from them, device or advertising identifiers, ad impressions and interactions, app interactions, crash information, performance information and other diagnostics. Uses include ad delivery, advertising measurement/analytics and invalid-traffic prevention. UMP may process a general region, consent-screen interactions and technical performance information to determine the appropriate privacy message and manage your choices. This approximate location is not access to precise GPS location.
Where required, a privacy message is shown before advertising. On iOS, Apple’s separate system permission applies to tracking across other companies’ apps and websites. Refusing it does not prevent use of the core game. Granting it may allow the advertising identifier to be used for that purpose. Refusal does not mean that no advertising data is processed or that all ads must stop; contextual advertising and security operations may follow different conditions. Manage choices through the Advertising privacy options offered in the app and your device’s privacy settings. Contact support if you cannot access the option.
To deliver a reward to the correct account once, Google receives an account-linked pseudonymous identifier and a random ad-session reference, rather than your real email address or password. Google returns these values in a signed reward-verification callback to the game server. The server checks the account/character link, ad unit, time, duplicate transaction and delivered reward, and retains related records. The pseudonym is not anonymous. Alpendos uses it for reward routing and abuse prevention, and does not set it as an account identifier in an ad-targeting field.
Google’s own advertising identifiers are separate from this reward pseudonym. Advertising partners’ combination of device data with information from their other services for targeting or measurement may constitute tracking, subject to applicable permissions. See the Google Privacy Policy, Google Mobile Ads iOS data disclosure and Android data disclosure.
Access, service providers and device choices
Authorized Alpendos operations and support personnel can access relevant records as their duties require. Hosting and recovery-backup providers host necessary data. Verification and support emails are processed by an email service, which may include Google Gmail. When purchases are enabled, Google Play on Android and the Apple App Store on iOS process payments and purchase data under their own policies. Your payment-card number is not supplied to Alpendos. These services may process data in different countries.
Alpendos does not supply your email address, game password or private-message content to the advertising SDK as advertising-targeting data. Google/Apple sign-in, store payments and Google advertising are different operations; signing into one does not automatically authorize another. Alpendos’s active-player counts are separate from Google’s advertising measurement.
Optional app and campaign measurement on Android
On Android versions that include this feature, if you consent, Google Analytics for Firebase processes data to measure how the app is used and how our ad campaigns perform. For example, we measure first opens, sessions and the proportion of players who return the next day. Google Ads data is linked for campaign measurement.
Google may process an identifier specific to the app installation, app and device information, approximate location derived from the IP address, interactions such as app opens and sessions, and advertising and in-app purchase activity. We do not send your game account ID, email address, password or private messages to Firebase Analytics. Android advertising ID collection and ad personalization are disabled for this measurement. Rewarded ads have separate privacy controls. How Google uses this data.
Measurement is optional and your choice does not affect access to the game. You can change your choice at any time using Analytics privacy in the app. Withdrawing consent stops future Analytics collection. For requests concerning data already processed, use the privacy contact in this policy.
Optional features such as notifications and voice chat depend on platform and version. Where an available feature requires an additional device permission, it is requested when you use that feature. Refusing notifications does not prevent gameplay. Alpendos does not request address-book, camera or precise-GPS access for the account, advertising and purchase operations described here. Connections are encrypted in transit; no security measure guarantees absolute security.
Retention, deletion and authorization revocation
Account and game data are retained to operate your account. Logging out, uninstalling the app or expiry of a sign-in request does not delete all account, transaction, audit, security or backup records. No single active automatic-deletion period is promised for every data type. Records needed for transactions, disputes, security and applicable obligations may be retained separately for limited purposes.
Where available in the app, Delete account requires your password or fresh provider authentication and an explicit two-step confirmation. Outstanding game obligations may need to be completed or cancelled first. When deletion completes, the main account is closed, sessions become invalid, and primary account/profile data are cleared. Financial transaction/refund records, audit/security records, dispute evidence and existing recovery backups are not all erased at the same moment.
Revocation of Apple sign-in authorization is also sent to Apple. Temporary Apple unavailability alone does not stop main-account deletion; the revocation job enters a secure retry queue. Encrypted credentials needed for revocation are retained for that purpose until completion and cleared after success. You may ask support about retained records and the outcome of your request. Creating a new account does not restore the deleted account’s progress.
See Account and data deletion for request methods. Account ownership is securely verified for access, correction and deletion requests. Support does not ask for your password, sign-in code or identity document. Hosting, email and store services may process necessary data. Copies remaining with a provider or in backups are considered separately as part of the request.
Automatic account deletion does not rewrite every purchase/refund record, preserved audit/security record or abuse-evidence record. Such records may contain an email address, IP information or reported text. Retention does not make them anonymous; access remains subject to their limited purposes. A code’s or session’s validity period is not the deletion period for these records or backups. Because no single verified automatic-cleanup schedule covers every data type, this policy does not promise a number of days.
The character’s display name is replaced with a deleted-account label. Character and inventory records and some game/transaction history may remain for settlement, audit and security. These records are not necessarily anonymous.
Policy changes
When data practices change, this policy and necessary store disclosures are updated. The revision date appears above. Contact alpendosonline@gmail.com for privacy, access, correction and deletion requests.