Privacy Policy

Effective and last updated: 29 October 2026

1. Scope and who is responsible

This policy covers edgekin.app, the Edgekin game in the browser and as an installable app (PWA) in its realms (game worlds such as test.edgekin.app and beta.edgekin.app), the Edgekin Chrome extension, and the API they use. Edgekin is the controller of player, device and service-operations data.

2. Data we process

• Device and session data. When the game first starts, your browser creates a cryptographic key pair. The non-exportable private key remains on your device. We store the public key and its fingerprint to authenticate signed requests, the surface it came from (extension, browser or installed app), when the device was registered and last connected, and whether it was revoked; after a key rotation, also the fingerprints of the replaced keys. Each connection opens an encrypted session: we keep its session keys encrypted for about an hour, and short-lived data that stops replayed requests for a few minutes.
• Account data. Every device belongs to a game account: an internal identifier, its status (guest, linked, choosing an island, archived), when it was created and its history of account events: created, pairing code made, device joined, left or revoked, key rotated, islands merged, account archived or deleted. A guest account carries no name, e-mail address or other contact details.
• Pairing codes. To add another device to your account, the game shows an 8-character code. It works once and expires after 10 minutes. We store only a one-way hash of the code, with the account, the device that made it, the device that used it and the times.
• Google account, if you link one. When you choose to link Google, we ask Google only for the openid and email scopes. We receive your Google account identifier and e-mail address and keep them with your game account, so that you can sign in on other devices. We do not receive your Google password, contacts or other Google data.
• Telegram account, if you link one. We verify Telegram launch data and store its account identifier, username and display name to identify the linked account in the game. Telegram launch proofs and device keys are not attached to feedback.
• Game state. The server stores your island's progress with your game account: observations and SP, kin, charges, buildings, inventory, activities and game actions needed to maintain that state. Your device also keeps settings and cached game data.
• Error reports. When the game hits an error, it sends us a short report: the kind and place of the error, its message, a stack trace with web addresses and query strings removed, the build version and commit, the realm type, the surface, the interface language and the build mode. A report carries no account, device, page address or game state. Reports are limited in size (4 KB) and number (3 per page load) and are written to our operational log, not to the database.
• Technical logs and IP addresses. Privacy-minimised operational logs record the time, the request method and path without query parameters, the status, the response size and the duration. The client IP address, user-agent and referer are not written to access logs; a web server's error log can record the IP address of a request that failed. The IP address is used for rate limiting: to limit how many new devices one address registers per hour it is kept in the database for about an hour and then deleted, and the limit on error reports is kept in memory only.
• Local storage. The game keeps on your device: the device key pair and up to 16 replaced public keys (IndexedDB), the island's state and settings and the latest game configuration (local storage; in the extension, Chrome's extension storage), an offline copy of the game's files (service worker cache) and whether it was opened as an installed app (session storage). The edgekin.app page remembers the width of its game panel. The landing remembers its language choice in a cookie. Product analytics uses no analytics cookies or advertising identifiers. Fonts are served by Edgekin. The optional feedback dialog on the landing loads the Ext Ops Panel script; the game uses its own form.
• VIP and billing, if you buy. We keep your account and world, product and price version, currency and amount, checkout attempt, a hash of its reference token, subscription and payment identifiers, status and paid period, refunds, VIP entitlement intervals, and the version and time of your beta acknowledgement. We retain necessary payment-event records to prevent duplicate delivery and reconcile payments. We do not collect full card numbers or security codes.

Practice puzzles on cozypuzzle.games

The practice puzzles on cozypuzzle.games use separate sessions. They do not create a game account or change your island. Your browser keeps a random session token for each puzzle and a pending command when a request needs to be retried. The server keeps the session rules and moves so that you can continue the same board. Clearing this site's storage removes your browser's access to those practice sessions. The site also remembers the width of the Edgekin panel.

Practice sessions expire after inactivity or when their lifetime ends. With the current defaults, inactivity is one day and the maximum lifetime is seven days. Expired and closed sessions are removed after a further retention period, currently one day. Short-lived command receipts allow a lost response to be retried safely. Abuse limits use hashed network keys that rotate with each limit period.

We count page views, broad source categories, language, country and limited interface actions without analytics cookies or a persistent visitor ID. For practice puzzles, we count accepted moves and closed sessions by puzzle and page category. A salted fingerprint of the random practice session lets us count a session once across pages and days. These anonymous counts remain after the practice session is removed. We do not attach them to an Edgekin account or store full page addresses, query strings, raw referrers or IP addresses in the analytics records.

The Edgekin panel connects to the same game and account system described in this policy. VIP uses the same products, account verification and payment providers. Returning from checkout does not by itself confirm payment.

3. Why we use data

We process data to run the game; authenticate your devices and link them to one account; secure and troubleshoot the service; prevent abuse; comply with law; and improve reliability. Depending on the context, the legal basis is performance of our agreement with you, our legitimate interests in operating and protecting the service, compliance with legal obligations, or consent where required for an optional capability.

We do not sell personal data, show advertising or use your data for profiling. For VIP, we process the billing records needed to fulfil your subscription, restore access, handle cancellation and refunds, prevent fraud and meet legal obligations. The seller and payment providers collect payment details under their own terms. The checkout may use cookies or similar technologies; the game does not access them.

4. Sources

Data comes from you and your devices and, if you link a Google account, from Google. If you buy VIP, we also receive necessary payment and subscription events from the seller and payment providers.

5. Service providers and disclosures

We disclose only what is needed to operate a selected capability:

• our hosting provider, REG.RU, runs the servers that process service traffic and store the data; our internal tools for game balance hold no player data;
• Google processes the sign-in request when you choose to link a Google account;
• the VIP seller, Pixel Rainbow Inc., Stripe and other payment providers process checkout and billing independently; we exchange the reference and transaction data needed for delivery, support, refunds and reconciliation;
• authorities or other parties may receive data when required by law or necessary to protect players and the service.

6. Retention

• device and account data, the account history and pairing-code hashes: kept while the account exists;
• guest accounts: a guest with progress is not removed by inactive-guest cleanup. Eligible guests without progress may be removed after the configured inactivity period;
• archived accounts (the island not chosen when two were merged): kept so that support can restore them, until the account is deleted;
• encrypted sessions: about one hour; data that stops replayed requests: a few minutes;
• IP addresses for rate limiting: about one hour in the database, one hour in memory for error reports;
• world resets: test data may be reset. In beta we preserve SP progress and the paid VIP contract, while all items and buildings may be reset;
• database backups: made before every update of the server; the 20 newest are kept, so a deleted record can remain in a backup until it rotates out, and a backup is restored only for disaster recovery;
• product analytics: successful game actions and automatic results are aggregated by UTC day and surface. Account/day membership is kept for 90 days to calculate active players and retention. Pseudonymous daily account contributions remain while the account exists so operator and test accounts can be excluded from past counts. Account deletion removes the account reference; the remaining anonymous totals have no fixed expiry. The landing counts page views and Play clicks, language, page category, source category and country; no visitor identifier, full URL, raw referrer or IP is stored with these counts. IP is used transiently for country lookup and abuse limits. Only aggregates reach Ext Ops Panel;
• feedback: the landing uses a separate standard Ext Ops Panel widget. The game sends your message, topic, server-signed account identifier, guest or linked status, game version, language, realm and surface to Ext Ops Panel. Your email, island state, pairing codes, Telegram launch proofs and device keys are not attached. Guests and linked accounts can read team replies and continue the conversation in the game. Anonymous landing feedback is kept there for 180 days; signed conversations remain until deletion while our CRM plan is active. After that plan ends, a 180-day retention period applies following a 30-day grace period. Support can request an account card through a signed server request: account type and creation date, realm, active-device count and VIP/subscription status. The panel does not store or cache that card. Do not include passwords or device codes in messages;
• error reports and privacy-minimised infrastructure logs: kept only for the operational lifecycle and used for security, abuse prevention and diagnostics, not product analytics;
• VIP and payment records: kept while needed to provide the paid service, reconcile payments and resolve refunds or disputes; records required for tax, accounting or other legal duties are retained for the applicable required period. Deleting a game account does not erase records that must legally be retained;
• local storage: until you clear it, or until you remove the extension or the installed app.

7. Your choices and rights

You can revoke a device in the account sheet of the game, and clear the site's or the app's local storage in your browser. Clearing it on the only device of a guest account makes that island unrecoverable. You may request access, correction, export, restriction, objection or deletion where applicable. Self-service account deletion is planned; until it is available, send a request by e-mail to privacy@edgekin.app. We may need to verify the requester before acting. You may also complain to your local data-protection authority.

8. International transfers

Edgekin's servers and the data they store are located in Russia (REG.RU). If you use Edgekin from another country, your data is transferred there. Where required, we use an applicable transfer mechanism and contractual or technical safeguards. Google, the seller and payment providers apply their own privacy terms to independent processing. VIP checkout and billing can involve processing outside your country, including the United States.

9. Security

We use encrypted transport and, inside it, an encrypted channel between the game and the server with signed device requests and pinned server keys; one-way hashing of pairing codes; access controls; data minimisation; and bounded payloads and rate limits. No service can guarantee absolute security.

10. Chrome extension

The Edgekin extension asks only for the side panel and storage permissions. It does not read the pages you visit, your tabs or your browsing history. Information received from Chrome APIs is used only to run the game, in line with the Chrome Web Store User Data Policy, including its Limited Use requirements.

11. Children and changes

Edgekin is not directed to children under 13, and we do not knowingly collect personal data from them. If you believe that a child under 13 has used Edgekin, write to privacy@edgekin.app: we delete the account on a verified request. We may update this policy as the game changes. We will update the date above and provide additional notice when a change materially affects your rights or our use of personal data.

12. Contact

Privacy questions and rights requests: privacy@edgekin.app. Help with the game: support@edgekin.app.