Privacy policy

Last updated 26 October 2026. Covers the game Kamira (including playtests), the websites daymarkgames.com and kamira.daymarkgames.com, and the bot on our Discord server.

In short

The game sends diagnostics only if you choose Share diagnostics. You can change that any time in Settings → Diagnostics.
A bug report is sent only when you press Send, and the panel shows what it contains.
We don't store your Steam name, Steam ID or IP address. The game removes them, your Windows user name and e-mail addresses from its logs on your computer before anything is sent.
Reports are stored on our server in Amsterdam, the Netherlands, and used only to fix and improve Kamira. We never sell them or use them for advertising.
To see or delete your data, e-mail [email protected] with the diagnostics ID shown in Settings → Diagnostics.

1. Who we are

DaymarkGames is an independent game studio in Türkiye. We decide how the data described here is used (we are its "data controller"). Contact: [email protected].

2. What the game sends, and when

Diagnostics are off until you choose Share diagnostics in the dialog the game shows on first launch. With diagnostics on, the game sends these reports:

Report	When	What it contains
Hardware summary	At launch, if your hardware or settings changed or 30 days have passed	Processor and graphics card model, memory, operating system version, screen resolution and refresh rate, the game's graphics settings.
Match performance	At the end of each match	Frame rate and frame-time statistics, processor and graphics timings, memory use, loading times, network delay and disconnects, the map positions where the frame rate was lowest, the errors the game logged (a short code and the first error message), and match facts: length, number of players, your role, whether you hosted and which side won.
Crash report	At the next launch after the game crashed or was closed unexpectedly	How the game ended (crash or unexpected exit), what was happening (scene, match phase, your role, number of players, time since launch), the error line that best explains it, the last part of the game's log file (cleaned, see below) and, after a real crash, the crash dump (see below).
Match statistics	At the end of each match, sent by the player who hosted it	Which side won, match length and match settings.

Bug reports are separate: the game sends one only when you open the bug report panel (F8, or Pause → Report a bug) and press Send. Because you decide each time, this works even when diagnostics are off. A bug report contains what you type (description, category, and a contact such as a Discord name if you add one), the screenshot if you leave "Include screenshot" on, the last part of the game's log if you leave "Include game log" on (cleaned), and the scene, match phase, number of players, frame rate and hardware summary code.

Every report also carries: a random installation ID the game creates on your computer (not linked to your Steam account), a random ID for the current game session, the report code shown to you (like KMR-7F3A9C2D), the game version and build, the Steam beta branch, the time, and your diagnostics choice. Our server adds the time it received the report.

How logs are cleaned

Before a log leaves your computer, the game replaces Steam IDs with a short code, the player and lobby names it has seen with placeholders such as <player#1>, your Windows user name and user folder paths, your computer's name, IP addresses and e-mail addresses. What remains are the game's own technical messages.

Crash dumps

After a real crash, the game engine writes a crash dump: a snapshot of part of the game's memory at the moment it crashed. It is what lets us find the code that failed. It can't be cleaned the way a log can, so it may contain fragments of whatever the game had in memory, such as player names or chat from that match, and file paths that include your Windows user name. The game sends a dump only if it is 8 MB or smaller. We use it only to find the crash, never share it, and delete it on the schedule in section 7.

Screenshots

A bug report's screenshot shows your screen at the moment you opened the panel, including any names or chat visible on it. Switch off "Include screenshot" if you don't want to send it.

3. What we never collect

your Steam name, Steam ID, friends list or game library;
your IP address (it is seen while a report is delivered, see section 6, but not stored);
voice chat;
files on your computer other than the game's own log, its crash dump and a screenshot you approve.

We don't sell data, share it with advertisers, or use it to profile you.

4. Why we use it, and on what legal basis

We use reports to find and fix crashes and bugs, to make the game run well on more computers, and to balance the game. The legal basis is your consent (GDPR Article 6(1)(a); in Türkiye, explicit consent under KVKK Article 5(1)): you give it with Share diagnostics, and for a bug report by pressing Send.

You can withdraw consent any time in Settings → Diagnostics. The game then stops sending reports and deletes the ones still waiting on your computer (bug reports you already sent stay queued until delivered). Withdrawing doesn't undo what was sent before, but you can ask us to delete it (section 8).

5. Where it is stored and who can see it

Our server at Oracle Cloud in Amsterdam, the Netherlands. Reports are stored there and never published or shown on the web.
Cloudflare carries the connection to our server and filters attacks.
Discord: a private channel only we can read receives a one-line summary of each crash and bug report: the report code, game version, scene and phase, the error line, and the first 300 characters of a bug description. Discord is based in the United States.
AI coding assistants we use to build the game (currently Google's Gemini, through Antigravity, and Anthropic's Claude): to investigate a crash or a bug, they may read the technical parts of reports on our instructions: cleaned logs, crash details and bug descriptions. They never receive your contact details, screenshots or crash dumps. Both companies are based in the United States.
Our development computer: we download reports to study them. They are never put in source control or shared, and they are deleted on the schedule in section 7.

Nobody else receives it. For players in Türkiye, storing data in the Netherlands, sending summaries to Discord and letting the AI coding assistants above read reports is a transfer of personal data abroad. The risk is that the data is then also subject to those countries' laws. You agree to this transfer when you choose Share diagnostics or send a bug report; our KVKK information notice (in Turkish) explains it in detail.

6. Network addresses

Like every connection on the internet, a report reaches Cloudflare and our server together with your IP address. Our server uses it only in memory to limit how many reports one address can send, and stores only a salted one-way hash of it (a scrambled code that can't be turned back into the address) to spot abuse. We keep no request logs with IP addresses.

7. How long we keep it

Logs, crash dumps and screenshots: deleted 30 days after we download them to study, and after 12 months at the latest.
The rest of a report (the numbers and codes described in section 2): deleted after 24 months.
Copies on our development computer: logs, crash dumps and screenshots are deleted 90 days after we download them; the rest after 24 months.
Discord summaries: deleted after 12 months, or within an hour of a deletion request being processed.
Reports waiting on your computer (not yet delivered): deleted after 14 days, and at once when you turn diagnostics off.

8. Your rights

You can ask to see your data, get a copy of it, correct it, delete it, restrict or object to its use, and you can withdraw your consent. To do so, e-mail [email protected] with your diagnostics ID from Settings → Diagnostics. We don't know who you are, so that ID is the only way we can find your reports. For entries made with the Discord bot (section 12), tell us your Discord name instead. We answer within 30 days, free of charge.

You can also complain to a data protection authority: in the EU, the one in your country; in Türkiye, the Personal Data Protection Authority (kvkk.gov.tr).

9. Children

Kamira is rated 16+ on Steam and is not meant for anyone under 16. We don't knowingly collect data from children under 16. If you think a child has sent us data, e-mail us and we will delete it.

10. Security

Reports travel only over encrypted connections (HTTPS). Logs are cleaned on your computer before they are sent. Our server accepts reports but never shows them on the web; they can be downloaded only with a key that can do nothing else. The server accepts logins only with cryptographic keys and installs security updates automatically.

11. Our websites

daymarkgames.com and kamira.daymarkgames.com set no cookies and carry no advertising or tracking. Cloudflare delivers the pages and may count visits with its cookie-free Web Analytics. The pages load fonts from Google Fonts, and the Kamira page loads its video player from Cloudflare's cdnjs and its trailer from Steam's servers; to do that, your browser contacts those services, which see your IP address. If you choose a language with the EN/TR links, your browser remembers that choice locally; it is never sent to us.

12. Our Discord server

On our Discord server, the bot's /bug and /feedback commands save what you submit together with your Discord name on our server, so that we can follow up, and post it in the #bug-reports and #feedback channels that the server's members can read. Everything else on Discord is covered by Discord's own privacy policy.

13. Changes

When we change this policy, we update the date at the top. If a change affects what the game sends, the game asks for your choice again.