Privacy
What PrismEdge collects, and what you control.
How PrismEdge handles the data needed to run the private terminal, billing, support, and the dashboard, which services process it, and the rights you hold over it.
What we collect
11 categories
| Data | Why | How long | Who sees it |
|---|---|---|---|
| Account email, name and password hashContract | Signs you in and identifies your account. | While the account exists. | Supabase. Resend sends email. |
| Subscription and access statusContract | Decides what your account is allowed to open. | While the account exists. | Supabase. |
| Stripe customer, subscription and invoice referencesLegal obligation | Matches payments and renewals to your account. | As long as legal record keeping requires. | Stripe. |
| Support messagesContract | Answers billing, access, setup and login issues. | While operationally needed. | PrismEdge support. |
| Cookie choice and login sessionpe_consent, pe_cookie_probeContract | Keeps you signed in and remembers your cookie choice. | While you stay signed in. The choice lasts until you change it. | Your browser. Supabase holds the session. |
| Chart drawings, saved drawing versions, chart settings, price alerts and which notifications you have readContract | Keeps your chart, alerts and notification bell the same on every device you sign in on, and watches your price alerts while the terminal is closed. | While the account exists, or until you delete them. Automatic drawing versions older than 30 days are removed. | Supabase. |
| Price alert emailsContract | Tells you when the market crosses a price alert you set. Each alert fires once. | The alert is kept until you delete it; the email is not stored by PrismEdge. | Resend sends the email. |
| Prism Arcade callsign, scores and saved gameContract | Saves your game to your account and ranks your runs on the daily board. | While the account exists. | Supabase. Other members see your callsign and score on the board. |
| Email address given for the free checklistConsent | Sends the checklist you asked for, and the product updates the form asks you to agree to. | Not set out separately. | Supabase stores it. Resend sends the email. |
| Error and performance reportsLegitimate interest | Finds and fixes faults after they happen. | Not set out separately. | Sentry. |
| Analytics and referral identifierspti_analytics_id, pti_referral_codeConsent | Product analytics, visit analytics and referral attribution. | Erased when consent is declined or withdrawn. | PostHog, Vercel, Sentry replay. |
Account email, name and password hash
Contract- Why
- Signs you in and identifies your account.
- How long
- While the account exists.
- Who sees it
- Supabase. Resend sends email.
Subscription and access status
Contract- Why
- Decides what your account is allowed to open.
- How long
- While the account exists.
- Who sees it
- Supabase.
Stripe customer, subscription and invoice references
Legal obligation- Why
- Matches payments and renewals to your account.
- How long
- As long as legal record keeping requires.
- Who sees it
- Stripe.
Support messages
Contract- Why
- Answers billing, access, setup and login issues.
- How long
- While operationally needed.
- Who sees it
- PrismEdge support.
Cookie choice and login session
pe_consent, pe_cookie_probe
Contract- Why
- Keeps you signed in and remembers your cookie choice.
- How long
- While you stay signed in. The choice lasts until you change it.
- Who sees it
- Your browser. Supabase holds the session.
Chart drawings, saved drawing versions, chart settings, price alerts and which notifications you have read
Contract- Why
- Keeps your chart, alerts and notification bell the same on every device you sign in on, and watches your price alerts while the terminal is closed.
- How long
- While the account exists, or until you delete them. Automatic drawing versions older than 30 days are removed.
- Who sees it
- Supabase.
Price alert emails
Contract- Why
- Tells you when the market crosses a price alert you set. Each alert fires once.
- How long
- The alert is kept until you delete it; the email is not stored by PrismEdge.
- Who sees it
- Resend sends the email.
Prism Arcade callsign, scores and saved game
Contract- Why
- Saves your game to your account and ranks your runs on the daily board.
- How long
- While the account exists.
- Who sees it
- Supabase. Other members see your callsign and score on the board.
Email address given for the free checklist
Consent- Why
- Sends the checklist you asked for, and the product updates the form asks you to agree to.
- How long
- Not set out separately.
- Who sees it
- Supabase stores it. Resend sends the email.
Error and performance reports
Legitimate interest- Why
- Finds and fixes faults after they happen.
- How long
- Not set out separately.
- Who sees it
- Sentry.
Analytics and referral identifiers
pti_analytics_id, pti_referral_code
Consent- Why
- Product analytics, visit analytics and referral attribution.
- How long
- Erased when consent is declined or withdrawn.
- Who sees it
- PostHog, Vercel, Sentry replay.
The consent tag marks data that stays off until you accept it and can be withdrawn any time. Legal bases are clause 03, periods are clause 07. Where this policy sets no period out, the cell says so.
Contents
Key points
Analytics only with consent. Product analytics, Vercel Analytics, Sentry session replay, and referral attribution stay off until you accept them on the cookie banner. Declining erases the identifiers. Sign-in, checkout, and every product feature work without them.
Stripe handles payments. Full card numbers and card security codes are processed by Stripe and never reach PrismEdge. PrismEdge stores the billing references needed to know your subscription status.
You control your data. Download everything PrismEdge holds about your account from the Account page in your dashboard, and request deletion from the same page. You can withdraw analytics consent at any time via Cookie Settings in the footer or on the Account page in your dashboard, and complain to your data protection authority.
01Who is responsible
PrismEdge is a business name of Robert Iordache, a sole trader in Ireland. Robert Iordache is the data controller for the data described here. For any privacy question or request, contact support through the Support page or write to privacy@prismedge.eu; requests are handled against the account the request comes from.
02Information collected
Account data: email address, name, password hash (held by Supabase Auth), subscription and access status. Billing references: Stripe customer and subscription identifiers, invoice status. Operational data: support messages, admin action logs, and security logs. Usage events are collected only after analytics consent.
03Why, and on what legal basis
Operating your account and access runs on contract. Billing record keeping runs on legal obligation. Security controls, fraud prevention, and error monitoring run on legitimate interest. Product analytics, session replay, and referral attribution run on consent only, and are off until given.
05Services that process data
Supabase (authentication and database), Stripe (payments), Vercel (hosting, and visit analytics only after consent), Resend (transactional email), Sentry (error monitoring; session replay only after consent, with text masked), PostHog (product analytics, only after consent). Each processes data only to provide its service. Lumen, the in-app assistant, is switched off at the moment: nothing you type into it is sent to any AI provider, and PrismEdge's servers keep no message text. Before it is switched on, this notice will name the provider, what it receives, what it keeps and the safeguard for any transfer. Where you have given us a TradingView username, TradingView receives it so that access to the invite-only PrismEdge indicator can be added to and removed from your TradingView account; TradingView handles your own TradingView account under its privacy policy.
06International transfers
Some of the services above process data in the United States. Transfers rely on the safeguards those providers offer under EU data protection law, including standard contractual clauses and, where applicable, the EU-US Data Privacy Framework.
07Retention
Account data is kept while the account exists. Billing records are kept as long as legal record keeping requires. Support messages and admin logs are kept while they are operationally needed. Analytics identifiers are erased when consent is declined or withdrawn.
08Your rights
Under EU data protection law you can request access, correction, deletion, portability, or restriction of your data, object to processing based on legitimate interest, withdraw consent at any time without affecting past processing, and lodge a complaint with your supervisory authority. Export is self-service from the Account page in your dashboard, where you can also request deletion; deletion is completed within 30 days and confirmed by email. Correction, restriction and objection are handled through support.
09Support messages
Support requests are used to respond to billing, access, setup and login issues. Do not send exchange passwords or private keys; support will never ask for them.
10Security controls
Protected routes, server side entitlement checks, environment variable secrets, Stripe webhook signature verification, and Supabase row level security policies reduce unauthorised access. Error reports are masked before they leave the browser.
Need a data correction, export, or deletion?
Export and deletion requests start on the Account page in your dashboard. Use support for questions about your account profile, subscription state, or stored access status.