Privacy Policy
Collect what the product needs. Do not pretend private means invisible.
WrektView is a developing beta service. This page describes the data practices that are currently known from the implementation and avoids claims of zero logging, perfect anonymity, or guaranteed deletion beyond what the system can verify.
Authentication data
WrektView uses Supabase for authentication and related backend services. If you sign up with email, Supabase processes the email address and authentication credentials necessary to operate your account. If you use Google sign-in, Google and Supabase process the authentication exchange and may provide account metadata to the authentication system.
Public trader identity
WrektView's public identity model is username-first. Your private email address and Google full name are not intended to be displayed as your public trader identity. Profile features may store a public username, biography, avatar, and user-created profile content.
Chat and direct messages
Public room messages and direct messages are stored so they can be delivered to participating users and synchronized in real time. WrektView is being built toward a one-hour live-application retention policy for chat messages and chat images. Until that retention feature is deployed and independently verified, users should not assume physical deletion occurs exactly one hour after posting.
Images and media
Chat images and profile media may be stored using Supabase Storage. Private media should be delivered through authorized or time-limited access rather than unrestricted public bucket listing. Media retention may differ between short-lived chat content and persistent profile content.
Operational data
Infrastructure providers may process technical information necessary to deliver and secure the service, such as network requests, timestamps, error information, IP-related connection data, authentication events, and security logs. WrektView does not promise that infrastructure backups, logs, or disaster-recovery systems share the same deletion timing as the live application database.
Third-party services
The service may load or link to third-party products such as TradingView, Google authentication, Supabase, and external market-information sites. Those services operate under their own privacy terms and technical practices.
Security and legal obligations
WrektView may preserve, disclose, restrict, or process information when reasonably necessary to secure the service, investigate abuse, comply with applicable law, or respond to valid legal process. The free-expression mission does not create a promise to conceal information from legally binding process.
Changes
This policy should be updated when the actual data model, service providers, retention behavior, or public features materially change. Product claims should follow verified implementation rather than aspirational privacy language.