# Energen Games beta privacy notice: Taktikverse and Lattice **Version:** privacy-2026-11-11-r1 **Effective date:** 11 November 2026 ## 1. Who is responsible and how to contact us **Synapse Tutor, LLC**, a Delaware limited liability company operating as **Energen Games**, is the controller of the personal information described in this notice. We operate Taktikverse: Football, a capacity-limited open beta of a single-player browser game, and Lattice, a separate capacity-limited strategy-game beta with AI and online modes, on energengames.com. The business is administered from Grenada. **Primary contact for privacy, account deletion and privacy complaints:** [privacy@energengames.com](mailto:privacy@energengames.com) **Taktikverse problem reports:** use its in-game **Send** feature while signed in; reports are uploaded to Cloudflare as described in Section 4. **Lattice safety, game or access concerns:** use its **Report this match** email control or email hello@energengames.com, as described in Section 11. Privacy requests and Lattice safety complaints or appeals do not require game access or sign-in. **Correspondence by prior arrangement:** Synapse Tutor, LLC, St. George’s, Grenada. Please email [privacy@energengames.com](mailto:privacy@energengames.com) first so we can arrange courier delivery. This is a correspondence route, not an office, establishment or standalone street-delivery address. Please do not dispatch an item until delivery instructions have been agreed. You can make a privacy request by email without arranging or paying for a courier; this route does not restrict any other contact or service method available under applicable law. This notice covers the shared Energen account and website and these two free betas. Sections 2–10 retain the Taktikverse account, sign-in, 13+ declaration, waitlist, service-email, cloud-save, security, voluntary-report and email-preference disclosures, with shared wording identified where needed. **Section 11 explains Lattice and its separate data, recipients and controls.** Lattice has no cloud saves, in-game chat, purchases, advertisements or analytics SDKs. This notice also explains shared public-page statistics and optional website videos. It does not describe unrelated tutoring services or other games. We will explain any additional payment processing before introducing paid access. The ordinary account and beta service is intended for people aged 13 or older. The usual route is sign in, then affirm the 13+ statement and the relevant game licence before joining. Taktikverse uses its existing [beta licence](/legal/licences/beta-2026-10-20-r1.txt); Lattice has its [separate licence](/legal/lattice/licences/beta-2026-11-04-r1.txt). We do not routinely ask for a date of birth or distinguish adult and teen accounts. All players retain the same privacy-protective game and account defaults; the separate public-page statistics use the controls in Section 4. New beta places remain subject to applicable requirements and available capacity. Each game has a separate capacity, initially 100 admitted gameplay accounts for that game, with no separate teen quota; completed eligible applications use original application order within the requested game. A pending application is not a guaranteed place. The [Taktikverse eligibility explanation](/legal/eligibility/eligibility-2026-10-20-r1.txt) and [Lattice eligibility explanation](/legal/lattice/eligibility/eligibility-2026-11-04-r1.txt) explain the ordinary route and applicable local requirements. A Lattice application, acceptance or departure does not rewrite a Taktikverse place or acceptance. Creating or signing into an account is separate from joining the beta and may happen before the Join confirmation. This means the authentication service can hold an account even if the person has not yet joined. We do not claim that an age screen always precedes collection. Where prior authorisation is legally required, the appropriate check or registration restriction must take place before the affected account collection, not merely when a place is requested. ## 2. Information, purposes and legal bases We receive information from you, the sign-in provider you select, your browser and the services operating the website and game. Joining is not blanket consent to everything in this notice. A private save or game record associated with an account is personal information even when it contains fictional game data. The table below retains the Taktikverse and shared-account processing; Lattice-specific information and purposes are in Section 11. | Information | Purpose | Basis or choice | |---|---|---| | Email, authentication account ID, selected provider and credential/session information, and limited provider metadata | Create and authenticate the account you request, secure sign-in and provide account support | Necessary requested-service processing; contractual steps/performance only where a valid applicable agreement supports that basis; otherwise our separately assessed legitimate interests where available. Other applicable law may use informed service consent or another stated ground. | | A private, generated or chosen manager name | Give the account a private identity without using a Google name or photograph | Necessary administration of the requested game; no public profile or advertising use. | | 13+ declaration, actual licence version/hash, affirmative event and server time, application time, place/waitlist status | Record actual eligibility confirmation and agreement; allocate the relevant game’s capacity fairly | Necessary requested-service and proportionate agreement/compliance evidence. A 13+ declaration is not verified age or a declaration of adulthood. | | Connection-country signal supplied by the delivery service, evaluated transiently; only where necessary a further eligibility result | Apply an applicable availability/prior-authorisation rule and determine whether the optional public-page beacon may load | Narrow eligibility and privacy-control processing, not advertising or queue priority. We do not put the connection country into the application/profile or our eligibility-event logs. CWA coarse country statistics, when permitted, are separate and described in Section 4. Provider connection/security processing remains separate. | | One chosen cloud career, short summary, save time/revision and random saving-device identifier; a small removal marker | Continue the requested career across devices and prevent stale overwrites | A separately chosen service feature, not marketing consent. Only information objectively needed for this private feature is used. | | Taktikverse report file, build, time, size, account reference, note and any deliberately included save | Receive, reproduce, diagnose, correct and verify the problem reported | Requested support and narrowly assessed reliability/security interests, or the applicable informed support request. A correction can benefit all players; identifiable data is not repurposed for unrelated research or advertising. | | IP address, request/browser information, authentication/App Check tokens, security signals and necessary diagnostics | Deliver and protect the service and accounts | Necessary security/delivery and legal-compliance purposes, not advertising or audience measurement. Section 11 explains Lattice’s interaction-risk scoring and regional exception. | | Application/service-message email address, status, content, ordinary headers and delivery/reply records | Tell you about your own application, available place or requested support | Necessary service administration and limited evidence; not an automatic newsletter subscription. | | Limited public-page Cloudflare Web Analytics: eligible page/referrer information, generated page-load identifier, navigation, browser/device and performance data; normal request metadata reaches Cloudflare | Measure public-page use and loading performance to improve this website, not individuals or gameplay | Valid prior permission where required; otherwise a documented lawful basis for the narrow website-improvement purpose, including legitimate interests where applicable, with the relevant measurement exception, child-default conditions and free objection. A licence or 13+ declaration is not analytics consent. See Section 4 | | Limited operational totals from existing delivery and account records: request/response/error and byte counts, request counts for fixed public-page categories or game-download endpoints, aggregate accounts created, places and account status; existing sign-in metadata only where needed for security and disclosed inactivity administration | Operate capacity, delivery, reliability and account administration; not reconstruct unique visitors, individual journeys or engagement cohorts | Separately assessed, proportionate operational/security and administration interests where legally available, or the applicable service/compliance basis; not consent inferred from a licence and not blanket authority for optional product analytics | | Optional news preference and its scope, time and withdrawal | Respect a separate account-page choice | Consent where valid and required. News sending remains paused; an earlier preference is not expanded by this notice. | | Privacy requests, deletion status, necessary authority checks and limited dispute records | Fulfil rights, handle complaints and demonstrate appropriate handling | Applicable legal obligation or proportionate rights/compliance interests. A specifically required authorisation is obtained before the affected processing. | **Our Taktikverse and shared-account assessment.** For jurisdictions using the GDPR framework, we do not assert that every minor can make an enforceable contract. We select proportionately balanced legitimate interests for minimum account, access, private identity, requested cloud/support and security processing where that basis is legally available, with particular weight given to children's interests. The beneficial purpose is the private game the player requests; public identity, advertising, broad telemetry and unrelated identifiable research are not needed. Valid-contract processing may apply to a particular service where capacity and objective necessity are established; the stated legitimate-interest purpose is not a retroactive switch after consent is withdrawn. Legal obligations and limited claims evidence have their own bases. In consent-based frameworks, the clear registration and deliberate feature actions support the locally required meaningful choice only when the person has capacity to give it; a parent or other authorisation is obtained where actually required. **Location is not residence.** A connection-country signal is an approximation. It is not a verified home address, nationality or precise location. We do not store a country against your account or use it to prioritise the queue. A necessary exception check can run before account creation as well as when a new place is requested. Where a law depends on residence or a subdivision, an inaccurate or insufficient connection result can require a limited clarification or review; we do not claim that changing networks changes the law applying to you. No browser precise-location permission is requested. We also use the transient connection-country signal to apply the relevant public-measurement rule. An uncertain routing result can leave the optional beacon Off without restricting site or game access. **Taktikverse optional features.** Cloud saving starts Off on a new account/device and can be turned On. Reports are sent only when you press Send, with a separate initially unticked save-attachment choice. You can use local play without either. These deliberate actions request the corresponding function; they do not authorise unrelated information use. Credentials, identity documents and unrelated private details do not belong in a save name or report. **News choices.** The Join box does not subscribe you or a parent to news. Any news preference is separate in Account, withdrawable there or through the privacy contact, and tied to the wording shown. Sending remains paused for this release. Before it is enabled, we will provide the relevant information and any additional legally required age/authorisation step, rather than assume a 13+ declaration permits every marketing use. Service messages remain separate. A future newsletter will have a no-login unsubscribe route. ## 3. Taktikverse local and cloud saves **Common defaults.** New accounts start cloud saving Off. The game uses the private manager name, not the Google provider name or photo. Existing explicit save choices are preserved unless you change them. The same controls apply to all players. **Local saves.** Careers are stored in your browser on the device you use. Local storage can include the latest checkpoint and its predecessor, saved worlds and recent scenarios. Clearing site data or losing access to the device can remove them. You can export backups yourself. We do not browse personal files on your device. **One cloud career.** When you are signed in and **Cloud saves** are On, the game maintains one career copy in your Firebase account. It contains the packed career data, a short summary including the club, season, matchday and manager information, the save time, revision information and a random saving-browser identifier. It is not a history of every previous save and is not published to other players. You can turn **Cloud saves** Off at any time. This stops uploads from that device; it does not itself remove a copy already in the cloud, delete your local careers or change another device's switch. **Removing the copy.** Choosing **Remove the cloud copy** removes the cloud career data in the removal operation and turns cloud saves Off on that device. Rely on the game's successful-removal confirmation: a recent save, connection problem or security check can require waiting or retrying before the operation succeeds. Another device that discovers the copy has been removed shows **Not in the cloud** and does not upload it again by itself. Uploading resumes only when you choose **Upload to the cloud again** or explicitly turn cloud saves back On. Removal does not erase local careers or exported files. **Expiry.** A cloud career is scheduled for removal after 90 days without a successful cloud save. Merely signing in does not restart that period. Expiry removes the career data, not the local copies on your devices, and the same explicit-upload requirement applies when a device finds the cloud copy gone. **The small removal marker.** After removal or expiry, the database retains a marker associated with your account: a removed flag, revision number, time and device identifier. An automatic expiry operation can use an administrative operation identifier instead of a saving-browser identifier. The marker contains no career, summary, players or manager data. Its revision prevents an older device from overwriting a newer career. Revision/removal metadata is retained until account deletion; a new explicit upload can replace the removed state with a live career. It is not retained as an archive of deleted career data. ## 4. Service providers and other recipients We use **Google Firebase/Google Cloud** for authentication and the cloud database, and **Firebase App Check with Google reCAPTCHA Enterprise** for security and abuse protection on the routes where it is enabled. The Lattice regional access and security arrangements are explained in Section 11. These services handle the relevant account, save and technical information. Google acts as our processor for Customer Personal Data covered by the applicable Cloud Data Processing Addendum. This is distinct from Google's processing for its separate consumer services and its own service-administration purposes. Google's separate Google-account sign-in service also processes information under its own account privacy information when you choose it. Section 5 explains the applicable contractual and transfer arrangements. We use **Cloudflare** for DNS, delivery through Cloudflare Pages, the sign-in relay to Firebase, and the problem-report upload and storage described below. It processes connection and request information for delivery, security and operation. Cloudflare's Data Processing Addendum forms part of the Self-Serve Subscription Agreement under which we use these services and governs the processing within its scope, including reports handled by Cloudflare Pages Functions and Workers KV. We have not enabled a separate stored request-log archive. **Public website measurement.** We use Cloudflare Web Analytics only on eligible public home, news, games and studio pages to understand which public content is used and how those pages load, and to improve the website. The beacon does not run on sign-in, join, account, play, game, approval, privacy-request or Website statistics settings pages. We do not send it account identifiers, emails, manager names, careers or problem reports, and we do not combine its results with account, gameplay, cloud-save, support or IP-history records. Signing out is not a way for us to disregard an applicable privacy choice or earlier contractual protection. Where valid prior permission is required, this optional measurement stays Off until that permission exists; where the applicable rules permit measurement without that prior action, we rely on the stated limited website-improvement purpose and provide clear information and a free objection control. We consider children's privacy and do not treat a 13+ declaration or an unknown age as proof of adult consent. Where the necessary permission or applicable conditions are not established, the beacon is not loaded. This does not prevent access to the website or game. When allowed, the Cloudflare script reads current-page technical information and sends it to Cloudflare: the eligible page address, referring-page information that passes our minimisation checks, a generated identifier for that page load, navigation type, browser/device information and performance measurements such as loading times, Core Web Vitals and browser memory figures where available. We exclude personal parameters and private referrers rather than use them for audience reports. The page-load identifier is not used by us as a persistent person or account identifier. Normal network handling also exposes the source IP address and request metadata to Cloudflare. Cloudflare states that its RUM service discards that IP at the nearest data centre and does not store it in RUM core databases or logs; this statement does not describe every other Cloudflare delivery or security record. Cloudflare states that this beacon does not use cookies or browser storage and works with current-page information held in memory. Our 16 October 2026 measurement found no beacon cookies, local storage or session storage in that sample. These facts reduce tracking but do not mean no information is processed. Cloudflare processes the covered service data under our incorporated Data Processing Addendum and the applicable international arrangements in Section 5. We use broad page-view, Cloudflare-defined entry-visit, referrer-host, coarse country/browser/device and performance summaries where that collection is permitted. They are not unique-person counts, player-retention measures or 30-minute sessions. Use **Website statistics** on public pages to see the current setting and turn measurement Off without logging in, losing access or clearing saves. A required prior choice is separate from joining, accepting the licence, enabling cloud saves or any future gameplay-statistics choice. The preference records and provider retention are described in Sections 6 and 7. Optional gameplay statistics, legacy C93 uploads and studio-news sending remain Off. **Limited operational reporting.** Separately, we may use limited totals from existing delivery and account systems to operate the service: requests, errors, bytes, requests to fixed public-page categories or download endpoints, accounts created and active places. Download requests are not a count of unique people or completed installations and can include retries or automated traffic. Existing sign-in metadata is used for account security and the disclosed inactivity process, not silently turned into gameplay histories or retention cohorts. We do not reconstruct visitors by IP, 30-minute visits, browsing paths or individual geography for these audience reports. Necessary security investigations remain separate and can examine relevant request details when actually needed. **Correction about earlier owner statistics.** Earlier owner reports used Cloudflare request information, including IP addresses, to estimate visitors, visits separated by a 30-minute gap, countries, landing pages and game downloads. The displayed reports contained totals rather than IP addresses, but creating them still involved IP-level processing. Our earlier explanation of necessary security/delivery processing and optional statistics being off did not clearly explain that separate statistical use. We have stopped new IP-based audience reconstruction, are reviewing retained working copies and are removing information that is not justified for a continuing lawful purpose. We retain only appropriately limited operational records, any genuinely non-identifying totals and the minimal record needed to document the review. This correction does not retrospectively obtain consent or change earlier legal texts. The optional gameplay statistics described in earlier development proposals remain disabled. **Taktikverse voluntary problem reports.** Taktikverse uploads a report only when a signed-in player presses **Send**. The authenticated upload is rate-limited and goes to a **Cloudflare Pages Function**, which stores the report in **Cloudflare Workers KV**. Each report holds the report file, account identifier, build, time, file size and the player's note. The file and note can contain game data and personal information you included. Cloudflare processes this report information on our behalf within the scope of our incorporated Data Processing Addendum. Submitting a report is optional and does not authorise access to unrelated personal files. Reports sent through this feature are not emailed or forwarded to Gmail or Porkbun. Section 6 explains deletion, including the automatic expiry. Authorised personnel use reports to investigate problems and improve reliability. A report is not published to other players merely because you submitted it. We may retain or publish a genuinely non-personal bug description or fix after removing personal information. **Application service-email provider.** We prepare application, admission and waitlist messages from **hello@energengames.com** in an ordinary **consumer Gmail account**, not Google Workspace. Gmail holds the drafts and sent copies. Outgoing messages are relayed through **Resend, operated by Plus Five Five, Inc. (United States)**, which uses **Amazon Web Services' Amazon Simple Email Service (SES)** for delivery. Resend processes the recipient address, message content (including the application status), and delivery information such as message identifiers, timestamps, delivery results, bounces and spam complaints on our behalf under its [Data Processing Addendum](https://resend.com/legal/dpa). Its [subprocessor list](https://resend.com/legal/subprocessors) identifies its delivery, infrastructure and other service providers. Incoming application replies to hello@energengames.com pass through **Porkbun forwarding into Gmail**; we are not using Resend's inbound-mail service. We do not include career saves, problem-report files, dates of birth or country profiles in application updates. Section 6 distinguishes mailbox retention from relay retention. **Local authorisation and retired parent flows.** The ordinary 13+ join route sends no parent emails and creates no parent record. The earlier teen parent-request route is retired for new ordinary sign-ups. If a specifically required authorisation route is later made available, its data, precise purpose, actor and mail delivery are explained before the relevant collection; it is not silently enabled by this licence update. Existing applicable approvals or requests, if any, remain subject to their lawful scope, withdrawal and deletion duties rather than being discarded to avoid those duties. **Privacy correspondence.** privacy@energengames.com remains available for privacy requests, account deletion and privacy complaints without sign-in. Incoming messages pass through **Porkbun's email-forwarding service** and are received in the same **consumer Gmail account**. These services handle the sender details, routing/header information, message and any attachments. We write and store our replies in Gmail and relay outgoing replies from **privacy@energengames.com through Resend and its SES delivery service**. Resend therefore also processes the reply recipient's address, our reply, any request text or attachments included in that reply, and delivery information under its DPA. Incoming privacy requests are not automatically forwarded to Resend merely because they arrive in Gmail. Please use Taktikverse’s in-game report feature for its game problems. Lattice’s separate private email reporting route is explained in Section 11. We have no separate data-processing agreement with Google for the consumer Gmail account used to compose and store application service emails and privacy correspondence. Gmail operates under [Google's consumer Terms of Service](https://policies.google.com/terms) and [Privacy Policy](https://policies.google.com/privacy), including Google's own service-operation, security and legal-compliance purposes. Neither Resend's DPA nor the Cloud Data Processing Addendum for our Firebase project covers this consumer mailbox. Relaying outgoing mail through Resend does not remove Gmail's handling of drafts, sent copies and incoming messages. We remain responsible for why we use the correspondence, who in our business can access it, and our retention and deletion decisions. This notice does not represent all of Google's consumer-service processing as processing solely on our instructions. Porkbun handles domain-address forwarding under its applicable service terms and [Privacy Policy](https://porkbun.com/legal/agreement/privacy_policy); it is not covered by our Firebase or Cloudflare data-processing arrangements. Please include only information needed for your application reply or privacy request, and do not include passwords, identity documents, sensitive information or unrelated personal files. You can use the account-page deletion control instead of emailing an account-deletion request. Email remains available for privacy requests without an account or sign-in. **Taktikverse private defaults.** There are no public player profiles, chat, shared worlds, purchases, in-game tracking or optional player statistics in Taktikverse. Lattice has the separate limited multiplayer and board visibility described in Section 11; it does not use the private manager name. We do not use a Google name or photograph as a manager identity or site avatar. Our separate manager profile uses a private name. Standard Google/Firebase sign-in can still supply and retain linked-provider profile fields, and replacing an application's display name does not itself establish their deletion. The provider information used in authentication, including any residual linked-provider fields, follows the account/provider retention described in this notice. We do not copy those optional fields into game saves or support reports. We do not describe provider receipt as 'no collection'. **Optional videos.** Some shared website pages offer click-to-load **YouTube** videos using the privacy-enhanced player. The embedded player is not loaded until you choose to load it. Loading connects your browser to Google's video service, which can process connection, device and playback information and use browser storage. Privacy-enhanced mode does not mean that no information is processed. Google explains its processing in its [Privacy Policy](https://policies.google.com/privacy). **News sending remains paused.** Selecting Resend for outgoing application messages and privacy replies does not activate studio newsletters or subscribe anyone to them. Neither Gmail nor Resend is being used to send studio news during this beta, and no subscriber list is supplied to Resend for that purpose. We do not use open tracking or link-click tracking in these application messages or privacy replies; delivery, bounce and complaint information is used for delivery and abuse prevention. Authorised personnel may access information as needed for operations, support and security, including from Grenada. Information may be disclosed to advisers or authorities for a specific legal obligation, claim or necessary protection of rights, subject to applicable law. We do not sell personal information, place third-party advertisements in the game, or share information for cross-context behavioural advertising. Optional news would be our own communications within the permission you give; an email preference is not permission for third-party advertising or unrelated tracking. ## 5. International processing The **Cloud Firestore database is in nam5, a United States multi-region**. Firebase Authentication also operates in the United States. This is not an EU-hosted account or cloud-save service. Taktikverse problem reports are stored separately in **Cloudflare Workers KV**, not in the Firestore database or the mailbox used for application service emails and privacy correspondence. Cloudflare's report processing is subject to its own service locations and applicable transfer arrangements; nam5 does not locate or confine the reports. Administration from Grenada and the operations of Google, Cloudflare, Resend and its delivery providers, Gmail, Porkbun and any video provider can involve other countries as well. Selecting nam5 does not restrict every provider or administrative activity to that location. **Google Firebase/Cloud.** Our Cloud Firestore, Firebase Authentication and Firebase App Check services are governed by the standard [Google Cloud Platform terms](https://cloud.google.com/terms), which incorporate the [Cloud Data Processing Addendum](https://cloud.google.com/terms/data-processing-addendum). Google's [Firebase privacy information](https://firebase.google.com/support/privacy) confirms that Firebase services governed by the Google Cloud Platform terms are already covered by that addendum. The separate Firebase Data Processing and Security Terms apply to the different Firebase services that specifically reference them. reCAPTCHA Enterprise Customer Data is also processed under Google's Cloud terms and addendum, not under the consumer Gmail arrangement. For covered EEA-to-US and UK-to-US transfers, Google states that it uses the EU–US Data Privacy Framework and its UK Extension. The Cloud Data Processing Addendum supplies the applicable Standard Contractual Clauses, including its UK provisions, for restricted transfers not covered by an applicable alternative transfer solution, subject to the addendum's conditions. Google's current [transfer-solution statement](https://cloud.google.com/terms/alternative-transfer-solution) explains the scope. These arrangements do not make every destination adequate or certify Synapse Tutor, LLC. **Cloudflare.** The [Cloudflare Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/) is incorporated into our [Self-Serve Subscription Agreement](https://www.cloudflare.com/terms/). It covers the applicable processing of Taktikverse problem reports through Pages Functions and Workers KV as well as the delivery, security and website-statistics services within its scope. Its transfer provisions recognise the Data Privacy Framework for transfers within that framework's scope and provide EU Standard Contractual Clauses and the UK Addendum for other restricted transfers as described there. These are the provider's applicable contractual arrangements, not a claim that we have signed a separate bespoke transfer agreement or that every report remains in one country. **Resend outgoing relay.** Resend's [standard Terms of Service](https://resend.com/legal/terms-of-service) incorporate its [Data Processing Addendum](https://resend.com/legal/dpa). It acts as our processor for the email data we submit for delivery. Resend states that it stores customer email content and delivery logs in the **United States**; selecting a sending region does not change that storage location. Its DPA incorporates the applicable EU Standard Contractual Clauses for EEA transfers, including the controller-to-processor module for this relationship, and the UK Addendum for UK transfers. Its authorised subprocessors, including Amazon Web Services for SES delivery, operate under Resend's subprocessing arrangements. Those arrangements do not extend Resend's DPA to our consumer Gmail mailbox or Porkbun forwarding. **Any specifically required authorisation.** No parent-contact processing is added by ordinary registration. A local authorisation feature, if separately enabled, must have its actual provider/transfer arrangements explained before use. Retiring the old teen route does not rewrite the contracts governing already received messages. **Gmail, forwarding and other Google services.** Consumer Gmail continues to handle drafts, sent copies and incoming application/privacy correspondence. Porkbun handles the domain-address forwarding into that mailbox. Outgoing messages from hello@energengames.com and privacy@energengames.com additionally pass through Resend as described above; this is not a replacement for Gmail or Porkbun. These email routes do not carry Taktikverse problem reports submitted through its Send feature. Lattice’s private email reports use the distinct route in Section 11. The consumer mailbox, forwarding service and Google's separate account/video services are not brought within the Firebase, Cloudflare or Resend addenda by this notice. Google's [consumer transfer-framework information](https://policies.google.com/privacy/frameworks) describes its use of the Data Privacy Framework and its UK Extension for covered transfers and Standard Contractual Clauses for its other relevant transfers. Those provider commitments do not create a consumer-Gmail processor agreement with us. Porkbun's Privacy Policy describes its own international processing and safeguards; no other provider's DPA is represented as covering Porkbun. The existence of a provider's transfer mechanism does not replace any separate obligation to have appropriate processor terms, assess a particular transfer or respect your rights. Synapse Tutor, LLC remains responsible for its own collection, use and disclosures. We do not treat your choice to email us as a waiver of these obligations or as blanket consent to overseas processing. You can ask privacy@energengames.com for information about applicable transfer safeguards or a copy, subject to necessary redactions. Synapse Tutor, LLC does not claim to be certified under the Data Privacy Framework merely because a provider is certified. Using the beta or accepting its licence is not blanket consent to international transfers. ## 6. Retention and deletion We retain information for the purposes described, using the following schedule. A record's retention in our live systems and a provider's residual deletion process are different. | Record | Retention | |---|---| | Local careers, worlds and exported backups | Controlled by you. Delete careers/worlds in the game, clear site data or delete exported files. The local library keeps the last ten scenarios. Browser eviction or loss of the device can also remove local data. | | Live cloud career | Scheduled for removal after 90 days without a successful cloud save, or earlier by successful cloud removal or an account-deletion request. Section 3 explains explicit re-upload. | | Cloud-removal/revision marker | Retained without career data while the account exists, including after cloud expiry/removal, so stale devices cannot overwrite a newer career. A fresh explicit upload can replace the removed state. The marker is removed as part of account deletion; it is not kept for the three-year licence-evidence period. | | Old local age-screen records | The routine age screen is retired. Legacy `energen.ageCheck` values are removed on the next migration visit; the new route does not continually recreate them. Clearing them does not erase known underage-account information or historical legal evidence. | | Account eligibility/acceptance | We store the actual 13+ confirmation and legal version/hash/time, not a new adult/teen age classification or full DOB. A necessary local threshold result is separately limited to that purpose. Existing contradictory underage information is not ignored. Operational eligibility records follow account deletion; minimal agreement evidence is separate. | | Waitlist and optional email choice | We retain only the active requested queue and scoped preference records. New connection-country decisions are not stored in the profile. Legacy country/age fields no longer needed for a lawful purpose are removed during migration; real evidence and known ineligibility are not falsified. | | Unsubscribe identifiers and withdrawal records, where issued | Used to apply a withdrawal and exclude that recipient from sending. Account-linked token records and links are removed during completion of account deletion. They are not part of the retained licence-acceptance record. No news is currently sent. | | Account and access profile | Kept while used. An inactive free-beta account becomes eligible for closure after 12 months without authenticated use, with at least 30 days' warning before closure. Live account/profile deletion follows within 30 days after closure. If the beta ends first, account/profile records are removed within 90 days unless you affirmatively choose a continuing service requiring them. Requested deletion uses the faster workflow below. | | Minimal licence-acceptance evidence | Taktikverse evidence is kept during the agreement and for three years after account closure. Lattice evidence has the separate agreement-end clock in Section 11. The retained record identifies the relevant account, acceptance time, version label and associated text hash; it excludes the erased profile fields, news choice, age result, country and career. Access is restricted. A specific dispute or binding requirement may justify a documented hold on relevant evidence, not a blanket indefinite archive. Known under-13 cases follow the prompt-erasure override below rather than automatic three-year retention of their full history. | | Routine application/access logs | We do not operate a separate application/web-server log archive. Logs in our Firebase project's Google Cloud Logging `_Default` bucket are retained for 30 days under the current setting. | | Required Google Cloud audit records | Applicable `_Required` bucket records, including Admin Activity and System Event audit logs, are retained for 400 days. This provider-fixed period is not a claim that all gameplay or all provider data is retained for 400 days. | | Cloudflare statistics and security records | Necessary delivery/security records remain separate from optional Web Analytics. Cloudflare provides traffic statistics covering at least the last 30 days, sampled security events and DNS analytics up to 31 days, and Pages Function request metrics up to three months under the previously disclosed service settings. Security events can contain request details. For Web Analytics, Cloudflare states that unsampled data is retained for seven days, then downsampled to around 10%, with history accessible for the previous six months; query sampling can also vary. This is not a promise that every event is erased or anonymised after seven days. Its RUM statement says the source IP is discarded at the nearest data centre and not stored in RUM core databases or logs; other Cloudflare delivery/security retention is separate. We do not keep a separate raw Web Analytics export or event-level archive. | | Voluntary reports in Cloudflare Workers KV and support copies | Kept while investigated and deleted within 90 days after resolution, or earlier at the automatic expiry of about 120 days from upload. The automatic expiry can remove a report even if it is still unresolved; these periods are not added together. We also delete reports on a valid request or as part of account deletion, without waiting for those limits. Associated support copies we created are removed too. Genuinely non-personal bug descriptions and fixes can remain. Provider-managed residual copies follow the applicable provider processes below. | | Application service emails and related correspondence in our Gmail mailbox | Kept only while needed to administer or explain your application. Sent messages are permanently deleted from our active mailbox, including Sent and Trash, no later than 12 months after sending; application replies follow the same maximum from receipt. We delete them sooner when no longer needed or in response to an applicable valid erasure request, and include account-linked copies in the account-deletion process below. Any temporary recipient exports or support copies follow these limits and are removed sooner when their task is complete. A specific complaint or legal matter may justify a separately limited record under the relevant rule, not retention of the whole mailbox. Resend's separate relay retention is below; messages in your own mailbox remain under your control. | | Privacy-request and complaint files, including incoming messages and outgoing replies | Used to handle the case, then only a minimal outcome/compliance record is kept for three years after resolution. Unnecessary identity-verification material is removed sooner. This is a separate case record where a case exists, not retention of the deleted account profile. Resend's relay copies have the separate schedule below. | | Resend relay email and delivery logs for both addresses | Resend's published standard retention for email and log data on its Free, Pro and Scale plans is **30 days**. We seek earlier deletion through Resend where needed to meet a valid erasure request. This is separate from our Gmail schedules and from the backup/end-of-service periods below. Deleting a Gmail message does not itself delete Resend's copy. | | Address-based delivery suppression records | Resend may retain a recipient address and reason after a hard bounce or spam complaint to prevent repeat failed or unwanted sending. These records are separate from the general email/log retention period. We use them only for delivery protection and respecting stop requests, review whether they remain needed, and remove records we control when no longer needed, including on account closure once further sending is blocked. We seek provider assistance where necessary. They are not newsletter permissions. | | Conditional parent-authorisation requests and unfinished enrolment | Only created where an applicable requirement needs them. Credentials expire after 24 hours. Incomplete/refused/expired requests are deleted within seven days from original creation; visits do not extend this. No such record is created for self-acceptance alone | | Conditional approval mail and delivery attempts | Resend's disclosed periods apply to messages actually sent. The current site does not retain a retry outbox: a missing mail key or exhausted limit leaves the request pending and reports that the message was not sent. Credential tables retain digests; an expired email link cannot authorise an action even if the message remains in a mailbox. Staff correspondence follows its existing schedule | | Studio-held operational aggregate reports | Keep only totals needed for the disclosed operation/administration purposes, for no more than 395 days from the end of the reporting period. Small or otherwise identifiable totals remain subject to personal-information safeguards. Existing provider-managed security records have their separate periods above; this row does not extend raw-log retention. | | Working copies from the earlier IP-level statistical queries | Restrict access while reviewing their purpose and remove unjustified raw exports or derived linkable working records promptly. Retain only a minimal documented review/outcome record or information justified for a specific legal/security matter, not an indefinite archive of IP histories. Provider-held records follow their applicable purpose and retention; deleting a studio export does not delete every provider copy. | | Website statistics preferences | An Off choice can be remembered by the non-unique `eg_webstats=off.v1` cookie for 180 days from the choice, without visits extending it; clearing site data removes it. Where a valid affirmative choice is needed, the initial On option is for the current tab/session only, with an absolute 24-hour maximum, stored as purpose/wording version and choice time in `energen.webStatsChoice.v1`, not as a tracking identifier. Account change, expiry or an incompatible notice ends that On permission. Off and stricter applicable restrictions take priority. These are privacy-control records, not audience identifiers. | | Our backups of accounts/cloud careers | We create no backup snapshots, database exports or separate recovery archive of those records for this beta. The single cloud career is not a version-history backup service. This does not affect files you export yourself. | **Rights and any historical authorisations.** A young user can request deletion independently. A claimed parent's authority is assessed rather than giving general access to a self-registered account. Where a legally required approval is withdrawn, stop its actual scope; cloud-only withdrawal does not remove unrelated local play. If continued account provision becomes unavailable, close operational data within 30 days unless the requirement is lawfully satisfied or a genuinely available independent route is established; earlier erasure requirements prevail. Delete relevant records across providers while retaining only justified minimal evidence. Unrelated adult/sibling records are unaffected. **Known under-13 accounts.** Once we have reliable information that an account belongs to a child under 13, we stop new authorised use, initiate deletion of its Auth/profile, cloud, report and related service-message data promptly and track completion. We do not wait for the weekly routine, inactivity expiry or three-year agreement policy. A failed deletion is retried and escalated. Only a specifically necessary, access-restricted legal/security or deletion-completion record may remain for its justified period. The aim is not to retain a shadow child profile. Provider security records and residual deletion schedules are not represented as instantly erasable. **Abandoned sign-in versus known underage.** A person who signs in without joining may have a normal authentication account. We keep it only under the disclosed account-inactivity schedule or a shorter documented abandonment setting. This is different from a known-under-13 account, which receives prompt action. No client-side deletion call alone proves that all associated records were erased. **Retired teen/parent records.** Published legal archives remain. Any real earlier parent request, receipt or legal event is handled under its original purpose and applicable deletion/withdrawal rules. We do not convert it into a new acceptance or delete a parent's unrelated account. **Account deletion is a request with immediate first steps.** Use the account-page deletion control or email privacy@energengames.com. Once an authenticated deletion request is recorded, the site immediately erases the profile fields containing your name, email, news choice, age result and country, removes the cloud career data and records that deletion is pending. Pending deletion blocks play. The site's profile and **Firebase Authentication's login record are different records**. Authentication can still hold your account identifier, email, name and sign-in metadata while the request is pending; deleting the profile is not a claim that those fields have already disappeared everywhere. A weekly administrative run removes the remaining live account data, entitlements, cloud-removal marker, related unsubscribe records, account-linked problem reports in Cloudflare Workers KV and the associated application service correspondence we control, retaining only the minimal licence-acceptance record in the beta account system. **The Firebase Authentication login is deleted last.** Completion is without undue delay and within 30 days of receipt of the request, or sooner where applicable law requires. We confirm completion. The weekly schedule does not extend a legal deadline. For a request sent outside the signed-in flow, we may promptly seek proportionate verification to prevent unauthorised deletion. Problem reports, application service correspondence and associated support copies are included in account deletion rather than retained for the three-year licence-evidence period. We also identify any related relay copies and suppression records within our control and seek Resend's assistance for earlier erasure where required; we do not wait for a provider retention period instead of acting on your request. The different case-record and provider-residual schedules below remain distinct. Separate privacy-request/complaint files and provider-generated logs follow their schedules above, subject to any applicable right to earlier deletion. We explain any lawful exception. Account deletion does not erase local browser records or files you exported. We do not use retained licence evidence to rebuild your profile or restart a subscription. **Provider residual copies.** Google Cloud's applicable deletion terms provide for deletion from its systems as soon as reasonably practicable and within a maximum of 180 days after a qualifying unrecoverable deletion instruction, subject to applicable legal-retention exceptions. Firebase states that deleted Authentication user information is removed from live and backup systems within 180 days; logged sign-in IP addresses are retained for a few weeks. App Check states that attestation material is not retained by App Check, while replay-protection tokens can be retained for up to 30 days where that feature is used. These periods are separate from the Google Cloud log-bucket periods above and from reCAPTCHA's own service processing. For application service emails and privacy correspondence, Gmail normally keeps deleted messages in Trash for up to 30 days unless it is emptied sooner; we empty it when applying our permanent-deletion policy. Google's general retention explanation describes a deletion process commonly taking around two months and encrypted backup retention of up to six months, with specified longer-retention exceptions. These are provider processes for application service emails and privacy correspondence, not an additional archive we choose to keep or the retention rule for reports in Workers KV. Cloudflare does not publish one fixed residual-deletion period for all relevant data. Porkbun does not publish a specific forwarded-message/mail-log retention period in the information reviewed for this notice. **Resend residual copies and service closure.** Resend's [published retention information](https://resend.com/security/gdpr) states that backups persist for **seven days**, and remaining customer data is deleted within **90 days after we terminate our Resend service account**. That 90-day period concerns closing our provider account, not a player's account, and does not extend our response deadline for a player's request. Resend directs customers to its support team when a particular message needs removal before the standard email/log period ends. We follow the applicable deletion process rather than assume removal from one provider erases every other provider's copy. A narrowly necessary legal or security hold can apply to particular records, with its purpose and duration reviewed. We seek deletion through the applicable provider processes where required; “provider-managed” is not a blanket exemption from your rights. If we restore or re-import records we control, we reapply deletion and withdrawal instructions. ## 7. Cookies, browser storage and security decisions The beta uses local storage, session storage, IndexedDB and caches, as well as provider cookies. Storage is scoped to an origin: preview and live-site records are separate. Session storage normally ends with the tab/browser session, but browser session-restoration features can preserve it. Persistent browser storage generally remains until an app removes or replaces it, you clear it, or the browser evicts it. The inventory below combines preview measurements and a signed-in capture on energengames.com in Chrome on 13 October 2026, and a measurement of Cloudflare Web Analytics on energengames.com in Chrome on 16 October 2026, with the website, game and Firebase source inventories. A provider-conditional entry is not a claim that it was seen in every visit. Google sign-in sets Google's own account cookies on its domains, under [Google's Privacy Policy](https://policies.google.com/privacy); we neither set nor read these cookies, whose observed lifetimes were 30 to 400 days and can vary by account, region and browser. | Storage / key | Purpose and when used | Retention / control | |---|---|---| | IndexedDB `firebaseLocalStorageDb`, store `firebaseLocalStorage`, record `firebase:authUser:{apiKey}:{appName}`; equivalent local/session-storage fallbacks | Firebase sign-in record, including account/provider details and access/refresh tokens. An empty database can be created before sign-in | No record TTL in persistent storage; removed on sign-out or appropriate invalid-session handling. Session mode follows the session. Token expiry is not record expiry | | `__sak` probes in local/session storage or Firebase's database; `validate-browser-context-for-indexeddb-analytics-module` | Tests whether storage is available. The latter name is a Firebase capability-test name, not evidence of Google Analytics use | Successful probes are removed; interrupted probes can leave an empty database or residue | | Conditional Firebase OAuth records: `firebase:pendingRedirect:…`, `firebase:redirectUser:…`, `firebase:persistence:…` | Only if a sign-in/link/reauthentication flow uses them. The cloud bridge's popup route does not itself initiate these redirect records | Redirect completion, sign-out or the selected storage/session lifetime; a serialised user can be present in redirect state | | IndexedDB `firebase-app-check-database`, store `firebase-app-check-store` | App-scoped attestation-token cache for protected game/account features and the unsubscribe flow | Configured token validity is seven days, with renewal while used. Expiry does not necessarily delete the database. Auth sign-out does not clear it; clearing site data does | | IndexedDB `firebase-heartbeat-database`, store `firebase-heartbeat-store` | Firebase compatibility diagnostics: SDK platform/version and usage dates used in Firebase request headers. This is distinct from career data and from Firebase Analytics | Up to 30 heartbeat entries plus the last-sent date in the audited SDK; entries are removed when sent. No fixed age-based TTL. Sign-out does not clear it | | Conditional Google cookie `_GRECAPTCHA` on `www.google.com`, path `/recaptcha`; site local storage `_grecaptcha`; Google-frame storage such as `rc::a`, `rc::f` (local) and `rc::b`, `rc::c` (session) | reCAPTCHA Enterprise security processing when App Check runs. Google decides whether to set `_GRECAPTCHA`, and its frame-storage keys vary between sessions. Not loaded by the measured ordinary signed-out pages; used by protected features and the unsubscribe flow | `_GRECAPTCHA` was observed with a 180-day lifetime in a signed-out preview sample on 13 October 2026, but was not set in that day's signed-in live-site sample. The live reCAPTCHA frame held `rc::a` only; the earlier sample also held `rc::f`, `rc::b` and `rc::c`. These are observations, not a fixed cookie lifetime or a guarantee that every listed key is present. The listed local-storage records have no automatic expiry; session records follow the session | | Legacy local/session `energen.ageCheck` | Old adult/teen/under13 route cache, no longer used for routine join | Removed on the next migration visit; no new DOB screen or cross-device recheck is created by this key. Server-known eligibility and historical evidence remain independent. | | First-party cookie `eg_private=1`, Secure, SameSite=Lax, path `/` | A fixed protective flag set for players/sign-in flows so optional statistics stay off; not an age label or unique tracking ID | Up to 400 days from its latest setting, or earlier browser deletion. It does not establish consent or prove age. A new/unrecognised browser must not be assumed an adult analytics visitor merely because the flag is absent. | | Legacy `energen.teenRequest` and old approval-page credentials | Retired workflow state, if previously present; not created by ordinary registration | Obsolete browser state is removed at migration. Any still-valid historical request is closed or completed under its lawful scope; server expiry and provider mail deletion are separate. | | Session storage `react-router-scroll-positions` | Restores position during back/forward navigation | Browser session | | Service worker for `/play/`; cache `taktik-play-v3` | Launcher and encrypted game release files for quicker loading; retains the newest two large releases, not a cloud-career archive | Replaced/pruned by release updates or removed by clearing site data | | Local storage `energen.play.install-card`, `energen.play.ios-card` | Remembers dismissal of the mobile installation prompts | No automatic expiry in the current code; clearing site data removes it | | IndexedDB `taktik-v16`, store `checkpoints`: `taktik.library.v1`, `taktik.career.slot.`, older `taktik.career.v16`, `taktik.world.`, `taktik.scenario.` | Local career index, checkpoints, summaries/settings, saved worlds and recent scenarios | Individual items can be deleted in the game; the last ten scenarios are retained. Clearing site data removes the local database | | Local-storage fallback `taktik.career.v16` / `taktik.career.slot.` | Career checkpoints where IndexedDB is unavailable | Until deletion in the game or clearing site data; a memory-only fallback may be used when persistent storage is unavailable | | Local storage `taktik.licence` | Local in-game acceptance flag in editions using that flag; not the website's account-linked legal evidence | Until replaced by a later local licence acknowledgement or site data is cleared | | Local storage `taktik.cloud.link`, `taktik.cloud.off` | Account-associated career link, revision/hash/sync state and accounts whose cloud saving is Off on this device | Updated with sync/choices, replaced when choosing a different cloud career, or removed by clearing site data. Turning saving On removes the applicable Off preference | | Local storage `taktik.cloud.device` | Random saving-browser identifier sent with cloud saves | Until site data is cleared. The cloud bridge's conditional fallback `taktik.cloud.device.v1` is created only if a caller supplies no device identifier; the documented game supplies its own | | Session storage `taktik.browserNote` | Remembers that the supported-browser notice was shown | Browser session | | Firestore bridge document cache and queued writes | Career/manifest/entitlement data in the bridge's memory-only cache, not Firestore disk persistence | Page/instance lifetime. This does not make Firebase Authentication or App Check memory-only | | Conditional Cloudflare `cf_clearance` | Records a passed security challenge if one is presented; not observed in the preview sample | Normally 30 minutes with the default challenge setting; the actual provider setting applies | | Cloudflare Web Analytics `beacon.min.js`, only after the public-page and privacy checks in Section 4 | Reads current-page performance information and sends the eligible page/referrer and technical measurements to Cloudflare. Never loaded on the excluded private/game routes | Cloudflare states that the beacon itself neither reads nor writes cookies or browser-storage records. Our earlier sample found no such storage; this does not mean no browser information is accessed. Provider data periods are in Section 6. An objection stops further optional measurement; removing a script element alone is not the withdrawal mechanism. | | Cookie `eg_webstats=off.v1`; conditional session storage `energen.webStatsChoice.v1` | Non-unique Off preference and, only after a valid affirmative action where needed, the current-tab permission record; no account or device identifier | Off cookie: 180 days from the actual choice, not sliding. Session On: absolute 24-hour maximum and reset on account change; browser restoration cannot extend validity. Neither record is sent as an analytics identifier. The existing `eg_private` protection remains separate. | | Optional YouTube frame on `www.youtube-nocookie.com`: local storage `yt-icons-last-purged`, `yt-player-caption-persistence`, `ytidb::LAST_RESULT_ENTRY_KEY`; IndexedDB `YtIdbMeta`; cache `yt-icons` | Player settings/resources after choosing to load a video on another shared website page | Provider-managed browser storage; no fixed expiry established by the preview sample. Removing site/provider storage removes local records, subject to the browser's controls | | Other editions only: cache `taktik-v-` | A standalone/offline edition's own file cache, not the protected website's launcher cache | Replaced by the next edition's cache or removed by clearing site data | The October 2026 baseline measurements found no site-set first-party cookies in those sampled flows. The account implementation uses `eg_private`; the separate Website statistics control can set the preference cookie described above. It would be inaccurate to describe this release as setting no first-party cookies. These privacy-control records are not analytics identifiers. Cloudflare's public-page beacon works with current-page information, including information in memory, even when it uses no durable analytics storage. Legacy C93 and optional gameplay statistics remain disabled. We have not enabled the Firebase Analytics module in the audited bridge; the separately disclosed compatibility heartbeat and necessary provider security processing remain. Accepting the game licence or requesting news does not provide consent to optional browser storage or tracking. Any consent legally required for a separate optional feature must be sought for that feature. You can use browser controls to delete storage, but this can sign you out or remove careers. A cookie setting may not clear IndexedDB or local storage. You do not need to clear a career or sign out to request a correction or deletion. **Security decisions.** Necessary checks may challenge or block abuse. A connection-country availability check for a new place is transient and is not stored as a profile attribute. In the limited situations requiring prior permission, a check or restriction must precede the affected account collection. We do not routinely age-screen or require existing players to repeat the 13+ declaration on a new device. Known under-13 information is acted on. Human review is available; a local cookie cannot grant entitlement, waive local law or replace actual licence acceptance. ## 8. Your rights and complaints Depending on the applicable law, you can request access, correction, deletion, restriction or a portable copy of your information and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it for future processing without making earlier lawful processing unlawful. Rights have legal conditions and exceptions. Contact privacy@energengames.com and explain the request. You need not accept a revised licence, remain a player or sign in to make a privacy request. We may ask for proportionate verification, but do not routinely require identity documents. An authorised agent can act where applicable law allows. We respond within the applicable legal deadline. EU/UK rights requests are ordinarily answered within one month, with any lawful extension explained within the required time. Our account-deletion process has the 30-day commitment in Section 6, subject to any shorter legal deadline. Applicable US state-law response, appeal and non-discrimination requirements also apply. Where an appeal right applies, reply to our decision through the privacy contact to request an appeal; we will explain the result and further complaint options. You can make a privacy complaint through the same address; “Privacy complaint” in the subject helps route it but is not a condition of handling it. We acknowledge complaints within 30 days, investigate without undue delay, keep you appropriately informed and explain the outcome. That acknowledgement period does not extend a separate rights-request deadline. You can also complain to the competent regulator, including your relevant [EEA data-protection authority](https://www.edpb.europa.eu/about-edpb/about-edpb/members_en) or the [UK Information Commissioner's Office](https://ico.org.uk/make-a-complaint/). Nothing in this notice removes a statutory complaint or court remedy. ## 9. General-audience games with protective defaults **Taktikverse ordinary join.** This is a free, single-player, general-audience football-management game for people aged 13 or older. The ordinary flow is sign in, then read and affirm the licence and 13+ statement, then play if admitted. We do not routinely ask for your birth date or whether you are under 18. We do not treat Google sign-in as proof of age. A successful first sign-in can create a Firebase account before you press Join; provider collection and account retention therefore start at sign-in, not only after the licence checkbox. **Taktikverse protections for all players.** Everyone receives a private manager name, no public profile or chat, no purchases, no optional game tracking or player statistics, and no news enrolment by joining. Cloud saving and sending a report are deliberate service choices. Necessary delivery/authentication/security processing remains. We provide understandable privacy information and an accessible help/deletion route. Applying these defaults does not mean we disregard age information that we actually receive. **Local legal requirements.** In limited cases an applicable rule requires an additional age/authorisation step or prevents us from giving a new place without a local setup. We explain the necessary step before taking it. A requirement for prior authorisation is applied before the covered collection, not retroactively after sign-in. If a threshold must be checked, the date or age is evaluated only for that purpose; we retain the necessary result and event rather than a full birth date unless a specific legal requirement is explained. An optional-feature requirement, where one actually applies, does not itself remove permission for unrelated local play. **No routine parental contact.** We do not collect a parent's email, create a parent account or send parental approval messages as a condition of ordinary joining. A general clause telling a minor to obtain any legally needed permission does not substitute for an actual parent action where the service is required to obtain one. An asserted parental relationship does not automatically grant access to another person's private saves, reports or correspondence. **When we learn a user is under 13.** We do not offer under-13 accounts. Reliable notice from the user, a parent, a report or other actual information is handled promptly: stop new authorised use, initiate deletion across the relevant services, and follow up failures. We do not ignore contradictory information because the user previously ticked 13+, nor manufacture a new adult declaration by removing an old age field. The special deletion rule in Section 6 takes precedence over ordinary inactivity periods. A proportionate correction process is available for mistakes. **Returning players.** Agreement and eligibility events are account-linked, not dependent on a remembered browser age answer. An already admitted player is not asked the same routine question again just because they use another browser. A real new legal requirement, credible underage information, changed eligibility or a material new agreement can still require action; 'not repeatedly asked' does not mean 'never reviewed for any reason'. **Voluntary communications.** Account/help messages are different from news. News sending remains paused, even if a future-news preference exists. A new marketing purpose cannot use licence acceptance as consent or rely on not knowing someone's age to avoid a required authorisation. ## 10. Security and changes We use access restrictions and secure service connections appropriate to the information and risks, but no system can guarantee absolute security. A privacy notice is not a promise that the beta will never lose a save; keep your own exports where needed. **Unified agreement records.** New participation uses one 13+ licence. Older adult licences, teen addenda, eligibility notices and the actual events accepted under them remain archived as history. We do not overwrite them or manufacture acceptance of the new licence. The site's active account route no longer requires a separate teen agreement; any real pre-existing authorisation remains limited to its applicable purpose until lawfully closed or replaced. **Licence records.** Taktikverse remains on **beta-2026-10-20-r1**, archived at its [existing permanent address](/legal/licences/beta-2026-10-20-r1.txt). Lattice uses **beta-2026-11-04-r1**, archived at its [separate permanent address](/legal/lattice/licences/beta-2026-11-04-r1.txt). The two games have separate acceptance records; this notice does not require a Taktikverse player to accept Lattice terms. Account-linked evidence records the accepted version, its associated text hash and acceptance time. Editorial fixes preserve the original acceptance and archived text; they do not create an acceptance that you did not give. A material change requires a fresh affirmative acceptance for continued participation under it. Public archives contain legal texts, not a list of players or their acceptances. **This notice.** We identify each published notice by an immutable version and its archived text/hash. We do not overwrite an earlier archived text when correcting or updating the notice. Material privacy changes receive appropriate prominent notice; new purposes are explained before the relevant processing begins, with separate consent where required. A privacy-notice update is not automatically a change to your game contract or a request for consent. Your privacy requests remain available without agreeing to a newer game licence. **Earlier change history, retained.** The 3 November 2026 revision privacy-2026-11-03-r2 added limited Cloudflare Web Analytics on eligible public pages, with regional/child-default checks, a free Off control and valid prior permission where required. It follows the separate operational-reporting correction; it does not erase that correction, authorise past IP-level queries, resume IP-based audience reconstruction, enable gameplay statistics or retrospectively change an earlier licence acceptance. The earlier correction's statement that the beacon was disabled describes that release. New measurement starts only after the matching contractual, privacy and implementation conditions are satisfied. [Archived text of this notice](/legal/privacy/privacy-2026-11-11-r1.txt). ## 11. Lattice: regional access, online play, private lobbies, team pings and local progress This section includes the additional features in **v17**: private lobbies for up to six players and fixed team pings. They become available when v17 is released. The existing two-player rooms remain under **Quick invite**. The new modes use the same game service and privacy controls; the update does not introduce chat, editable online names or a new use of past match records. ### A separate place and regional availability Lattice is a free browser strategy beta for players aged 13 and over, with a separate temporary cap of 100 places, application order and licence acceptance. You use Google sign-in through Firebase Authentication on the existing Energen account. Signing in is separate from applying and may create an authentication account before Join. We store the Lattice place and the licence version, exact text hash and time actually accepted in Firestore. Joining Lattice neither grants nor removes a Taktikverse place. During this beta, **Lattice is not offered in Australia, South Korea, mainland China, Vietnam, Indonesia or Brazil**. These are Lattice-only availability limits. In the **EU/EEA and United Kingdom**, solo features, Quick invite duels, online co-op, private-link spectating and Daily/challenge boards are available, together with v17’s unranked lobbies for up to six players in Versus, Teams or Co-op and their fixed team pings. Ranked matchmaking and persistent Elo ratings are unavailable there. The regional unranked route does not create, retrieve or update a continuing skill rating or cumulative performance profile, including from board results. Account authentication, the Lattice place and licence record, and the protected release-key check still operate. Local solo gameplay does not mean that account or delivery processing stops. **Connection-country decision.** Cloudflare supplies the connection’s country field. We use it transiently to enforce the applicable whole-game or online-feature availability decision at admission, release-key delivery and online connection/board access. We do not store that country in the account, rating, board or application logs, or use it to build a location history. Lattice’s application code does not read or store the source IP address; Cloudflare still receives it to route and protect the connection. This is a necessary regional-access decision, not GPS collection, a request for device location permission or audience measurement. An unavailable or unrecognised country does not unlock online access. A network location is not proof of residence; you can ask hello@energengames.com to review an apparent error. The shared eligibility safeguards continue, and a Lattice availability decision does not change Taktikverse. **Token handling.** The website puts the Lattice entitlement and accepted licence version in a custom claim in the Firebase sign-in token. The online service validates the signed token, its necessary account/access fields and the regional decision, and enforces current restrictions and deletion. A standard provider token can contain email or other authentication metadata even though Lattice’s game logic uses only the necessary identity and access fields. We do not copy optional Google profile fields into a Lattice identity, publish them to peers or write tokens to application logs. Updating a claim does not itself erase a previously issued token; current revocation is enforced separately. A denied online request does not create a handle, rating, board entry or presence record merely because it carried an otherwise valid token. ### Information and purposes | Information | Purpose and visibility | Basis and safeguards | |---|---|---| | Lattice application, place, actual licence/13+ confirmation and server time | Allocate separate capacity and verify requested access. Kept in the shared account service, not displayed to players | Necessary requested-service processing and limited agreement/compliance evidence, subject to contractual capacity and the local rules explained in Section 2 | | Transient Cloudflare connection-country field and access result | Apply regional game/feature availability without a stored country profile | Necessary compliance, availability and access administration; no unrelated analytics or location-history use | | Account identifier, assigned handle, rating, room and connection role | Operate authorised participant/viewer connections and reconnection | Minimum service/security data; private account keys are not displayed or sent as player identity to other participants or viewers | | Lobby and room code/settings, internal account and connection references, assigned handles, seat, faction, two doctrines and ready state | Assemble the chosen match and preserve its room across server sleep/wake. Lobby participants see handles, choices and readiness; internal account keys are not sent as player identity | Current session metadata in memory and the Cloudflare Durable Object snapshot; event-based removal described below; no rating or player profile created by a lobby | | Match state and fixed gameplay commands, including a team ping’s sending seat, target node, Attack/Defend/Help signal and game tick | Run the match and let authorised private viewers catch up and watch. All participating clients and viewers receive the commands; pings are displayed to allies and spectators | Bounded memory only; no persistent move/ping archive or saved online-match replay; server validation of permitted inputs | | Rating, games, wins, losses, draws and last played | Ranked competition, matching and proportionate continuity | Limited performance evaluation; deliberately chosen ranked play, no advertising or cross-game engagement profiling | | Overall presence counts and limited handle/rating preview in the chosen ranked queue | Show availability for requested matchmaking | Aggregate counts elsewhere; no public live-match list or retained last-seen history | | Private watch token, live viewing connection and count | Admit an entitled viewer to the privately shared live match and rematch | No guest viewing; no viewer identity displayed to players; no viewer command or message channel | | Deliberately submitted starting state and the submitting client’s own commands, up to 2 MB | Re-simulate a Daily/challenge result before accepting it | Transient verification input discarded after processing; a failed check is not an automatic cheating ban | | Board account key, handle, completion time, submission time and Daily difficulty; challenge code as the board key where relevant | Show an optional result and apply its own expiry | The board API displays only handle and time. Internal expiry, account and difficulty fields are not a public profile | | Minimal restriction, review and temporary deletion-fence information | Enforce a justified action and prevent stale access or delayed work from restoring erased records | Restricted access, defined duration and necessity reviews; not a hidden rating or move-log archive | | Voluntary private help, complaint or appeal and limited case outcome | Respond, assess safety/fair-play concerns, correct mistakes and meet applicable obligations | Existing private email route, no automatic replay attachment or new report database; specific retention below | The purposes are distinct. Acceptance of the licence is not consent to marketing, tracking or every use of a child’s information. In GDPR-framework jurisdictions, contract performance is used only where contractual capacity and objective necessity support it; any legitimate-interest basis is assessed separately with children’s rights given particular weight. Applicable local consent and parental-authorisation rules still apply. We do not use a legitimate-interest label or the fact that gameplay is local to bypass an applicable requirement. Optional result publication remains a deliberate, separate choice. ### What players and viewers can see Your handle is **pseudonymous personal information**, not fully anonymous data. We can associate “Commander 48213” with the account that holds it. The server assigns it; you may re-roll once every 24 hours. A re-roll changes the current displayed identity without changing the account, rating or valid restriction. It cannot retract a handle already seen or captured. The freely editable Energen manager name, email, Google name and photograph are not used as your Lattice handle. Match participants see the other players’ handles, factions, draft picks and in-game actions, and ratings where ranked ratings are available. The EU/EEA/UK unranked route does not use or display the player’s persistent Elo. Presence is otherwise counts, with a limited sample of handles/ratings visible to people deliberately in the ranked queue. Daily and challenge boards show handle and time inside the admitted game only after the player chooses to submit a result. They are not published on the public website. **Private spectators.** A player can choose **Invite a viewer** to create a private 12-character watch link and share it outside Lattice themselves. There is no public live-match list. A viewer must be signed in, hold a Lattice place and have regional online access. Viewers receive the match settings, full gameplay state and commands needed for catch-up/viewing, and the players’ handles. The viewing projection does not include the watched players’ account identifiers, email or rating metadata. Players see how many viewers are watching, not who they are. Viewers cannot send commands, messages or other material to players; their arrival/departure can change the count. Where a rematch is available, the viewing session follows the players until ended. A v17 lobby uses a new lobby for another round. A recipient may forward a watch link, so it should be shared only with intended viewers. Re-rolling or leaving cannot remotely recall a screenshot or recording another person has already made. There is no text or voice chat, player-written name or room title, shared social profile, friend list or image channel. Interactions use fixed gameplay commands, including the three tactical pings described below. The Profile screen is private local progress. **Quick invite** rooms support at most two human players; Triad/Realm add AI seats for versus or co-op. **Lobbies** support up to six human players in unranked Versus, Teams or Co-op, with AI in the other seats. Players choose a faction and two doctrines and mark themselves ready before the host starts. People in that lobby see each other’s assigned handles, choices and ready state. There is no public lobby list: entry uses a code or link a player shares. Generated room, watch and challenge links are shared through an external service the player chooses; we do not send them to contacts. A link is not an entitlement and does not bypass sign-in, a Lattice place or regional access. **Team pings.** In Teams and Co-op, a player can select a node and choose **Attack**, **Defend** or **Help**. The signal uses fixed game labels, not player-written text. It records the sending seat, node, signal and game tick. Allies see the ping and its notification; authorised spectators see the ping too. Like other match commands, it is relayed to **every participating player’s browser and to spectators**. Rival players’ games receive it but do not display it. Pings are therefore not a confidential allies-only channel. They are not added to ratings, boards or application logs. **Self-contained challenges.** A challenge code carries the world’s settings and seed. There is no server-side challenge-world store and no 60-day deletion promise for copies of a code someone holds. A submitted score uses the code to identify its board; each board entry has a separate 60-day expiry. Code compatibility can change with game updates. ### Server operation and device storage **Cloudflare Workers and Durable Objects** operate Lattice’s online service as our processor under the Cloudflare terms and Data Processing Addendum described in Section 5. This includes connections, transient verification and the limited persisted records below. Cloudflare service locations and transfer arrangements apply; Firestore’s nam5 region does not confine Durable Object processing to that region. We do not promise a single geographic hosting location for the online service. Players and viewers connect through our server. There are no peer-to-peer connections or exchanges of players’ IP addresses. Lattice application diagnostics contain counts and error codes, not IPs, country values, tokens, account identities, command payloads or a move history. Necessary provider security and delivery records remain subject to Sections 4–6; application minimisation does not mean a provider receives no network information. **Operator status.** The routine operator view contains totals only: online now, in matches, matches today, board posts today and ratings stored. It has no per-player activity view. The underlying limited account-linked records needed for access, ratings, deletion and a justified case still exist as described here; a totals-only page does not make those records anonymous. **Connections and match memory.** A newer connection normally replaces the older account connection, but a playing tab is not displaced by a second tab. The second tab cannot queue, create, join, watch or rematch while that match is active. A closed connection or 8 seconds of silence triggers a 30-second grace period. The game attempts automatic reconnection; reloading within about 25 seconds is intended to rejoin while time remains, subject to network conditions. At grace expiry, a ranked dropout forfeits with a loss/rating change; in an unranked invite or lobby match the AI takes over for the rest of the match. **Lobby and room snapshot.** The service keeps current room metadata in memory and in Cloudflare Durable Object storage so a room can survive the server object sleeping and waking. This includes its code, settings, seats, internal account references, assigned handles, faction/doctrine choices and ready state; it does not include the live move or ping record. The snapshot is rewritten on changes rather than kept as a history. Before a match starts, leaving removes the player’s seat, handle and choices; if the host leaves, the lobby closes for everyone. After it starts, AI takes over a departing seat and its existing handle can remain attached for the continuing match. Necessary room metadata can remain at the result screen until participants leave or the room closes; it is not a retained match archive. When no player is seated and no reconnection grace remains, the room is removed and the changed snapshot no longer contains it. Leaving Lattice or account erasure also removes the player’s account/handle references from any remaining room. Provider-managed residual storage follows the limits explained above. **Live commands and pings.** For live play, spectator catch-up and reconnection, the initial state and commands are kept in bounded memory only, subject to a record-size/entry cap of about 8 MB and a short recent-command tail. This is a capacity limit, not a fixed match duration. The full command record is dropped when the cap is reached, leaving the bounded resume tail. The live input record is cleared at a result or when the live session ends, and is lost if the server object restarts. In a larger lobby match, one player leaving or exhausting their reconnect grace does not clear the record while others continue playing: earlier pings remain with that ongoing record. When the last participant and reconnect grace are gone, it is discarded. These commands and pings are never written to the Durable Object snapshot or a persistent move log, and online matches are not saved as replays. Remaining clients may still hold their current game state. Leaving/deletion also removes or invalidates pending account references so a delayed result cannot recreate an erased record. **Local game records.** Preferences, setup, last snapshot and progression use browser storage, including `lattice15.prefs`, `lattice15.setup`, `lattice15.profile`, `lattice15.snapshot`, `lattice15.replays` and `lattice15.rejoin`, or clearly identified successors. In v17, local IndexedDB storage keeps up to eight of the newest solo, non-online replays; the fallback localStorage list keeps up to six. Earlier-version records can remain on the device but be hidden when their rules version is incompatible. Online matches are not saved as replays. The local profile holds progress and a generated client reference; it is not a public social profile. During an online match the rejoin note holds the server address, room code, seat and time. The game removes it when it observes the match ending or you leave; an expired note is discarded when you next open the game. Closing a browser does not remotely clear its storage. Local records otherwise remain until replaced, cleared, deleted or evicted by the browser. They are not a cloud backup. Hiding mission/mastery prompts leaves local progress in place. No attendance penalty, lost streak or mastery decay is applied for taking a break. V17’s campaign saves, autosaves, Saga progress, completed lessons and colour-blind setting also stay on the device. Share images and replay clips are generated locally and sent to the device’s share sheet or downloaded only when you choose; Lattice does not upload them. A service you choose for sharing handles the copy under its own terms. The local benchmark’s frame-rate and GPU result is displayed on your device and copied to the clipboard only if you choose Copy; it is not sent to Energen. **Protected launcher.** We use security checks to protect account access and release-key delivery. Where Firebase App Check with reCAPTCHA Enterprise is used, Google assesses interaction risk before Firebase issues a security token. Energen’s backend verifies the token; it does not receive reCAPTCHA scores or interaction data, store the token, or use it for matchmaking, analytics or marketing. Browser token caching and the providers’ own processing follow Section 7. Google’s provider processing is described in Sections 4, 5 and 7. The Lattice access route in the EU/EEA and UK uses security checks without that behavioural assessment. Account sign-in, current Lattice entitlement/licence and server-side release-key and cryptographic checks still apply. This Lattice route does not change Taktikverse’s protection. Its Lattice service-worker cache (`lattice-play-v1`, or a clearly identified successor) can contain the launcher, configuration, signed manifests and encrypted delivery resources, keeping at most the two newest large release resources. Temporary retry state is in session storage. These delivery files are not cloud saves. The **Clear Lattice data on this device** control removes Lattice’s local records, launcher cache and retry state while preserving shared Energen sign-in and Taktikverse records. Provider/sign-in storage follows Section 7. Account or place deletion cannot clear a disconnected browser or exported file; clearing all shared website data can also remove Taktikverse information. ### How long Lattice records are kept | Record | Limit and deletion trigger | |---|---| | Live participant/viewer connection, account reference, handle, rating and room role | While the connection is active; necessary continuing match/room references end with their purpose and are covered by leaving/deletion and write invalidation | | Lobby/room metadata snapshot | While the lobby or continuing room is needed; overwritten on changes. A pre-start departure removes that player’s lobby entry; host departure closes a waiting lobby. A started room, including necessary result-screen metadata, is removed when no participant or reconnect grace remains. Leaving Lattice/account erasure removes the affected account/handle references even if others continue | | Live match state, commands, team pings and resume tail | Bounded memory as described above; discarded at result or live-session termination, including the last participant/grace ending; lost on server restart. A departure from a continuing larger match does not erase its earlier commands immediately. No persistent move/ping log | | Daily/challenge verification input | Starting state and own commands processed transiently, then discarded on completion, failure or timeout; only permitted result fields remain | | Account-linked handle, re-roll state, rating, games, wins, losses, draws and last played | No later than leaving Lattice, account deletion or 12 calendar months without an online match starting or an accepted Daily/challenge result being deliberately published for your account, whichever is earlier. These records may expire sooner, including after 365 days without a ranked result. Local solo activity is not reported to us and does not extend this maximum. Another game, board viewing, handle refresh or remaining in a lobby does not restart it | | Daily/challenge board entry and internal expiry fields | No later than 60 days after that entry’s own submission; earlier on leaving, account deletion or a valid erasure request. Other activity does not extend its life | | Challenge-world record | None: the code is self-contained. Board entries keyed by the code follow the separate board limit | | Lattice place, queue and operational acceptance fields | While needed for the requested place/application; removed through leaving/account deletion, apart from minimal historic agreement evidence | | Minimal Lattice licence-acceptance evidence | During the agreement and for three years after it ends under the limited evidence rules in Section 6; known-under-13 erasure overrides apply | | Active restriction marker | Only for the stated restriction’s duration, with necessity reviewed at least every 90 days; no preserved gameplay profile | | Temporary deletion fence | Only until stale credentials and in-flight or delayed work can no longer restore erased information. A fixed timeout does not justify dropping the fence while a restoration path remains | | Raw Lattice report, safety complaint or appeal material | Deleted by the earlier of 90 days after closure and 120 days from receipt, unless specific material is still necessary under a recorded, restricted active-case or legal hold reviewed at least every 90 days | | Minimal closed-case outcome/compliance record | Up to three years after closure; raw reports, replays, attachments and full correspondence do not automatically become this record | | Connection-country value | Used transiently for the availability decision; not retained in the account, online data stores or application logs | | Device records | As described above; the temporary rejoin note is cleared on an observed end/leave or after expiry when the game next opens, v17 solo replays are limited to up to eight current replays in IndexedDB (up to six in the fallback list), older incompatible-version records can remain hidden, and local records can be cleared separately | Expired entries are no longer served, including on an inactive board; scheduled cleanup does not depend on another submission. Deletion/revocation covers active connections, aliases, indices and delayed rating/result work. We do not confirm deletion merely because one store acknowledged it. Provider-managed residual storage and recovery processes are separate; we apply the relevant provider process and reapply deletions to a restoration we control. **Leaving versus deleting the account.** **Account → Lattice → Leave Lattice** stops Lattice access, removes its live handle/rating and board entries, and releases the place after safe cleanup. The Energen account and Taktikverse remain. Whole-account deletion also removes linked Lattice records. We follow the Section 6 account-deletion workflow and 30-day completion commitment, subject to any shorter applicable deadline. Contact privacy@energengames.com without sign-in if a control fails. Any specifically retained limited evidence follows the table and cannot be used to rebuild the deleted profile. ### Fair play, private reports and review Ranked Elo and local insights evaluate game performance. They are not advertising profiles or a basis for targeting engagement across games. Deliberate board publication is separate from ordinary play. **We do not impose a cheating ban solely through an automated decision.** A person reviews access removal, available evidence and relevant explanations and communicates the reason, scope and review route under the licence. Failed verification, a complaint or a disconnection alone does not prove cheating. A Lattice restriction is not automatically a Taktikverse or whole-account sanction. **Report this match** prepares an email with the fixed subject **Lattice report**, a selected reason and limited context such as build, random match reference, time and the handle concerned. You inspect and send it to **hello@energengames.com**; merely opening the draft sends nothing. No replay or device file is attached automatically. You can explain a concern privately, complain about our handling or request review by email without signing in, including while suspended. There is no new report database. For privacy/deletion, use privacy@energengames.com. Do not include passwords, tokens, identity documents or unrelated information. The sole beta operator acting for Synapse Tutor, LLC checks the mailbox at least twice a week and uses a filter to flag Lattice reports. Urgent concerns are acted on as soon as they come to attention; applicable prompt-action and legal deadlines still apply. This is not continuous emergency monitoring. The website provides a public complaint/appeal route without sign-in. Reports use the existing **Porkbun forwarding → consumer Gmail mailbox**, with outgoing replies prepared in Gmail and relayed through **Resend/SES**, as explained in Sections 4–6. This is separate from Taktikverse’s in-game file upload to Workers KV. Case material follows the specific limits above; relay and provider residual schedules remain separate. Access is restricted to the operator and necessary providers. Complainants’ identities and case material are not published to players. ### Public pages and this update The public **/games/lattice** page and eligible news posts use only the existing public-page statistics rules in Sections 4 and 7. Lattice join/account/play routes, room/watch/challenge links, game and online server are excluded. Existing player-browser protections, regional Off rules and objection controls continue. There is no Lattice analytics SDK and no new IP-based audience reconstruction. The 4 November notice added Lattice’s separate processing. This **11 November 2026** revision explains v17’s private lobbies, fixed team pings, their visibility and storage, and the updated local records. These are used to provide the game features you choose, not a new advertising or player-profiling purpose. We publish this explanation before those features go live and show a short update with a link at online entry. The Lattice licence **beta-2026-11-04-r1**, Taktikverse licence **beta-2026-10-20-r1** and actual acceptance histories remain unchanged; this notice update requires no new agreement checkbox. Taktikverse’s gameplay processing and cloud-save choices are unchanged. Any later change to an existing purpose is explained before it begins and obtains separate permission where law requires it.