Tiny Logic Privacy Policy
Effective date: 9 October 2026 · Version 2.1 · Applies to Tiny Logic (all editions, including the free demo) version 1.1.1 and later, the Tiny Logic Discord community and bot, and the Tiny Logic websites.
Plain-language summary. Tiny Logic collects no personal data unless you give consent in the game, and never from players below the age of digital consent for their region. What we collect is used to make the game better, more stable and faster. It is linked to a random installation ID, not to your name. We do not sell your data, do not show advertising, and do not build advertising profiles. You can turn collection off at any time in Settings. This summary is provided for convenience; the full policy below is what governs.
1. Who we are
Tiny Logic is developed and published by Mazell Smack-Dubose, an individual developer resident in the State of Delaware, United States ("we", "us", "our"). We determine the purposes and means of the processing described in this policy and are therefore the controller under the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR") and the UK GDPR, and the business or controller under applicable United States privacy laws. Given the nature and scale of our processing, we are not required to appoint a data protection officer. Contact details are in section 30.
2. Scope and acceptance
This policy applies to: (a) the Tiny Logic software, including the full game, the free demo and any future editions, on every platform ("the Game"); (b) the Tiny Logic Discord server and its bot ("the Community"); (c) the Tiny Logic websites, including this site and the update service ("the Sites"); and (d) your communications with us. It does not apply to third-party services you use to buy, download or play the Game, such as itch.io, Steam or Discord, which have their own privacy policies.
This policy explains how we handle personal data. It is not itself a request for consent. Where we rely on consent, we ask for it separately and specifically inside the Game, as described in section 6.
3. Definitions
| Term | Meaning in this policy |
|---|---|
| Personal data / personal information | Any information relating to an identified or identifiable natural person, including information linked to an online identifier such as an installation ID or IP address. |
| Installation ID | A random identifier generated on your device when the Game is first run. It contains no information about you and is not derived from your hardware or accounts. |
| Pseudonymous data | Data that cannot be attributed to a specific person without additional information (such as your installation ID) that is kept separately, here on your own device. |
| De-identified data | Data that cannot reasonably be linked to a particular person or device, which we commit not to re-identify. |
| Aggregate data | Statistics combining data from many players, from which no individual can be identified (for example, the total number of transistors placed by all players). |
| Processing | Any operation performed on data, such as collection, storage, analysis, disclosure or deletion. |
| Processor / service provider | A company that processes data on our behalf and under our instructions. |
4. Laws we comply with
We design the Game and the Community to comply with the privacy and data protection laws of the places our players live, including:
| Region | Laws | How we comply |
|---|---|---|
| European Union and EEA | GDPR; ePrivacy Directive (2002/58/EC) as implemented nationally | Opt-in consent before any analytics, age gate at 16, data minimisation, documented legal bases, transfer safeguards, full data subject rights. |
| United Kingdom | UK GDPR; Data Protection Act 2018; Privacy and Electronic Communications Regulations 2003 (PECR); ICO Age Appropriate Design Code | Same as EU; privacy-by-default settings (stats off unless chosen); no nudging toward sharing; age gate at 16. |
| United States (federal) | Children's Online Privacy Protection Act (COPPA); FTC Act Section 5 | No collection from users under 13; accurate, non-deceptive disclosures. |
| United States (states) | California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA); Delaware Personal Data Privacy Act; Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa and other comprehensive state privacy laws | No sale or sharing for cross-context behavioural advertising; no targeted advertising; no profiling with legal effects; rights to know, access, correct, delete and port; appeal process. |
| Canada | PIPEDA and provincial equivalents | Meaningful consent, purpose limitation, access and correction rights. |
| Brazil | Lei Geral de Proteção de Dados (LGPD) | Consent and legitimate interest bases, data subject rights equivalent to GDPR. |
| Other jurisdictions | Including Switzerland (revFADP), Australia (Privacy Act 1988), Japan (APPI), South Korea (PIPA) | We apply GDPR-level protections to all players worldwide as our baseline. |
Where these laws differ, we apply the protection that is most favourable to you, unless a law specifically requires otherwise.
5. Children and age of digital consent
On first launch, the Game asks whether you meet the minimum age to consent to optional data collection. The applicable age is determined from your device's language and region settings, not by locating you:
| Region | Minimum age | Basis |
|---|---|---|
| United States | 13 | COPPA |
| United Kingdom, EU, EEA, and every other or unknown region | 16 | GDPR Art. 8 (highest age used by any member state); UK Age Appropriate Design Code |
Your answer is stored only on your device and is never transmitted. If you indicate you are below the applicable age: no consent is requested, no analytics, questionnaire answers or crash reports are collected or transmitted, and every gameplay feature remains fully available. We do not knowingly collect personal data from children below these ages. If we learn that we have, we will delete it without delay. Parents or guardians who believe their child has provided personal data may contact us at the address in section 30. The Community is additionally subject to Discord's Terms of Service, which require users to be at least 13 or the higher age required in their country.
6. How consent works
- Opt-in only. Analytics are off by default. Nothing in section 7 that requires consent is collected until you choose Share anonymous stats.
- Equal choice. Share anonymous stats and No thanks are presented with equal prominence, and refusing changes nothing about the Game.
- Granular. Analytics, crash reports and itch.io account linking are separate choices. Crash reports are requested individually after each crash (Yes, No or Always).
- Informed. The consent screen summarises what is collected and links to this policy.
- Withdrawable. You may withdraw at any time in Settings, as easily as you gave consent. Withdrawal stops collection immediately and deletes any data still waiting on your device. It does not affect processing carried out before withdrawal.
- Re-asked when needed. If we introduce a new category of data that falls outside section 7, the Game will ask for your consent again before collecting it.
7. Categories of data we collect
The categories below are defined by type and purpose, and apply to the Game's current and future features (see section 12). Within each category we collect only what is reasonably necessary for the purposes in section 9.
7.1 Collected only with your consent
| Category | Description and examples |
|---|---|
| A. Identifiers | Installation ID; an itch.io username, only if you separately choose to link it; and the IP address from which data is received (see 7.4). |
| B. Device and technical data | Operating system and version; processor model and core count; memory; graphics hardware and driver; display count, size and refresh rate; window size and mode; UI scale and rendering settings; input devices present (mouse, keyboard, touch, pen, controller); display server; language; game version, edition and build. |
| C. Gameplay and interaction data | How the Game is used, including: sessions and their length and time of day; days since installation and return visits; time spent in each mode, menu and screen; progress through lessons, steps, puzzles and challenges; hints used; quiz and question answers and whether they were correct; content completed, skipped or abandoned and where; parts, components, tools and features used and how they were found; chips, programs and projects created, opened, saved, exported or shared (as counts, sizes and types, never their names or contents); settings changed; in-game notices viewed and buttons pressed; features discovered for the first time; and interactions with any feature added in future versions of the Game. |
| D. Performance and diagnostic data | Frame rate and frame times; stutters and freezes and what was happening at the time; simulation speed; compile and load times; memory use; the size and complexity of boards and circuits (counts of parts, wires, chips and transistors); errors and warnings; network request outcomes for the Game's own services. |
| E. Crash reports | The type of error, game version and edition, operating system, a technical stack trace of the Game's code, and recent technical log lines from the Game itself. File paths are reduced to file names so that system user names are excluded. |
| F. Questionnaire responses | Optional answers you choose to give, such as age range, occupation or field of study, how you found the Game, and what you want to build. Every question can be skipped. |
| G. Inferences | Non-sensitive conclusions drawn from the categories above solely to improve the Game, such as which lessons are too difficult or which devices perform poorly. We do not draw inferences about sensitive characteristics or use inferences for advertising. |
7.2 Collected without consent because the service requires it
| Category | Description |
|---|---|
| Update check | When the Game starts, it requests small public files from the Sites (such as version.txt) to check for updates and current notices. No identifier or personal data is included in the request; the hosting provider receives your IP address as a technical necessity of serving any file. |
| Community data | See section 22. |
| Purchase data | See section 23. |
| Communications | If you contact us, we process your message and contact details in order to respond. |
7.3 Sensitive data
We do not request or intentionally collect special category or sensitive personal data, such as racial or ethnic origin, health, religious or political views, sexual orientation, biometric or genetic data, precise geolocation, or government identifiers. Optional pronoun roles in the Community are chosen voluntarily, are visible only within Discord, and are not used for any other purpose.
7.4 IP addresses
Any service on the internet necessarily receives the IP address of the device it communicates with. Our analytics provider is configured not to derive geolocation from IP addresses, and we do not use IP addresses to identify, track or locate players. IP addresses may be used, where necessary, to prevent abuse of our services (such as fraudulent or automated submissions).
8. Data we do not collect
We do not collect: your real name, email address, postal address or payment details through the Game; the names or contents of your projects, circuits, chips or programs; text you type, including search terms, notes and code (only the length of a search may be recorded); names of files or folders on your device; your precise or approximate location; your contacts, photos, camera, microphone or any files outside the Game; browsing history; advertising identifiers. We do not use cookies or tracking pixels on the Sites.
9. Purposes of processing
- Improving the Game: understanding which features, lessons and content are used, enjoyed, confusing or abandoned, and deciding what to build, change or fix.
- Quality and stability: detecting, diagnosing and fixing crashes, bugs and errors.
- Performance: measuring and improving speed and stability across the hardware our players use.
- Education design: improving the effectiveness of lessons, hints and quizzes.
- Service operation: delivering updates, update notices and the Game's online features.
- Community: operating, moderating and keeping the Community safe, and verifying purchases for community roles.
- Customer support: responding to your messages, bug reports and requests.
- Business analytics: understanding the size and composition of our audience (in aggregate) to plan development, platforms and translations.
- Aggregate reporting: publishing aggregate, non-identifying statistics about the Game and its community (for example in update notes, store pages or promotional material).
- Security and integrity: protecting the Game, the demo and our services from tampering, fraud and abuse (see section 13).
- Legal compliance: meeting tax, accounting and legal obligations and responding to lawful requests.
We do not use personal data for advertising, sale to third parties, or training artificial intelligence models offered to others.
10. Legal bases (EU, EEA and UK)
| Processing | Legal basis |
|---|---|
| Analytics, questionnaire, crash reports, itch.io linking (categories A to G) | Consent, GDPR Art. 6(1)(a); storage and access on your device under ePrivacy Art. 5(3) / PECR reg. 6 likewise on consent. |
| Update check and service files | Legitimate interests, Art. 6(1)(f): delivering updates and keeping players on a secure, working version. The request is strictly necessary for the service you use. |
| Community operation, moderation and safety | Legitimate interests, Art. 6(1)(f): maintaining a safe, functioning community; performance of a contract, Art. 6(1)(b), where you request a feature such as purchase verification. |
| Integrity checks in the demo | Consent where combined with analytics; otherwise not transmitted. |
| Purchase records, tax and accounting | Performance of a contract, Art. 6(1)(b); legal obligation, Art. 6(1)(c). |
| Responding to requests and communications | Legitimate interests, Art. 6(1)(f); legal obligation, Art. 6(1)(c), for rights requests. |
Where we rely on legitimate interests, we have balanced our interests against your rights and concluded the processing is limited, expected and low-risk. You may object at any time (see section 18).
11. Pseudonymous, de-identified and aggregate data
Game analytics are pseudonymous: they are linked to your installation ID, not to your name or contact details. We do not hold any information that lets us connect an installation ID to a real person unless you choose to link an itch.io account or provide your ID to us. Because of this:
- In accordance with GDPR Article 11 and equivalent provisions, we are not able to identify you from our analytics on our own. To exercise rights over analytics data, you must provide information that lets us locate it: your installation ID, or the itch.io username you linked (see section 21). Without one of these, we cannot find, and therefore cannot act on, your analytics data.
- We may create de-identified and aggregate data from analytics. Such data is no longer personal data. We may retain it indefinitely, use it for any lawful purpose, and publish it, and we commit not to attempt to re-identify it.
12. Future features and versions
The Game is in active development and receives frequent updates. This policy is written so that it applies to new features, modes, content and editions as they are added, as long as the data involved falls within the categories in section 7 and is used for the purposes in section 9. For example, new lessons, parts, tools, challenges or game modes generate gameplay and interaction data (category C) and performance data (category D) covered by your existing consent.
If a future feature requires a new category of personal data or a new purpose not described here (for example user accounts, cloud saves, online multiplayer, shared online content, voice, or payment within the Game), we will update this policy before launching it and, where consent is the legal basis, the Game will ask for your consent before that data is collected.
13. Demo edition and integrity checks
The free demo collects the same categories, under the same consent, as the full Game, with an indication that the data comes from the demo. To protect the Game, the demo may check on launch whether its own files have been modified. If analytics consent has been given, the result of that check (which type of modification, the demo version and operating system, and how far you have played) may be sent once. No file contents, file paths or personal files are read or sent. These checks never affect the operation of the demo or your device, and no action is taken against any player as a result. If a player who used the demo later installs the full Game, the full Game may send, with consent, a single indication that it was upgraded from the demo. In the background the demo also requests one small public file from the Sites (demo_offer.txt), the price note shown in its menu, under the same terms as the update check in section 7.2; nothing about you is sent with it, and offline the note is simply not shown. The demo does not expire. Its settings and saves are stored in the same place on your device as the full Game's (see section 14), so the full Game continues where the demo stopped.
14. Storage on your device
The Game stores files on your device that are necessary to function, including settings, save files, your consent choices and age answer, the installation ID, logs, caches, and analytics waiting to be sent. These remain on your device under your control and can be deleted by uninstalling the Game and removing its data folder:
- macOS:
~/Library/Application Support/Mazell/TinyLogic/ - Windows:
%APPDATA%\Mazell\TinyLogic\ - Linux:
~/.local/share/Mazell/TinyLogic/
The Sites do not use cookies, local storage or similar technologies for tracking.
15. Service providers and recipients
We do not sell personal data and do not disclose it to third parties for their own purposes. We share it only with the following categories of recipients:
| Recipient | Role and purpose | Location |
|---|---|---|
| PostHog Inc. | Processor: analytics and crash report storage and analysis | United States |
| Google LLC (Google Cloud) | Processor: hosting the Community bot; automated content moderation of Community messages | United States |
| GitHub, Inc. | Processor: hosting the Sites and update files | United States |
| Discord Inc. | Independent controller: operating the Discord platform | United States |
| Leafo Games LLC (itch.io); Valve Corporation (Steam), when available | Independent controllers: sale, delivery and payment; purchase verification | United States |
| Professional advisers, authorities | Where necessary for legal, tax or accounting obligations, or under section 26 | As applicable |
We may replace or add processors that provide equivalent services under equivalent safeguards. Material changes will be reflected in this section.
16. International data transfers
We and our providers are located in the United States. If you are in the EU, EEA, UK or Switzerland, your personal data is transferred to the United States. We rely on the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum or Swiss equivalents) included in our providers' data processing terms, together with supplementary measures such as encryption in transit and data minimisation.
17. Retention
| Data | Retention |
|---|---|
| Analytics and questionnaire responses (categories A to D, F, G) | Up to 36 months from collection, then deleted or irreversibly de-identified |
| Crash reports (category E) | Up to 24 months |
| Data waiting on your device | Deleted from your device once sent, or immediately when you withdraw consent |
| Community moderation records | Up to 12 months, or longer where required to resolve an ongoing safety matter |
| Community content you post | Until you or we delete it, or the Community is closed |
| Purchase verification records | While the associated role exists, to prevent reuse of a key |
| Purchase and tax records | As required by tax and accounting law (typically up to 7 years) |
| Correspondence | Up to 24 months after the matter is closed |
| De-identified and aggregate data | Indefinitely (no longer personal data) |
18. Your rights: EU, EEA and UK
Subject to the conditions in the law, you have the right to:
- Access your personal data and receive information about its processing (Art. 15).
- Rectification of inaccurate data (Art. 16).
- Erasure ("right to be forgotten") (Art. 17).
- Restriction of processing (Art. 18).
- Data portability for data you provided on the basis of consent or contract (Art. 20).
- Object to processing based on legitimate interests (Art. 21).
- Withdraw consent at any time (Art. 7(3)).
- Not be subject to solely automated decisions with legal or similarly significant effects (Art. 22).
- Lodge a complaint with a supervisory authority, in particular in the member state of your habitual residence, place of work or place of the alleged infringement, or with the UK Information Commissioner's Office (ico.org.uk).
As explained in section 11, rights over pseudonymous analytics can be exercised only where you provide information that allows us to identify your data (Art. 11(2)).
19. Your rights: United States
19.1 California (CCPA/CPRA)
In the preceding 12 months we have collected, only with consent, the following categories of personal information as defined in the CCPA: identifiers (installation ID, optional itch.io username, IP address as received); internet or other electronic network activity information (categories C and D); and inferences (category G, non-sensitive, for product improvement only). Sources: directly from your device and from you. Business purposes: those in section 9, including debugging, quality and safety, and improving our services. We disclose this information only to service providers listed in section 15.
We do not sell personal information and do not share it for cross-context behavioural advertising, and have not done so in the preceding 12 months. We do not knowingly sell or share the personal information of consumers under 16. We do not use or disclose sensitive personal information. California residents have the right to know, access, delete, correct, and limit the use of sensitive personal information (not applicable, as we do not use it), and the right not to be discriminated against for exercising these rights.
19.2 Delaware and other states
Residents of Delaware, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa and other states with comprehensive privacy laws may have rights to confirm whether we process their personal data, access it, correct it, delete it, obtain a portable copy, and opt out of targeted advertising, sale and profiling in furtherance of decisions with legal or similarly significant effects. We do not engage in targeted advertising, sale or such profiling. If we decline your request, you may appeal by replying to our decision; we will respond to an appeal within the period required by law, and if the appeal is denied you may contact your state Attorney General.
19.3 Signals
Because the Game collects nothing without opt-in consent and the Sites do not track you, no additional opt-out is required. We honour Global Privacy Control and any other request to stop processing, however it is made.
20. Your rights: other countries
Players in Canada, Brazil, Switzerland, Australia, Japan, South Korea and other countries have the rights provided by their local laws, which generally include access, correction, deletion and withdrawal of consent. We extend the rights in section 18 to all players worldwide, regardless of where they live.
21. How to exercise your rights
- In the Game (immediate): Settings > Stats > off withdraws consent, stops collection and deletes data waiting on your device. Settings > itch.io link > off stops sending your username. Settings > Stats > ask again repeats the consent questions.
- By email: write to dubosemazell90@gmail.com. To locate analytics data, include your installation ID (the
installIdline insettings.jsonin the data folder listed in section 14) or the itch.io username you linked. Without one of these we cannot identify your analytics data (see section 11). For Community data, include your Discord username. - Verification: we may ask for information to confirm the request comes from you. We will not ask for more than necessary.
- Timing: we respond within one month under the GDPR and UK GDPR (extendable by two further months for complex requests) and within 45 days under US state laws (extendable by 45 days where permitted), and inform you of any extension.
- Authorised agents: where the law permits, you may use an authorised agent, who must provide proof of authority.
- Cost: requests are free, unless they are manifestly unfounded or excessive.
22. Discord community, bot and Rich Presence
22.1 Rich Presence
If the Discord desktop application is running, the Game may display your current activity on your Discord profile (for example "Building in sandbox" and a transistor count; never a project's name). The Game communicates only with the Discord application on your own device. Visibility is controlled by your Discord Activity Privacy settings.
22.2 Community and bot
When you participate in the Community, our bot processes: your Discord user ID, username, display name and roles; the content of messages you post and attachments you share; your submissions through bot commands (bug reports, ideas, builds, votes and their attachments, including any speech transcribed from submitted videos); activity used for community levels; and any itch.io download key you choose to submit with /verify, which is checked with itch.io solely to confirm a purchase and assign a role. Messages are analysed automatically to detect hate speech, harassment and spam, which may involve Google Cloud's content moderation service. Moderation actions are logged for moderators. Submitted bug reports and ideas may be used to improve the Game and may be displayed publicly in the Community. We may analyse Community activity in aggregate or de-identified form to improve the Game. Message content is not sold, not shared for advertising, and not used to train AI models offered to others.
23. Purchases and Steam keys
Purchases are processed by itch.io and, when available, Steam, which act as independent controllers of your payment and account information. We receive limited purchase records from them (such as the date, amount, currency, country, and the name and email address you gave the store) to fulfil orders, deliver Steam keys to existing buyers, handle refunds and support, prevent fraud, and meet tax and accounting obligations. We never receive your full payment card details. If you contact us to receive a Steam key, we use the details you provide only to verify your purchase and deliver the key.
24. Security and breach notification
We protect personal data with measures appropriate to the risk, including encryption in transit (TLS), restricted access limited to the developer, minimisation of the data collected, separation of identifiers from player identity, and the use of reputable providers bound by data processing agreements. No method of transmission or storage is completely secure. If a personal data breach occurs that is likely to result in a risk to your rights, we will notify the competent supervisory authority within 72 hours of becoming aware of it where required, notify affected individuals without undue delay where required by law, and take steps to contain it.
25. Automated processing
We do not make decisions producing legal or similarly significant effects based solely on automated processing, and we do not profile players for such decisions. Automated moderation in the Community may remove a message or apply a temporary timeout; you may request human review of any such action by contacting a moderator or us.
26. Disclosures required by law
We may disclose personal data if we believe in good faith that it is necessary to comply with a law, regulation, court order or valid legal process; to respond to a lawful request from public authorities; to protect the rights, property or safety of players, the public or us; or to detect, prevent or address fraud, security or technical issues. Where permitted, we will notify you of such a request.
27. Business transfers
If Tiny Logic or its assets are transferred to another entity (for example through the formation of a company owned by the developer, a merger, acquisition or sale), personal data may be transferred as part of that transaction. The recipient will be bound by this policy or a policy providing at least equivalent protection, and we will notify players of any material change in who is responsible for their data.
28. Changes to this policy
We may update this policy to reflect changes in the Game, our practices or the law. The effective date and version number at the top will change. Material changes will be announced in the Game's update notes and in the Community before they take effect. Where a change introduces a new category of data or a new purpose that requires consent, the Game will request your consent before any such data is collected. Previous versions are available on request.
29. Language and interpretation
This policy is written in English. Any translation is provided for convenience; if there is a conflict, the English version prevails to the extent permitted by applicable law. Nothing in this policy limits any right you have under mandatory law in your country of residence.
30. Contact and complaints
Controller: Mazell Smack-Dubose (Tiny Logic), Delaware, United States
Email: dubosemazell90@gmail.com
Community: discord.gg/tinylogic
If you have a concern about how we handle your data, please contact us first and we will try to resolve it. You also have the right to complain to your data protection authority as described in section 18, or, in the United States, to your state Attorney General.