Privacy Policy
Beta draft for owner and legal review before any broad launch. This page describes the data processed by the current Zevintos beta.
Account and profile data
We process your email address, username, display name, password hash, account status, and the creator profile details you choose to provide, such as your bio, Instagram handle, and profile image URL.
Content you publish
We process the Reels, resources, descriptions, dates, categories, and links you add so they can appear on your dashboard and public creator profile.
Brand enquiries
When a visitor submits a brand or collaboration enquiry to a creator who has enabled enquiries, we process the sender's name, company, contact email, optional budget range, and message so it can appear in that creator's private dashboard inbox. This information is not displayed on the creator's public profile. Disabling enquiries stops new submissions but does not automatically remove earlier enquiries.
Analytics and public activity
We record resource-click timestamps and the referrer and user-agent information sent with those clicks. Referrer and user-agent metadata are removed after 30 days. Creator-facing traffic-source analytics use only broad categories such as direct, Instagram, or search; they do not retain the referring URL, visitor identity, or IP address. For profile views, we use a visitor cookie to create an HMAC-derived identifier for daily de-duplication; the application does not store the raw visitor identifier in the profile-view record. We maintain daily view and click aggregates for creator analytics.
Authentication and security
We use authentication and CSRF cookies to keep you signed in and protect account actions. We also process short-lived rate-limit data to help protect registration, password recovery, and other sensitive routes. Password-reset records contain a hashed token, expiry, and use status; the raw reset token is not stored.
Retention and deletion requests
Profile-view de-duplication and raw resource-click records are intended to be retained for no more than 90 days, while daily view, click, and coarse traffic-source aggregates are retained for 24 months initially. Brand enquiry records are intended to be retained for no more than 12 months and can be deleted sooner by the receiving creator; deleting a creator account also removes its enquiries. Account, profile, Reel, resource, and authentication-related records are retained while the beta account is active unless a valid deletion request or operational need requires a different outcome. For account deletion, access, correction, or a brand-enquiry data request, use Support; we aim to acknowledge beta requests within five business days.
Infrastructure providers
The production beta uses Google Cloud services for application hosting, PostgreSQL data storage, and Redis-backed security rate limiting. Password-reset email delivery is configured for the beta.
Your choices and questions
You can update profile content from your dashboard. For privacy, deletion, or data-access requests, contact us through Support.