Privacy · Updated September 19, 2026

Your application information.

This notice describes marketing visits, applications and account services operated by Sebastin Lyonns under the LeaxAI brand. Contact support@tlyonns.com with questions about your information or to request access, correction, or deletion.

What the application collects

Your name, email address, website or channel link, offer, preferred access, and the question you want to explore. Please do not include customer records, passwords, or sensitive personal information.

Why it is collected

We use your answers to review pilot fit and contact you about the application. Submitting does not subscribe you to a marketing list, create a paid account, or authorize a charge. Application records are available through an administrator-only review page.

Storage and service providers

Applications are stored in the site’s database. The website and database hosting services process information needed to operate this flow. Records are retained while evaluating and following up on your application; contact us to request deletion when you no longer want to be considered.

Content-to-client self-assessment

Quiz answers, optional notes and goals stay in this browser tab’s session storage for up to 24 hours after your last interaction. Starting over clears those answers. The quiz does not collect an email address or send a results email. Fixed progress events and one of eight broad result categories may be sent to Meta, without your individual answers, notes, goals or customer counts. A separate first-party cookie keeps that result category for up to 24 hours. When you start checkout, the category is saved with the checkout source record so we can compare quiz routes with verified purchases. That record follows our checkout retention, rather than the browser cookie’s expiry. Contact us to request deletion.

Dashboard agent

If agent access is enabled for your workspace, LeaxAI sends your question, a bounded portion of recent conversation history, and the authorized dashboard evidence needed to answer it to the model provider you select: OpenAI, Anthropic, or Google. Do not put passwords, payment details, or unrelated sensitive personal information in agent chats. Conversations are saved to your LeaxAI account until you delete them. Coaches cannot open a customer’s saved conversations. Provider processing remains subject to the selected provider’s business API data terms.

Connected data sources

When you authorize a data connection, LeaxAI retrieves the source metrics needed for that import from YouTube, Google Analytics, Instagram, TikTok, X, Calendly, or Stripe. Authorization credentials are encrypted on the server. We store account identifiers, granted permissions, source values, reporting periods, timestamps and import history. Calendly invitee names, email addresses and answers are not retained by these imports. Imported metrics are not sent to advertising services, and connection credentials are not sent to the dashboard agent.

Disconnecting stops imports and deletes imported source values and source corrections. Records you enter or approve for publication, including automatic publication, stay until you delete them. We also request Google grant revocation; an encrypted token may remain in a retry queue for up to seven days if that request fails. Google revocation can affect your other Google connections. For Instagram, TikTok, X, Calendly and Stripe, also remove LeaxAI in the provider’s connected-app settings to revoke the provider grant.

Source observations expire after 365 days, with shorter limits for social and Google data: Instagram, TikTok and X source observations expire after 30 days. YouTube publication data expires after 30 days without a refresh. Google, Instagram, TikTok and X source history is deleted if authorization has not been verified within 30 days. Detected revocations remove imported data. Temporary import checkpoints expire after one day and recent-import previews after 30 days. Weekly publication previews also expire after 30 days; their approval expires after 30 minutes. Published revisions retain the values and mapping used for that record until account deletion. Source references are removed on disconnect and after 365 days, or 30 days for Instagram, TikTok and X. Provider processing is subject to that provider’s own privacy terms.

Cookies and source information

A first-party cookie can retain first- and last-touch campaign labels, landing paths, referring origins and an advertising click identifier for up to 90 days. These are attached to an application or checkout to understand where interest came from. A separate, signed, HTTP-only receipt cookie lasts one hour so the confirmation page can verify your saved application. Signing in uses the existing account authentication cookies.

Advertising measurement

Public marketing pages use the Meta Pixel to measure page visits and advertising performance. Meta may receive page URLs, browser and device information, IP addresses, and cookie identifiers, and may associate visits with your Meta account for advertising. Our integration sends PageView events on public marketing pages, plus custom events for example interaction and completion, pricing views, plan selections, and checkout submissions. These custom events contain only fixed event names, not form answers or payment values. They indicate interest, not a purchase. After Stripe verifies a purchase, the account setup page may send one browser Purchase event. When server-side Meta measurement is configured, we also send the same Purchase event ID, currency, pre-tax value, hashed billing email and available Meta browser or click identifiers. Meta uses the shared event ID to deduplicate the browser and server copies. Application answers, passwords and customer dashboard data are not sent. The general PageView pixel is not installed on account or dashboard pages.

Abuse prevention

The application endpoint uses hashed email and, on Vercel, hashed network identifiers for short-lived submission limits. Raw network identifiers are not stored in the application database by this endpoint. Hosting services may maintain their own operational request logs.