What we hold, what we don't.
The list below is enumerative, not aspirational. Every cookie, every local-storage entry, every sub-processor that touches a byte of your data is named. Last reviewed 2026-05-24.
Cookies the browser receives
EDGE Terminal sets one cookie. It exists so we can recognise you across requests — pure authentication, no tracking, no behavioural profiling.
| Name | Purpose | Lifetime | Legal basis |
|---|---|---|---|
| edge_session | HMAC-signed payload carrying your email, tier and expiry. Read on every authenticated request to prove you are you. | 7 days (trial), 30 days (paid). Cleared on sign-out. | Strictly necessary — ePrivacy Directive Art 5(3) exemption. No consent required. |
What we don't set: no Google Analytics, no Plausible, no PostHog, no Mixpanel, no Vercel Analytics, no Cloudflare Insights, no Hotjar, no LogRocket, no marketing pixels (Meta, X, LinkedIn, TikTok). No third-party JavaScript runs in your browser on a normal page load.
Local storage
One key, browser-local only, never transmitted to our servers:
| Key | What it stores |
|---|---|
| edge-fullscreen | Whether the dashboard chrome is collapsed. Set when you click the fullscreen toggle in the top bar. Clearing your browser data removes it. |
Personal data we hold
The minimum to run the product. Listed by table — these come straight from the production database schema.
- Account. Email, hashed password, tier, trial start/expiry, last sign-in timestamp, Stripe customer ID.
- Trade journal.Trades you log: pair, side, entry, stop, target, size, P&L, your notes. Tagged to your account ID.
- Prop trackers. Challenge progress you set up (firm, account size, profit target, drawdown limits, current equity curve).
- Watchlist + alert rules. Pairs you watch, alert thresholds, delivery channel (email / Discord webhook URL you supplied).
- Billing history. Stripe subscription IDs, invoice IDs, payment-method last four. The full card number never reaches us.
Sub-processors
Companies that process data on our behalf. Each has its own DPA in place. The full list with hosting region and data scope lives at /trust/sub-processors. Headline four:
| Vendor | What it touches | Region |
|---|---|---|
| Supabase (database, auth) | All operator + journal data | EU (Frankfurt) |
| Vercel (hosting, edge) | Request routing, static assets, function logs | EU + US edge (no PII in logs) |
| Stripe (billing) | Email, card, subscription state | US (SCCs in place) |
| Resend (transactional email) | Email address + email body | US (SCCs in place) |
Optional: Sentry receives server-side exceptions when SENTRY_DSNis configured. We do not load Sentry's client SDK in your browser, so no browser events are forwarded.
What we do not do
- We do not train AI models on your trading data.
- We do not sell or rent your data, ever.
- We do not co-locate operator data with our marketing systems (the marketing landing and the dashboard are separate route groups, separate caches, separate analytics posture).
- We do not embed third-party trackers or advertising pixels.
Your GDPR rights
You can exercise any of these by emailing privacy@edgefx.xyz. We respond within 30 days, free of charge for the first request per calendar year.
- Access (Art 15). A full export of every row we hold against your email, as JSON.
- Rectification (Art 16).Correct anything that's wrong. Most fields you can edit yourself in /account.
- Erasure / right to be forgotten (Art 17). Cancelling your subscription already deletes your app_users row (and cascades to journal, trackers, alerts). You can also request a hard delete without cancelling.
- Portability (Art 20). Same export as access, machine-readable. Trades arrive as CSV + JSON.
- Object / restrict (Art 21 + 18). Pause specific processing — e.g. stop email digests but keep the account open.
- Withdraw consent. The auth cookie is the only thing requiring consent (by signing in). Sign out, clear the cookie, done.
- Complain to a supervisory authority. You can lodge a complaint with your national DPA at any time.
Data retention
- Active account: data retained for the life of the subscription.
- Cancelled / deleted account: app_users row purged immediately; cascading rows deleted within 24 hours by the nightly cleanup job.
- Stripe billing records: retained 7 years for tax compliance (held by Stripe, not us).
- Server-side logs (Vercel): 30 days, then aggregated counters only, no PII.
Changes to this policy
When we add a sub-processor, a cookie or a new data category, we update this page in the same commit that ships the change. Material changes trigger an email to every active operator. The change log is part of the public git history at github.com/0nly4Weed/edge.
Contact
Privacy questions, data requests, or DPA negotiation: privacy@edgefx.xyz. General support: hello@edgefx.xyz. For institutional procurement see /trust.
Last reviewed 2026-05-24 · Reviewed quarterly · Source of truth lives in the commit at apps/web/app/privacy/page.tsx