Privacy Policy
The short version
- Hong Kong pickleball social / sports app from WILDDIVE GAMING.
- This free test build uses Google Play Games sign-in and Saved Games for character / progress.
- Cloud saves live in your Google account’s app-data folder — not on a WILDDIVE first-party game server today.
- Local device saves also kept.
- No ads, no ad tracking, no analytics or crash-reporting tools in the current test build. We don’t sell personal information.
- No IAP / no card details in this free test build.
- Venue map pins are an in-app HK courts catalog — not continuous GPS tracking. Policy will be updated before any device-location features.
- Privacy requests: support@p8kle.com (subject “Privacy request”).
What we collect (current test build)
Google Play Games sign-in
When you sign in, the client uses your Play Games player ID and display name from Google Play Games Services.
Saved Games (character / progress)
- Pull / Push of a character recipe JSON (nickname, avatar / cosmetics / character profile, related progress).
- Conflict strategy: UseLongestPlaytime.
- Stored in your Google account app-data folder for this app — not on our server today.
- Device also keeps local per-player saves. Production uses Play Games; DEV / internal builds may use a local test path without Google identity.
Venue map
In-app venue pins from a curated Hong Kong courts catalog. Not continuous GPS or background location tracking. We will update this policy before asking for device location.
What we don’t collect in this test build
- No advertising ID, ads, analytics, or crash-reporting SDKs (no Firebase Analytics, Crashlytics, Unity Analytics, or standalone crash/analytics tools — only Play Games / Play services for sign-in and Saved Games).
- No in-app purchases / Google Play Billing products; we never see card or bank details.
- No leaderboards, achievements, or Play Games Friends / Circles APIs.
- No first-party player DB, Cloudflare Workers / D1 game API, Firebase / Firestore account backend, or push service receiving player data today.
- No continuous GPS tracking. Chat, photo upload, booking payments, and social messaging are not claimed as live collection until they ship and this policy is updated.
Google Cloud project
Project p8kle-514015 is for OAuth / Play Games Services configuration for com.wilddivegaming.p8kle. It is not a custom game API storing your play data on our servers today.
How we use information
To run P8kle; keep your signed-in session and character / progress via Play Games and local saves; show in-app venue information; and answer support or privacy requests. We do not use data for advertising, ad profiling, or selling personal information.
Who we share with
We do not sell or rent personal information and do not share it for advertising.
- Google Play / Google Play Games Services — distribution, sign-in, Saved Games. Google Privacy Policy
- Cloudflare — may host p8kle.com (static site / this page). No P8kle player database on Cloudflare yet.
We may also share information if the law requires it, to protect users, or in a business transfer (with notice).
Planned features (not live yet)
Community tabs, meet-to-play / court booking, messages, schedule, rankings, match records, chat / invites, possibly photos, and optional Cloudflare Workers / D1 APIs. These do not receive player data on our servers today. We will update this policy before they go live.
Website (p8kle.com)
The domain is for product / studio pages (including this privacy page when published). We do not currently operate a Wish List, Forum, or player account system on p8kle.com. Site features that collect personal data will be disclosed here first.
For parents and guardians
P8kle is aimed at a general sports / social audience in Hong Kong. A separate kids-directed mode has not been decided. Please supervise Play Games sign-in and Google account settings if a child uses the app. Email support@p8kle.com (subject “Privacy request”). If we learn we collected a child’s data without required consent, we will delete what we control.
How long we keep data
- Local saves / session: until you clear app data, uninstall, or overwrite in-app.
- Play Games Saved Games: retained in your Google account under Google’s controls — no separate first-party retention period because we do not host that cloud copy.
- Support / privacy emails: only as long as needed to handle the request, then deleted unless law requires longer.
- Website (when live): Cloudflare may process short-lived technical request data under Cloudflare’s terms.
Deletion and your rights
There is no first-party account-wipe API yet (no first-party player database today).
- Local data: Android Settings → Apps → P8kle → Storage → Clear data, or uninstall.
- Saved Games: manage via Google account / Play Games controls for this app’s data.
- Returning to login clears the local session only; Play Games may keep you signed in to Google until you change device / Google settings.
Email support@p8kle.com (subject “Privacy request”). We aim to respond within 30 days. Under Hong Kong’s Personal Data (Privacy) Ordinance, access / correction requests: within 40 days. We may verify identity first. A formal deletion SLA beyond these windows is not separately defined yet.
Other regions (EEA / UK / US states and elsewhere): you may have rights to access, correct, delete, or restrict use of personal data, and to complain to a regulator. Email us. More detailed regional wording will be confirmed before production launch.
Where data is processed
We are based in Hong Kong. Google Play / Play Games may process sign-in and Saved Games data in the United States and other countries under Google’s terms. When live, p8kle.com may be served by Cloudflare’s global network.
Security
Website connections (when live) use HTTPS. Play Games authentication and Saved Games follow Google’s security practices. No system is perfectly secure; we will notify you and regulators of breaches as the law requires.
Changes
Updates will be posted here with a new effective date. For material changes (device location, chat, booking, photos, analytics, ads, IAP, or a first-party cloud backend) we will update this page before those features go live and, where required, ask for consent again.