Privacy
Privacy for account, access, and billing state.
How PrismEdge handles the data needed to run private TradingView access, dashboard setup, support, and subscription status.
Account and access data
PrismEdge uses account details, email, display name, TradingView username, subscription state, and access status to operate private access.
Stripe handles payments
Full card numbers and card security codes are processed by Stripe. PrismEdge stores billing references needed for subscription status only.
Supabase backed app data
Authentication, profiles, support, setup state, and access records are handled through Supabase backed routes and policies.
Details
The practical terms stay readable.
These notes explain the operating model in plain language. They do not replace solicitor-reviewed launch documents.
Information collected
The app may collect email address, name, TradingView username, subscription status, payment references, support messages, onboarding progress, and admin review logs.
How data is used
Data is used to create accounts, sync subscriptions, review TradingView access, provide support, send service messages, and protect the platform.
Support messages
Support requests are used to respond to billing, access, setup, login, and TradingView username issues. Do not send exchange passwords or private keys.
Analytics
If PostHog or similar analytics are configured, the app may record product usage events such as page views, button clicks, setup progress, and support interactions.
Security controls
Protected routes, server checks, environment variables, Stripe webhook signature verification, and Supabase policies reduce unauthorised access.
Data corrections
Customers can contact support for account, email, TradingView username, access, or billing-record questions tied to their profile.
Need a data or account correction?
Use support for questions about your account profile, TradingView username, subscription state, support request, or stored access status.