frequently asked
Yes — Apex is the primary use case Loryn was built around. Multi-account capture, mirrored copy-trade aware, prop-firm thresholds and trailing drawdown baked in. Loryn knows how Apex accounts size up, what counts as a blown account, and where you stand against your trailing drawdown at any moment.
Note: Loryn is not affiliated with Apex. Use of Loryn does not change your obligations under your Apex agreement.
If they route through Tradovate, capture works. The journal's prop-firm UI (drawdown thresholds, payout targets) is currently calibrated to Apex; other firms render as plain accounts. Better explicit support is on the roadmap.
Chrome and any Chromium-based browser — Brave, Edge, Arc, Opera. Not Safari, not Firefox.
Loryn is desktop-only on purpose. The journal needs the screen.
Today, no — Loryn captures from Tradovate's WebSocket. Broker-agnostic capture (NinjaTrader, IBKR) is on the roadmap; if it matters to you, sign up and tell us.
No, and we never will. The extension listens to fill events that come through the same public Tradovate WebSocket your own browser is already using. It doesn't see your password and doesn't capture the authentication frames that carry your JWT.
Supabase (Postgres), us-east-1, encrypted at rest. Row-Level Security at the database means your data is scoped to your account — another Loryn user querying our database can't see your rows under any condition.
You own your data. CSV export is in your settings page. Account deletion wipes every row tied to you.
Yes — from your settings page, one click. Cancels your Stripe subscription immediately, wipes every fill, every note, every conversation, removes your sign-in. It's not a soft delete.
No. Loryn is a journal companion. She reads back what's already happened — your fills, your patterns, your P&L — and holds you to the rules you wrote. She doesn't recommend trades, set targets on positions you haven't put on, or tell you which direction the market is going.
Capture latency is a few seconds from when the fill clears on Tradovate. Round-trip matching is per-account, in chronological order. We've run Loryn against tens of thousands of real fills; capture is consistent with Tradovate's own statements within rounding.
You should still reconcile against your broker statements monthly — that's good practice for any journal.
Yes — voice mode is in every tier. You speak, she answers. Hands stay on the platform. Standard tier has 30,000 voice characters per month; Pro has 100,000.
No. The daily AI caps are how we keep a paid customer from burning the budget — they're not a thing we can offer free without inviting abuse.
If you want to evaluate, sign up for Standard for a month and cancel before the next billing date. Cancellation takes effect at period end; you keep your data either way.
Stripe retries automatically. After 14 days of unresolved failure your account is restricted — Loryn pauses, but your data stays viewable. After 30 days the subscription is canceled. Data is retained for an additional 30 days then permanently removed unless you reactivate.
Yes — from your settings page. Cancellation takes effect at the end of the period you've paid for; you keep full access until then.
No refunds for partial periods. If a charge was in error, contact us within 30 days from your settings page and we'll sort it.
Anything else? Reach out from the contact link in your account after signing in.
Get started →