BREACH:EVACUATIONBack to the website

BREACH:EVACUATION

Privacy

Information about the BREACH:EVACUATION website.

Who is responsible and what this covers

The website is presented by the BREACH:EVACUATION team. Contact: support@breachevacuation.com. This notice covers this presentation website, its previews, learning exercises and optional email support. The browser game, online player market and native apps are separate services; this notice does not describe them as offline or free of telemetry.

Visiting the website

Your browser sends technical request information, including IP address, browser information, page address and time, to the hosting and network providers to deliver and protect the site. The GPT Sites edition also uses the platform’s access and session services. Our website code does not add advertising trackers or visitor analytics SDKs. This does not mean that hosting providers keep no service or security logs.

Settings on your device

The site stores your requested reduced-motion preference in local browser storage (breach-reduce-motion). The language is selected in the page address; the game-launch page may store the chosen language (breach-language-v1) on the game domain. These settings do not contain a name or email address. You can change motion in the section menu and language in the header. Settings remain until changed or removed through your browser. Clearing all data for the game domain may also erase game progress.

Videos and external links

Tutorial videos and previews are loaded from this site. YouTube and TikTok links open those services only when selected; their policies then apply. Starting the game can pass the chosen language and limited campaign labels from the link, such as utm_source. Do not put personal information in campaign labels. The market, game and external author links have their own data flows.

Email support and retention

Email support is optional. We receive the address, message and attachments you choose to send, to answer and investigate your request. Support mail is not used for marketing. Closed support correspondence is automatically deleted after 90 days; backup versions expire within 30 days, so removal from backups may take up to a further 30 days. Specific records may be retained for a legal obligation or dispute, with the reason explained when applicable. Deleting local browser data does not delete your support email.

Service providers and international processing

Hosting, email delivery and support providers process the information needed for their services. The documented support setup uses Mailcow hosted by Hetzner in Germany, Outlook on the operator’s Mac and private backups in Ukraine. Provider processing, including Microsoft cloud services where enabled, can occur outside your country. Contact us for current recipients and applicable transfer safeguards; we do not claim that every copy remains in the EU.

Purposes and your rights

Where applicable, delivery and security of the site and answering support requests rely on legitimate interests; a requested contractual service or a specific legal obligation may provide another basis. You may request access, correction, deletion, restriction or portability where applicable, and object to processing based on legitimate interests. Contact support@breachevacuation.com. Where processing relies on consent, you may withdraw it. You may also complain to the competent data protection authority. Applicable law sets response deadlines, normally one month under the GDPR.

Share only what is needed

Do not email passwords, payment-card details or identity documents. Remove unrelated personal information from screenshots. If information about a child was sent unintentionally, contact us to review and remove it where appropriate. We update this notice when relevant practices change and show the revision date above.

Open the guideAuthors and licencesContact the team · support@breachevacuation.com

Website log retention — 18 November 2026

This supplement applies to origin-server request and error logs for breachevacuation.com and www.breachevacuation.com. It does not set retention periods for the separate game, support email or third-party providers.

From this revision, site requests are written to dedicated origin logs. Access logs retain the current daily file and up to 13 daily archives (approximately 14 days); technical error logs retain the current file and up to 29 daily archives (approximately 30 days). Daily scheduled rotation removes the oldest archives. A missed scheduler run can delay deletion and must be investigated. This is a configured schedule, not a guarantee of deletion from every copy at an exact hour.

Records isolated for a documented security incident, legal claim or binding legal obligation are limited to what is necessary and reviewed separately. Older shared logs remain subject to their existing rotation and have not been force-deleted. Hosting snapshots or backups can contain earlier records until those copies expire; this supplement does not promise a 14/30-day expiry for backup copies. Cloudflare or other delivery/security providers process their own request records under the applicable service arrangements; their records are not governed by the origin-log schedule above. Contact support@breachevacuation.com for questions or requests.