Account registration
When you register, ABRIDYN receives the name and email address you provide. Your password is submitted to Supabase Auth for account authentication; ABRIDYN does not display it in the application.
Your data and your privacy.
How Abridyn uses your account information, trading records and research requests.
Session cookies
Supabase Auth uses cookies to maintain your authenticated session and support server-side route checks. Do not share your browser session or email verification link with anyone.
Your trade records
Trade details you enter in the journal are stored with your account in Supabase. Journal access is scoped to your authenticated user. Metrics and observations are calculated from the records you provide.
Stripe subscription records
If subscription checkout is enabled, Stripe processes payment details on its hosted checkout. ABRIDYN stores your selected plan, subscription status and related Stripe identifiers to manage access. ABRIDYN does not store raw card numbers.
Trade uploads and demo data
Your Journal uses the trades you enter or upload by CSV. Product images marked DEMO or SAMPLE use illustrative records, separate from customer accounts.
Information used to respond
Waitlist requests include your name, email, experience, selected markets and interests, and consent to beta updates. These are stored to manage invitations and contact you about access. Contact-form details are used to answer your inquiry. Contact support@abridyn.com to request a change or stop beta updates.
Prompts and research context
News/Macro AI sends your prompt, selected context, limited recent conversation context and available source evidence to OpenAI to generate a response. The integration requests non-storage of responses from the provider. Personal Journal records are not connected to this research feature. Do not include credentials or sensitive account details in prompts. Current conversation history is session-based.
Your choice on public pages
Optional measurement is off until enabled through the public footer. A consent cookie remembers the choice for six months. When enabled, first-party event logs count public page paths, broad traffic categories, waitlist CTA clicks and accepted beta requests. They do not include names, emails, user IDs, raw referring URLs, URL queries or trade records. Disable measurement from the same footer at any time. Do Not Track is respected. Hosting infrastructure may separately process request information for operation and security; event logs follow the hosting account’s retention settings.
Account data is processed by Supabase for authentication and journal storage. Stripe processes billing details when paid checkout is enabled. For access, correction or deletion requests, contact support@abridyn.com. Retention and request handling depend on the data involved and applicable obligations.