Privacy notice
This notice explains what information Liquid Learn collects, why it is used, and the choices available to you.
Last updated October 30, 2026Who operates this site
Liquid Learn is a product of Fluid Business, based in Seattle, Washington. Questions about this notice or your information can be sent to info@fluidbiz.com.
Information you provide
When you submit the contact form, we collect your name, work email, company, role, enquiry topic, message, and communication preference. When you submit the health check, we collect your contact and organization details, answers, calculated results, and report preferences.
For demo bookings, we also collect your selected time, time zone, region and answers to any demo questions. Your approximate country from our hosting provider and your browser time zone help suggest a region; you can change that suggestion. We do not request your device’s precise location. Confirmed bookings create an event in a team member’s Microsoft 365 calendar and send a meeting invitation to your email address.
LiquidLearn Essential early access
When you register interest in Essential, we collect your contact name, company name, work email, preferred employee plan and optional marketing preference. We record the Republic of Ireland as the campaign market and retain permitted campaign attribution. Fluid Business reviews registrations and may enter them into its CRM manually to respond to your request and contact you when subscriptions become available. Occasional news and product updates require the separate, optional checkbox on the form.
A random request reference and a digest of your form details may be kept in session storage to prevent duplicate registrations on retry. The form does not store your contact details in browser storage. Registration creates no subscription, payment or learner account.
Browser storage and optional site analytics
Essential storage keeps your privacy choice, assessment draft and enquiry forms working. A random identifier and limited campaign attribution stay in session storage for the current browser tab, for at most 24 hours. We retain only campaign labels, a public landing-page path, referring hostname and UTC timestamps. Do not put personal information in campaign links. We do not create a persistent visitor identifier or device fingerprint.
If you accept site analytics, we record campaign arrivals, assessment starts and successful supported enquiries and assessments in our own database. We do not place names, email addresses, messages or assessment answers in this event table. We do not retain raw IP addresses, IP-derived identifiers, device characteristics or browsing histories for attribution. Network information may be used transiently for abuse prevention; hosting access logs are managed separately.
How information is used
- Respond to enquiries and provide requested assessment reports.
- Calculate assessment results and recommendations.
- Understand site performance and improve product communication.
- Protect the service, prevent abuse, and diagnose operational problems.
- Contact you about the enquiry when you have requested follow-up.
Service providers
The site uses infrastructure providers to host the application, store submitted records, and deliver email when configured. Current integrations include Vercel, Supabase, and Microsoft 365. When email delivery is configured, enquiry details and requested assessment reports are sent through Microsoft Graph and Exchange Online using our Microsoft 365 mailbox. These providers process information only to deliver their respective services.
Optional minimal advertising conversion reporting
We do not load Google Analytics, Google Tag Manager, Google Ads browser tags or Microsoft UET. If you separately permit minimal conversion reporting, and the integration is enabled, our server reports a successful enquiry or completed assessment only to the Google or Microsoft Advertising account that originated the paid visit.
The report includes that platform’s ad click reference, conversion type and UTC conversion time. Google also receives a random event reference for deduplication and consent indicators. No names, email addresses, messages, assessment answers, visitor IP addresses or browser histories are included. The click reference allows the advertising provider to link the conversion to its original ad click; it is not anonymous.
Before a choice, the click reference is held only in memory on the landing page. With permission it may stay in session storage and is encrypted in a separate server-side store. Unconverted references expire within 24 hours; a queued conversion reference is erased after provider acceptance or after seven days. Delivery-status records are kept for 30 days. Click references are excluded from enquiry attribution, marketing events and reports.
Google and Microsoft process the limited information under their own policies: Google privacy policy and Microsoft privacy statement. They may process it in other countries. We do not send hashed contact details, use enhanced conversions, create remarketing audiences or record browser sessions.
Your choices
Use “Privacy & cookie choices” in the footer to change site analytics and minimal advertising conversion reporting independently. Both are optional. Declining leaves forms and assessment results available. Withdrawing advertising permission deletes accessible click references and cancels unsent reports. A report already sent or in flight cannot be recalled through this control. Clearing browser storage removes your saved choice and draft. Contact info@fluidbiz.com to request access, correction or deletion of submitted information.
Retention and protection
Marketing events and attribution attached to enquiries and assessments are retained for 180 days. Submitted contact details and answers follow the separate operational retention policy and are retained only for as long as needed for the purposes described above, operational record keeping, security, or applicable legal requirements. We use access controls, encrypted transport, request validation, and restricted server-side credentials to protect it.