Privacy policy

This policy covers the Votzuno website-discovery marketplace and its account, submission, voting, ownership, ranking, sponsorship, and analytics features.

Launch blocker: the production operator’s legal name, business address, privacy contact, and applicable representative details have not been configured in this repository. They must be inserted before launch.

• Account data: email address, display name, verified authentication identifier, account role, and Supabase-managed session cookies. Passwords are submitted to Supabase Auth and are not stored in Votzuno’s application tables.
• Marketplace activity: website submissions and metadata, votes, ownership claims, verification attempts, owner edits, referral clicks, moderation records, and audit events.
• Ownership proof: DNS or hosted-file verification method, a one-time proof token stored as a hash, attempt count, status, and timestamps. Proof tokens expire after 24 hours.
• Privacy-minimized analytics: profile views, outbound clicks, sponsored impressions and clicks, the related website or campaign, event time, bot-filtering status, and a pseudonymous deduplication key.
• Sponsorship records: campaign selection, amount, currency, status, schedule, inventory slot, and provider transaction identifiers if production payments are enabled later. Votzuno does not collect full payment-card details.
• Operational data: security and rate-limit records plus minimized runtime logs. Application error logs omit query strings and raw error messages by design.

• Authenticate accounts, keep sessions secure, and provide password recovery.
• Review, publish, rank, moderate, and maintain website listings.
• Record one vote per account and detect suspicious voting velocity or repeated attempts.
• Verify website ownership and provide owner editing and aggregate analytics.
• Label, schedule, measure, and reconcile sponsored placements independently of organic ranking.
• Prevent abuse, enforce platform rules, diagnose failures, and meet legal obligations.

Votzuno does not currently sell personal information or use it for cross-context behavioural advertising. Organic ranking calculations do not use sponsorship or payment inputs.

Votzuno uses essential Supabase authentication cookies to sign users in and refresh verified sessions. A first-party votzuno_analyticscookie stores a random pseudonymous visitor identifier for up to one year. It is Secure, HttpOnly, and SameSite=Lax.

Marketplace analytics cover listing profile views, outbound clicks, sponsored impressions, and sponsored clicks. Events are deduplicated and likely bots or prefetches are filtered. Votzuno’s analytics tables do not persist IP addresses, referrer URLs, or browser user-agent strings, and they do not record arbitrary homepage page views.

Information may be processed by infrastructure providers needed to operate Votzuno, including:

• Supabase for authentication and PostgreSQL database hosting.
• Vercel for application hosting, delivery, runtime logs, and operational monitoring.
• A payment provider if sponsorship payments are enabled after production review.
• Authorities or professional advisers when reasonably necessary to comply with law or protect rights and safety.

Votzuno does not give verified owners access to individual visitor identities; owner dashboards use aggregate counts.

• Raw privacy-minimized analytics events are deleted after 90 days.
• The analytics visitor cookie expires after one year unless it is cleared sooner.
• One-time ownership proof tokens expire after 24 hours; only their hashes are stored.
• Account, listing, vote, ownership, moderation, payment, security, and aggregate records are retained while needed to operate, secure, document, or legally defend the service.

Launch blocker: counsel and the operator must approve specific deletion periods for every remaining record category and backup before launch.

Depending on where you live, you may have rights to know about, access, correct, delete, restrict, object to, or obtain a copy of personal data, withdraw consent where processing relies on consent, and complain to a regulator. Applicable exceptions may allow or require some records to be retained.

You can remove your own vote using the vote control. Account and listing corrections can be made through the available dashboard flows. A verified contact channel for privacy requests and account deletion must be published before launch.

Votzuno uses verified server-side authorization, restricted database access, hashed ownership tokens, cross-site request checks, rate limits, security headers, and minimized logging. No online service can guarantee absolute security.

Supabase, Vercel, and future providers may process information in multiple countries. The operator must document production hosting locations and any required transfer safeguards before launch.

The service is not designed specifically for children. The final Terms must define an age threshold that is valid in each launch region and the operator must implement any required parental-consent process.

Privacy contact pending: a monitored email address, operator postal address, and escalation process must be published here before launch. Material updates should receive a new “last updated” date and, when required, an in-product or email notice.

Read the Terms of service for marketplace participation rules.