Who is responsible
Artificial APU is a personal project operated by Aurélien BERANGER, based in France, the controller of the personal data described here. This policy covers artificialapu.com and its game. Contact artificialapu@gmail.com about your information or this policy.
A wallet address or game identifier can be personal data even without a real name. Other services have their own privacy notices for processing they control.
Information we use
- Game information: player identifier, chosen name, save, progress, inventory, purchases, access rights, activity dates, time played, visits and social results. Guest profiles also have server-side saves. Authorised administrators can search account identifiers, names, linked wallet addresses and verified Google emails to support accounts and allocate bonuses. Internal Diamond credits and optional APU distributions have an audit record to prevent duplicate grants and track their outcome.
- Time played and scores: for APU Evolution, your total time with the game open on screen, the number of play sessions and the first and last play dates. For the 200 hives with the most honey, we also keep an hourly honey total so administrators can see how scores moved over the last day.
- Player file: administrators chosen by the owner can open a player file that brings this information together for one player, with token balances, Diamonds, Frens, time played and the recent network records described below. Each opening of a player file is kept as an administrative record with the administrator, the player and the time.
- Sign-in information: session records, a connected wallet address or linked Google account identifier, verified email address and optional profile-image URL, and temporary authentication challenges. Wallet sign-in uses a signed message to check control. We do not ask for your seed phrase or private key.
- Payments: products, quotes, amounts, payer addresses, transaction hashes, confirmations, receipts, status, dates and review notes. Name-change quotes can contain the requested name. Swaps involve source and destination transactions.
- Technical and usage information: network requests, IP addresses received by hosting services, a hashed IP identifier for rate limits, country supplied by Cloudflare, game inputs, screen dimensions, visits linked to a player and day, aggregate event counts and operational logs.
- Recent network records: for each player profile, the last 5 networks seen with the game, each with the last IP address seen on it. IPv6 addresses that share their first half count as one network. For each network we keep the approximate city, region and country and the network name and number that Cloudflare derives from it, when it was first and last seen, and how often it was seen. We use them to protect accounts, prevent abuse and spot one person using several accounts to collect rewards. Only administrators chosen by the owner can see them, together with the other game profiles that recently used the same network. The location is approximate and can show a VPN, mobile network or relay instead of where you are, and a shared network can link people who do not know each other.
- Correspondence: your email address and the information you send us.
Information comes from you, your browser or wallet, gameplay, service providers and public blockchain records. Google and wallet connection are optional for basic play. Features requiring a particular identity, wallet or payment cannot work without the relevant information.
Optional Google sign-in
Where enabled, Google sign-in lets you access or link an adventure. Google sends a signed identity token; the server verifies it and stores the unique Google account identifier, called sub, linked to your player. We also store the verified email address, when Google provides one, so you can recognise the Google account linked to your adventure. This address appears in your private account display, not your public player name, Town profile or social rankings. Only sub identifies the Google account; email is never used to match or merge adventures.
When Google supplies a supported profile-image URL in the verified sign-in information, we also keep that URL to show your photo in the private connected-account card. We accept only HTTPS image URLs on Google's image-hosting domains. We do not store a copy of the image, your Google full name or the identity token. The photo does not replace your public player name or in-game character and is not shown in public Town, arena or guild profiles. Displaying the email and photo requires no additional Google permissions. Earlier connections may have no stored email or image URL until you confirm the same Google account again.
Opening the connected-account card can cause your browser to request the image from Google's image host. That host receives ordinary request information, including your IP address and browser information. The image request uses a no-referrer policy, so it does not send the game's page address as a referrer.
Restricted tests also require a verified email matching an approved list. That list is kept separately in server configuration. The verified email is compared with it before sign-in can finish. Tokens and email claims are not written to application logs for this check.
Google's sign-in library can load when the sign-in option is displayed, before you press its button. Google receives browser and authentication requests under Google's Privacy Policy. We do not request access to Gmail messages or Drive files. Saves remain in our Cloudflare D1 game database. Google sign-in uses the game's own session cookie and does not authorise wallet payments.
Information visible to others
Town and occasional adventure visitors can display a full wallet address, chosen name, token balance and rank. When a game save exists, the public character also uses its selected outfit and equipped items and can show its level, recorded active playtime and latest activity date. These characters move automatically; their presence does not mean the holder is currently playing. The holder directory imports public token-holder records through blockchain services, including wallets whose owners have never opened a game account. Holders without a save use a default character and have no invented game statistics. Arena and guild features show participating profiles and results.
Public blockchain transactions, addresses and balances can be inspected and copied by others. We cannot erase or rewrite those records. Account deletion does not remove blockchain information or automatically exclude a wallet from the holder directory. You can contact us about our use of your information, including to object to the directory processing.
Why we use information
- Providing the service you request: creating and saving an adventure, authenticating access, linking accounts, fulfilling purchases and related support, where necessary to perform our agreement with you.
- Legitimate interests: protecting accounts, preventing abuse (including one person using several accounts to collect rewards) and payment reuse, diagnosing faults and analysing service usage. Community profiles and the public holder directory support the game's community and holdings features. You may object to processing based on these interests.
- Legal obligations and claims: meeting an applicable legal requirement, or keeping necessary evidence to establish, exercise or defend claims. These grounds do not mean every retained record is subject to a fixed statutory retention period.
If a separate optional purpose requires consent, consent must be obtained for that purpose. Reading this policy or continuing to browse is not itself consent. Game rules automatically calculate progress, eligibility and payment confirmation; contact us to dispute a result.
Cookies and storage
We use one cookie, apu_session. It keeps you signed in and links your browser to your game save. It is created only when you play, sign in or open your account, never when you only read a page. It lasts 30 days and is renewed while you play. After a Google or wallet sign-in, you sign in again at least every 90 days. It is HttpOnly, uses SameSite=Lax, is marked Secure on HTTPS and is limited to this site. The server stores only a hash of its token.
Your browser also keeps small entries for this site. Session storage, which is cleared when the tab closes, keeps a random tab identifier and pending game or Bank requests. Local storage keeps your sound, music, motion and video choices, the wallet you used, introductions already seen, and unfinished payments, approvals and Bank positions so a payment is never made twice. Some entries contain a wallet address, a transaction hash or an order identifier. Many stay until you clear them or the task ends. Clearing them can remove guest access, preferences and payment recovery information. Wallet software manages its own storage.
We use no advertising, social-network or analytics cookies. The cookie and storage above only run the game and remember your choices, so there is no cookie banner. If we add something that needs your consent, we will ask first. Our pages load their fonts from our own site. Google sign-in loads only when a sign-in option is shown to you, WalletConnect only when you use it, and the DEXTools chart only after you press Load chart. These services can then use their own cookies or storage under their own policies. Our host Cloudflare can set a short security cookie and ask your browser to report network errors. We count visits and game events on our own server from your game session, without a separate tracker.
Services involved
- Cloudflare: site and API hosting, the D1 database, network security and operational logging. It receives requests, including IP addresses, and supplies the approximate location and network details used for recent network records.
- Wallet providers and WalletConnect: selected wallet connections and signing requests. WalletConnect is used when configured and selected. Its usage reporting (telemetry) is turned off.
- Blockchain services: configured RPC providers, including PublicNode, and explorers such as Blockscout handle address, balance and transaction queries. Alchemy can receive wallet and network queries when configured.
- Relay: currency information and prices; for requested swaps or tracking, wallet and recipient addresses, networks, tokens, amounts and transaction information.
- Google: optional sign-in, profile images in the private connected-account card and Gmail correspondence sent to our contact address. Profile-image and sign-in requests expose ordinary browser request information, including IP addresses.
- DEXTools: an optional APU market chart in the Financial District. Nothing loads from DEXTools until you press Load chart. It then receives ordinary browser request information and can use its own cookies and storage.
- Other providers: external hosts supply token images and receive browser requests; market-data services supply prices. Opening an external explorer sends a request to that service.
MoonPay card purchasing is planned but is not active in the public game. Artificial APU does not currently collect card details or identity-verification documents for MoonPay. A future integration will require updated disclosures before activation.
Information may also be disclosed where an applicable legal process requires it or a dispute justifies it, subject to the relevant legal conditions.
International processing
Providers operate internationally. Information can be processed outside France and the European Economic Area; this service does not guarantee EU-only processing.
Cloudflare's Data Processing Addendum describes its contractual transfer arrangements. Google's transfer framework information describes the mechanisms it uses. Depending on the recipient and transfer, an applicable adequacy decision or safeguards such as standard contractual clauses may be relevant.
A provider-by-provider confirmation of the locations and safeguards applicable to this service is not yet complete. The linked provider documents do not establish that every transfer by this service has been individually verified. Contact us for the information available about a particular recipient or transfer.
How long information remains
A game session ends 30 days after it was created or last renewed, and a Google or wallet session ends at most 90 days after that sign-in. Wallet and Google sign-in challenges last 5 minutes; account-choice requests last no longer than 5 minutes. Scheduled cleanup removes expired records and old rate-limit windows. Expiry does not guarantee immediate physical deletion if cleanup is delayed.
Recent network records keep at most 5 networks per player profile, and each record is deleted 90 days after it was last seen. Time played is kept until the account is deleted. Hourly honey totals of the top 200 APU Evolution hives are deleted after 48 hours.
Game saves and profiles remain while the account exists, unless deleted as described below. There is no automatic removal of inactive accounts, including guests who lose their browser session.
The linked Google identifier, verified email and optional profile-image URL remain with the account until account deletion. A later verified Google sign-in can update the email and replace or clear the image URL. A pending account-choice request can temporarily contain the verified email and optional image URL. It expires within 5 minutes and is removed by scheduled cleanup, or when the choice is completed or cancelled.
Visits, event metrics, administrative records and retained payment evidence currently have no general automatic expiry. There is also no fixed deletion schedule for correspondence or the configured test-email list. Such records can therefore remain until manually removed. Provider log and backup periods have not all been confirmed.
Retention needs depend on the record's purpose, an active account, unresolved payment or support request, prevention of payment reuse, disputes and applicable legal obligations. These criteria do not represent an automatic review or deletion process already in place for every category. Contact us to request erasure or restriction. Public blockchain records follow the network's operation rather than our retention schedule.
Account choice and deletion
If signing in or linking Google and a wallet finds two different adventures, you must explicitly choose which to keep. The other save, inventory and paid game rights are deleted, not merged or transferred. The selected adventure keeps its own progress and rights, and the proven identities are linked to it. Existing sessions are revoked. Pending payments can block this operation.
Wallet-connected and Google-linked accounts can request deletion in account settings. This removes the active profile, save, inventory, paid game access, identity links including the linked Google email and profile-image URL, sessions and associated social records, visits, recent network records, time played, hourly honey totals, Honey-spending history and stored swap quotes. A minimal technical account record remains to support retained references. Deleting an APU account does not delete your Google account or wallet assets.
Orders, receipts, contribution records and payment evidence remain, including information needed to prevent transaction reuse. They can contain wallet addresses, transaction hashes and names from earlier quotes. This is not complete anonymisation. Pending payments can block automatic deletion. Email us for a manual review, including for a guest account or retained evidence.
Logging out or disconnecting is not account deletion. Deletion does not clear every browser-storage entry or public blockchain record, and does not by itself remove applicable consumer claims.
Your rights
Subject to the GDPR's conditions, you may request access and a copy, correction, erasure, restriction or portability, and object to processing based on legitimate interests. For consent-based processing, you may withdraw consent without affecting earlier lawful processing.
Email artificialapu@gmail.com with your request and enough information to locate the account or wallet. There is no automatic full-data export. We may need proportionate evidence of control; an identity document is not automatically required. Never send a private key or seed phrase.
The normal response deadline is one month. Complex or numerous requests can justify up to two additional months, with an explanation within the first month. You may complain directly to the CNIL or another competent supervisory authority. See the GDPR rights and information rules.
Security, age and changes
Session controls, signature checks and request limits help protect the service, but no online system guarantees complete security.
The service is intended for adults aged 18 or older. The game does not currently verify age. Contact us if you believe a child's information is present.
This policy will be updated when processing changes. The displayed date identifies the version. Material new purposes may require additional information or consent.