Privacy policy
Draft for review · Version 2026-10-22-draft-2 · Prepared 22 October 2026. Effective on approval, not yet effective for live sales.
Operator
Chanzo is operated by Anshika Maithil. This identifies the operator and does not describe a registered company.
Privacy contact and requests
Privacy and complaints contact: team.chanzo@gmail.com. The operator reviews account privacy requests in the private admin inbox.
Children and parental consent
The owner intends Chanzo to be available to all ages. A verifiable parental-consent flow for users under 18 is not yet implemented. Google login and an agreement checkbox do not verify age or parental authority. Child-account processing remains an unresolved privacy requirement.
Data we process
Supabase Auth handles email, passwords, sign-in sessions and Google sign-in identity where enabled. Chanzo stores account ID, email, profile fields, roles, ban status, wallet balance, listing submissions and public YouTube metadata (channel ID, title, description, images, country and counts). Public holder labels say owner; internal account records are not anonymous.
Payments and policy records
We retain order references, USD and INR amounts, status, minimal verified-event references, wallet entries, policy version, acceptance time and relevant account/order or submission reference. We do not store full card numbers or CVV. Razorpay processes checkout information under its own terms. Older webhook records may contain additional data and require a minimization review before launch.
Purposes and sharing
We use data for login, channel review and promotion, payment reconciliation, fraud prevention, complaints and legal duties. Supabase provides authentication, database and realtime infrastructure; Razorpay handles payments; Google/YouTube provides public metadata and image hosting. Vercel hosts this website. Our support mailbox provider is not yet operational. Provider contracts, regions and international transfer arrangements require review.
Cookies, images and connections
Supabase session cookies support login; local storage remembers theme preference. Realtime presence sends an ephemeral random tab ID and connection time to Supabase and counts connections, not unique people. YouTube images and external video links may reveal IP/browser information to Google. Google Analytics, when configured, loads only after renewed optional analytics consent on the public chanzo.site domain. Google processes browser/device and connection data; our manually sent event fields exclude names, emails, account IDs, private paths, query strings and channel handles. Advertising features and Google Signals are disabled. Google-side data retention/deletion settings are managed in the Analytics property. Withdrawing consent disables future Google measurement and clears readable GA cookies on this domain. Checkout loads only when requested.
YouTube API access
We use an API key for public YouTube data, not YouTube channel-management OAuth scopes. Google login does not verify channel ownership. You can request removal of Chanzo-held API data through Contact; this does not delete data from YouTube. If authorized YouTube access is introduced, its scopes, revocation and deletion controls must be implemented and disclosed first.
Retention, requests and security
Stored account, ledger and support data currently has no automatic deletion schedule. Final retention periods, lawful financial-record holds and backup deletion procedures are under review. Account → Privacy offers a private JSON export of linked account records after a recent sign-in. It excludes passwords, tokens, internal security logs, other users’ private identities, external-provider records and backups. Large exports require assisted preparation instead of silently omitting records. After a recent sign-in and typed DELETE confirmation, eligible accounts with no financial, listing, shared-history, audit or provider-file dependencies can be erased from the active authentication and app database in one transaction. Accounts needing retention, settlement or shared-record review must request assisted erasure instead. Directly owned profile, notifications, agreement and current-verified-email support records are removed on successful erasure. A minimal restricted erasure receipt retains keyed hashes of the deleted identity and email, signing-key version and deletion time for backup-restoration checks; it does not retain the raw name, email or user ID. Managed backups, mailbox copies and provider security logs need their own retention/deletion procedures. Backups must not be reopened publicly until the latest signed offsite erasure manifest has been checked and any restored erased records have been removed. Signed-in users can submit access, correction, erasure, withdrawal, nomination-assistance and grievance requests in Account → Privacy (/account/privacy). Requests go to the private admin inbox for manual review; they do not automatically erase records or establish a nomination. Users unable to sign in can use Contact once the support mailbox is operational; we may need proportionate identity confirmation. We restrict access and validate payments, but cannot guarantee absolute security. Do not send passwords or card details in requests. Support configuration must be completed before public launch.
Optional analytics and support notifications
If you opt in, Chanzo uses a random first-party browser identifier, signed and stored in an HttpOnly cookie for up to 400 days, to estimate unique visitors. The database stores a hash of the identifier, first/last visit dates, daily deduplication records for up to 35 days, and aggregate daily visitor/funnel-event totals. Identifier records inactive for over 400 days are removed on the next daily maintenance run, triggered by traffic. Aggregate totals have no automatic deletion schedule. No names, emails, account IDs, IP addresses, full page URLs or user-agent strings are stored in visitor analytics; separate security rate limiting still applies. Daily counts use India time. Known bots and local/development/preview traffic are excluded, but cookie deletion, multiple devices, blocked tracking and undetected bots affect estimates. Public charts show aggregate counts only. It does not treat checkout starts as completed purchases. Cookie preferences in the footer let you change or withdraw analytics consent. When configured, Resend sends private contact-request notifications containing your submitted details to the support mailbox. Its verified sender and provider setup remain launch requirements.