Privacy Policy

1. Overview

This Privacy Policy covers Wordscape - Puzzle Game and wordscapes.online (the "Services"). It explains what personal information is handled, why it is used, who receives it and how to make a privacy request.

The operator responsible for the Services is [LEGAL_ENTITY_NAME_AND_ADDRESS] ("we", "us" or "our"). Our privacy contact is listed in Section 11.

2. Information collected

Information you provide

When you send us a privacy or support enquiry, we receive the information you include, such as your contact details and message. Please do not send passwords or complete payment-card details.

3. How information is used

Information included in a support or privacy enquiry is used to understand the request, communicate with you and address the issue raised.

[OTHER_PURPOSES_AND_BASES: Match each additional data category to its actual purpose, such as saving progress, account management, diagnostics, advertising or purchase validation. State the applicable legal basis where relevant, and explain required versus optional processing.]

4. Service providers and information sharing

[PROVIDERS_AND_SHARING: Name the actual hosting, support, analytics, crash-reporting, advertising, login and payment providers used. For each, describe the data received, purpose, role and privacy-policy link. Include SDK collection even when you do not directly receive that data. State whether information is sold, shared for advertising or otherwise disclosed; do not claim "we never share data" without verification.]

[OTHER_DISCLOSURES: Describe any applicable legal, safety or business-transfer disclosures, and the limits and safeguards that apply.]

5. Cookies, local storage and device permissions

[COOKIES_AND_CONTROLS: Identify the cookies, local storage, tracking technologies and advertising/analytics tools actually used on the website and in the app. Explain purposes, providers, durations and the working method to accept, reject or change optional choices. State explicitly if none are used, only after verification.]

[APP_PERMISSIONS: List the permissions actually requested, why they are needed and how users can manage them. Explain any consequences of declining optional permissions. State if no additional permissions are requested.]

6. Data retention and deletion

[RETENTION: Give the actual retention period or meaningful criteria for each data category, including support messages, logs, gameplay, accounts, purchases and backups. Explain any legal retention exceptions.]

[DELETION_PROCESS: Give the verified deletion request method, any necessary identity check, the completion timeframe and what is deleted or retained. If accounts exist, provide both the in-app deletion steps and an external request route. If there are no accounts, say so and explain deletion of any other information still collected.]

Removing the app from a device does not, by itself, send a deletion request for information held separately by the operator or service providers.

7. Privacy questions and requests

Contact us using Section 11 to ask about your information or request access, correction or deletion. Describe the request and provide a way for us to reply. Do not include unnecessary sensitive information.

[RIGHTS_AND_REQUEST_HANDLING: Describe the rights available in the regions you serve, applicable response deadlines, verification process, consent withdrawal and any complaint or appeal route. Include the relevant privacy authority or grievance contact where required.]

8. Children's privacy

[CHILDREN_AND_AGE_RULES: Specify the app's actual intended audience and applicable age rules in the regions served. Describe any parental consent, age checks, child-data collection, advertising restrictions and deletion process. Do not assume a universal age threshold or declare the app is not child-directed without confirming its design and audience.]

A parent or guardian with a question about a child's information can contact the privacy contact below.

9. Security and international processing

[SECURITY: Describe the technical and organisational safeguards actually implemented, such as protected connections, restricted staff access and secure storage. Do not claim encryption or certifications that have not been verified.]

[PROCESSING_LOCATIONS: State where you and your providers process information, whether international transfers occur, and the safeguards or transfer mechanisms used where required.]

10. Updates to this policy

We will revise this page and its effective date when the policy changes. Where applicable requirements call for additional notice or consent, we will provide that notice or obtain consent before the relevant change takes effect.

11. Contact us