Cookie notice

1.1 This notice covers the pages served at cloudridge.im, published by CLOUDRIDGE TECHNOLOGIES PTY LTD, ACN 696 705 478.

1.2 It does not cover a game published by a customer of the Company. A game's own storage is a matter between that studio and its players, and the studio's notice is the one that applies.

1.3 It does not cover a site reached by following a link from here. A link is not an endorsement of the destination's storage practices.

1.4 It is read with the privacy policy, which deals with personal information generally and which records the website request log in Part 1 of its Schedule A.

2.1 Nothing is written to your device by these pages. No cookie is set, first party or third party. No entry is placed in local storage or session storage. No IndexedDB database is opened, no cache is populated by a service worker, and no service worker is registered at all.

2.2 No visitor is identified, counted, tagged or followed between pages. There is no analytics product on this site, no tag manager, no advertising pixel, no heatmap recorder, no session replay tool and no A/B testing framework.

2.3 No canvas, font-enumeration or audio fingerprint is taken, and nothing else is done that would substitute for the identifier a cookie would otherwise carry.

2.4 The absence is not an oversight to be corrected later. A company that intends to hold player data on other people's instructions has a weak position if it cannot resist instrumenting its own brochure.

3.1 Take nothing in clause 2 on trust. Every statement in it is checkable from the browser already open on this page, in about a minute, without any tooling beyond what the browser ships with.

3.2 If a check produces a different result, the Company would rather hear about it than not. Write to ops@cloudridge.im with the browser and the panel that disagrees, and the answer will come on the same or the next business day.

4.1 A single JavaScript file is served from this origin. It opens and closes the navigation menu on narrow screens, and it reveals a few sections as they scroll into view.

4.2 It reads one thing about your device: whether the operating system is set to reduce motion. That preference is read through a standard media query, is used to skip the reveal animation, and is neither stored nor transmitted anywhere.

4.3 It writes nothing to disk and sends nothing outbound. A response header restricts this site's scripts to this origin, so a third-party script could not be injected and run even if one were somehow referenced.

4.4 With scripting disabled the pages still work. The menu falls back to a visible list and the revealed sections are simply visible from the outset.

5.1 A consent banner exists to obtain permission for storage that has already been built. Where the storage does not exist, the banner has nothing to ask about, and presenting one anyway would misdescribe the site to its own readers.

5.2 A banner also has a cost that is rarely counted. It obscures the page, it trains people to dismiss privacy language without reading it, and in many implementations the tracking begins before the choice is recorded.

5.3 If a page on this site ever needs storage, Schedule C states what the mechanism would be and what would be asked for before it was used. The order there is deliberate: build the need, disclose it, then ask.

6.1 Australia has no standalone statute requiring consent before a cookie is placed. There is no local equivalent of the European instrument that produced the banner, and the obligation here arrives through a different door.

6.2 That door is the Privacy Act 1988 (Cth). Where a cookie or similar identifier collects information about an identified individual, or about an individual who is reasonably identifiable, the collection is regulated by the Australian Privacy Principles like any other collection: APP 3 governs whether it may be collected, APP 5 requires notification, and APP 6 governs what may then be done with it.

6.3 The Company's view is that an identifier which follows a person between sites is capable of being personal information in that sense, and it does not rely on the technical form of the identifier to argue otherwise. The point is academic on this site, since nothing is stored, but it is the reasoning that would apply if anything were.

6.4 A reader in the European Union or the United Kingdom is entitled to ask the narrower question of whether consent was obtained for storage. The answer is that no storage occurs, so the question resolves itself without a consent record.

7.1 Some browsers send a Do Not Track header or a Global Privacy Control signal. This site honours both by default, in the sense that it does none of the things either signal asks a site to stop doing.

7.2 The signals are not read, recorded or acted upon, because acting on them would require distinguishing between readers, which is the behaviour they exist to prevent.

7.3 Blocking cookies, blocking third-party requests, or browsing in a private window costs nothing here. The pages render identically, and the only visible difference from blocking the font host is described in Schedule B.

8.1 The effective date and version at the head of this document change whenever the text does.

8.2 If storage is ever introduced, this notice is amended before the change is deployed rather than afterwards, and Schedule A gains a row naming the mechanism, its purpose and its lifetime.

8.3 A superseded version is supplied on request to anyone who asks, so a statement made here can be checked against the version that was live at a given date.

Every client-side storage mechanism a current browser offers, and what this site puts in it. The schedule is written as an inventory with empty rows rather than as a list of what is used, so that a reader can see the mechanisms that were considered and rejected as well as the ones in use.

The final row is the ordinary caching every website relies on. It stores a copy of a file, not a record about a person, it carries no identifier, and it is cleared by the browser's own cache controls.

Storage is only half of the question. The other half is which hosts a page contacts, because a request carries an IP address whether or not anything is stored afterwards. This is the complete list for any page on this site.

The typefaces, stated plainly

Petrona and Spline Sans Mono are requested from hosts operated by Google LLC. That request discloses an IP address to a company in the United States, and it is the only routine overseas disclosure this website creates. It appears in Schedule B of the privacy policy for that reason rather than being folded into a general reference to third-party assets.

Google states that requests to these hosts set no cookies. No cookie appears under this origin or under either font host after a page loads, which is a claim clause 3 invites you to confirm for yourself rather than accept on the strength of the assertion. Self-hosting the font files would remove the disclosure altogether, and it sits on the list of things to do before a Service opens.

What is not on that list

No content delivery network for scripts, no icon service, no embedded video, no map, no chat widget, no comment system, no social platform button, no error reporting service and no consent management platform. Each of those would add a host to the table above, and none of them is worth the row.

A customer console for the catalogue Services will need storage that a brochure site does not, and the shape of it is settled here so that the commitment is on the record before the code is written.

Those rows describe an intention rather than a deployment. Schedule A remains the accurate statement of what happens when a page from this site is loaded today, and it governs until this notice is amended.