Dinkzo Privacy Policy
Your privacy at a glance
Dinkzo, by Pixel Nomads, helps people organize and join pickleball activities, manage playing queues and tournaments, communicate, and keep shared results. This policy explains the information used for those features and the limits of privacy controls. Optional developer support is separate from event fees. You can request account deletion or deletion of specific data using our Account & Data Deletion page, without signing in or reinstalling the app.
In this policy
1. Who operates Dinkzo
Pixel Nomads operates Dinkzo and is responsible for the personal information it processes as controller. Contact our privacy representative through the contact form. This policy covers the Dinkzo app and its supported services. Our separate Website Privacy Policy covers this studio website and its forms. Features and providers can vary by platform, release and configuration.
2. Information we handle
- Account and sign-in: account identifier, email address, name, username, authentication provider and account-security information. Firebase Authentication handles email/password and supported Google sign-in or account linking. Review your display name and username before participating; initial values can be derived from your sign-in details.
- Player details: biography, profile photo, chosen location, play type, player type, usual playing schedule, equipment, pronouns and appearance preferences. A self-entered DUPR rating can be used to derive a skill category; it is not independently verified by that calculation.
- Eligibility: optional date of birth and chosen gender for relevant event categories. The account stores the date of birth privately; participation records can contain a derived age and, where a category requires it, the gender supplied for eligibility. This is not identity or age verification.
- Profile publishing: profile cover, prompt answer, social play preferences, selected clubs, pinned badges, optional field audiences, profile style and publication choices. Draft/source information and published copies are separate records. Community highlights participation is an optional choice; features that depend on an enabled release or backend job may be unavailable.
- Location: foreground coordinates when you choose location-assisted discovery or a picker, location search text, selected map pins, venue details, address components and place identifiers. A location you save to a profile or event is different from a temporary device location.
- Events and play: event and club details, membership and organizer roles, join requests, invitations, teams and categories, availability, attendance and check-in records, queue entries, court assignments, match pairings, scores, standings, scoring roles, schedules and shared history. QR-based check-in and spectator-display links also use event identifiers or access tokens.
- Event fee records: amounts due, recorded payments, payment status, waivers and related administration entered by users or organizers. These are records of arrangements made outside Dinkzo, not payment-processor confirmation.
- DUPR coordination: identifiers, names, profile links, self-reported ratings, club identifiers, match-result drafts, export batches, status notes and reminders used for organizer-led reporting. Storing an identifier does not itself verify the person, their rating or delivery of a result to DUPR.
- Communication and community: follow relationships and requests, event-chat text, sender details and timestamps, message-read information, notifications, feedback, support correspondence and, where enabled, recognition requests, withdrawals, reports, receipts or awards.
- Optional developer support: selected store product, platform, purchase token or signed transaction information submitted for verification, order or transaction identifier, account identifier, verification environment, status and timestamps. Refund reconciliation may also record a refund timestamp and reason. The supported purchase flow uses Google Play Billing or Apple in-app purchasing; Dinkzo does not receive your full payment-card details.
- Technical information: session and local-storage information, service request metadata, IP address and logs processed by infrastructure providers. In-app feedback includes the message, category, app version, platform and account/name/email when provided or available. The current feedback payload does not add a device model or screen size.
Please avoid putting passwords, authentication codes, card details, sensitive medical information or another person's private information in a profile, event description, chat or feedback message.
3. Permissions, analytics and device storage
Location: you can decline foreground location access and use available manual location choices. The reviewed location features do not implement continuous background route tracking. Saving a place, using nearby discovery and opening external directions have different purposes; review what you choose to publish. Revoke device permission through your operating-system settings.
Photos: choosing a profile photo or cover uses the available picker and cropping tools. The app uploads processed images rather than treating your whole photo library as uploaded content. Profile-photo and cover files can be readable by other signed-in users who have their addresses; hiding a profile field is not a confidentiality control for the underlying image file.
Local storage: the app and its providers can store authentication state, appearance and text-size choices, cached images or places, drafts and other feature state on your device. Signing out, clearing app/browser storage or uninstalling can remove local copies but does not by itself delete cloud records or provider records.
Browser analytics: on supported browser builds, the reviewed implementation initializes Google Analytics for Firebase. This may process usage events, browser/device information, identifiers and IP-related information under Google's terms. This code path is browser-specific; it is not evidence that native Android or iOS builds run the same analytics collection. This website's optional Google Fonts consent panel does not control Dinkzo app analytics. Applicable consent or opt-out requirements must be handled within the relevant service.
4. Purposes and legal bases
We use information to authenticate accounts; provide discovery, profiles, clubs and event administration; check category requirements; coordinate attendance, queues and scoring; show results; deliver communication and available notification preferences; verify optional developer support; investigate reports; prevent abuse; maintain security; and respond to support and privacy requests.
Depending on the information and applicable law, processing relies on providing the service you request, your consent for optional processing, compliance with legal obligations, or legitimate interests such as maintaining reliable services and protecting participants, balanced against your rights. Where sensitive information or a particular permission requires consent or another specific legal basis, that requirement applies separately. Withdrawing consent does not invalidate earlier lawful processing, but can affect the optional feature concerned.
5. Who can see information
Profiles: optional published details can be set to Only me, Accepted followers or Everyone on Dinkzo. A draft is not automatically the published profile; use the available publish/unpublish controls. Some basic identity, event participation or results can appear independently of a published profile. An audience choice is not a promise that every copy already shared with someone can be recalled.
Statistics and history: the “Who can see your record” setting offers Everyone, People who follow you, or Nobody, and you can still see your own record. Accounts with no choice recorded default to Everyone. This controls Dinkzo's profile-statistics and history displays. It does not make underlying match records secret: the reviewed database rules permit signed-in users to read match records, so another client could derive results. Event-specific scoreboards remain shared records.
Events and clubs: other players and organizers can see information needed for participation, roles, queues, scoring and club operations. The app's database rules permit signed-in access to a wider set of event/match information than an individual profile screen displays. Event chat is restricted by event-participation rules; it is not end-to-end encrypted. Authorized administrators can access information for support, moderation and administration.
Public spectator displays: when an organizer enables casting or shares a display link, names, match identifiers, live or completed scores and related scoreboard information can be available without signing in, including on a venue screen. Anyone who receives the link may copy or share it. Turning the display off restricts future access but cannot erase a screenshot or independently saved copy.
External sharing: organizers or users can export, screenshot or share event and result information. DUPR reporting, directions, linked sites and independent event communications may disclose information to the provider or recipient involved. Do not upload another person's information without an appropriate basis.
6. Providers and disclosures
- Google/Firebase: account authentication, Firestore data storage, Cloud Storage images, enabled Cloud Functions and browser analytics. See Google's Privacy Policy.
- Maps and location providers: map, search, geocoding and directions requests can disclose the search text, place or coordinates needed for that request. Provider choice can depend on platform and configuration.
- Google Play and Apple: process optional developer-support purchases and provider refund requests. Available backend verification contacts the store and records the result. Store products, approval, credentials and deployed services affect availability; source code alone does not establish that a purchase flow is live.
- DUPR and other external services: use of their links or an organizer's export/submission is governed by their own terms. Dinkzo does not claim an official DUPR partnership or verified rating merely because a user supplies DUPR details.
- Website contact requests: forms on this Pixel Nomads website are processed through Netlify Forms and our support correspondence channel. See the Website Privacy Policy.
We do not sell personal information. We may disclose information to providers helping operate the service, recipients you or an organizer choose, or where reasonably necessary for legal obligations, valid requests, safety, fraud prevention or protecting rights. Providers can hold their own records independently of Dinkzo.
7. Security and international processing
We use authenticated access, database/storage rules and provider safeguards to protect information. Account records, published profile projections, shared matches and public display links have different access rules. No internet service is completely secure, and audience choices should not be treated as encryption. Keep your credentials private and report suspected unauthorized access.
Providers may process information outside your country. The reviewed app uses a named Firebase database and configured regional functions, but that does not mean all authentication, analytics, store or support processing stays in one country. Applicable cross-border safeguards and privacy rights continue to apply.
8. How long information is kept
We retain information for the purposes described here, including operating your account, maintaining shared event records, handling support and disputes, security, and legal obligations. The reviewed implementation does not establish a universal expiry period for every record. We therefore do not promise that all information is automatically erased after a fixed number of days.
Purchase verification records can remain separately from the account, including the stored account identifier, order/transaction identifier and status; the reviewed deletion routine does not erase or automatically de-identify this ledger. Feedback, reports, shared records, provider logs, backups and independent recipient copies may have different retention needs. We review deletion requests and explain the reason and applicable period or criterion for any information retained. Shared use or a technical limitation alone does not make identifying data permanently exempt from deletion.
9. Account and data deletion
Use Profile → Settings → Delete account, or submit an account/deletion request on our Account & Data Deletion page. You may also request deletion of specific data while keeping the account. No app installation or Dinkzo sign-in is needed to submit the website request.
The current in-app process attempts to remove the profile photo, deletes selected account and published-profile records, personal notifications, hosted event documents and matches booked by that account, releases its linked DUPR-ID claim where applicable, and then deletes the authentication account. The photo step is best effort. Recent sign-in may be required, and a failure can leave the process incomplete.
It is not a complete automatic cleanup of every associated record. Shared matches you only played in can keep names and identifiers. Event chat and participation references, club/follow relationships, nested saved items or attendance records, profile-cover files, support purchases and feedback or other operational records can require additional review. Deleting a parent record does not itself erase every nested record.
See the dedicated deletion page for request steps, the data affected and remaining-data review. Uninstalling is not account deletion; deleting an account does not cancel external registrations, refund a store purchase or erase another provider's records.
10. Your rights and requests
Subject to applicable law, you may request information, access, correction, deletion or blocking, objection, applicable portability, and withdrawal of consent. Use the contact form or the deletion request form. We may ask for reasonable evidence that you control the account; never send a password or one-time code. We will explain a lawful restriction or retention requirement. You may complain to the Philippine National Privacy Commission or another competent regulator and seek remedies available under applicable law.
11. Younger users
Dinkzo's independent account-use policy is for people aged 18 or older. A younger person must not independently create or maintain an account without the legally valid authorization and arrangements required under applicable law. A parent or legal guardian should contact us before providing a child's information. The current implementation does not establish verified parental consent or automated age verification. An organizer offering an age division does not itself authorize a child's account. Contact us about inappropriate collection so we can review and arrange appropriate restriction, correction or deletion.
12. Changes and contact
We publish revisions with a new date and provide appropriate notice of material changes. Any consent required for a new purpose must be obtained through the relevant service. Contact Pixel Nomads through the contact form; for deletion, use Account & Data Deletion.