1. Scope and publisher identity
This policy explains the personal-data handling visible in the supplied code for scoutshelfstorypuls.mom. It distinguishes what the static website does from processing that may occur through a hosting provider or an email service. It is not confirmation that any particular hosting or mailbox configuration has been audited.
The supplied publisher identity is Scoutshelf Storypuls Publishing Ltd, company number SC839214, with an illustrative registered office at 18 Rose Street, Edinburgh, EH2 2PR, United Kingdom. These details and the domain-matched mailboxes were generated for this publication template. They are not independently verified registrations or confirmation of an operational inbox. Before commercial launch, the actual operator must confirm its identity as data controller, configure contact channels and update this policy to reflect its services and practices.
The designated privacy contact in this template is [email protected]. Labelling this address for privacy lead or DPO enquiries does not confirm that a statutory Data Protection Officer has been appointed. Further publisher information is on the Contact page.
2. Reading the guides
No account, payment details or profile are needed to read this website. The supplied pages contain no analytics libraries, advertising pixels, session-replay tools or embedded third-party maps. Fonts use your device’s available typefaces, and the illustrations are included directly in the pages.
When a website is hosted, its server or delivery provider necessarily receives technical connection information, such as an IP address and the requested resource. Depending on configuration, access or security logs may also include request times, browser information, referring pages and response codes. The files supplied here do not establish which of these details a host retains, for how long, or in which country. Those deployment details must be checked and documented by the operator; an absence of analytics scripts is not a guarantee that server logs do not exist.
3. Your browser preference record
After you make a privacy choice, the website attempts to store one first-party localStorage record named ssp-consent. It contains the choice, policy version, category flags and a timestamp. Analytics and functional flags remain false for every available choice because this build has no optional services.
This record stays in the browser’s storage for the site origin. The supplied script does not send it to a server, attach a visitor identifier or use it to track activity across websites. It treats the record as valid for 180 days and removes an expired or invalid record when next checked. LocalStorage does not automatically expire while the site is closed.
You can reopen the choices using “Cookie preferences” in the footer or delete the site’s data through your browser. If storage is blocked, the pages remain readable, although the banner may return after navigation. The Cookie policy provides the inventory and removal instructions.
4. The contact form does not send a message
With JavaScript enabled, the Contact page validates your name, email address, subject and message within your browser. It then creates a mailto: link containing an email draft. Preparing the draft does not submit your details to a website endpoint, save them in the site’s localStorage or send an email to the publisher.
Opening the draft passes its contents to your chosen email application or registered mail handler. That service may save or synchronise drafts under its own settings. You must review the message and send it there before it becomes correspondence. If JavaScript is disabled, the form uses browser-dependent email-form handling instead; writing directly from your email application is an alternative.
Your browser may independently remember or restore form entries, and your email service may keep a draft even if you leave this website. On a shared device, clear the form, close the page and check any draft created in the email application. Please avoid including passwords, payment-card details, identification documents or unnecessary sensitive personal information.
5. Correspondence and purposes
If you send a message to a configured publisher mailbox, the recipient and its email provider may receive your sender address, name, message, attachments and email metadata. These details would be needed to consider corrections, answer questions, handle accessibility feedback or respond to privacy requests. Sending a correction does not sign you up to a mailing list; this build contains no newsletter subscription or marketing automation.
For an operational UK publication, handling ordinary editorial enquiries and maintaining website security would generally need an assessed lawful basis, such as legitimate interests in managing correspondence and protecting the service. Processing needed to comply with a legal obligation, including applicable data-rights duties, may rely on that obligation. Any future processing based on consent must identify its purpose and allow withdrawal. The actual operator must confirm the applicable bases before processing rather than treat this template as a completed assessment.
A factual correction may inform a published update, but private contact details and full correspondence should not be published merely because a reader supplied them. Credit or publication of identifiable contributions should be agreed separately where appropriate.
6. Providers, transfers and retention
The supplied application code does not sell personal information or send it to advertising or analytics providers. Hosting, security and email providers may nevertheless process information as part of delivering their services. No specific provider, processing location or international-transfer arrangement is established by these files. Before launch, the operator must identify its providers, assess their terms and document any required safeguards for transfers outside the applicable jurisdiction.
The only retention period enforced by the site’s own script is the 180-day validity of the browser preference record. There is no server-side contact database in this build. Retention of sent correspondence, provider logs and backups depends on services that have not been specified here; no verified deletion schedule can therefore be stated for them.
An operational retention schedule should limit correspondence to the period needed to resolve the enquiry and any justified follow-up, and limit technical logs to a documented security or service purpose. Legal obligations or disputes may require particular records to be kept longer. The operator must publish its actual periods or meaningful criteria and apply appropriate access and security controls before launch.
7. Your rights and complaints
Where UK GDPR or other applicable data-protection law applies, you may have rights to access your personal information, correct inaccuracies, request erasure, restrict processing, object to certain processing and receive portable data in qualifying circumstances. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. These rights have conditions and exceptions; they do not all apply to every record.
Use the privacy contact above to describe a request, once the operator has verified and activated that channel. Include only enough information to identify the relevant correspondence. Proportionate identity checks may be necessary, but do not send identity documents unsolicited. Under UK GDPR, requests are generally answered without undue delay and within one month, subject to lawful extensions and other applicable rules.
You may complain to the UK Information Commissioner’s Office where appropriate, or to the supervisory authority in your jurisdiction. You do not have to use this website’s contact process before exercising a right to complain. The supplied code performs no profiling or automated decision-making with legal or similarly significant effects.
8. External services, children and updates
Following an organiser or transport link takes you to a separately operated website with its own privacy practices. Opening an email draft likewise involves your selected email service. The static Contact-page map does not load a map-provider service.
The editorial content is intended for adults aged 18 and over. There is no child-focused registration or age-verification database in this build. If personal information about a child has been sent unnecessarily to an operational publisher mailbox, contact the verified operator to request appropriate action.
This policy should be revised when the operator, providers or processing practices change, with the effective date updated accordingly. Optional tracking must not be introduced on the strength of an earlier choice made for this essential-storage-only build. See also the Terms of service and Cookie policy.