18+ adults-only game · This public website uses SFW promotional material
Chronoromancer
Clockwork time mechanism

Legal information

Privacy Policy

A clear explanation of the limited pseudonymous game telemetry and first-party promotional-page analytics we collect.

Chronoromancer Studio ("we", "us") is committed to respecting your privacy. This policy explains what data we collect, why, and how it is handled.

What We Collect

During startup and gameplay, including when you start or load a game, Chronoromancer sends pseudonymous reports to our private server. Their purposes are distinguished below. Depending on the report, these may contain:

  • Random installation and session IDs — generated by the game and not derived from your identity or hardware.
  • Game version — which version of the game you are playing.
  • Operating-system environment — system name, version and architecture.
  • Non-unique hardware specifications — GPU vendor/model and renderer, CPU model family and logical-core-count range, and installed-RAM range. Supplementary startup integrity reports on Windows may also include motherboard manufacturer and product model. These product specifications are shared by many devices. Together with the operating-system environment, they support the security purposes and hardware configuration matching described below.
  • In-game progress data — such as current in-game day, era, character class, story progress, and redeemed codes.
  • A one-way hash of your character name — your character's name is scrambled using a cryptographic function before being sent. We do not receive the original name, and the hash is not intended to reveal it.
  • Gameplay statistics — pseudonymous totals and values used for security, customer support and bug diagnosis, and as the basis for aggregate audience, marketing and development analysis.
  • Player-selected settings — selected game language, optional adult-content toggles, or similar settings used for support and troubleshooting and, in aggregate, to understand language and feature use.
  • Internal integrity data — consistency checks used to detect corrupted, modified, pirated, or tampered game states.

Pre-Game Security and Compatibility Check

When Chronoromancer starts, its Pre-Game Security and Compatibility Check attempts to send a limited pseudonymous security report before the in-game Terms screen or normal gameplay. It may include operating-system, hardware and game-file integrity information. This report may still be attempted if startup is stopped because of an integrity concern. On Windows, a supplementary startup integrity report is attempted only when startup checks detect missing or failed telemetry delivery, missing hardware details, missing or changed game-package components, unexpected unapproved loose game scripts, or a match to a developer-designated hardware test configuration.

Promotional-Page Analytics

When you visit one of our promotional landing pages, we collect limited first-party event counts so we can measure whether a campaign leads to a real game download and launch. Events may include a confirmed page view, selection of a download link, copying a promotional code, and selection of a Patreon or Afdian support link. Records may include the page language and path, promotional code, campaign and source values supplied in the page URL, chosen platform or download channel, support-link target, and the server receipt time. We do not use cookies or browser fingerprinting. A random value is stored only in the browser's session storage and is used to prevent duplicate counting. The server stores only a one-way hash of that value for up to 48 hours, then deletes it. Longer-term reporting consists of daily aggregate counts.

Network Data

We do not intentionally store IP addresses or user-agent strings in our promotional analytics tables. Our hosting, content-delivery, and database providers necessarily process connection data to deliver and secure their services and may retain operational or security logs under their own policies.

Pseudonymous Installation Identifier

The game may generate a random installation identifier stored locally with the game's persistent data. This identifier is not based on your device hardware, real identity, advertising ID, or account information. It is used to group pseudonymous game sessions for security, customer support and troubleshooting, and to produce the aggregate audience, marketing and development statistics described below.

Detailed Gameplay Statistics

The game collects pseudonymous gameplay statistics. We use relevant individual records for security, customer support and bug diagnosis, including missing progress, items or rewards. Aggregate totals and percentages help us assess audience and campaign activity, identify balance issues, prioritize translations and plan future content. Statistics may include:

Combat & Exploration

  • Enemies defeated and bosses beaten
  • Dungeon steps taken and flee attempts
  • Back alley searches and break-and-enter attempts
  • Locations visited

Character Progression

  • Equipment levels, key items collected, character proficiency class, and current crystal balance

Social & Story

  • Current story beat reached, NPC relationship progress, and intimate conversations completed

Brothel Management

  • Workers recruited, training sessions completed, and brothel ownership status

Minigames & Activities

  • Minigame results, scores, winnings, and feature engagement counts

Extras Gallery

  • Overall gallery completion percentage and whether the gallery has been fully completed

World & Time

  • Time spent in each era, time spent in dungeons and special realms, total playtime, and longest session

Miscellaneous

  • Caterpillars clicked, baths taken, meals cooked, Christmas gifts given, rare catches, and accomplishments

Internal Integrity

Telemetry may include whether the game session was a fresh launch or a save load, which crystal redemption codes have been entered, pseudonymous installation grouping data, and internal consistency checks used to detect corrupted, modified, pirated, or tampered game states.

A once-per-launch integrity record may recursively examine executable Ren'Py files and archives inside Chronoromancer's own installation folder. For reportable files, telemetry may include a normalized relative filename, file type, byte size, a full or sampled one-way SHA-256 hash, whether Ren'Py discovered, admitted, loaded, ignored or rejected the file, and locally detected target categories such as gallery, entitlement, telemetry, integrity, save, input or loader systems. It may also include observed hashes and sizes of official game archives, coarse runtime configuration flags, scan-health information, and one-way fingerprints of selected Ren'Py loader functions. Approved known modifications may be omitted. We do not transmit file contents or absolute system paths. Automated file checks examine only files within Chronoromancer's installation folder.

What Our Game Telemetry Does Not Collect

  • Your real name, email address, username, computer name, or account credentials
  • Device-specific hardware identifiers such as firmware UUIDs or hardware serial numbers, MAC addresses, advertising IDs, browser fingerprints, cookies, or precise location data
  • Information from files outside Chronoromancer's installation folder. Non-unique operating-system and hardware specifications are system environment data, not a scan of outside files.
  • Your IP address in our game telemetry database. Your IP address may be used by network systems to establish the HTTPS connection, but it is not intentionally stored in our game telemetry database.

These limits describe automatic game telemetry. Information you voluntarily provide when contacting us for support, such as contact details or screenshots, is handled as part of your support request.

Why We Collect This Data

Startup security reports are used only for anti-tamper checks, detecting licence bypass or unauthorized redistribution, investigating repeated abuse, and checking failures or mistaken blocks. We do not use startup hardware or game-file security reports for marketing, audience analysis, performance analysis or product planning.

We use relevant gameplay records to investigate tampering and paid-access bypasses, respond to customer-support requests, check redeemed-code and access problems, diagnose bugs, and help resolve missing progress, items or rewards. Individual records are reviewed for security, support and related troubleshooting. When you contact us, information you provide, such as screenshots or an installation ID, may help us locate and interpret relevant reports.

For audience, marketing and development planning, we use aggregate totals and percentages, such as language usage, feature use, player return rates and campaign performance. This helps us assess promotions and plan translations, balancing and future content. The underlying gameplay reports are collected as pseudonymous installation/session records before aggregation; viewing aggregate results does not make those underlying records anonymous.

Promotional-page analytics is separately described above.

How Data Is Stored

Game telemetry is transmitted via encrypted HTTPS to a private database. Relevant extracts may also be held in private support or security case records. Telemetry and case records are not sold, shared for advertising, or made accessible to the public.

Data Retention

Routine game telemetry is automatically deleted after up to 28 days. Relevant extracts preserved for a support case or security investigation may be retained longer while needed to resolve the case or document its findings. Aggregate statistics may be kept longer when they no longer identify or single out a particular installation, session or player. Promotional-page analytics has the separate retention periods described above.

Hardware Configuration Matching and Tracking Limits

For the security purposes described above, we compare combinations of reported operating-system and hardware specifications across reports, sessions and installation identifiers to recognize recurring configurations and relate repeated attempts, including records with different installation IDs. Many devices share these specifications, so a match is not proof that records came from the same device or person. We do not collect motherboard serial numbers, firmware UUIDs or MAC addresses, or generate a persistent identifier from those values. These records are pseudonymous, are not necessarily anonymous, and remain subject to this policy's privacy protections.

On Windows, startup checks in both the Community and Promotion editions also recompute a SHA-256 hash from the normalized CPU model, set of display-adapter models, and motherboard manufacturer and product model, and compare it with an embedded restriction list. This check does not use installation IDs and can prevent launch across installations or after reinstalling, including an otherwise clean copy. Different devices with the same combination can match. Startup may stop before a game window or explanation appears, and a reference ID is not guaranteed; an attempt to send a startup security report may already have occurred.

We do not use browser fingerprinting, third-party advertising trackers, or identifiers intended to track you across unrelated websites or services. Promotional-page analytics uses no cookies and only a random, temporary browser-session value for duplicate prevention. The game's random installation identifier, if present, groups pseudonymous game sessions for security, customer support and troubleshooting, and for the aggregate audience, marketing and development statistics described above.

Your Rights

Where applicable under law, you may request access to, correction or deletion of your personal data, restriction of processing, or data portability, and you may object to processing. You may also lodge a complaint with a competent data protection authority.

Contact us at chronoromancerstudio@gmail.com to exercise these rights, ask privacy questions, or request review of a suspected mistaken block. Because automatic game telemetry does not include real-world contact details or account credentials, we may need information from you, such as the approximate launch time, game version and hardware details, or an installation or reference ID if available, to locate relevant records. A reference ID is not required to contact us. If we cannot reasonably verify or locate the records, we will explain the limitation and what further information, if any, is needed.

Changes to This Policy

If we change what data we collect or how it is used, this policy will be updated.

Contact

Questions or concerns? Contact us at chronoromancerstudio@gmail.com.