Privacy Notice

Who is responsible

Marko Bajlo, a natural person, operates AI Ascendancy and determines the purposes and means of processing personal data. Contact: info@aiascendancy.com. This mailbox is regularly monitored. This notice covers website visitors, existing internal and expressly authorised testing accounts, and people who write to us. Public registration is closed; a public Demo is not available.

Public website visits

The server processes your IP address and technical request information to deliver pages and protect the website. Technical and diagnostic records can include request times, requested paths, browser information and errors. The public application has no analytics or advertising integration. A visit does not require an account.

Existing accounts and saved play

Account data include your name or account name, email address, password hash, email-verification status, language and number-format preferences, and account timestamps. Authentication processes session and security information, including IP address and browser information where recorded by the session system, remember-me information and reset tokens. Optional two-factor authentication uses a security secret and recovery codes; optional passkeys store identifiers, public credential information, names and last-use information.

Saved Runs, Plans, Operations, Cycle results, gameplay history and Recognition are linked to your account so that you can continue play and review outcomes. Account and authentication details are required for existing account access; game access requires verified email. Additional messages, two-factor authentication and passkeys are optional.

Purposes and legal bases

Public page delivery and proportionate abuse prevention use technical request data for the legitimate interests of operating and protecting this website (GDPR Article 6(1)(f)).

For existing private/internal accounts, the proposed basis under assessment is Article 6(1)(f), separately for: restricted account access and account protection using identity, authentication and security data; restoring your own saved play using account-linked Runs and history; and diagnosing faults during authorised private testing using the relevant account, game and diagnostic records. These purposes do not authorise unrelated profiling or advertising. Necessity, reasonable expectations and the balance with each participant's rights still require confirmation before this assessment can be treated as final or extended to further testers. No testing contract or consent is inferred from having an account.

Answering an ordinary enquiry you initiate uses your address and correspondence for the legitimate interest of responding to that enquiry (Article 6(1)(f)). Handling a personal-data rights request, including proportionate identity checks where needed, follows GDPR Articles 12–22 and the legal-obligation basis in Article 6(1)(c). A separate fixed period for retaining evidence after a request closes has not been adopted.

Reading this notice is not consent. Gameplay automatically resolves Operations and Containment responses; those game outcomes are not decisions about a person with legal or similarly significant effects.

Messages and application email

If you contact us, we process your sender address, message, any attachments you choose to send and our reply. The contact mailbox uses Proton Mail.

External transactional email delivery is not currently configured. New password-reset email requests and verification resends are temporarily rejected before generating new security messages or reset tokens. Email-address changes are also temporarily unavailable. Existing login, valid sessions, two-factor authentication, passkeys, authenticated password changes and valid previously issued links remain subject to their usual safeguards.

The application refuses production delivery through the log mail transport. This prevents new message bodies being written by that transport; it does not erase historical messages or links that may already exist in logs or backups. For access difficulties, contact info@aiascendancy.com without sending passwords, recovery codes or security links. Contact does not bypass identity checks or guarantee recovery.

Hosting and other service providers

Hetzner Online GmbH hosts the server in Nuremberg, Germany, under a data processing agreement accepted on 18 October 2026. The agreement provides for EU processing and EU technical/customer support for this hosting location. Hetzner disk Backups are enabled.

Proton Mail provides the contact mailbox; Proton AG is based in Switzerland. Switzerland is outside the EEA and benefits from a European Commission adequacy decision for personal-data transfers. This does not mean that every provider or processing operation is confined to the EEA. Forge is used for server administration and publishing application updates and can provide administrative access to application logs. Porkbun is the domain registrar, and GitHub hosts the private source repository; those roles alone do not establish that either receives saved gameplay. You can ask us about recipients and applicable transfer safeguards at info@aiascendancy.com.

Current retention and deletion

The current application keeps internal accounts and saved Runs until account deletion; it has no automatic inactivity-deletion schedule. Abandon Run ends a Run while retaining its history. It is not a request to erase personal data.

Account deletion removes the user record and linked game and passkey records covered by database cascades, and invalidates the current session. It does not guarantee immediate removal of other session records, reset-token records, correspondence, logs, backups or browser storage. You can request erasure by email even without access to your account.

The source defaults provide 120-minute idle session expiry and 60-minute password-reset validity. Expiry prevents use but does not by itself erase stored records; session cleanup is probabilistic and no scheduled reset-token cleanup is implemented. The production application uses a single log file without application-managed time-based rotation. A fixed operational maximum for server logs has not been verified.

Backup copies can retain data after removal from the live application. Their actual coverage and expiry have not yet been verified, so no fixed backup-erasure deadline is promised. Correspondence is retained in the contact mailbox; operation of a fixed deletion schedule has not been verified. The approved targets below are not implemented deletion controls.

Approved targets and remaining decisions

The approved operational targets are: ordinary application/access logs, 14 days; security logs, 30 days; cleanup of expired session and reset-token records within 24 hours of expiry; review of the continuing need for internal accounts every 90 days; and ordinary correspondence, six months after closure, subject to justified exceptions.

These are policy targets only. Their operational enforcement has not been implemented or verified as part of this release, and they are not a promise that every existing copy is already deleted within those periods. Deletion of accounts and Runs within 30 days after testing ends remains provisional. A proposed 12-month period for rights-request evidence still needs legal and operational justification. Backup retention remains subject to verification of the actual provider lifecycle.

Cookies and browser storage

Anonymous reads of the public marketing and legal pages do not create a session, set a language cookie, write application LocalStorage or SessionStorage, or register a service worker. The URL determines English or Croatian. The public pages do not use encrypted application history storage.

Once the updated service worker controls the page, it bypasses its cache for public pages and their resources. An older active worker may continue its previous caching until it is replaced. Previously stored cookies, caches and other browser data are not automatically deleted. Ordinary browser caching and visited-URL history can still exist.

Sign-in and protected pages use session and security cookies. Remember-me and authentication-page language selection can add storage. Protected game pages can store sidebar, map, legend and introductory-help preferences, encrypted navigation history and cached static resources. Public browsing does not renew those account cookies.

Your rights

You may ask for access, correction, erasure or restriction where the GDPR provides those rights. You may object to processing based on legitimate interests for reasons relating to your situation. Portability applies where its legal conditions are met, including automated processing based on consent or contract. If processing relies on consent, you may withdraw that consent without affecting earlier lawful processing.

Send requests to info@aiascendancy.com. Where there are reasonable doubts about identity, proportionate additional information may be needed. We must respond without undue delay, normally within one month; any lawful extension must be explained within that period. You may complain to the Croatian Personal Data Protection Agency (AZOP) or another competent supervisory authority.

Changes to this notice

This text describes the current development stage. A change of operator, transactional email service or public availability will require this information to be reviewed and updated.