Privacy policy

Data controller

In Soo Seguier — Individual

Email: florye.com/signup

Data collected

For the waitlist, we collect: email address, first name, last name, occupation, CRM tool used, and interest in an AI agent.

This data is collected only when you voluntarily sign up via the waitlist form.

Processing purposes

  • Managing the waitlist and communicating about the launch
  • Sending information about the Florye service
  • Qualifying needs to adapt the product

Legal basis

Processing is based on your consent (Article 6.1.a of the GDPR), collected when you sign up for the waitlist.

Data recipients

Your data is processed by the following sub-processors:

  • Brevo (Sendinblue SAS, France) — contact and email management
  • Baserow (Baserow B.V., Netherlands) — qualification tracking
  • Vercel Inc. (United States) — site hosting and performance measurement
  • Umami (EU Cloud) — anonymous audience measurement, no cookies
  • PostHog (PostHog Inc., EU servers — Frankfurt) — session recording and heatmaps
  • Slack (Salesforce Inc., United States) — internal sign-up notification (no personal data transmitted)

Retention period

Your data is retained for the duration of the pre-launch phase, then deleted within 12 months after the service launches, unless you become a customer.

Your rights

Under GDPR, you have the following rights: access, rectification, erasure, restriction, portability, and objection.

To exercise these rights, contact us at: florye.com/signup

You may also lodge a complaint with your local data protection authority.

Cookies and analytics

This site does not use any tracking or advertising cookies.

We use Umami for anonymous audience measurement (page views, traffic sources). Umami sets no cookies and collects no personally identifiable data.

We use PostHog for session recording and heatmaps to improve the user experience. PostHog is hosted in the EU (Frankfurt) and uses browser localStorage to maintain session continuity. Input fields are automatically masked in recordings (mask_all_inputs enabled).

Policy updates

This policy may be updated. The date of last modification will be shown below.

Last updated: 25/03/2026