Security and data handling
TradingSurv is multi-tenant, which means the interesting question is not whether there is a login but what stops one organisation's workspace reaching another's. This page answers that, and is explicit about the certifications it does not hold.
Tenant isolation
Every organisation-scoped table — watchlists, alert rules, memberships, subscriptions — is protected by Postgres row-level security. The policy is enforced by the database on every query, so a missing filter in application code returns nothing rather than returning someone else’s rows.
That is deliberate layering rather than belt-and-braces theatre. Access control that lives only in application code fails open the first time a new query path forgets it; access control in the database fails closed.
What is shared and what is not
- Market data
- Shared reference data. Prices, load, generation and bid curves are published by exchanges and TSOs — every tenant reads the same rows, because they are the same public facts.
- Watchlists and alert rules
- Organisation-scoped and isolated by row-level security.
- Billing
- Organisation-scoped. Card details are never held by TradingSurv; checkout and storage are handled by Stripe.
- Your own order and trade data
- Not held at all. TradingSurv surveils the published market, not your book — so there is no customer trade data in the system to isolate.
Authentication
Sessions are issued and verified by Supabase Auth. Every request is checked against the auth server rather than trusted from a cookie, so a tampered or expired token reads as signed out. Protected pages are gated three independent times: at the edge by middleware, again inside the render, and finally by row-level security — which is the one that actually holds the data back if the first two are misconfigured.
Where data lives
- Application database
- Supabase (managed Postgres), EU region.
- Raw upstream payloads
- Cloudflare R2 object storage, written before parsing so a finding can be replayed against the exact bytes that produced it.
- Web application
- Vercel.
- Collectors
- Cloudflare Workers.
What we do not claim
TradingSurv does not currently hold SOC 2, ISO 27001 or any comparable attestation, and there has been no third-party penetration test. Saying so plainly is more useful to a procurement review than a page of security language that avoids the question — if one of those is a hard requirement for your firm, it is a reason not to buy yet, and you should find that out now.
The architecture above is what exists and can be verified. Anything beyond it would be a roadmap item described in the present tense.