Privacy statement

1. Who runs this site

UnitDigest is a personal editorial page about one mobile game. This site is run by an individual, Declan O'Connor, at 1468 Albany Hwy, Cannington WA 6107, Australia, telephone +61 8 6150 9656. The only contact channel is notes@unitdigest.com.

As a private person publishing a small non-commercial page, I am very likely a small business operator under section 6D of the Privacy Act 1988 (Cth) and therefore outside the direct reach of that Act. I have chosen to follow the Australian Privacy Principles in Schedule 1 of the Act voluntarily and in full, because saying so plainly is more useful to a reader than claiming an obligation that may not apply.

2. The short version

This site does not collect personal information through its pages. There is no form of any kind on this site, no search box, no comment field, no registration, no account, no newsletter and no notification prompt. No cookie is set by this site. Nothing you read here is sold, and no product or service is offered for sale.

Three things do happen automatically whenever any web page is served, and they are described in full below: the hosting server writes a technical log line, the content delivery network in front of the server processes the same technical details, and your own browser may keep one small entry that remembers whether you dismissed the storage notice.

3. What information is handled, and where it comes from

3.1 Hosting server logs

The server that stores these files writes a standard access log for every file it sends. Each line contains the internet protocol (IP) address that made the request, the date and time, the address of the file requested, the response code, the size of the response, the browser user-agent string, and, where the browser supplies one, the referring address. This information is generated by the request itself; it is not typed in by you and it is not linked to a name.

3.2 Content delivery network

Requests reach the server through Cloudflare, Inc., which operates a content delivery network and a security layer. Cloudflare processes the same technical details in order to route the request, to serve cached copies of the files, and to filter automated abuse. Cloudflare may also compile aggregate performance measurements for the site without setting a cookie for that purpose. I do not run any analytics product on this site and I do not place any advertising or measurement tag on these pages.

3.3 Email you choose to send

If you write to the address above, I receive your email address, whatever you put in the subject line and body, and the technical headers your mail service attaches. That message travels through your own mail provider and mine; it is not submitted through this website, because this website has nothing to submit it with.

3.4 Storage inside your browser

If you dismiss the storage notice at the bottom of the page, a single entry named ud-consent is written to the sessionStorage area of your browser with the value ok or nope. It never leaves your device, it is not readable by anyone else, and your browser discards it when you close the tab. This site does not use localStorage, IndexedDB or any cookie of its own.

4. Purpose and basis for each category

• Server logs are handled to deliver the pages you asked for, to keep the site available and to investigate faults or abuse. The basis is my legitimate interest in running a working, secure page, and the practical impossibility of serving a file without an address to send it to.
• Delivery-network data is handled for routing, caching, and protection against automated attacks. The basis is the same legitimate interest in a site that stays reachable.
• Email correspondence is handled solely to read and answer the message you sent. The basis is your own decision to write.
• The browser storage entry exists only so that the notice does not reappear on every page in the same tab. It is set by your action of dismissing the notice.

5. How long each category is kept

• Hosting server logs: rotated and deleted by the hosting provider on its standard cycle, which does not exceed thirty days for the raw log files.
• Delivery-network records: retained by Cloudflare under its own schedule, which for edge logs is measured in days rather than months.
• Email correspondence: kept for as long as the exchange is useful, and in any event no longer than twenty-four months after the last message, unless a longer period is needed to deal with a legal claim.
• The ud-consent entry: until you close the browser tab, or until you clear site data, whichever happens first.

6. Who receives this information

The recipients are limited and named: the hosting provider that operates the server for this site, and Cloudflare, Inc., which operates the delivery network. If you write to me, your message is also handled by the email provider that carries it. No information is shared with advertising networks, data brokers or analytics companies, because none are used here. No information is sold or exchanged for any consideration.

7. Handling outside Australia

Cloudflare, Inc. is established in the United States and operates servers in many countries, so the technical details described in section 3 will be processed outside Australia. Consistent with Australian Privacy Principle 8, I have satisfied myself that the recipient operates under published data-protection commitments and contractual terms that require it to handle the information in a way broadly consistent with the Australian Privacy Principles. Because the information involved is limited to technical request details and is not tied to an identified person by me, the practical effect on any individual is small.

8. Access and correction

Australian Privacy Principles 12 and 13 give an individual the right to ask for access to personal information held about them and to ask for it to be corrected. You may make either request by writing to the address in section 1. Please describe what you are looking for, because a bare IP address in a rotating log is rarely enough to identify a record. I will answer within a reasonable period, normally thirty days, and I will explain my reasons in writing if I cannot give access or make a correction.

You may also ask me to erase a message you sent by email, and I will do so unless I need to keep it to deal with a legal claim.

9. Complaints and the OAIC

If you believe your privacy has been handled badly here, write to me first and set out what happened. If you are not satisfied with my answer, or if you would rather not deal with me at all, you may complain to the Office of the Australian Information Commissioner:

• Office of the Australian Information Commissioner (OAIC)
• GPO Box 5218, Sydney NSW 2001, Australia
• Telephone 1300 363 992
• Website: www.oaic.gov.au

10. Data breaches

The Notifiable Data Breaches scheme in Part IIIC of the Privacy Act 1988 (Cth) sets out what must happen when a breach is likely to cause serious harm. If a breach touching this site occurred, I would assess it promptly, and where the scheme's threshold were met I would notify the affected individuals and the Australian Information Commissioner as the scheme requires, even though I follow the Act voluntarily. Given that this site holds no account data, no contact list and no submitted content, the realistic scope of any such event is a technical log file.

11. No marketing, and the Spam Act 2003

The Spam Act 2003 (Cth) governs commercial electronic messages sent to Australian addresses. This site does not send any. There is no mailing list, no address is gathered from these pages, and no message will ever be sent to you unless it is a direct reply to an email you wrote first. Because nothing is collected, there is no list to be removed from.

12. Children

This site is written for a general audience and is not directed at children under 13 years of age. No information is knowingly gathered from children, which is straightforward here because no information is gathered from anyone through the pages. A parent or guardian who is concerned about a message received from a child's address may write to me and ask for it to be deleted.

13. Security

The site is served over an encrypted connection. The files are static, so there is no database, no user account and no administrative login exposed to the public. Access to the hosting account is protected by a long unique passphrase and a second authentication factor. No safeguard is perfect, and I do not claim otherwise, but the amount of information held here is deliberately kept as close to nothing as a working website allows.

14. Changes to this statement

If the way this site works changes, this statement will be updated before or at the same time as the change, and the date at the top of the page will be revised. Material changes will be described in the opening paragraph for at least one month. There is no mailing list, so please check this page if the detail matters to you.

This version takes effect on 4 September 2026 and replaces any earlier version.