Narrow permissions. Server-side secrets. Clear user control.

1. Read-only provider access

FRA Prop HQ requests the account and completed-trade information needed for the product. It does not request order-placement permission and cannot place, modify or cancel trades.

2. Credentials and tokens

Trading passwords are entered with the provider and are not stored by FRA Prop HQ. Provider access tokens are kept server-side and encrypted before storage. API keys and service-role credentials are not shipped in the website.

3. Customer separation

Supabase authentication and row-level database policies separate customer records. Administrative member functions require server-side role checks; hiding a page in the browser is not treated as the security boundary.

4. Billing

Stripe processes card details, Checkout and the billing portal. FRA Prop HQ stores only the customer, subscription, invoice and status data required to manage access and support.

5. Webhooks and email

Stripe webhook signatures are verified before billing changes are processed. Transactional email events use deduplication records to avoid repeated welcome, payment, cancellation and refund messages.

6. Coach

OpenAI credentials stay server-side. Only the selected context needed to answer a Coach request is sent. Coach is optional and does not control trades or provider accounts.

7. User control

Members can disconnect provider logins, hide or archive accounts, manage billing, sign out and request deletion. Provider authorisation can also be revoked through the provider where available.

8. Reporting a concern

Email support@fraprophq.com with the time, affected account and a clear description. Do not include passwords or keys.