• Start
  • Eryhouse Short Games
  • More
    • Start
    • Eryhouse Short Games
  • Start
  • Eryhouse Short Games

SIGNAL HUSH – Privacy Policy

 Last updated: 29 September 2026


1. Controller

ERYHOUSE UG (haftungsbeschränkt)
c/o Mert Görgün
Badensche Straße 19
10715 Berlin
Germany

Email: contact@eryhouse.com
Phone: +49 174 9483635


2. Scope

This Privacy Policy explains how personal data and related technical information are processed in connection with SIGNAL HUSH, including Google Play Games Services, the ERYHOUSE backend, Google Play Billing, optional rewarded advertising, privacy choices, support and security.

SIGNAL HUSH does not require a separate ERYHOUSE username and password. Where Google Play Games Services is used, a persistent player identity may be linked to an internal ERYHOUSE player identifier so that server-side Ticket balances, purchase fulfilment and recovery can be provided.


3. Google Play Games Services and Player Identity

SIGNAL HUSH uses Google Play Games Services ("PGS") for game-related authentication and player identity. Depending on the platform flow, Google may present an authorization or sign-in experience.

For this integration, the project is configured with the following Google authorization scopes:

  • .../auth/games – access required for Google Play Games Services activity.
  • .../auth/games_lite – limited Play Games access used for game identity and server-side authorization.
  • .../auth/drive.appdata – access to the application's own hidden configuration-data area in Google Drive.

The drive.appdata scope does not give ERYHOUSE access to the user's ordinary Google Drive files. ERYHOUSE does not use these scopes to obtain the user's general email inbox, contacts, ordinary Drive documents, or unrelated Google Account data.

For secure server-side authentication, the app may obtain a short-lived authorization code from Google and send it to the ERYHOUSE backend. The backend uses it to establish or verify the game identity. ERYHOUSE may store a pseudonymous Play Games player identifier and an internal ERYHOUSE player identifier, but does not store the user's Google password.



4. ERYHOUSE Backend, Cloud Hosting and Ticket Wallet

SIGNAL HUSH uses an ERYHOUSE-controlled backend hosted on Google Cloud. The primary Cloud Firestore database for the service is configured in the Google Cloud region europe-west10 (Berlin, Germany).

The authoritative Ticket balance is maintained server-side. The app may cache a recently confirmed balance for display, but the server-side ledger is the authoritative source for Ticket credits and debits.

Backend records may include:

  • an internal pseudonymous player identifier;
  • a Play Games identity mapping required for sign-in, recovery and fraud prevention;
  • the current Ticket balance;
  • Ticket ledger entries, such as amount, reason, transaction/request identifier and timestamp;
  • purchase fulfilment records and purchase tokens where required for Google Play Billing;
  • technical and security metadata needed to operate, troubleshoot and protect the service, such as request timestamps, app version and server logs.

Ticket-related server records are used to provide the wallet, recover eligible balances across installations or devices, prevent duplicate grants, investigate abuse and maintain the integrity of paid and earned virtual currency.


5. Local Game Data

SIGNAL HUSH may continue to store non-authoritative gameplay and preference data locally on the device, including language and audio settings, tutorial state, selected difficulty, local presentation preferences, highscores, cosmetic presentation and other gameplay information.

Local data can be removed by clearing application data or uninstalling the app, subject to Android and Google Play platform behaviour. A locally displayed Ticket value does not override the server-authoritative Ticket ledger.


6. Google Play Billing and In-App Purchases

SIGNAL HUSH may offer consumable Ticket packs through Google Play Billing. Payment processing is performed by Google Play. ERYHOUSE does not receive the user's full card or bank-account details.

To verify and fulfil purchases securely, the app and backend may process the product identifier, purchase state, purchase token, acknowledgement or consumption state, timestamps, an obfuscated player/account reference and related fulfilment status. Purchase tokens are used to detect replay or duplicate fulfilment and to verify purchases with Google before Tickets are granted.

Tickets are not granted for purchases that are merely pending. Consumable Ticket products are processed after successful verification and fulfilment.


7. Optional Rewarded Advertising and Privacy Choices

SIGNAL HUSH is intended to offer optional rewarded advertisements using Google Mobile Ads / AdMob. A rewarded ad is shown only after the player actively chooses the rewarded-ad option.

The Google Mobile Ads SDK may process information such as IP address, device or app identifiers, ad interactions, diagnostic information and performance information, depending on the user's region, device and consent choices.

Where required, SIGNAL HUSH uses Google User Messaging Platform (UMP), or an equivalent Google-supported consent mechanism, to request or update privacy choices before ads are requested. Where a privacy-options entry point is required, users can review or change applicable choices.

ERYHOUSE does not use Play Games identity data to build advertising profiles and does not sell personal data.


8. Support and Communications

If a user contacts ERYHOUSE, ERYHOUSE may process the contact details, contents of the request and related correspondence needed to respond, provide support, investigate security issues or handle legal requests.


9. Purposes and Legal Bases

Depending on the processing activity and applicable law, processing may be based on:

  • performance of a contract or steps necessary to provide requested game, wallet and purchase functions;
  • legitimate interests in service security, fraud prevention, abuse prevention, support and reliable operation, where those interests are not overridden by the user's rights;
  • consent, particularly where required for advertising, device storage or access, or other optional processing;
  • compliance with legal obligations and the establishment, exercise or defence of legal claims.

Where German Section 25 TDDDG or equivalent rules apply to storing or accessing information on a device, consent is obtained where required. Strictly necessary storage or access may be used where legally permitted.


10. Recipients and Service Providers

Depending on the feature used, data may be processed by or disclosed to Google entities providing Google Play, Google Play Games Services, Google Cloud / Cloud Firestore, Google Play Billing, Google Mobile Ads / AdMob and Google User Messaging Platform. Additional technical providers will be disclosed if they are included in the production service.


11. Google API User Data – Limited Use

ERYHOUSE's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the applicable Limited Use requirements.

Google API user data is used only to provide or improve the user-facing SIGNAL HUSH features for which access was granted, to protect security and prevent abuse, to comply with applicable law, or as otherwise permitted by Google's policies and the user's authorization. ERYHOUSE does not sell Google API user data or use it for personalized advertising.


12. International Data Transfers

Although the primary Firestore database is configured in Berlin, Google and other service providers may process technical, support, security or service data in other countries. Where required, international transfers are based on an applicable adequacy decision, appropriate safeguards or another lawful transfer mechanism.


13. Retention

ERYHOUSE retains data only for as long as needed for the purposes described above, including service delivery, wallet continuity, purchase fulfilment, duplicate-prevention, fraud prevention, support, legal defence and applicable statutory retention obligations.

  • Player identity mappings and wallet records are retained while needed to provide the persistent game wallet and recovery features.
  • Purchase tokens and fulfilment records may be retained as necessary to prevent duplicate grants, handle refunds or disputes and meet legal or accounting obligations.
  • Security and operational logs are retained only for a proportionate period needed for troubleshooting, abuse prevention and security.
  • Support correspondence is retained only as long as required for the request and applicable legal obligations.

14. Deletion, Revocation and Player Data Requests

SIGNAL HUSH does not create a separate password-based ERYHOUSE account, but a persistent server-side player record may exist when Play Games Services and the server-authoritative Ticket wallet are used.

Users may request access, correction or deletion of personal data held and identifiable by ERYHOUSE by emailing contact@eryhouse.com. ERYHOUSE will verify the request where necessary. Certain purchase, fraud-prevention, accounting or legal records may need to be retained where required or permitted by law.

Users can also manage or revoke Google authorization through their Google Account settings. Revoking Google access does not automatically erase ERYHOUSE records that must be retained for legal, security or purchase-integrity reasons; deletion requests can be sent to ERYHOUSE separately.


15. Security

ERYHOUSE uses technical and organisational measures appropriate to the nature and risk of the data processed. Sensitive purchase-verification logic and authoritative Ticket records are kept on the backend rather than trusted to client-side HTML or local storage. Data is transmitted using encrypted network connections where supported and required.

No electronic system can be guaranteed to be completely secure.


16. Children and Target Audience

SIGNAL HUSH is designed to be broadly suitable and family-friendly in presentation, but it is not specifically directed at children under 13. The intended Google Play target audience is 13+.

If the intended audience, advertising configuration or data practices change, ERYHOUSE will review the app, disclosures and SDK configuration before release of the change.


17. Automated Decision-Making

ERYHOUSE does not use automated decision-making that produces legal or similarly significant effects on players. Game difficulty, ordinary Ticket rewards and gameplay failure states are not based on personal advertising profiles.


18. User Rights

Subject to applicable law, users may have rights including access, rectification, deletion, restriction of processing, data portability, objection and withdrawal of consent. Withdrawal of consent does not affect processing already lawfully carried out before withdrawal.


19. Right to Lodge a Complaint

Users have the right to lodge a complaint with a competent data-protection supervisory authority. For ERYHOUSE in Berlin, the competent authority may include:

Berliner Beauftragte für Datenschutz und Informationsfreiheit
Alt-Moabit 59–61
10555 Berlin
Germany


20. Changes and Contact

This Privacy Policy may be updated if SIGNAL HUSH, its backend, SDKs, purchase model, advertising configuration or legal requirements change. The current version will be made available on the ERYHOUSE website.

Privacy-related requests: contact@eryhouse.com



© 2026 ERYHOUSE UG (haftungsbeschränkt) · SIGNAL HUSH 

Copyright © 2026 ERYHOUSE - All Rights Reserved.

Powered by

  • Impressum / Kontakt
  • Signal Hush PrivacyPolicy
  • Signal Hush Terms

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

DeclineAccept