DRAFT / privacy-notice-draft-2
Privacy information
Pre-launch website, with separately gated isolated test features
Who is responsible
Squaddies is the trading name used for this prototype. The legal data controller, verified privacy contact and geographic address are not yet confirmed. A final controller notice and usable rights-request channel are required before live personal-data collection is approved. This page is pre-launch information, not a claim of legal approval.
Current law, amendments and commencement have not been verified from official sources in this environment because access is blocked. Lawful bases, retention, recipients, international transfers and regulatory status require review. No claim that all data stays in the UK, that no third parties are involved, or that registration or compliance is complete is made.
What this preview uses
Demo newsletter, checkout and contact field values remain in page memory; the forms do not submit those values to an external service. Use fictional details. Reloading or navigating away normally clears page state; browser autofill and recovery may behave independently. The contact preview creates no email or support ticket.
The demo basket and completed-order preview use this tab’s sessionStorage keys sqd-basket and sqd-order for selected product identifiers, quantity, size and colour, not entered contact or address details. They are not durable purchase records. The application can also set session and CSRF cookies when serving public pages. Hosting and infrastructure logs may contain request information; their real deployment configuration is not verified.
Required information, optional choices and withholding
In the default preview, use fictional values only. Required form markers demonstrate validation; no real support or purchase request is created. A name, email and message are used only to show the local contact preview; withholding them prevents that preview from completing. No optional marketing choice is implied by completing a preview.
Separately gated isolated test newsletter signup needs an email and an affirmative request for optional updates. Withholding them means no signup request. Marketing permission is optional and separate from a purchase, terms acceptance, service messages or digital early-supply choices.
The isolated guest checkout needs a contact email and name to identify the requested purchase and service communications. A physical order additionally needs necessary delivery-address fields; address line 2 and region are optional where the supported destination permits. Digital-only orders do not need a shipping address. Withholding necessary information prevents the requested test checkout, rather than signing the person up to marketing.
Future approved support or rights handling should request only contact, scope and proportionate identity or representative evidence needed for the specific request. A cancellation reason is not universally required. Missing assurance may require review before disclosure, not automatic rejection or resetting the original receipt date. These future purposes and field choices require final controller, lawful-basis and privacy review; this draft does not announce production collection.
Separately gated features
Isolated test features can store subscriber email, consent and withdrawal events, confirmation-token hashes and status; checkout names, contact/address and item snapshots; payment, refund and reconciliation references; digital entitlements, token hashes, recovery events and download access evidence; email outbox, delivery attempts and feedback; and fulfilment address, supplier-submission and tracking evidence. These systems remain separately gated and are not evidence that live sales or messaging are active.
Administration includes staff account, role, authentication, MFA and audit data. Test email capture can include message bodies and signed links and is private evidence. Raw card number and CVV collection is not implemented by Squaddies checkout; the proposed hosted payment provider and any actual processing require separate approval. No live provider or production processing is authorised by this notice.
Marketing and service messages
A newsletter request is separate from a purchase and from transactional messages. The isolated newsletter flow records standalone consent wording and verification, and supports withdrawal and suppression. Double opt-in is the chosen technical confirmation flow, not a claim that every instance is a universal statutory requirement.
Where enabled, use the offered unsubscribe mechanism to withdraw marketing permission. A transactional message must remain restricted to its service purpose; it must not become marketing merely because an address or order exists. Production sender identity, lawful basis and privacy wording remain unapproved.
Purposes, safeguards and retention
Proposed purposes include a requested service or contract, separately consented marketing, security and abuse prevention, and applicable legal obligations. These are review inputs: each actual processing purpose needs a confirmed lawful basis, necessity, minimisation and, where relevant, an interests assessment. Do not provide medical or other sensitive information through this preview.
Access controls, hashing of bearer tokens, restricted administration and append-only evidence are technical controls, not a guarantee of absolute security. Local HTTP preview is not HTTPS production. Encryption at rest is not universal. Retention needs approved purposes, triggers, review dates, access and legal-hold rules for source records, logs, message bodies, backups and suppression data; expiry of an access token is not deletion of the underlying record.
Rights and complaints
Depending on applicable law and circumstances, rights may include access, rectification, erasure, restriction, portability, objection and withdrawal of consent. Rights are not all unconditional. A real request process must verify identity proportionately, establish scope, track the applicable deadline and any permitted extension or refusal, and communicate an outcome. Current rules and deadlines require verification.
The preview contact form is not a monitored rights-request or complaints channel. A verified channel and escalation owner are outstanding launch requirements. The UK Information Commissioner’s Office is the relevant public authority for UK data-protection concerns; see ico.org.uk for its current information. A request must not bypass immutable-record controls or delete audit history ad hoc. Controlled correction, redaction, legal holds and deletion design require separate approval.