Privacy Policy

1. Scope and data controller

This policy covers emtilabs.com and Hollow Playground: Hide & Seek, provided by Erhan Toros, an independent developer operating as eMTi Labs in Türkiye. Contact support@emtilabs.com for privacy questions and data requests. This policy covers the website, test builds and released game versions. Processing described for a feature depends on that feature being offered and used in the relevant version and platform; not every feature is available everywhere.

2. Website and correspondence

The current promotional website has no account registration, payments, contact form, advertising or visitor analytics. Its code uses no cookies or browser storage. Our host, Netlify, may process technical data such as IP addresses, requested pages, browser information and connection times to deliver and protect the website. If you email us, your address, message and attachments are processed through our Google Workspace email service to respond to your request. Please avoid sending unnecessary sensitive information.

3. Google sign-in in the game

When you choose Google sign-in, Google authenticates your account. We do not receive your Google password. The identity token issued by Google is sent to Unity Authentication to verify your account and create or retrieve a game identity. This involves your Google account identifier and Unity player ID; the token may also contain email and basic profile information provided by Google. Sign-in does not request access to your Gmail messages, Drive files or contacts. Sign-in and session data is used for authentication; we do not sell personal data.

4. Username/password and account recovery

In versions offering this method, the username and password are sent over a secure connection to Unity Authentication. The game does not save passwords in PlayerPrefs, logs or project files. This method does not collect or verify an email address; the username is separate from the display name. Linking adds credentials only to the same authenticated Unity player identity; accounts are not merged by similar names or email addresses. When recovery is enabled, the current password is checked with Unity through our game server, which processes it in memory for this operation without storing it. A private recovery key is generated on the device and shown to the player; the server stores only its hash, creation time and bounded retry state. During recovery, the key and new password are processed through a secure connection; a successful reset consumes the key. Knowing a public ID or username is insufficient. Do not email your key or password to support. Recovery is not represented as enabled until server permissions and real acceptance have been completed.

5. Device and service data

Online connections may involve IP addresses, app/SDK versions, connection times, installation or session identifiers and error information for service operation and security. The Unity SDK may keep session data on your device to maintain sign-in. Device details, error descriptions and screenshots you voluntarily send to support are used to investigate your issue. Do not send passwords or sign-in tokens.

6. Diagnostics and problem reports

In new versions containing this feature, automatic diagnostics are off by default and can be enabled or disabled in Settings → Account → Share error and performance data. Turning off takes effect immediately: the unsent automatic queue is cleared and any active automatic client request is cancelled. Records already received by the server remain subject to the retention period below. Manually submitting through the separate Report a problem screen does not enable automatic sharing. When enabled, the managed error type, up to 8 short method names, repeat count, app version/build, device model and operating system are sent over HTTPS to our game server, linked to the authenticated game account. Raw exception messages, file paths, chat and microphone recordings are not included automatically; passwords and tokens are not recorded. A main-thread stall longer than ten seconds may be reported when the app resumes responding. This is not a claim to capture every native crash or Android ANR. You may send a short description through Report a problem; the filtered text and technical information are shown before sending. Do not enter passwords, tokens, chat or someone else’s sensitive data. Similar events are grouped; retried submissions are counted only once. Automatic reports are accepted at most once per 5 minutes and 10 times a day; manual reports once per 30 seconds and 10 times a day. The device queue is limited to 32 groups/64 KiB; entries older than 7 days are removed when the app runs. Manual drafts are not saved to disk. At most 64 server groups and their receipts expire 30 days after the initial record and are removed by scheduled maintenance; repeats do not extend this period. Account deletion also covers these diagnostics; additional backup periods are described below. Google Play Android vitals is a separate platform diagnostics flow subject to Google’s settings and terms.

7. Profile, progress, missions and inventory

Player names/public IDs, optional profile preferences, social relationships, room admission, content ownership, Cash and Hollow Cash records are processed by the game service on Google Cloud Run and its PostgreSQL database. Unity Cloud Save compatibility/projection records may also exist. Personal HUD preferences are stored on the device. Live match rewards, rank and Pass progression remain closed until trusted match results and advertising verification are accepted; this notice does not promise unavailable features.

8. Multiplayer and visible information

For online matches, Photon (Exit Games) processes IP addresses, game user identifiers, room/session details and in-game movement/state data to establish connections and synchronize matches. Your chosen display name, character, cosmetics and match actions may be shown to players in the same session. Do not put an email address or sensitive information in your display name. Optional Photon Voice transmits microphone audio to authorized room participants, with permission, mute and transmit controls. Game code does not record audio files. Encrypted transport is not a claim of end-to-end encryption. Social messages, blocks and abuse reports may be processed by the service. Do not share personal contact information in your profile. Permissions and safeguards required for the particular country and service apply separately; being aged14–17 is not itself a blanket online-access ban.

9. Written chat between friends

In versions offering this feature, written messages are sent only between mutual friends; blocking stops communication. Message content, sender/recipient game identifiers and server timestamps are processed by our game service over HTTPS using an authenticated session. You must accept the chat rules before sending. Messages become unreadable 24 hours after sending according to the server clock; expired rows are removed by scheduled maintenance and when the relevant conversation is accessed. A maintenance interruption may delay physical cleanup, but the API still excludes expired messages. Bodies are encrypted with AES-256-GCM before reaching the database; the authorized game service can decrypt them for delivery, so this is not end-to-end encryption. The game does not write message content to application logs or persistent on-device chat history; an open screen holds it temporarily in memory. Limits are 300 characters, at least 2 seconds between sends, 20 per minute and 200 active sends within 24 hours. Encrypted copies in backups and transaction logs may remain for the additional periods below; 24 hours does not mean physical destruction of every backup. You can block a player or use Report from the chat screen. Chat is not automatically attached to reports; your short description is processed separately as an abuse report and is not subject to the chat’s 24-hour expiry. Do not copy private information or an entire conversation into a report. Security reports require a separate erasure/retention review; no automatic final expiry has yet been set. Support may apply a temporary restriction to message sending only; game progress and purchased entitlements are unchanged. The restriction record contains a case ID, short reason code, account-identifier hash and expiry time. Its effect ends automatically at expiry and support can restore sending. Final record erasure is reviewed separately with security reports.

10. Store, payments and Royal Pass

Where offered, Android purchases use Google Play Billing Library and the game server verifies purchase evidence with Google; Unity IAP is not used. Product/transaction IDs, purchase tokens, status, delivered entitlements and refund records are processed; the game does not receive card or bank details. Google Play displays the price before payment. The ten planned products are one-time permanent entitlements. The starting robot and R621 remain free. remove_ads removes only forced ads; optional rewarded ads are excluded. This service is not sold without an accepted real ad provider and verification. A verified rewarded ad can bring eligible base XP and Cash to 1.5 times their base amount; HC is excluded, and neither an unviewed ad nor duplicate evidence grants a reward. New sales remain closed pending real provider and payment acceptance.

11. Game configuration and service quality

In versions using Unity Remote Config, player or installation identifiers and technical connection information may be processed to deliver catalogue, event, version compatibility and game configuration settings. Technical records relating to sign-in, saves, store or match errors support operations, troubleshooting and abuse investigations. These functions do not authorize advertising profiling. Before introducing advertising or optional analytics tools, the provider, data types, purposes and required permission/preferences will be separately disclosed.

12. Purposes, collection and legal grounds

Data is collected electronically through website visits, sign-in requests, technical service communications and emails you send. Processing necessary to provide requested sign-in, saves, online play, rewards, purchases and support relies on entering into or performing a contract. Necessary technical processing to prevent abuse and keep systems secure relies on legitimate interests balanced against your rights. Where a legal obligation or the establishment, exercise or defence of a right requires records, the corresponding legal ground applies (including Article 5(2) of Türkiye’s Personal Data Protection Law). Where processing requires consent, it is requested separately; reading this page or visiting the website does not itself give explicit consent.

13. Providers and transfers

Netlify hosts the site; Google Workspace handles support email; Google provides identity and Play payments; Unity Authentication/Cloud Save/Cloud Code provide game identity and related records; Google Cloud Run/PostgreSQL provide the game data service; Photon provides multiplayer and voice. If the photo service is enabled, Google Cloud Storage and Vision will provide storage and verification/moderation. Necessary data is sent for the relevant function. International transfer conditions, provider contracts and safeguards required by applicable law must be met separately; reading this notice is not itself consent or transfer authorization. Authorities receive necessary information only under valid legal requests.

14. Retention and transport security

We retain your account profile, progress, inventory and balances while maintaining your account. Removal from active systems follows the account-deletion process below. Google/Unity account authentication and our game profile API use HTTPS. Voice audio packets are encrypted in the current test client, but encryption covering all Photon Fusion gameplay and room traffic is not enabled. We therefore do not currently claim that all user data is encrypted in transit. This is not a claim of end-to-end encryption. Access is restricted; passwords and session tokens are not written to application logs.

15. Your rights and account deletion

Request deletion of your Hollow Playground account and associated data at support@emtilabs.com. The request link on this website is available even when the game is not installed. Use “Hollow Playground account deletion” as the subject and include your public ID, if available, and whether you can access the account. Do not send passwords, recovery keys, session tokens, identity documents or payment-card details. Knowing a public ID or email address alone is not proof of ownership. Support records your request and guides secure ownership verification. Players with account access can submit an authenticated request through Sign-in/Account management → Privacy and account → Account and data deletion request; its receipt is bound to that account. If you cannot access the account, say so: official account recovery or secure alternative ownership verification must be completed before erasure. An email claim alone cannot authorize erasing another account. Receiving a request is not completed erasure. On 23 October 2026, a dedicated disposable test account passed erasure of its Unity identity, two Cloud Save environments and game database, retry checks and reapplication of the erasure journal against an old backup. This does not mean every account is automatically erased; ownership, linked services and retention exceptions are verified separately for each real request. A provider failure preserves the same request for retry. Our reply distinguishes completed steps from pending erasure or retained data. Requests under Türkiye’s data-protection law are answered within 30 days; other applicable rights and the right to contact a supervisory authority remain intact. Your Google account is not deleted; uninstalling or revoking Google access does not automatically delete your Hollow account.

Your email app opens; you send the message yourself. If it does not open, write to support@emtilabs.com. This page does not automatically erase data.

16. Children and changes

Hollow Playground permanently targets people aged 14 and over. This is not a store-issued content rating. Access is not offered below 14; an age response does not automatically delete an existing account or permanent entitlement. A neutral, initially blank date-of-birth check precedes sign-in. The date is neither stored nor sent to the server; only an age group is kept on the device. A local declaration is not identity/age proof or verified parental consent. People aged 14–17 are not treated as adults. Basic online play and optional voice are intended for players aged 14–17; there is no blanket exclusion solely for that age group. Any permission actually required for the country and service must still be satisfied. A truthfulness declaration does not replace mandatory guardian verification. Photo, advertising and payment providers retain their separate availability requirements. Contact support about an incorrect entry or existing-account access; do not misstate your age. Contact support@emtilabs.com about child data. Material changes will update this policy and necessary in-game disclosures.

17. Optional profile photo

profile_photo_unlock is a one-time permanent upload entitlement, not per-photo credits. Successful replacements are separated by 72 hours according to the server clock. The source is at most 8 MiB and 64–4096 px; cropped output is 512×512 JPEG, and the server accepts at most 1 MiB and one frame. Photos are not published before verification/moderation. Failure, cancellation or rejection preserves the old photo and replacement timestamp. Only after the new photo is successfully published is the old object queued for deletion. The service and its sale remain closed pending real-provider acceptance.

18. Deleted data and linked services

The erasure operator covers the Unity Authentication game identity and linked Google/username identities; profile name and preferences, progress, inventory, Cash/HC balances, in-game entitlements, recovery hashes and retry state on our game server; friendships, blocks, invitations, party membership and related caches; diagnostic groups and receipts; sent and received written messages; default/protected/public/private player data and files in the Unity Cloud Save environments used. Each service is cleared separately and read back to verify the result. If the optional photo service is enabled, published, pending and old photo objects must also be removed separately; deleting Authentication does not automatically erase them. Other players’ accounts and entitlements are preserved. An active match, purchase/security record or unfinished provider operation pauses the affected step for a separate review with an explanation; we do not report all data as erased. Our game server does not record Voice conversations. Your Google account and Google Play’s own transaction records are separate from your Hollow account.

19. Records remaining after deletion and their periods

Verified on 23 October 2026: the public ID remains reserved indefinitely without its account link so it is not reassigned. A one-way hash of the UGS identity and erasure status/timestamps prevent account resurrection; no automatic expiry has been defined for this protection record, and it is not treated as anonymous. A separate encrypted erasure/restore journal can be opened only by the authorized operator; this restricted security record also has no automatic expiry yet. Cloud SQL retains the most recent 7 automated backups and 7 days of transaction logs; seven backups is not a guaranteed seven days, and failed backups can extend retention. A 30-day cleanup task is installed for recognized manual DB backups and isolated restore copies. It runs daily and when the operator signs in. It cannot run while that computer/account is offline; missed cleanup runs when next available. Copies made elsewhere require separate assessment. Hourly Apps Script automation operates on support@emtilabs.com for closed deletion requests. Correspondence labeled HP-Deletion-Closed/YYYY-MM-DD is permanently removed from the mailbox, including Trash, in the first successful hourly run after 90 full days have elapsed from the end of the closure date. A new reply or conflicting closure labels sends the thread for review instead of automatic deletion. On 23 October 2026, the mailbox operator confirmed that 16 condition tests, a real-account preview and the first run passed, and that the current subscriptions have no Vault. We have not independently inspected the mailbox. Automation failures or quotas may delay cleanup and are monitored by the operator. Permanent mailbox removal does not mean Google’s separate provider-side recovery/backup periods end simultaneously; those periods depend on Google’s terms and the service used. Documented legal-retention exceptions require a separate scope, reason and period. Google Cloud application logs in _Default are retained for 30 days; the provider’s locked _Required audit logs for 400 days. The latter does not mean all player data is retained for 400 days. Other providers’ own technical logs and necessary financial/dispute records require their actual scope and applicable periods to be established before any blanket fully-erased result. After restoring a backup, the erasure journal must be reapplied and verified before serving players.