Authenticated accounts
ABRIDYN account registration and sign-in use Supabase Auth, including email verification. Protected terminal requests are checked on the server before access is granted.
Security, without overstatement.
A clear view of the protections currently implemented—and the capabilities that are not connected.
Credentials stay server-side
The browser uses the Supabase publishable key for authentication. Supabase service-role and Stripe secret keys are used only by server-side code and are not sent to the browser. Do not share account passwords, session cookies or email confirmation links.
Private journal records
Journal trades are stored in Supabase and scoped to the authenticated account with row-level security. Broker connections and financial account aggregation are not connected.
Hosted payment processing
When checkout is enabled for a deployment, card payment is collected by Stripe-hosted Checkout. ABRIDYN stores subscription identifiers and status for account access; it does not receive raw card details.
ABRIDYN does not claim independent security certifications or regulatory approvals.