ilei.hu

Privacy policy

1. Who we are and what this policy covers

AWSH&SEA is the developer and publisher name shown on Google Play for applications and games released under that name. It is a publishing name, not a separate company or legal entity. The publisher operates through the website ilei.hu and is based in Hungary, European Union. In this document, "we", "us", and "our" refer to the independent publisher operating under AWSH&SEA.

This notice covers the ilei.hu catalogue, the applications and games published on Google Play as AWSH&SEA, and the developer’s Windows and web editions listed in the catalogue. The data involved depend on the edition and features you use. This notice also covers support correspondence with us. Independent stores and services have their own notices.

Privacy contact: awshsea@gmail.com. This is also the contact for privacy requests. Website hosting a copy of this policy: ilei.hu.

2. Privacy approach and categories of data

Our applications are designed around data minimisation. A game may be playable without creating a publisher-managed account or providing a name, mailing address, telephone number or email address. The fact that information exists on a device does not mean that it is transmitted to us.

Local game and app data
What it may include
Game progress, puzzle solutions, scores, achievements, saved sessions, preferences, interface language and configuration.
Where and why
Usually stored on the user's device to operate the game and remember preferences. Normally not sent to AWSH&SEA merely because it is saved locally.
Data explicitly provided in a request
What it may include
Name or email address shown in a support message, message contents, and attachments voluntarily sent by the user.
Where and why
Processed in our correspondence systems to respond to the request and, where necessary, document its resolution.
Technical data processed by a platform provider
What it may include
Device or app identifiers, installation and update events, diagnostic information, crash information, payment or security events where the relevant platform feature is used.
Where and why
Google Play, Android, an app store, a device manufacturer or another operating-system provider may process such information under its own terms. Their independent processing is not the same as us receiving the information. Some platform dashboards may make aggregated statistics or limited diagnostic reports available to us.
Feature-specific data, if the feature exists
What it may include
Information required for a feature that needs network access, an Android permission, or a third-party service.
Where and why
Only to the extent the feature is offered and used. When such processing is materially different from this general description, its purpose, data categories and recipients must be identified in the application or an updated notice.

3. Local storage and device backups

Local game files and preferences are intended to support normal operation, not to identify players. Local data generally remains under the control of the user and the device operating system. Some devices may include application data in operating-system backups, cloud backups, device transfers or restore processes, depending on device settings and the application's technical configuration. Such platform-level operations are subject to the applicable provider's rules and may mean that uninstalling an application does not immediately erase every backup copy.

We do not treat data stored only on a user's device as a central AWSH&SEA account or cloud database. Where an application offers an export, share or similar user-initiated function, the user chooses whether to send that exported information to another destination.

4. Purposes and legal bases

To the extent that we process personal data, we do so for identified purposes and in accordance with applicable law, including the EU General Data Protection Regulation (GDPR) where it applies:

  • Delivering and securing the catalogue: remembering a language you select and handling technical requests so the site works securely. Legal basis: our legitimate interest in providing and protecting the site (GDPR Article 6(1)(f)).
  • Responding to support and privacy enquiries: handling voluntarily submitted messages. Legal basis: our legitimate interest in replying and supporting our products (GDPR Article 6(1)(f)), or steps requested before entering into an agreement where applicable (Article 6(1)(b)).
  • Compliance with legal obligations: retaining or disclosing limited information when lawfully required (Article 6(1)(c)).
  • Optional data-based functions: where a feature actually requires processing by us, the relevant purpose and legal basis will be communicated before collection. Consent will be requested where the law requires it; consent can then be withdrawn without affecting earlier lawful processing.

Processing performed independently by Google, Android, device manufacturers or other providers is governed by their own notices and applicable legal bases. We do not claim to determine their purposes or retention periods.

5. Advertising, analytics, profiling and sale of data

We do not sell or rent users' personal information. Our general publishing practice is not to use personal data to build advertising profiles or to track people across unrelated applications. We do not operate a publisher-managed database of player profiles merely for advertising purposes.

We do not assume that every software library or platform diagnostic counts as zero data processing. If an application uses an analytics, advertising, crash-reporting, sign-in or other third-party SDK that accesses or transmits personal or device data on the application's behalf, its operation must be accurately reflected in that application's Google Play Data safety declaration and in the relevant disclosure to users. We will not describe such an SDK as "not collecting data" simply because its processing occurs through a third party.

6. Platform permissions and optional features

An application may request an Android permission only when it is needed for functionality actually provided by that application. The permission prompt, the feature's interface, and any required in-app notice explain the relevant use. Denying an optional permission may disable the corresponding optional feature without affecting unrelated features.

Access to sensitive information, such as camera images, microphone recordings, approximate or precise location, contacts, or user-selected files, is not implied by this general policy. Such data is accessed only if a specific application offers that functionality, the access is technically necessary and applicable permissions and disclosures have been satisfied. Any transmission or retention beyond what the user would reasonably expect from the feature must be disclosed separately.

  • ilei.hu catalogue. Your language choice is stored in a first-party cookie and in browser storage. The cookie allows the server to load that language on your next visit. The hosting service may process IP addresses and standard request information to deliver and protect the site. The catalogue itself does not ask you to sign in or display advertising trackers.
  • Parolu! The web reader processes selected documents and generates speech in your browser. It can store drafts, preferences and books in browser storage. The news feature separately requests selected public feeds through the site. In the installed versions, file access is used to open the documents you select. Android and Windows handle file access according to their respective system settings.
  • OmniVoice for Windows. Neural speech generation and voice cloning run locally. Text, recordings or voice samples that you choose for these functions are processed on the device. Audio you save remains in the location you select.
  • Online dictionaries. On PIV 2026, game progress is local by default. If you choose Google sign-in, Firebase Authentication identifies the account and Cloud Firestore syncs game state, statistics, puzzle IDs and update times. On EHV, optional Google sign-in syncs dictionary settings across devices. These features describe the browser editions. The data handled by an installed edition depend on its own functions.
  • Skrablo. Normal browser play is available without an account. Optional Google sign-in is used for personal learning and word reports. Firebase associates personal learned words with an account identifier. The report stores the submitted word and reason without linking the report to the reporter’s identity.
  • Stores and external sites. Google Play and Microsoft Store handle their own installation, diagnostic and payment information. Ko-fi, PayPal, YouTube and GitHub process visits or transactions on their services under their own notices.

7. Sharing and service providers

We use service providers for hosting and protecting the site, handling correspondence and supplying the optional authentication and synchronisation functions described above. We may also disclose information to a destination you choose or to comply with a binding legal obligation. Any disclosure is limited to information relevant to the stated purpose.

Google and Android may independently process installation, diagnostic, security, payment or service-related information when users interact with their products. For information about Google's own practices, see Google Privacy Policy. This reference does not mean that Google is a recipient of every category of data listed here.

8. Security measures

We limit collection and access to information needed for a stated function or communication. Where information is transmitted through a feature controlled by us, we aim to use appropriately secured communications and restrict access to those who need it. Local data is protected primarily by the operating system's application isolation, device security settings and, where enabled, its backup controls. No technical environment is entirely free of risk.

We do not claim that all data on every device is end-to-end encrypted or that independent platform providers follow security practices under our direct control.

9. Retention and deletion

Local game data: normally remains on the device until the user deletes it through the application's available controls, clears the application's storage or uninstalls the application. Actual removal, restoration and any retained device backups depend on Android and the backup provider.

Support correspondence: messages voluntarily sent to us are kept only as long as reasonably necessary to handle the enquiry, any follow-up and legitimate recordkeeping or legal requirements. We periodically review whether continued retention is needed and delete messages that are no longer necessary.

Information held by third-party platforms: deletion is controlled by the platform provider under its own procedures, not by deleting a local game save.

Requests: email awshsea@gmail.com to ask about information we actually hold or request deletion where applicable. We may need enough information to identify the relevant correspondence and protect it from unauthorised access. We cannot remotely erase information held solely on a user's device.

Accounts, if introduced: if a future application allows creation of a publisher-managed user account, we will provide the in-app and external account-deletion methods required by Google Play and explain the related data-retention rules before offering that function. Temporarily disabling an account will not be presented as permanent deletion.

Website preferences and optional sync: you can delete catalogue preferences and other local browser data through your browser. Clearing browser data or signing out does not by itself delete a synced copy. For a request concerning data synced through an app, contact us as described below and identify the app.

10. Children and families

We do not intentionally request children's names, contact details or other directly identifying information merely to play our games. Privacy protections, applicable age restrictions and consent requirements must be observed in any application directed to children or families. If a parent or guardian believes that a child has provided personal information to us through a message or feature, they may contact awshsea@gmail.com so we can assess and, where appropriate, remove the information.

11. International processing

Our publisher is based in Hungary, in the European Union. External communication or service providers, including email and platform providers, may process information in other countries. When we are responsible for a transfer of personal data from the European Economic Area to a country outside it, we apply the safeguards required by applicable law, such as a valid adequacy decision or an appropriate transfer mechanism where needed. Users may ask for information about the applicable safeguards via our privacy contact.

12. Your rights in the EEA and other regions

Where the GDPR applies and we hold personal data about you, you may have rights to request access, correction, erasure, restriction, data portability, or objection to processing, subject to the conditions and exceptions in applicable law. You may withdraw consent where processing is based on consent. You may also lodge a complaint with a competent data-protection authority, including Hungary's National Authority for Data Protection and Freedom of Information (NAIH).

Residents of US states or other jurisdictions may have additional privacy rights under applicable local laws. Where such laws apply, we will honour applicable requests to know, access, correct or delete personal information and other legally available choices. We do not sell personal information or use it for cross-context behavioural advertising. Contact us at awshsea@gmail.com; we may take reasonable steps to verify a request before disclosing or deleting information.

13. Third-party websites and independent services

Links from an application to external websites, app stores or platform services do not make us responsible for their independent privacy practices. Their applicable privacy notices govern the data they collect in their own capacity. Where a service is integrated directly into our application and processes data on our behalf, the app's actual implementation and disclosures must reflect that integration.

14. Changes to this policy

We may update this policy to reflect changes in functionality, services, law or our handling of information. The "Last updated" date identifies the version shown here. Material changes affecting personal data will be communicated through an appropriate method before the changed processing begins, where legally required. Translations are intended to carry the same substantive information; if a translation discrepancy is discovered, it will be corrected.

15. Contact

Developer name on Google Play: AWSH&SEA
Status: publishing name of an independent developer; not a separate legal entity
Operating website: https://ilei.hu/
Country: Hungary (European Union)
Privacy and data-rights enquiries: awshsea@gmail.com