Night Audit Privacy Policy

Last updated: 8 September 2026

Night Audit is developed and published under the registered trade name InfoSci, operated by a sole proprietor in Croatia. Privacy requests may be sent to support@nightaudit-game.com or through the Night Audit support contact linked from its Steam store page. That contact is monitored by the operator of InfoSci.

This policy covers the optional diagnostics, bug-reporting and feedback features inside Night Audit. Steam separately controls the account, purchase, payment and platform information it processes under Valve's own privacy terms.

Summary

Night Audit does not contain advertising and InfoSci does not sell player data. The game does not send gameplay diagnostics until the player explicitly opts in. Bug reports and feedback are sent only when the player submits their respective forms. The diagnostics choice can be changed at any time under Options ▸ Diagnostics.

The submitted information is pseudonymous. It is associated with a random Firebase identifier stored by that installation of the game, but it is not associated by InfoSci with a Steam ID, player name or email address.

Information processed

Optional finished-night diagnostics

When diagnostics are enabled, the game submits a summary after a shift. It may include:

• build version, operating-system family and selected difficulty or modifiers;
• random night seed, duration, party size and final hotel rating;
• incidents raised and resolved, and aggregate activity for numbered player slots; and
• a pseudonymous random installation identifier.

The game does not include player display names or Steam IDs in these summaries. InfoSci uses the summaries to balance the game, identify unreliable mechanics and understand whether a build performs as intended. The legal basis is the player's consent. Disabling diagnostics stops the creation and upload of future summaries.

Bug reports

A bug report is sent only after the player opens the form, enters a description and selects Send. Before submission, the form identifies which attachments are available. A report can contain:

• the description entered by the player;
• build and current-shift information;
• a screenshot captured for that report;
• up to the last 512 KB of the Unity player log; and
• the newest crash dump from the preceding day, when one exists and is below the size limit.

Before queuing the report, the game removes recognizable usernames, local file paths, email addresses, IP addresses and Steam-ID-shaped values from the log. Automated removal reduces risk but cannot guarantee that arbitrary text or a screenshot contains no identifying information. Players should review what is visible and avoid entering personal information in the description.

Feedback

Feedback contains the tags and free-form comment the player chooses to submit, plus the build version and, when available, aggregate information about the most recent shift. It does not attach a screenshot, log or crash dump. Submitting the form is the player's request to transmit that message and is independent of the background diagnostics setting.

Identifiers and network data

The game creates a Firebase anonymous-authentication account when it first needs to upload something. Its random UID and refresh token are stored locally so that retries work and multiple sessions from the same installation can be recognized. This makes the information pseudonymous personal data, not anonymous data.

InfoSci does not intentionally store the connection IP address in the submitted Firestore documents. As with any internet service, Google and network providers necessarily process IP addresses and technical request information to deliver, secure and operate the service.

Recipients and location

The submissions are hosted using Google Firebase and Google Cloud. Firestore is configured for the europe-west1 region. Google processes the information as a service provider to InfoSci. Access from the shipped game is create-only: the game cannot list, read, alter or delete submitted records. Administrative access is restricted to the operator of InfoSci and providers needed to operate the service. Information is not shared for advertising.

Retention

• Finished-night diagnostics and bug reports are scheduled for deletion 365 days after submission.
• Bug-report files in Cloud Storage are scheduled for deletion after 365 days.
• Voluntary feedback is scheduled for deletion 730 days after submission so it can be compared across major versions.
• A shorter period may be used when the information is no longer needed, a valid deletion request is received, or continued storage is no longer lawful.

Deletion jobs may complete after the stated expiry time rather than at the exact minute. Local queued reports remain on the player's computer only until they are uploaded or discarded by the queue limit.

Player choices and rights

Players may disable future diagnostics under Options ▸ Diagnostics without affecting gameplay. They may also request access, correction, deletion, restriction or a portable copy of information associated with them, object where applicable, and withdraw consent for future processing. A request can be sent to support@nightaudit-game.com or through the support/privacy contact on the Steam store page.

Because no name or Steam ID is stored with a submission, InfoSci may need the random installation identifier, approximate submission time, report text or other details to locate a particular record. InfoSci will not collect additional identity information merely to identify a person when it is not otherwise necessary. Players may also lodge a complaint with the Croatian Personal Data Protection Agency or the supervisory authority where they live.

Deleting local game data removes the saved identifier and pending local queue, but it does not by itself identify or delete information already submitted.

Security

Firebase rules restrict the game client to creating narrowly shaped records and bounded bug-report attachments. The client cannot read the collected database. No internet service can be guaranteed completely secure; InfoSci reviews access, retention and abuse controls and will respond to confirmed incidents as required.

Children

Night Audit is not directed to children and InfoSci does not knowingly seek personal information from children through these features.

Changes

Material changes will be identified through game or Steam update notes, and the date at the top of this policy will be updated. Where a change requires new consent, the game will ask before the affected processing begins.