Cookie Policy
Effective date: 9 September 2026 Version: 1.1.0 · Supersedes the version dated 16 April 2026
This policy explains how Flyb Digital Solutions, LLC (“FlyB”) uses cookies and similar technologies. Read it alongside the Privacy Policy.
1. What these technologies are
- Cookies are small text files a site stores in your browser and reads back on later visits.
- Local storage and session storage hold data in your browser without sending it back to the server on every request. FlyB uses them heavily for preferences and drafts.
This policy covers both. Where it says “cookie”, read “cookie or equivalent browser storage”.
2. Where this policy applies
FlyB operates several kinds of host, and they behave differently:
| Surface | What it is |
|---|---|
| flyb.app | The marketing site |
| The dashboard | Where you build and manage things |
| docs.flyb.app | This documentation site |
| Published pages and blogs | Sites our customers build and publish |
| Short-link hosts | Where tracked URLs and QR Codes resolve |
On a published page or blog, the site belongs to a FlyB customer, and that customer decides which additional tags run on it — their own Google Analytics, their own Google Tag Manager, their own scripts. FlyB provides the mechanism; the customer chooses what to load and is responsible for the notice and consent that choice requires. This policy covers only the cookies FlyB itself sets.
3. Categories
3.1 Strictly necessary
Required for the Services to function. They cannot be switched off, and the Services will not work without them.
| Name | Purpose |
|---|---|
flyb_api_key | Keeps you signed in to the dashboard (browser storage) |
flyb_org_id, flyb_current_org_id, flyb_organization_id | Which organisation you are working in, so the right data is loaded |
flyb_session_handoff | Carries a sign-in securely between FlyB hosts |
flyb_blog_{slug} | The member session for a private or community blog. Scoped to that one blog |
flyb_blog_join | The one-time, two-minute ticket that joins you to a blog after signing in |
flyb_chat_{page} | The FlyB Chat session on a published page or blog, so the chat opens straight into your conversation on your next visit instead of asking for the form again. One per page, for up to 12 months. It holds a random token, not your name or e-mail |
flyb_chat_ws:{organisation}:{member} | The session of the support chat in the dashboard (browser storage). Renewed from your sign-in every few hours |
flyb_consent | Records your cookie choice, so we do not ask again |
| Stripe cookies | Set by Stripe during checkout, for payment processing and fraud prevention |
3.2 Functional
Remember your preferences. Turning them off does not break the Services, but it makes them less convenient.
| Name | Purpose |
|---|---|
NEXT_LOCALE | The language you are using FlyB in — the one you picked, or the one the site opened in — so every FlyB site opens in it |
flyb_onboarding_dismissed | Whether you dismissed the onboarding guide |
flyb_analytics_start_date, flyb_analytics_group_by | Your last Analytics explorer settings |
flyb_contacts_export_prefs | The columns and delimiter you last exported with |
flyb_crm_table_prefs | The columns and page size you chose for the CRM table view |
flyb_agenda_calendar:{organisation} | The calendar you last opened in the team’s agenda (Inbox and contact record), so it opens on it again (browser storage) |
flyb_recent_variables | The variables you inserted last, offered first the next time you open the variable picker |
flyb_page_wizard_data | Your answers in the page wizard, so a reload does not lose them |
flyb_lead_search_*, flyb_lead_crm_funnel, flyb_lead_crm_stage | Your last Active Search settings |
flyb_test_email, flyb_apidoc_key | The last test address and the API key selected in the docs console |
flyb_videos_gen_setup, flyb_images_gen_setup, flyb_videos_gen_history, flyb_images_gen_history, flyb_videos_gen_job | Your AI generator settings, recent results and the job being tracked |
flyb_subscription_confirmation_seen, flyb_intended_plan, flyb_open_page_floating | Small interface states |
The OpenRouter key
flyb_openrouter_key and flyb_openrouter_models hold the API key and model choices
for the AI video and AI image
generators.
These stay in your browser and are never sent to FlyB’s servers. The key cookie is deliberately scoped to the dashboard host alone, so it cannot travel to any other FlyB host. Clearing your cookies means pasting the key again. See Privacy Policy, section 7.2.
3.3 Analytics and attribution
Let us and our customers understand how content performs. FlyB’s own analytics are stored as aggregated daily counts, not as a per-visitor profile.
| Name | Purpose |
|---|---|
flyb_analytics_daily_id | Links a form submission, or a purchase started from a pricing table, back to the visit that produced it, so a lead or a sale can be attributed to the right page, campaign or QR Code |
flyb_utm_source, flyb_utm_medium, flyb_utm_campaign, flyb_utm_term, flyb_utm_content | Carry the campaign parameters of the visit through to the moment a contact is created |
flyb_clid | Carries the advertising click identifier of the visit (such as Google Ads’ gclid) through to the moment a contact is created, so a lead can be reported back to the advertisement that produced it. It identifies the click, not the person, and is not used to target advertising |
flyb_contact_origin, flyb_native_destination | Record where a visitor came from and where they were headed |
flyb_ab_variant | Keeps a visitor on the same version of a page in an A/B test, so the test result means something |
flyb_book_{slug} | Keeps a visitor with the same team member on a booking distribution link |
flyb_tool_log_id | Carries what you built with a free public tool into your new account, so you do not retype it |
flyb_affiliate_ref | Attributes a signup to the affiliate who referred it |
| Google Analytics cookies | Product analytics on FlyB’s own sites |
Attribution cookies serve a purpose our customers depend on: without them, a lead cannot be linked to the campaign that produced it.
3.4 Advertising
FlyB sets no advertising or cross-site tracking cookies, and does not sell or share personal data for cross-context behavioural advertising.
4. Third-party cookies
| Provider | On which surface | What for |
|---|---|---|
| Stripe | Checkout | Payment processing and fraud prevention |
| Google Analytics | FlyB’s own sites | Aggregate product analytics |
| Sign-in and Calendar authorisation | Authentication | |
| Our customers’ own Google Analytics / Tag Manager | Published pages, blogs and short links, where the customer configured them | Whatever the customer configured |
Cookies set by a third party are governed by that party’s own privacy policy.
5. Your choices
5.1 The consent notice
Where the law requires consent — principally the EEA, the United Kingdom and Brazil —
we ask before setting non-essential cookies, and record your answer in flyb_consent.
You can change your mind at any time by clearing that cookie and reloading.
5.2 Your browser
Every major browser lets you view, delete and block cookies, and clear local storage, from its settings. Some offer a per-site control.
5.3 Google Analytics
You can opt out of Google Analytics across all sites with Google’s browser add-on.
5.4 What breaks if you block them
- Strictly necessary cookies — you cannot sign in, your organisation cannot be resolved, checkout will not complete, private blogs will not open, and the FlyB Chat on a page asks you to identify yourself again on every visit.
- Functional cookies — preferences reset on every visit, and the AI generators ask for your OpenRouter key each time.
- Analytics and attribution cookies — visits are still counted in aggregate, but leads can no longer be attributed to the campaign, page or QR Code that produced them, and A/B tests stop being reliable.
6. Do Not Track and Global Privacy Control
There is no common standard for how sites should answer a Do Not Track signal, so we do not respond to it. We do honour the Global Privacy Control signal where the law requires it — though FlyB does not sell or share personal data for advertising in any case, so there is nothing for it to stop.
7. Changes
We may update this policy. The version and effective date at the top identify the current one, and material changes are announced as described in the Privacy Policy.
8. Contact
Questions about cookies: [email protected].