Cookie notice

Current · governs the whole document

Each entry states one thing that is true about storage on your device today. Each carries the version its wording started at. Entry 11 explains what happens when one of them changes, and the short version is that the number moves before the behaviour does.

This document is a companion to the privacy policy, which covers everything else. Where the two touch, the privacy policy carries the detail and this one carries the list.

Current · applies to scriptshift.cc

Nothing. The pages here carry one small script, which opens and closes the navigation on a narrow screen and reveals sections as they scroll into view. It writes no cookie, no local storage key, no session storage key and no database entry.

That is checkable in about fifteen seconds and the check beats the assurance. Open the developer tools in your browser, go to the Application panel, and read the storage list for this origin. Whatever entry 3 describes will be there. Nothing else will.

Current · set by the hosting provider

The network that serves these pages separates readers from automated floods, and it does that with two cookies of its own. Both are strictly necessary in the ordinary sense of the phrase: without them the site is harder to keep reachable.

Neither reaches us as an identifier of a reader, neither is used for anything beyond keeping the site answerable, and neither is passed to a third party. There is no second table and no item filed under a different heading.

Current · Privacy Act 1988 (Cth)

Australia runs no separate cookie consent regime. There is no local counterpart to the European ePrivacy Directive, no statutory obligation to ask before writing a cookie, and no obligation to display a banner. A banner on an Australian site is therefore a design choice or an imported habit rather than compliance with a domestic requirement.

What does govern the question is the Privacy Act 1988 (Cth). Where a cookie collects information about a reasonably identifiable individual, that information is personal information and the Australian Privacy Principles apply to it as they apply to anything else. APP 3 decides whether it may be collected. APP 5 requires that you be told, which is the job of this page. APP 6 confines what it may then be used for. APP 11 requires it to be protected and destroyed once it is no longer needed.

So there is no banner here, and the reason is not that banners are tiresome. Consent is the mechanism for storage that is not strictly necessary, and entry 3 is the whole inventory. Asking you to agree to that would be asking you to agree to nothing, and it would teach one more click of reflex dismissal to a person who will meet a control that matters on the next site.

A reader in the European Economic Area or the United Kingdom is under a stricter instrument. It changes nothing practical here, because storage limited to what entry 3 lists would be exempt from a consent requirement under those instruments as well.

Current · one request leaves the page

The typefaces on this site are fetched from Google's font hosts, fonts.googleapis.com and fonts.gstatic.com. That is the only request these pages make to a machine this company does not control, and it deserves a precise description rather than a footnote.

What the request reveals

Your IP address, your user agent string, and the page that referred the request

What Google states

That the font service writes no cookie, and that the requests are not used for advertising or profiling

What we can verify

Not that. The sentence above names who is making the claim, because we are in no position to confirm it from here

If you block it

Every page keeps working and renders in a system font instead. Nothing depends on the request succeeding

Serving the font files from this domain would remove the request altogether, and that change is intended. When it is made, this entry moves to v1.1 and the wording it replaced stays on file.

Current · applies to scriptshift.cc

An inventory is only useful if the reader knows which categories were considered. These were, and none of them is here:

• Analytics of every kind, hosted or self-hosted, including the privacy-preserving ones.
• Advertising cookies, advertising identifiers and conversion tracking.
• Social and marketing pixels of any platform.
• Session recording, heat mapping, scroll depth and click frustration detection.
• Embedded video, maps, comment systems, chat bubbles and social widgets.
• Fingerprinting, and any other attempt to recognise a returning reader.
• A/B testing and feature flag services.

Open the Network panel beside the Application panel and the request list will match this page. That check is the only assurance on the subject that is worth anything.

Current · cross-reference to the privacy policy

Every web server writes down the requests it answers, and a page about storage that skipped this would be telling a comfortable half of the story.

Those lines are written by the hosting provider and they sit on the provider's own rotation, currently under 30 days. They record the source address, the time, the path, the user agent, the referring page and the response code. None of that is on your device, so none of it is a cookie. It is still personal information under Australian law, and the fields, the reasons and the retention are set out in the privacy policy.

Current · your controls, not ours

Every current browser lets you inspect what a site has written, delete it, and refuse more of it. Blocking what entry 3 lists may mean the network challenges you a little more often; it will not stop the pages loading.

• Chrome. Settings, then Privacy and security. Site data holds what is already written.
• Safari. Settings, then Privacy, then Manage Website Data.
• Firefox. Settings, then Privacy and Security, then Cookies and Site Data.
• Edge. Settings, then Cookies and site permissions.

A private window discards everything when it closes, which here changes almost nothing, since nothing on this site is designed to survive between visits in the first place.

Current · both signals honoured

Both signals are honoured, and honesty requires the admission that honouring them is trivial here: there is nothing on this site for either one to switch off. Send them and the behaviour is identical to sending neither.

The commitment is still worth writing down. A site that ignores those headers and stays quiet has made a decision it would rather you did not inspect, and the difference between that site and this one is only visible if somebody puts it in a document.

Current · applies to the release tooling

A cookie is a browser mechanism. The release tooling described elsewhere on this site is a command that runs on your build machine. It has no browser, no session and no page, so there is nothing in it that could write one.

What it does with the credentials it is given is a bigger question than cookies, and it is answered in entry 5 of the privacy policy. The summary is that nothing about your deployment reaches this company at all.

Current · governs the whole document

1. Anything new that writes to your device is added to entry 3 before it goes live, not after somebody notices it.
2. The entry's version rises and the effective date at the top of this page moves with it.
3. Where the law that applies to you requires consent for the new item, you are asked first, refusing is exactly as easy as agreeing, and refusing degrades nothing on this site.
4. The superseded wording is kept and sent to anybody who asks.

Questions about this page go to [email protected] and are answered inside 5 working days. A request under the Privacy Act 1988 (Cth) is answered inside 30 days. If an answer does not satisfy you, the route to the Office of the Australian Information Commissioner is in entry 25 of the privacy policy: GPO Box 5218, Sydney NSW 2001, telephone 1300 363 992, oaic.gov.au.

Published by SCRIPTSHIFT TECHNOLOGIES PTY LTD, ACN 698 500 542, ABN 21 698 500 542, an Australian proprietary company in Western Australia.