Privacy, with clarity.

1. Information you provide

An account requires an email address and password. We use your email to identify your account and support sign-in. Passwords are stored as security hashes, not readable passwords. Your account also has an identifier, a unique nickname and a points balance.

You choose whether to add an avatar, publish posts or comments, upload photographs, like or save content, or answer the daily question. We store the information needed for these features, including submitted text and images, interaction records, answers, rewards and relevant dates. Not providing optional information does not prevent ordinary browsing; account features require sign-in and the information necessary for that action.

Please avoid uploading sensitive personal information or photographs of other people without appropriate permission.

2. Why we use it

• To create and secure accounts, maintain sessions and show your profile.
• To publish and manage community contributions, comments, likes and collections.
• To review avatars and posts, apply content rules and communicate review outcomes.
• To provide daily questions, maintain answer snapshots, award points and display rankings.
• To respond to support and privacy requests, investigate errors and protect the service from misuse.
• To understand how app features are used and improve navigation, content presentation and reliability through usage analytics.

Moderation and account administration can include internal records of actions, responsible administrators, review reasons and points adjustments. These records support accountability and are separate from the activity shown in your growth centre. Account administration also includes normal or frozen account status and actions to freeze or unfreeze an account; freezing invalidates existing sign-in sessions.

3. What other people can see

Your public nickname and approved avatar can appear with published posts, comments and leaderboard entries. Published text and images are visible to other people. Rankings may display your points and rank. Your account email and pending avatar are not part of public profile responses.

Pending or returned submissions and review reasons are available to you and authorised administrators. A new avatar stays private while awaiting review; an existing approved avatar can remain visible.

4. Information on your device

The app keeps a sign-in credential and your language preference in app-private storage. Local post drafts and their selected image copies are kept on your device under the relevant account. Signing out does not automatically delete these local drafts. Clearing app data or removing the app can remove them.

Photos are selected through the device's selection interface. A selected photo is sent to the service when you initiate an upload for an avatar or post; selecting a photo does not give us access to your whole photo library. Uploaded media can remain on the service even if the associated submission is not completed.

Downloaded images may be cached in app-private storage to reduce repeated downloads and improve loading. Cached images have a seven-day freshness period and may be removed earlier by cache management or the device. The settings page lets you clear the image cache. This removes cached copies on the device, not your account, local post drafts or content held by the service.

5. Service security and access

The service processes connection information, including the connecting IP address, to handle requests and limit repeated attempts. Technical error diagnostics help identify failures. The app's diagnostic implementation avoids recording passwords, session credentials and request text in error messages.

Authorised staff may access information necessary to provide support, moderate content and administer accounts. If you request password assistance, staff must verify your identity before resetting the password; a reset invalidates existing sessions. Staff cannot retrieve your original password.

Technical service providers engaged to operate or support the service may need limited access for those functions. Information may also be disclosed where required by applicable law or a lawful request. Public contributions are, by their nature, disclosed to other users. The app uses Google Analytics for Firebase for usage measurement, as described below.

6. Usage analytics

We use Google Analytics for Firebase, provided by Google, to understand use of the app and improve its features and reliability. Analytics collection is enabled from the first launch, including when you browse without an account. The app does not currently provide an in-app switch to turn analytics collection off.

Analytics includes an app-instance identifier for an installation, session and app lifecycle information, pages viewed, time spent on pages, feature interactions, language choices, and the status of operations such as sign-in, posting, translation and daily questions. Events may include numeric counts, fixed categories, general failure reasons and randomly generated operation identifiers used to relate events for the same operation. Google's SDK also derives coarse location information from masked IP addresses. This is not precise GPS location.

Our custom analytics events do not send account IDs, email addresses, passwords, nicknames, search text, post or comment text, uploaded images, local file paths or raw error messages. We do not set your business account ID as a Google Analytics user ID. These limits on custom event payloads do not mean that the SDK collects no installation or usage data.

The app disables collection of the Android Advertising ID and sets advertising storage, advertising user data and ad-personalisation consent to denied. These advertising restrictions do not disable usage analytics. Analytics data is sent to Google over encrypted connections and may be processed outside Hong Kong. Google's handling of Analytics data is described in its Privacy Policy and Analytics data disclosure information.

Retention and further processing of Analytics records are subject to the applicable Google Analytics terms and the settings governing the service. We do not promise a fixed retention period or that uninstalling the app deletes previously transmitted Analytics records. Contact us about Analytics information or a privacy request; handling a request may require sufficient information to identify the relevant records and is subject to applicable rights and retention obligations.

7. Translation services

To provide content in your chosen language, our server may send text to MyMemory, operated by Translated, to obtain a machine translation. This can include community posts and comments when translated, as well as relevant content or moderation explanations displayed in another language. The translation request includes the text and source and target languages. It does not intentionally include your account email, password, sign-in credential or selected photos.

Some translations are requested through an explicit Translate action; others, such as comment translations, can be generated when content is displayed in another language. We may cache translated results to reduce repeated requests. The translation provider receives the submitted text and handles it under its own terms and privacy practices. Avoid placing confidential or sensitive personal information in content submitted to the service. Translation is distinct from Firebase Analytics: the translated text is sent to the translation provider, not included in our custom Analytics events.

8. Deletion and retention

When a post deletion is accepted by the service, the post becomes unavailable through public content endpoints. This is different from erasing every stored copy. Submitted content, media references, moderation records, security records and transaction history can remain where needed to administer the service, address disputes or meet legal obligations. Copies held in backups may also remain until dealt with under the applicable backup arrangements.

Retention depends on the purpose of the record and applicable obligations; we do not promise a fixed deletion period for every type of information. Please contact us to ask about a particular record or to request deletion. There is no automatic account-deletion control in the app. A request to remove account information is reviewed, including whether some records must be retained.

9. Your requests and choices

You may request access to and correction of your personal data, and ask us to consider deletion. You can edit your nickname, submit a replacement avatar, remove your own posts or comments, and cancel likes or collections through the available app controls.

Send privacy requests to the contact below. Tell us which account or information the request concerns. We may request proportionate information to verify your identity before responding. Do not send your password. Access and correction requests are handled subject to applicable Hong Kong personal-data requirements.

10. Changes to this policy

We may update this policy when the service or its information practices change. The date above identifies this version. Material changes to collection or use will be communicated as appropriate; this policy does not authorise unrelated uses of your personal data.