How we protect your work & your audience

Accounts sign in with email + password or Google. Passwords are hashed by our auth provider — we never see them in plaintext. Each account can only view and edit its own profile, links, subscribers, inquiries, broadcasts, and billing; Row-Level Security policies enforce these boundaries at the database layer, not just in the app UI.

Admin actions (moderation, SSL queue, team roles) are gated by a separate server-checked role. Session tokens live in the browser and can be revoked by signing out or changing your password.

We store the fields you create: profile details, links, product links, subscriber emails you collect, inquiries sent to you, broadcast drafts, and anonymized analytics events (link clicks, referrer, coarse device type).

Public profile pages expose only the fields you publish (handle, display name, bio, avatar, headline, links, booking URL). Your account email and internal integration IDs are never returned to visitors.

The application runs on Lovable's edge runtime. The database, auth, and file storage are managed Postgres on Lovable Cloud (Supabase). Avatars and uploaded files live in a private bucket and are served through scoped URLs.

We rely on the platform's backups and encryption-at-rest for the managed database and storage. We do not export or copy your data to any location outside the subprocessors listed below.

Transactional emails (welcome, inquiry notifications, password recovery) and broadcasts are sent through Resend from our verified sending domain.

Every subscriber email includes a one-click unsubscribe link backed by a unique token. Unsubscribed addresses are automatically excluded from future broadcasts. Coaches are responsible for how they collected the emails they upload or link to their subscribe form.

Subscriptions and one-off product sales are processed by Paddle as Merchant of Record. Paddle handles tax, invoicing, and card storage. We only receive the transaction status and metadata needed to grant your plan or unlock a purchase.

Every Paddle webhook is signature-verified before any subscription or entitlement change is applied.

We use a session cookie set by our auth provider so you stay signed in, and minimal local storage for UI preferences. We do not run third-party advertising or cross-site tracking pixels.

Public profile visits are recorded as anonymized events (page/link, referrer host, coarse device type) so coaches can see what's working. We do not sell this data.

You can delete your account at any time from Dashboard → Account. Deletion removes your profile, links, subscribers, inquiries, broadcasts, product links, and uploaded files.

Payment and invoice records held by Paddle are retained per their own policy and applicable tax law. Aggregated, non-identifying platform metrics may be retained for reliability and abuse prevention.

• Lovable Cloud (Supabase) — database, authentication, file storage.
• Resend — transactional and broadcast email delivery.
• Paddle — payments, tax, and invoicing as Merchant of Record.
• Google — only when you choose to sign in with Google.