Privacy Policy
Understand the information used to run your PIVORA account, channel access and private support.
Account and Google sign-in
Google sign-in is handled through Supabase Authentication. The application uses your user ID, Google email address, name and profile image when provided. A linked profile stores these display fields, registration date and protected VIP/admin status. Authentication session information is used to keep you signed in and authorize requests; PIVORA does not ask you to enter your Google password into its own forms.
Membership and signal activity
Membership flags determine Free, VIP and administrative access. Administrators can view the client directory and manage VIP membership. VIP changes record the acting administrator, client, previous/new status and time. Signal posts store their author, body, creation time and any private image attachment; V2 attachments also use upload verification information such as file type, size and hash. Channel access and subscriber statistics support service operation.
Private support conversations
Support messages, sender identity, conversation history, creation times and read positions are stored to provide client-to-admin assistance and unread indicators. Clients can access their own conversations; authorized administrators can access the support inbox. Do not send passwords, authentication tokens or unnecessary sensitive financial details.
Notifications and optional browser push
The application stores signal notification records, read status and preferences for Free/VIP alerts and language. If you enable supported browser push, a browser subscription endpoint, delivery keys and delivery-job status are processed for alerts. Push delivery depends on browser permission and service configuration. Push alerts are designed not to include private signal content.
Browser storage and service providers
Language and theme choices are saved in localStorage. Supabase authentication uses session cookies; optional push uses a service worker and browser subscription. Google provides sign-in; Supabase provides authentication, database, private file storage and realtime features. Browser push providers may process delivery requests. Choosing Telegram opens a separate service governed by its own terms and privacy practices. The production hosting provider and processing locations still require confirmation.
Security and your requests
Access controls are used to restrict profiles, private conversations and channel images, but no online system can guarantee absolute security. Depending on applicable law, you may have rights to request access, correction, deletion or other handling of your personal data. Contact support through the Contact & Support page so the request can be reviewed and identity verified where necessary. This page does not promise automatic deletion, a particular retention period or a fixed response deadline.