What cookies and local storage do
Cookies are small pieces of information stored by a browser and, where applicable, sent with later requests to a website. localStorage and sessionStorage are browser storage mechanisms accessed by scripts. They are different technologies, although both can be used to remember choices.
The journal's editorial features
The supplied editorial pages and script do not set cookies or write to localStorage or sessionStorage. There are no embedded advertising, analytics, video or social-media services in these pages. Reading the guides, using the navigation and expanding questions do not require optional tracking.
The correspondence tool keeps its working text in the current page. Copying and downloading are explicit actions: they place text on your clipboard or create a local file, rather than setting a cookie. Browser autofill, caching and form restoration are browser features and may behave according to your own settings.
| Feature | Storage behaviour | Your control |
|---|---|---|
| Navigation and reveals | Temporary page state only | Reload or leave the page |
| Message preview | Current-page memory; no site storage | Edit or close the page |
| Clipboard Copy | Device clipboard, after your action | Clear or replace clipboard contents |
| Blob Download | A file saved by your browser | Delete the downloaded file |
Cookie preferences
There are no optional cookies to enable or disable in the journal's editorial code. If the hosting platform presents a separate consent panel, use that panel to manage the services it identifies. Accepting an optional service is not necessary to read these static guides.
You can also inspect and remove site data through your browser's privacy or site-settings controls. Blocking cookies does not prevent the editorial pages or message preview from working. Removing saved site data may reset preferences managed by a separately provided consent service.
Hosting and external websites
Hosting infrastructure may operate security or delivery features separately from the editorial files. Any cookies or storage introduced by those services should be identified in the deployment's consent information. This page does not represent an audit of infrastructure outside the editorial code.
Manufacturer and reference websites have their own cookie practices. A link does not load their site until you follow it, and this journal cannot change their preferences for you.
Changes and enquiries
If optional storage or tracking is introduced, its purpose and controls should be disclosed before activation, with consent obtained where required. For questions, contact [email protected]. The privacy notice explains correspondence and general connection information.