Dinkzo Account & Data Deletion
Request deletion here
You can request deletion of your Dinkzo account and associated personal data, ask us to remove specific information while keeping the account, or request a review of information remaining after an in-app deletion. You do not need to sign in, reinstall Dinkzo, or make a payment to submit this form. Submitting a request does not immediately delete the account; we first verify ownership and review what needs to be removed.
Delete through the app
- Open Dinkzo and sign in to the account you want to delete.
- Go to Profile → Settings → Delete account.
- Read the confirmation and confirm only if you want to remove that account.
- If the app asks for a recent sign-in, log out, log back in, then retry. If it reports failure or you cannot access the account, submit the website form above and describe what happened.
Removing Dinkzo from your phone, signing out or clearing its local storage does not delete its cloud account.
What the current in-app process removes
- The sign-in account, after the app's data-deletion steps complete.
- The main account document; selected private, public and follower-profile records; personal notification documents; and legacy account-owned host/venue profile documents.
- Event documents hosted by the account and match documents booked by it. This should not be read as a complete cascade through every related event record.
- The account's linked DUPR-ID claim, where the existing claim belongs to that account.
- The referenced profile-photo file is attempted first on a best-effort basis. An image-cleanup failure does not necessarily stop the rest of the process.
What may remain and need review
- Shared results: matches you only played in can retain your name and participant identifier so other players' results remain readable. We can review removal or de-identification of your identifying data without assuming every shared result must be destroyed.
- Event/community records: participation entries, chat messages, club membership, follow relationships, attendance, queues, QR/display records and related records are not all cleared by the current self-service routine.
- Nested and image records: saved/pinned events or other nested records and uploaded cover images can remain. Deleting a parent account/event document is not the same as recursively deleting all associated data.
- Support, feedback and purchase records: feedback, reports and correspondence, and the separate developer-support ledger can remain. The reviewed ledger stores the account identifier, store order/transaction identifier, product, platform, status and timestamps; it is not automatically erased or anonymized by in-app deletion.
- Other holders: store, authentication/infrastructure logs, backups, exported results and copies held independently by organizers, participants or external providers can need separate handling.
These are implementation limits, not a claim that all remaining personal data is exempt from deletion. Tell us what remains using the form. We review deletion, de-identification or restriction and any legitimate retention requirement. If information must be kept for legal obligations, fraud/security, an unresolved dispute or another lawful purpose, we explain the category, reason and retention period or criterion. The current implementation has no single automatic expiry period covering every category.
Delete only specific data
Choose “Delete specific Dinkzo data; keep my account” and identify the field, photo, message, event or other record. Available app controls can also edit profile details, change audiences, unpublish a profile, remove a photo or leave an event/club where allowed. Those actions have different scopes and do not substitute for an account-deletion request.
What happens after a request
Our team uses your reply address to confirm the request, verify account ownership where needed and clarify its scope. If you no longer control the account email, explain that; we assess another reasonable verification route without asking for your password. Sending the form is a request to the support team, not an automated database deletion.
We aim to respond within 30 days after we can verify and understand the request, subject to applicable legal deadlines. We explain any delay, additional verification or lawful limitation rather than promising instant erasure. This is a support-response target, not a claim that every backend record expires after 30 days.
Account/data deletion does not automatically cancel a venue booking, withdraw an external registration, refund developer support or erase another organization's independently held records. Use the relevant provider's official channel for those matters. If sending fails, the form keeps your entries; try again later or use the contact form and identify the request as Dinkzo account/data deletion.