Current features
This version has no visitor accounts, payments, newsletter subscriptions, comments, petition-signature collection or contact submissions to a Human Readers database. The reader checklist and contact form operate within the browser. The website code does not transmit those entries to an AI service or to the project.
Checklist and note entries
Answers, notes and generated plans are held temporarily in the open page. They are not saved in localStorage. Copying puts the output on your device’s clipboard. Downloading creates a text file through your browser. Printing may send content to the printer or print service you choose. Closing or reloading the page discards entries held in page memory.
One optional preference
The motion setting uses localStorage under the key “hr-motion”, with the value “on” or “off”. It contains no name, email, draft, checklist answer or revision plan. You can clear it using your browser’s site-data controls.
Technical delivery
The hosting or access provider may process IP address, browser details, requested page, request time and other technical data needed to deliver and secure the site. Its own terms and retention arrangements apply. This website code adds no analytics, advertising pixels, session replay or marketing tracking.
External references and sharing
Sources open as ordinary links. They are not embedded trackers or previews. Visiting an external source takes you to a service with its own practices. Copying or saving the petition uses your device; the share button copies its page link. Self-hosted fonts and code-native illustrations are delivered with the website.
Operator and privacy contact
The publisher’s verified legal identity, applicable jurisdiction and privacy contact have not been supplied in this build. The operator must complete them before enabling further processing or claiming a live enquiry service. Please do not enter sensitive information into a local draft.
Changes
Update this notice before enabling email transmission, analytics, accounts, subscriptions or other collection or sharing. The notice should describe the implementation that is actually running, including any added hosting integrations.