Serakki Privacy Policy
Last updated 2026-10-15
The Serakki website does not track you, and Serakki Mini, the full game and the Editor do not send me telemetry or automatic crash reports. Hosting providers process requests to deliver the website and downloads. I receive personal data if you choose to contact me or send me files.
1. Who is responsible
I am Marek Hanzal, a self-employed individual (sole trader), identification number (IČO) 87911418, with my business address at Mezirolí 309, 362 25 Nová Role, Czechia. You can contact me about privacy at support@serakki.dev or by post at this address.
I am the controller of personal data I receive and use for Serakki enquiries, support and legal obligations. This policy covers serakki.dev, Serakki Mini, the full Serakki game and its Editor. External hosting, stores and communication platforms have their own responsibilities and privacy notices.
3. Hosting and downloads
The website at serakki.dev and its hosted development deployments are delivered through Bunny Storage and CDN. Bunny processes the technical request information needed to deliver them. CDN request logs are available to me with IP anonymisation enabled; they are used for delivery troubleshooting, not visitor profiling.
The hosted API runs on Neon. Its current hello and health endpoints do not receive gameplay or project uploads or implement a user login flow. Bunny and Neon also process service information under their own notices.
Mini download links lead to GitHub Releases. Following them sends a request to GitHub, whose privacy notice applies to its delivery and logging. I do not maintain a visitor or download history identifying you.
4. Offline applications and local files
Serakki Mini, the full game and the Editor do not automatically send me usage data, gameplay history, diagnostic reports or your files. Playing does not require a Serakki account. Saves, settings, authored projects and imported resources are stored locally, not uploaded to a Serakki service.
The applications automatically write local technical logs for troubleshooting. A failed game session can also leave a local incident snapshot with game data. These files stay on your device unless you share them. Local logging is separate from the voluntary Export Diagnostics action described below.
Your operating system, store client or a backup/synchronisation service you use may process local files under its own settings. Optional Editor agent connections are described in section 10.
5. What Export Diagnostics contains
Export Diagnostics in the application menu opens a save dialog and creates a ZIP file at the location you choose. Cancelling creates no archive. Exporting does not upload the ZIP, send an email or notify me. You decide whether to inspect, keep, delete or send it.
The archive contains the following:
- A manifest with the export time, application version, operating-system platform and release, CPU architecture, and display dimensions and scale factor.
- Filtered support logs: timestamps, severity and technical summaries; for installed games and Editor Board sessions, session identifiers, game/package or project versions, gameplay events and performance or failure information needed to reproduce a problem. Session identifiers are not an account or a persistent player identifier.
- The last played game's package identifier, version and content hash, plus its available save slots and backups. Saves contain gameplay progress, state and authored game content.
6. What the standard export leaves out
The standard ZIP does not include game packages or artwork/audio bundles, private Editor project files, detailed application logs, MCP tool logs or the local incident snapshot. It includes the support-log files and last-played game saves described above.
Detailed error bodies are omitted from the support log. Structured support events redact fields designated for email addresses, paths, project identifiers, credentials, tokens and raw errors. Installed-game and Editor Board support logs can still contain authored Item and production Line names and identifiers, gameplay events and state; saves can contain authored game content. Excluding complete Editor project files does not remove this content from the technical evidence. The export is designed for technical troubleshooting, not to collect contact details or sensitive personal data. This filtering is not a guarantee that every possible piece of personal information is removed. An archive may constitute personal data in my support records when associated with its sender.
Review files before sharing them, including authored content in support logs and saves. Detailed local logs or files you attach separately may additionally contain filesystem paths, raw errors or complete project files that the standard export excludes. Do not send passwords, access tokens or unnecessary personal information.
7. Contact and voluntary support
If you email me, I receive your email address, any name you provide, the message, ordinary email metadata and any attachments you send. The support@serakki.dev mailbox is provided by Webglobe, s.r.o., a Czech provider, which processes email content and delivery data to operate the mailbox.
If you contact me on Discord, I receive the account name, messages and attachments you choose to share. Messages in public community channels can also be read by other members. Discord processes platform data under its own privacy policy.
Contact and diagnostic sharing are voluntary. You can browse and play without sending them. Without information relevant to a request, I may be unable to investigate it. This policy does not create a support entitlement beyond the license or applicable law.
8. Purposes and legal grounds
I use submitted information only as needed to answer enquiries, investigate technical problems, fix defects, handle complaints and privacy requests, or establish, exercise or defend legal claims. I do not sell personal data or use support correspondence for advertising. I do not make decisions about you through automated decision-making or profiling.
Under the GDPR, the legal grounds depend on the request: legitimate interests in responding to enquiries, troubleshooting and protecting legal claims (Article 6(1)(f)); performing a contract or taking steps you request before a contract (Article 6(1)(b)), where applicable; and complying with legal obligations (Article 6(1)(c)). Browsing, downloading or sending a message is not treated as blanket consent to personal-data processing.
9. AI-assisted diagnostic analysis
I may use OpenAI Codex to analyse standard diagnostic archives you voluntarily send me, solely to investigate technical problems and develop fixes. From your support submission, I provide only the diagnostic archive or relevant extracts from it. I do not provide your email or Discord correspondence, contact details, sender identity or other attachments, and I do not add information identifying you to the analysis.
Standard diagnostic archives contain the filtered technical logs, application and system information, and available last-played game saves described above. Session identifiers identify individual game sessions, not an account or a persistent player profile. The application creates the archive locally; exporting it does not automatically send anything to me or OpenAI.
I use a personal OpenAI account with contributions to model improvement enabled. With this setting, OpenAI may also use content processed through the account to improve and train its models under its applicable terms and data controls.
10. Optional agents and external services
The Editor can connect to an agent through MCP if you enable and configure it. A connected client can receive project information, artwork previews and Board screenshots, and use the tools you make available. A remote connection can also involve a tunnel provider. Those connections are your explicit choice; they are not telemetry sent to me. The connected agent and other providers may process the supplied content under their own terms and privacy policies.
Links to Discord, YouTube, Steam, GitHub and other websites open external services. Store purchases and accounts are handled by the store. These providers process information under their own privacy notices when you use their services.
11. Recipients and international processing
Information you send is available to me and to the providers needed to deliver and store that communication, including Webglobe for email and Discord when you use it. I may disclose necessary information if required by law or to resolve a legal claim. I do not publish your submitted diagnostic archive as part of routine support.
OpenAI receives the diagnostic content I provide for AI-assisted analysis. Its processing and retention are governed by the terms, privacy policy and data controls applicable to the service and account used. Processing may take place outside the European Economic Area, including in the United States. Further information is available in OpenAI's Europe Privacy Policy linked below.
Webglobe's published notice describes recipients in Czechia, the EU or countries covered by an adequacy decision. GitHub and Discord describe international processing, including in the United States, and their transfer safeguards in their privacy notices. This does not mean that all data handled by external services stays in the EU.
Any transfer I arrange of personal data outside the European Economic Area must comply with the GDPR, using an applicable adequacy decision or appropriate safeguards. You can contact me for information about the recipients and safeguards applicable to your data, including a copy of relevant safeguards where applicable.
12. How long information is kept
Local application logs rotate within fixed size and file-count limits; an incident snapshot is replaced by a later failed session. Exported ZIPs, saves and projects remain on your device until you remove them or your own storage system does so. I cannot remotely access or delete those files.
For information you send me, retention depends on whether the enquiry or investigation remains open, whether follow-up is needed and whether the information is still necessary to resolve the problem. I delete personal data when it is no longer needed for these purposes. Material needed for a legal obligation or claim may be kept for the applicable statutory retention or limitation period. Where possible, a technical defect record is kept without unnecessary sender information.
I keep submitted diagnostic archives only while analysing the reported issue and, where applicable, developing a fix. Once that work is complete, I delete the archive, whether it results in a bugfix or no change. I do not retain it for later support. OpenAI applies its own applicable retention rules to content processed through its services.
Hosting and communication providers apply their own retention and backup rules. I cannot access or delete GitHub Pages visitor logs; requests about GitHub's own processing should be addressed to GitHub.
13. Your privacy rights
Where the GDPR applies, you may request access to your personal data, correction, erasure, restriction of processing and portability where its conditions are met. You may object to processing based on legitimate interests on grounds relating to your situation. These rights are subject to the conditions and exceptions in applicable law.
Send requests to support@serakki.dev or my postal address in section 1. I will respond without undue delay, normally within one month; a lawful extension will be explained. I may need proportionate information to confirm your identity. The discretionary nature of game support does not limit my privacy-law obligations.
You can complain to a supervisory authority, including the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Praha 7, Czechia, or the authority in your place of habitual residence, work or the alleged infringement.
14. Policy updates
This notice describes the current website and applications. Changes will be published here with a new update date. A future tracking or data-collection feature would require an updated notice and, where legally required, a separate choice or consent before it starts. This policy is information about processing, not a request to agree to optional processing.
Privacy contact: support@serakki.dev.