Privacy Policy
The dingDUNK mobile app offers product discovery through videos and content sharing. This text describes the current technical data flows.
Account and profile
Email, account ID, username, name, profile photo and biography are processed in Supabase. Email registration also sends date of birth and gender to Auth account metadata. Google or Apple sign-in uses identity and profile information supplied by the provider. Supabase Auth handles password verification; admin accounts have additional security verification.
Content and interactions
Uploaded videos and images, comments, follow relationships, likes, saves and lists are stored to operate the product. Public content and profile fields are visible to other users. Watch duration, category preference scores, product clicks and interaction events are processed for discovery ranking and usage measurement.
Information on your device
Sessions, account cache, theme and preferences are stored locally on the device. Anonymous usage measurement uses a random device/visitor identifier. Some optional account and address settings are held on the device; persistent server storage is not implemented for every field. The marketing website stores your explicit language choice in a preference cookie and, where available, local storage. Initial language selection uses Cloudflare country context when available, otherwise browser language, without asking for precise device location.
Infrastructure and external links
Supabase provides account and application data services. Cloudflare Pages/R2/CDN provides website and media delivery. Transactional Auth emails use separate sending infrastructure. These providers may retain request/Auth logs for security and diagnostics. Product links lead to external marketplaces; dingDUNK does not process payments. External websites apply their own data practices.
Deletion and rights requests
Account deletion methods are described on the account deletion page. Contact [email protected] for privacy and data requests. Deletion scope and retention of technical backups and security records require operator and legal review; no indefinite retention or unverified legal obligation is asserted.
Details requiring review
The data controller’s official name/address, legal bases, international transfer mechanisms, provider regions and retention settings, and response timelines require legal review before launch. These details have not yet been verified.