STILL ALIVE: IDLE
Privacy Policy
Who operates the game
Still Alive: Idle is developed and operated by Alistair Kerr, trading as The Crooked Corbie, a sole trader based in Scotland. Alistair Kerr is the controller of the personal information used to operate the game and its administration services.
Privacy and support contact: support@stillaliveidle.com. Business address: Sawmill Cottage, Philiphaugh, Selkirk, TD7 5LU.
Information we use
We use account identifiers, email addresses, authentication provider information and verification status to identify your account. Supabase provides authentication; we do not store your plaintext password in the game's save database. Google sign-in is not currently offered in the reviewed configuration.
We store your survivor roster, progress, settings, recent save history and technical records that help saves work reliably and prevent duplicate requests. These describe game activity and fictional survivors. Guest play can also use an anonymous authentication identity and device storage.
For purchases, we record checkout intentions, the receiving account, product and provider references, transaction status and amounts, adjustment/refund evidence and ownership entitlements. Complimentary ownership records include the recipient, administrator, reason, operation identity and audit history. Paddle handles payment information through its checkout; our game does not collect raw card details.
Testing applications include the information you submit, such as contact details, availability and testing interests. Access records include approval/status and access activity. Bug reports may contain descriptions, technical diagnostics and optional screenshots. Please avoid including passwords, payment details or unnecessary personal information. The operator is currently the only person who signs in to Studio and can review relevant account, save, testing, support and ownership information.
Deletion requests and their processing records support account-removal review. Security and error logs can contain technical request information and information included in error messages. The public marketing website has no application contact form in the audited source; external community links take you to independently operated services.
If you email support@stillaliveidle.com, Google Workspace delivers your sender address, message, attachments and correspondence directly to our support mailbox. The Owner confirms that no support emails were received through the former Cloudflare-to-Outlook forwarding route. This confirmation is not an independent mailbox audit or confirmation that every former forwarding rule has been removed. Please send only the information necessary for your enquiry.
Why we use it
We distinguish the following purposes and legal bases:
| Purpose | Basis |
|---|---|
| Account access, cloud saves and delivery of the game/licence | Performance of our contract with you, or requested steps before it |
| Security, abuse prevention, save integrity and proportionate diagnostics | Legitimate interests in protecting users and the service |
| Testing applications and administration | Legitimate interests in selecting and managing testers; requested pre-contract steps where applicable |
| Support and ownership administration | Contract where needed to deliver your rights; legitimate interests in resolving issues and preventing duplicate or fraudulent actions |
| Required business, tax and legal records | Applicable legal obligations |
| Optional storage or tracking that requires permission | Consent, obtained before that technology is used |
Accepting this notice is not consent to every use of personal information. Each use must be necessary for its stated purpose.
Optional game analytics are disabled in the configuration reviewed for this notice. Error reporting, security logs and support diagnostics are separate. A game interface crash can send an error message, stack trace and page path for diagnosis; these are not a full save export, but error text can contain contextual information.
Providers and transfers
| Provider | How it supports the service |
|---|---|
| Supabase | Account authentication and relevant testing, support and deletion records. |
| Cloudflare | Public website, Game and Studio hosting, databases, assets, connection delivery and security. Restricted administration and review previews also use Access authentication. |
| Google Workspace | Current support and privacy correspondence, delivered directly to the support mailbox. |
| Microsoft Outlook.com | A former forwarding route was configured, but the Owner confirms no support emails were received through it. This does not establish that no technical metadata existed or that the former route has been removed. Current support uses Google Workspace. |
| OpenAI Sites | Former public website hosting and historical visitor/security processing. The former deployment is retained for recovery; it no longer serves the public website domains. Historical provider records or browser cookies may remain subject to their own retention. |
| Resend | Transactional authentication email delivery. |
| Paddle | Sandbox checkout testing and the intended paid offering. Production purchases remain disabled. Paddle acts as Merchant of Record and an independent controller for its payment activities. |
The operator currently has sole Studio access and accesses relevant information for administration and support. External community links open independently operated services. Providers may also process information for their own account, security or legal purposes under their own privacy notices.
Information may be processed outside the UK. Our account-authentication project is in London; previously inspected Cloudflare database and asset placement was in Western Europe, which is not a UK-only processing guarantee. Cloudflare operates an international network. Resend reports US storage despite the authentication-email sending domain using its Ireland region. Google, Microsoft and the former website provider may also process information in other countries. An overseas server location alone does not tell you which legal transfer rules apply: the receiving organisation and the arrangement also matter.
For covered processing, Cloudflare's and Resend's service agreements incorporate data-processing terms, and Supabase's data-processing addendum forms part of its service agreement. These terms provide for European Commission Standard Contractual Clauses with the UK Addendum for relevant transfers. These are contractual protections for personal information sent to recipients outside the UK; they are not a promise that all information stays in the UK or a guarantee that every international-transfer obligation has been resolved.
Google Workspace processes current support correspondence under its Cloud Data Processing Addendum. The Owner verified acceptance of that addendum and certification of EU/UK data-protection-law applicability on 14 October 2026. Google's transfer terms provide for recognised adequacy arrangements or contractual safeguards, depending on the destination and recipient. Google states that it uses the UK Extension to the EU-US Data Privacy Framework for covered transfers to and onwards from the US. These confirmations do not establish UK-only processing, a particular storage location or that every international-transfer obligation has been resolved.
Paddle acts as an independent controller for its payment activities. Its privacy notice explains its international transfers and the safeguards it uses, and how to request copies from privacy@paddle.com. Sandbox checkout testing is implemented; Production purchases remain disabled. We do not treat Paddle's own processing as processing under our instructions or claim that live payment consent has been verified.
The former Outlook forwarding configuration is not evidence that support messages were processed or transferred. On the Owner's confirmation, no support correspondence was received through that route, so we do not describe a historical Outlook support-message dataset or an international transfer of those messages as established. This does not establish that no configuration or security metadata existed.
You can request information about international processing and a copy of the transfer safeguards applicable to your personal information by emailing support@stillaliveidle.com.
Storage, retention and deletion
Game browser storage supports authentication, preferences, Device progress and interrupted-operation recovery. Choosing to remember sign-in determines whether the session is held in Local Storage or limited to Session Storage. Clearing storage does not itself delete Cloud records and may affect your Device copy. Studio uses a protected administration-session cookie. Optional game analytics are disabled in the reviewed configuration; error and security processing are separate. Optional storage controls prepared locally are not claimed to be live.
The public website is hosted on Cloudflare. In first-visit checks of the current public configuration, no website cookies or Local Storage, Session Storage or IndexedDB entries were observed. The reviewed application does not load optional analytics or advertising trackers. Cloudflare can process connection and security information and may use necessary security cookies when its protection requires them; a cookie-free check is not a guarantee that every future security response sets no cookie. Restricted review previews use separate Access authentication cookies and are not the public website. Historical cookies from the former Sites website may remain in a returning browser until they expire or are removed. Paddle checkout can use its own payment and security technologies when opened in the Game; it is not embedded in this marketing website.
Optional technology requiring consent must remain off until appropriate controls are in place. No optional authentication-email open or click tracking has been authorised. Normal delivery, bounce and failure diagnostics are distinct from engagement tracking.
Recent save history keeps up to ten distinct archived revisions per account and survivor. Older entries can be removed after a save, and maintenance may be delayed if it fails. This is not a permanent archive or a promise of a set number of recoverable days. Save diagnostics have count limits; minimal records used to reconcile retries currently have no routine expiry.
We keep account, survivor and ownership information to support ongoing access. There is no general automatic expiry of accounts or Public saves for inactivity. Financial information is retained where law requires it. Ownership audit records and minimal retry records currently have no routine expiry; this does not mean every field must legally be retained forever.
Our retention targets are set out below. Some are prospective targets; automatic cleanup does not currently enforce every period.
| Category | Approved target and limitations |
|---|---|
| Accounts and current saves | Keep while supporting ongoing access; no automatic Public progress deletion solely for inactivity. Review verified rights requests individually. |
| Tester applications | Declined or withdrawn applications: six months after closure unless a documented dispute hold applies. Review waiting-list applications after 12 months without engagement and ask whether interest continues before removal. Active admission authority remains separate. |
| Support and reports | Personal screenshots/attachments: 90 days after case closure unless needed for an unresolved issue. Correspondence and personal report details: 12 months after closure. Retain useful issue knowledge separately without identifying details. |
| Security/error logs | Routine logs under our retention control: only as needed, with a maximum 30-day target. Provider-managed datasets have separate periods described below. Investigated incidents: up to 90 days; longer only under a documented, reviewed legal/dispute hold. |
| Save diagnostics and receipts | Preserve existing count caps. Routine server diagnostics: 30-day target. Minimal receipts remain for retry and duplicate prevention; no safe time-expiry contract has been established. |
| Ownership and financial records | Minimal licence provenance while honouring ownership. Self-employed business tax records are normally kept for at least five years after the relevant tax year's 31 January submission deadline; special rules, including very late returns, may apply. Other legal obligations and justified holds are assessed separately. This is not a retention period for all gameplay or support data. |
| Recovery exports | Manual exports: 30 days after incident/change closure unless a documented hold applies; register purpose/expiry and restrict access. Provider backups follow verified product windows. |
The operator is responsible for the planned monthly review of support records. This commitment does not mean historical records have already been reviewed or deleted.
Contact support@stillaliveidle.com to request account deletion or exercise your privacy rights. Automatic account deletion is not available in the Public game. Purchases, ownership and administration evidence can require individual review and justified retention. A technical restriction does not remove your legal rights. We assess deletion, restriction and minimisation individually, explain any necessary retention and respond under applicable law. Immediate removal from every provider or recovery copy is not promised.
Backups and restricted recovery copies may retain information after removal from live systems. Valid deletion decisions must be carried through any recovery; a restored backup must not reinstate deleted accounts for ordinary use. The inspected Cloudflare databases have up to 30 days of recovery history, limited by their creation dates. Our inspected Free Supabase project has no customer scheduled backups or point-in-time recovery enabled; provider-internal copies may still exist. Uploaded Studio files have no automatic expiry in the inspected storage; the seven-day rule for abandoned unfinished uploads does not delete completed files.
Your rights and complaints
Depending on the circumstances, you can request access, correction, erasure, restriction or portability, object to legitimate-interest processing, and withdraw consent without affecting earlier lawful processing. We may need proportionate identity checks. We respond to rights requests without undue delay, generally within one month, subject to the timing rules and extensions permitted by law. We will explain any applicable extension or justified limit.
Contact support@stillaliveidle.com to complain about our handling of personal information. We will acknowledge a data-protection complaint within 30 days. We begin investigating on receipt and explain the outcome; the acknowledgement period is not a waiting period before investigation. You can also complain to the Information Commissioner's Office: https://ico.org.uk/make-a-complaint/.
Children, security and changes
Our intended minimum age for account creation and purchase is 16. This is an eligibility policy, not an official PEGI classification or a claim that age verification already exists. People aged 16 and 17 are still children for the UK Children's Code. If you believe an account is being used by someone below our eligibility age, contact support@stillaliveidle.com so we can review it proportionately. We will not require everyone to supply identity documents by default.
New permanent registrations will require a 16+ self-declaration when enforcement launches. This is self-report, not independently verified age, and does not require birthdates or identity documents. Existing accounts retain access, progress and ownership. Historical anonymous accounts created before the policy takes effect may convert their existing identity to a permanent account under the approved exception. Future anonymous creation will be restricted at launch; the exception is not a bypass for new accounts.
We use authentication, restricted administration and server-side controls to protect information. No internet service can promise absolute security. We will date material changes to this notice and communicate changes appropriately; a new notice does not retrospectively authorise incompatible uses.
Support copies and provider retention
Current support is delivered directly through Google Workspace, as confirmed by the Owner. We have not assumed particular Workspace device-sync, backup, retention or deletion settings. Our support-retention targets apply to support information actually received. The former forwarding setup does not establish that historical Outlook support messages, attachments or synced support copies exist.
Operational request logs
The game uses Cloudflare request logs separately from optional game analytics. Previously reviewed documentation specifies seven days of Workers Logs retention for the reviewed paid plan. This differs from recovery history, other provider logs, exported logs and separately retained incident evidence; it is not a promise that every copy disappears after seven days. Application request logging is disabled for the reviewed public marketing Worker; Cloudflare security and network processing are separate.
IP addresses and provider logs
Hosting and authentication providers process technical information, including IP addresses, to deliver connections, authenticate accounts and protect the service. Depending on permissions, relevant logs may be available to the operator through restricted provider administration. Retention varies by product and does not cover only the information displayed in Studio.
Current support-mailbox arrangement
Google Workspace is the current support provider. The Owner confirmed its CDPA acceptance and EU/UK applicability certification on 14 October 2026. This does not establish the removal of all former forwarding rules or particular storage and retention settings.
Provider security and authentication log periods
Cloudflare currently documents 31 days of Security Events history, separately from the seven-day Workers Logs period. Security Analytics history depends on the domain plan. Supabase describes a one-day accessible log window for its Free plan. Optional writing of authentication audit events to our project database is currently disabled. This does not establish deletion of any historical audit-table records or every provider copy. Those copies and any restricted incident records must be considered separately when handling a request.