Disclaimer and Privacy Policy

Last Updated: August 11, 2026

1 - Disclaimer

1.1 Content

The information on littlebigbyte.com is published in good faith and is for general information purpose only. While we strive to keep our information up to date, we do not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information on this website is strictly at your own risk. We will not be liable for any losses and damages in connection with the use of our website.

From this website you may find links to other sites. While we strive to only provide links to useful and ethical websites, we have no control over the content and nature of those websites. The links we provide do not imply a recommendation for all of the content found on those websites.

2 - Privacy Policy

Little Big Byte Pty Ltd, ABN 86 689 835 961 (“Little Big Byte”), operates littlebigbyte.com and may operate other websites. It is Little Big Byte’s policy to respect your privacy regarding any information we may collect while operating our websites.

Our game does not collect any data. Cup and Counter sends nothing to us while you play. Information reaches us only when you choose to send it, for example by filling in and submitting the bug report form described in section 2.3.

2.1 Website Visitors

Like most website operators, Little Big Byte collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. Little Big Byte’s purpose in collecting non-personally-identifying information is to better understand how visitors use its website.

2.2 Gathering of Personally-Identifying Information

Certain visitors to Little Big Byte websites choose to interact with Little Big Byte in ways that require Little Big Byte to gather personally-identifying information. The amount and type of information that Little Big Byte gathers depends on the nature of the interaction.

Little Big Byte does not disclose personally-identifying information other than as described below. Visitors can always refuse to supply personally-identifying information, with the caveat that it may prevent them from engaging in certain website-related activities.

2.3 Bug Reports and Support Submissions

When you submit a bug report through our website, we collect:

the text you write: the title, description and steps to reproduce;
the game, version, platform and operating system you select;
any email address you choose to provide for follow-up;
any files you choose to attach: a save file and up to three screenshots;
your IP address, used only to limit how many reports may be submitted from one address in a short period.

Every attachment is optional. You can send a report without any files at all. If you send one without a save file, the form asks once whether you would like to include it, because it is by far the most useful thing for diagnosing a problem. You can always decline and send the report as it is.

Providing an email address is also optional. If you provide one, we use it only to contact you about that report. It is shown with the report in the private Discord channel our team reviews; it is not copied into a GitHub issue if the bug is confirmed.

We no longer collect the game’s Player.log. The bug report form used to offer it, and stopped on August 11, 2026, because it rarely told us anything the report itself did not. Logs attached to reports submitted before that date are still held for a time; section 2.9 describes what happens to them.

Save files and screenshots are stored exactly as you send them. We do not alter them, because modifying a save file would corrupt it and make it useless for investigating your problem. Please check a screenshot before attaching it if something private may have been visible on your screen at the time.

How reports reach us. Reports are posted to a private channel on Discord, where our team reviews them. Attachments are stored in Cloudflare R2 object storage and linked from that channel. Those links are never published or indexed, and each contains a long random identifier that cannot be guessed. Attachments are deleted automatically after a set period, and their links stop working at that point.

If we confirm the bug. A report that our team confirms is turned into an issue in our development repository on GitHub, so that the work to fix it can be tracked against the report that raised it. That issue carries the report text, the environment details, a reference back to the original report, and, for a report written in another language, your original wording alongside the translation. The repository is private and is not visible to the public. This step is never automatic: a person reads the report and decides.

Automated processing. A report written in a language other than English is translated so that we can read it; your original wording is always kept and stored alongside the translation. Every report is also automatically classified to help separate genuine reports from spam and abuse. Reports the classifier flags are routed to our team for human review; they are never discarded automatically.

Anti-spam. Submissions are checked by Cloudflare Turnstile before they reach us, to prevent automated abuse of the form.

You may ask us to delete a report you have submitted, along with any files attached to it. See section 2.10.

2.4 Analytics

We use a single analytics tool to understand how visitors use our website.

Plausible Analytics is a privacy-friendly analytics tool that we self-host on our own infrastructure at stats.littlebigbyte.com. It does not use cookies, does not collect any personally-identifying information, and does not share data with any third party. More information about Plausible is available at: https://plausible.io/privacy-focused-web-analytics

We previously used Google Analytics. It was removed in August 2026 and is no longer present on any page of this website.

2.5 Protection of Certain Personally-Identifying Information

Little Big Byte discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors and affiliated organisations that (i) need to know that information in order to process it on Little Big Byte’s behalf or to provide services available at Little Big Byte websites, and (ii) that have agreed not to disclose it to others.

Little Big Byte will not rent or sell personally-identifying information to anyone. Little Big Byte discloses personally-identifying information only in response to a subpoena, court order or other governmental request, or when Little Big Byte believes in good faith that disclosure is reasonably necessary to protect the property or rights of Little Big Byte, third parties or the public at large.

2.6 Cookies, Browser Storage and Embedded Content

A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns.

We do not set any cookies of our own. Our analytics are cookie-free, and we do not use advertising or tracking cookies of any kind.

Embedded content on the game development page. That one page embeds two pieces of content served by other companies. Because they load as part of the page, those companies can receive your IP address and browser information, and may set their own cookies:

(a) The Steam store widget, served by Valve Corporation, which loads when the page opens. It is not loaded on smaller screens, where a plain link to the Steam store page is shown instead. See Valve’s privacy policy;

(b) The game trailer, served by YouTube. We embed it through youtube-nocookie.com, so YouTube does not set cookies unless you press play. See Google’s privacy policy.

The bug report page separately loads Cloudflare Turnstile, the anti-spam check described in section 2.3. No other page on this website loads content from a third party, and everything else the site needs — fonts, icons, scripts and analytics — is served from our own infrastructure.

The bug report page does save two small items on your own device, using your browser’s built-in storage rather than cookies:

(a) Your chosen language: if you pick a language from the selector on that page, we remember it so that returning to the page shows it in that language again;

(b) Your unsent draft: if you switch language part-way through writing a report, the information you have entered is held briefly so that changing language does not discard your work. It is cleared as soon as it has been restored.

Neither is sent to us, neither is used to identify or track you, and both are removed if you clear your browser’s stored data for this site.

Most browsers allow you to refuse to accept cookies and to delete cookies and stored site data. You can obtain up-to-date information about this from your browser’s help documentation.

2.7 Business Transfers

If Little Big Byte, or substantially all of its assets, were acquired, or in the unlikely event that Little Big Byte goes out of business or enters bankruptcy, user information would be one of the assets that is transferred or acquired by a third party. You acknowledge that such transfers may occur, and that any acquirer of Little Big Byte may continue to use your personal information as set forth in this policy.

2.8 International Transfers

Little Big Byte may transfer and process data anywhere in the world where Little Big Byte or its sub-processors maintain data processing operations. Little Big Byte shall at all times provide an adequate level of protection for the data processed, in accordance with the requirements of applicable data protection laws.

2.9 Data Retention

Generally, data is retained until it is no longer useful. For example, we keep web server logs that record information about a visitor to Little Big Byte websites, such as the visitor’s IP address, browser type, and operating system, for approximately 30 days in order to investigate issues if something goes wrong.

A bug report is kept for as long as it stays useful, which in practice is a long time. A reported problem may not be reproducible for months, and an attached save file is often the only way to investigate it later, or to confirm that a fix worked.

A report can end up in more than one place, and the parts are not all kept for the same length of time.

The report itself, including any follow-up email address you provided, stays in the private channel our team reviews it in.
Files you attached are held separately, in object storage, and are deleted automatically after a set period. Once that happens the links to them stop working, and we no longer hold your save file or your screenshots.
If we confirmed the bug, an issue in our private development repository holds the report text and the environment details. That issue is kept indefinitely, because it is the record of why a change was made to the game.

Reports submitted before August 11, 2026 may include a Player.log. The form offered one until that date, and where a log was attached it was treated as follows. Identifying details found within it — account names, email addresses, IP addresses, Steam IDs and default computer names — were replaced with placeholders before it was stored, and where the log was very large only the first portion of it was kept. Those files expire from object storage on the same schedule as any other attachment.

One part of that outlives the file, and it is worth being clear about: where we confirmed the bug, an excerpt of the log was copied into the development issue raised from the report, and that excerpt is not removed when the original attachment expires. The full file goes; a portion of the log stays with the issue it explains. Asking us to delete a report removes this too, along with everything else raised from it.

If you would like a report you submitted to be deleted, see section 2.10.

2.10 Your Rights Over Your Data

You can request to receive an exported file of the personal data we hold about you, and you can request that we erase it. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

In practice, a bug report is the only way we come to hold personal data about a visitor to this website. If you have submitted one, you can ask us to delete that report and any files you attached to it. Please quote the reference number shown to you when the report was submitted. If you no longer have it, tell us the approximate date you submitted the report and the title you gave it, and we will do our best to find it.

Because a report can end up in more than one place (see section 2.9), deleting it means removing the report itself, any files you attached, and any development issue raised from it. The reference number is what ties those together, which is why quoting it makes the request much quicker to honour.

If you are located in certain countries, including those that fall under the scope of the European General Data Protection Regulation (the “GDPR”), data protection laws give you rights with respect to your personal data, subject to any exemptions provided by the law, including the rights to:

Request access to your personal data;
Request correction or deletion of your personal data;
Object to our use and processing of your personal data;
Request that we limit our use and processing of your personal data; and
Request portability of your personal data.

To exercise any of these rights, please contact us using the details in section 2.13 below. EU individuals also have the right to make a complaint to a government supervisory authority.

2.11 Security

While no online service is 100% secure, we work hard to protect information about you against unauthorised access, use, alteration, or destruction, and take reasonable measures to do so, such as monitoring our services for potential vulnerabilities and attacks. We make use of two-step authentication where available and strong password practices.

2.12 Privacy Policy Changes

Little Big Byte may change its Privacy Policy from time to time. Little Big Byte encourages visitors to frequently check this page for any changes. Your continued use of this website after any change in this Privacy Policy will constitute your acceptance of such change.

2.13 Contact

If you have any questions about this Privacy Policy or the practices of Little Big Byte, please contact us at support@littlebigbyte.com

3 - Sub Processors

Little Big Byte currently uses the following sub processors

Sub Processor	Service Provided	URL
Cloudflare	Hosting, DNS, and bot protection (Turnstile). For bug reports: serverless compute, object storage for attachments, and translation and classification of report text	https://www.cloudflare.com/
Discord	Delivery and review of bug reports (Private Server)	https://discord.com/
GitHub	Issue tracking for confirmed bug reports (private repository)	https://github.com/
Gmail	Email	https://mail.google.com
Plausible Analytics	Analytics (self-hosted)	https://stats.littlebigbyte.com
Valve Corporation	Steam store widget embedded on the game development page	https://store.steampowered.com/
YouTube (Google)	Game trailer embedded on the game development page	https://www.youtube.com/