Privacy Policy

Last updated 18 November 2026.

This policy explains what NetMediaOne, LLC ("Flyder", "we", "us") does with personal data across every Flyder service. It replaces the separate policies that previously covered each product.

Service What it is Where
Flyder The AI assistant and the Flyder Plugin. flyder.ai
Flyder Engage AI engagement and messaging built on the same platform. engage.flyder.ai
Flyder Elevate A multi-tenant help desk. elevate.flyder.ai
Flyder Account The account, sign-in and directory service the others sign you in through. account.flyder.ai
Elevate Time A desktop timer for Flyder Elevate, and an optional browser extension that goes with it. Your own computer
Elevate Scribble A browser extension that sends a marked-up screenshot of a page to Flyder Elevate as a ticket or task. Your browser

Everything here applies to every service unless a section opens with a marked callout naming the products it covers. Nothing is repeated per product — where the products behave the same, it is said once.

#Which relationship you are in

Flyder Elevate is used by companies to support their own customers, so there are two different relationships and the difference decides who you ask:

You are Who decides what happens to your data Who to ask
An end user — you emailed a company's support address, used their help center, or opened a ticket in their portal That company. We hold and process the ticket on their instructions only. That company. If you cannot reach them, write to us and we will pass it on.
An account holder — an agent, an admin, or the company itself Us, for your login and how you use the Service. You, for the tickets in your account. support@flyder.ai

In data-protection terms: for tickets and everything in them we are a processor acting for the account. For sign-up, logins, billing and service logs — and for everything in Flyder, Flyder Engage and Flyder Account — we are the controller.

#What we collect

Your login and profile (Flyder Account, and every product through it) — name, email address, whether it is verified, a hashed password, two-factor secrets, active sessions, the organizations you belong to and your role in each, the applications you can reach, invitations and access requests, and your notification preferences. Passwords are never stored in readable form.

Your content

  • Flyder and Flyder Engage: the Input you provide — prompts, file uploads, feedback — and the Output generated from it.
  • Flyder Elevate, on behalf of an account: ticket subjects and bodies, comments and internal notes, email headers and routing metadata, attachments, contacts and companies, tags, CSAT responses and knowledge base articles. This is whatever your customers and agents write; we do not choose what goes into it.

Communication and other information you give us — your name, contact details and the contents of messages you send us, anything you provide in events or surveys, and information used to verify your identity. If you interact with our pages on social media, whatever you choose to share there, plus the aggregate analytics those platforms give us.

Payment and transaction information for paid plans.

Email operations data (Flyder Elevate) — delivery and bounce results, complaint and unsubscribe records, suppression lists and spam signals. Suppression records are kept as long as needed to stop us mailing someone who asked us not to.

Technical data — IP address (read from the connecting address, never from a header a caller can set), user agent and device information, request paths and timings, date and time of access, and error records. Used to run the Service, enforce rate limits, and investigate abuse and incidents.

Activity recorded by the Elevate Time desktop app — recorded on your own computer and never sent to us. See The Elevate Time desktop app and browser extension below.

Usage counters — per-account ticket, storage and API volumes, for limits and billing.

Security and audit records — administrative actions taken on an account or an organization, sign-in failures, and rate-limiting counters.

Where it comes from. Most of it you give us. The rest comes from:

  • Your organization — an administrator who invites you gives us your email address and the role they chose for you; a directory your organization connects (SCIM, from Okta or Microsoft Entra, for example) gives us your name, email address and whether you are active; and a single sign-on provider your organization uses tells us who you are when you sign in.
  • Your email domain — if an organization has verified the domain of your email address, we match your new account to that organization.
  • Stripe — whether a payment for a paid plan succeeded.
  • Your device — the technical data above.
  • Companies that use Flyder Elevate — the tickets and contact details they hold about you, as their processor (see Which relationship you are in).

What you have to give us. To have an account we need your name and email address, and either a password or a sign-in from an identity provider your organization uses. Without them we cannot create an account. A paid plan also needs payment details, which you enter on Stripe's own pages. Everything else is up to you.

#Cookies and local storage

Instead of cookies, the site uses your browser's local storage, and only for features you use:

  • Your theme — whether you chose light or dark mode.
  • The Flyder Engage chat window (loaded from engage.flyder.ai), so a chat survives reloads and moving between pages. It is kept only on your device:
    • a visitor token our server issues, used solely to link your browser to your own conversation so you can carry on with it. It is not used for analytics, advertising, profiling, or tracking you across sites;
    • the conversation's ID, and a local copy of your recent messages — the last 200 at most;
    • contact details you choose to type into the chat, such as your name or email address, so you are not asked for them again; and
    • whether the chat window is open or expanded.

This storage is strictly necessary to provide something you asked for — the display you chose, and a chat you started — which is the exemption for strictly necessary storage under Article 5(3) of the EU ePrivacy Directive and the UK's equivalent rule in PECR. That is why the site does not ask for consent with a banner.

You can remove all of it at any time by clearing your browser's site data (local storage) for flyder.ai. Doing so resets your theme and starts a new chat.

What you write in the chat — your messages and any contact details — is also sent to and stored on our servers so we can provide the chat. That is covered under What we collect above, as your content and as information you give us.

#How we use it

To provide, administer, maintain and analyze the Services; to sign you in and tell an application who you are; to let your organization's administrators manage access; to improve the Services and develop new ones; to communicate with you about the Services; to bill you; to prevent fraud, abuse and misuse and to protect the security of our systems; to carry out business transfers; and to comply with the law and protect our rights and yours.

We may aggregate or de-identify data and use it for analysis, research and product improvement, and publish or share aggregate statistics. We will not attempt to re-identify it.

Our legal basis. Under the GDPR and UK GDPR, each use rests on one of these:

What we do Legal basis
Provide the Services you signed up for: your account, signing you in to applications, your organizations, the features you use, support, and messages about your account Contract — it is what you asked us to do
Bill paid plans Contract
Keep invoices and tax records Legal obligation
Keep the Services secure: rate limits, fraud and abuse prevention, sign-in security and audit records Legitimate interests — protecting you, other users and the Services
Let your organization's administrators manage access, and tell an organization that someone with its verified email domain has an account Legitimate interests — the organization's interest in managing who uses its accounts
Improve the Services and develop new ones, from aggregated or de-identified data Legitimate interests — making the Services better
Respond to lawful requests and enforce our terms Legal obligation, and legitimate interests in protecting our rights

Where we rely on legitimate interests, we have weighed them against your rights, and you can object (see Your rights). We do not rely on consent for any of the above.

Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects on you. Rate limits and spam filtering act automatically on requests and messages.

We do not sell personal data, and we do not "share" it for cross-context behavioural advertising. We do not process sensitive personal data to infer characteristics about anyone.

#AI and model training

How AI processing itself works differs by product:

#Connected mailboxes (Google / Microsoft)

If an admin connects a Gmail or Microsoft 365 mailbox, we request the narrowest scope for the capability you turn on — read access to poll for new support mail, and send access only if you enable sending. Messages are read to create tickets; they are not marked read, deleted, or used for anything else. Access and refresh tokens are encrypted at rest and used only to poll that mailbox. Disconnecting in Settings → Email deletes the tokens, and you can revoke access from your Google or Microsoft account at any time.

#The Elevate Time desktop app and browser extension

Elevate Time is a timer that runs on your own computer. The time entries you save with it are ordinary Flyder Elevate data and are covered by everything above: they reach your account over the same API the web app uses, under a token that can read and write time and reach nothing else.

Everything else the app is able to record is different in kind, and one sentence governs all of it:

It is off until you turn it on. A new install records nothing, and neither does an update. When you do switch it on, the app records — locally — which application was in front and for how long; the title of that window, if you enable window titles separately; the address and title of the browser page you were on, and the sites of your other open browser tabs, if you install the browser extension; a count of key presses and mouse clicks; and a screenshot every few minutes, if you enable screenshots separately.

Counts, never content. The app counts how many times a key was pressed. It never reads which key: on each operating system it is built so that the keystroke is not available to the program at all, rather than being read and then discarded. Nothing you type is recorded, and on Windows and Linux nothing that could read input is installed until you turn counting on.

Screenshots carry stricter rules than anything else here, because a picture of your screen is not the same as an application's name — it is whatever happened to be on it. They need their own permission from your operating system, have their own switch and their own shorter retention, are skipped while you are away from the machine and while an excluded application is in front, and have a delete-them-all button of their own.

You can exclude an application or a site, and excluding one also deletes what has already been recorded about it — the activity, the screenshots and anything learned from them. Turning the exclusion back off starts again from nothing; there is no hidden history to restore.

The browser extension tells the app on the same computer two things, through the local channel your browser provides for talking to a program already installed on that machine: the address and title of the page in your active tab, and the site and title of your other open tabs, so the app can offer your own sites when you set up automatic time tracking.

For those other tabs it is the site only — figma.com, not the page you have open on it. The path, the query string and anything after a # are removed inside the browser before anything is sent, because the site name is all the app uses them for. Tabs in a private or incognito window are never read at all. The extension makes no network requests of any kind — no server, no account, no analytics — and it reports nothing while its own switch is off or while the app is not running.

Idle time is the one measurement that needs no permission and has no switch: the app asks the operating system how many seconds have passed since you last touched the keyboard or mouse, so it can ask you whether a running timer should keep running. That is a number of seconds, and the app learns nothing else from it.

#The Elevate Scribble browser extension

Elevate Scribble captures a picture of a web page so you can mark it up and send it to your Flyder Elevate account. Unlike the Elevate Time extension, sending is its whole purpose, so here is exactly what is sent, when, and where.

It captures only when you ask it to. A capture happens when you click the extension's button (or press its shortcut), and it is a picture of the tab in front of you, as it looks at that moment — nothing scrolled out of view, no other tab, nothing in the background. The extension has no access to a page until you click on it, and loses it when you leave that page or close the tab.

Nothing leaves your browser until you press Send. The capture opens in an editor on your own computer. If you close it without sending, it is discarded. When you do send, these go to your Elevate account, and only there: the picture with your markup, the title and note you wrote, and the page's address and title, your browser's name and version, and the picture's size.

Redaction is permanent. A redact box is drawn into the picture before it is sent, so what was under it is not in the file that leaves your computer.

After that it is ordinary Flyder Elevate data. It is filed as an attachment on the ticket or task you chose and is covered by everything above: visible to the people who can see that ticket or task, kept and deleted with it, and with no retention period of its own. It reaches your account over the same API the web app uses, signed in as you, under a token limited to filing tickets and tasks, adding to existing ones, uploading their attachments, and finding the ticket or task you choose to add to. The extension reads your project list and searches your tickets and tasks only to show you what to pick; it keeps none of it.

Adding to an existing ticket never emails anyone by itself. It is saved as a draft reply on that ticket, and nothing reaches the customer until a person on your team sends it from Elevate.

It talks to Flyder Elevate and nothing else — no other server, no analytics, no advertising. It keeps your sign-in in your browser's extension storage so you stay signed in, and signing out in the extension revokes it.

#Who else sees it

We disclose personal data only to:

Who For what
Cloudflare Hosting, storage, queueing, and email sending and receiving. The Services run on Cloudflare's network.
Stripe Payment processing for paid plans. You enter card details on Stripe's own pages; we never see or store your card number.
Sentry Error reports from Flyder Elevate and Flyder Engage, so we can fix what broke. Configured not to send IP addresses, cookies or user details.
Google Fonts The typeface used by Flyder Account, Flyder Elevate and Flyder Engage, and in our emails, is loaded from Google's servers, so your browser or email app sends Google its IP address and user agent when it loads it.
Other vendors and service providers Customer service, communications and other IT functions — acting on our instructions only.
Applications you sign in to Your identifier, name, email address, verification status, and your role and organization for that application — the standard OpenID Connect claims, and nothing more. What each application does with it is governed by this policy where it is ours, and by its own where it is not.
Administrators of your organization Your name, email address, role and activity within that organization. If you sign up with an employer's email domain, we may tell that organization you have an account so they can add you.
Flyder Engage Only if a Flyder Elevate account turns AI features on: that account's ticket content is sent to Engage to generate its own responses, isolated to that organization.
Slack, ClickUp Only the tickets and messages you configure an integration to send.
Google, Microsoft Only for a mailbox or identity provider you connect.
Zendesk Only during an import you start, and only to read your own data.
Platform staff What they need to operate and support the Service. Access is limited, logged, and — in Flyder Elevate — shown to the account in Settings → Access log.
Authorities Only where legally required, or to protect rights, safety or the integrity of the Services. We will tell the affected account unless we are prohibited from doing so.
A successor If we are acquired or reorganised, data moves with the Service and this policy continues to apply until it is replaced.

Some features let you share information yourself — a shared link, an integration, a custom action. Trust the person or service you share it with; once shared, it is governed by them.

#Where data is held

We are based in the United States. People outside the United States can use the Services, and this policy applies to them in full, including the GDPR and UK GDPR rights set out above. The Services run on Cloudflare's global network, so your data may be processed in countries other than your own, and any transfer out of the UK/EEA relies on Standard Contractual Clauses through our infrastructure provider.

#How long we keep it

  • Account and login data — for as long as the account exists. Sessions are deleted once they expire.
  • Technical data — IP addresses and browser details in our records are removed after 1 year. Error reports are held by Sentry and deleted on its retention schedule.
  • Tickets and comments (Flyder Elevate) — until the account deletes them. A deletion is a soft delete first; the account sets the window (Settings → Account, default 30 days), after which a nightly job hard-deletes them.
  • People (Flyder Elevate) — deleting a person hides them immediately and purges them after 30 days. An admin can also erase a person outright, which strips their personal data from tickets and leaves the ticket history intact.
  • Attachments — with their ticket, removed when the ticket is purged.
  • Activity records (Elevate Time) — held on your own computer and deleted automatically after 30 days, screenshots after 7. They are never uploaded, so there is no copy of them for us to keep or to delete for you. Excluding an application deletes its records at once, and each can be deleted outright from the app at any time.
  • Suppression and abuse records — as long as needed to stop us mailing someone who asked us not to, and to keep out abuse we have already seen.
  • Audit records — deleted 2 years after the action they record, and stripped of IP address and device details after 1 year. They deliberately survive a ticket deletion and outlive the account they describe, because their purpose is to answer "what changed, and when" after the fact. When an account is purged, its audit entries are kept only in anonymized form: the name, email address, account identifier, IP address and device details are removed, so what remains is a record of the action and nothing that identifies the person.
  • Billing records — invoices and payment history are kept for at least 7 years after the transaction, as tax and accounting law requires. They are held in Stripe's records, which Stripe also keeps under its own legal obligations, and are not deleted when your account is.
  • A closed account, or a deleted organization — held for 30 days so a deletion can be undone, then purged automatically: the account, its profile and memberships are deleted, and each Flyder product deletes the personal data it holds about it. Records other people or organizations rely on — a support ticket you raised with a company, for instance — are kept in anonymized form, under an identifier that no longer leads back to you.

#Your rights

Depending on where you live you may have the right to know what we hold and how we process it, to access a copy, to correct it, to delete it, to export it, to restrict or object to processing, to withdraw consent where consent is the basis, to be free from discrimination for exercising these rights, and to complain to your data-protection authority.

  • End users of a help desk: exercise these with the company you contacted — they control the ticket. We will help them respond.
  • Account holders: most of it you can do yourself. Your profile, your sessions and account deletion are on the Account page in Flyder Account; Flyder Elevate's API exports everything in your account. For anything else, write to support@flyder.ai.

Verification. To protect your data we may ask you to verify your credentials before acting on a request to know, correct or delete. If you have no account with us, or we suspect fraud, we may ask for more information and proof of residency. If we cannot verify who you are, we cannot act on the request.

Your right to object. Where we rely on legitimate interests (see How we use it), you can object at any time by writing to support@flyder.ai. We will stop, unless we have compelling grounds that override your interests, rights and freedoms, or need the data to establish, exercise or defend legal claims.

Authorized agents may submit a request with signed written permission; we may still verify you independently.

Appeals. If we decline a request, you can appeal by writing to support@flyder.ai with "Appeal" in the subject line. We will answer within 45 days and explain our decision. If we deny your appeal and you live in a US state with a consumer privacy law, you can contact your state's attorney general.

A note about accuracy. Flyder and Flyder Engage generate responses by predicting likely text, so output about a person can be factually wrong. Tell support and we will correct it where we can; where the way the models work makes that impossible, you may ask us to remove your personal data from the output instead.

#California

What we collect, by the categories the CCPA uses:

Category What it covers here Where it comes from Why we use it Disclosed to
Identifiers Name, email address, account and user IDs, IP address You, your organization, your device Providing and securing the Services Cloudflare; applications you sign in to; your organization's administrators; Stripe
Customer records Name and email address, and the billing address you enter with Stripe You Billing and support Stripe; Cloudflare
Commercial information Plans, subscriptions and invoices You, Stripe Billing Stripe
Internet or network activity Sign-in and session history, audit records, user agent Your device Security and troubleshooting Cloudflare; Sentry (error reports, without IP addresses)
Professional information The organizations you belong to and your role in each You, your organization Managing access Your organization's administrators; applications you sign in to
Content Prompts, files, chat and support messages You Providing the feature you are using Cloudflare
Sensitive personal information Your account login, password and two-factor secrets You Signing you in and securing your account, and nothing else No one

How long each is kept is set out under How long we keep it.

No sale, no sharing. In the past 12 months we have not sold personal information or shared it for cross-context behavioural advertising, and we have no actual knowledge of selling or sharing the personal information of anyone under 16.

Sensitive personal information is used only to sign you in and keep your account secure. The CCPA does not let that use be limited further, so there is no "Limit the Use of My Sensitive Personal Information" link.

Making a request. Flyder is an online-only service with a direct relationship with you, so requests to know, delete or correct go by email to support@flyder.ai. We will confirm a request within 10 business days and answer it within 45 days.

Do Not Track. We do not track you across other websites, and apart from the font requests described under Who else sees it, no third party collects information about your online activity over time and across websites through the Services. A Do Not Track or Global Privacy Control signal therefore changes nothing: there is no tracking to switch off.

Shine the Light. We do not disclose personal information to third parties for their own direct marketing purposes.

#Security

  • Tenant isolation in Flyder Elevate is enforced mechanically, in one place, on every query — not by convention.
  • Traffic is TLS-encrypted end to end. Data at rest is encrypted by our infrastructure provider, and secrets on top of that: passwords are hashed, and mailbox tokens, API keys and application signing secrets are hashed or encrypted.
  • Sessions are scoped, expiring and individually revocable. Two-factor authentication and single sign-on are available, and an organization or application can require them.
  • Attachments are checked structurally on upload and are never served as executable content.
  • Staff access to an account is limited and logged.

No system is perfectly secure, and no email is. Take care what you send us. If a breach affects your data we will notify affected accounts, and the relevant regulator, without undue delay.

#Children

The Services are not directed to anyone under 18, and we do not knowingly collect their data. If you believe a child's data has reached us, tell us and we will delete it.

The Services may link to sites we do not operate. What you share there is governed by their policies, not this one. A link is not an endorsement.

#Changes

We may update this policy. Before a material change takes effect, we email the address on your account. Other changes take effect when they are posted here. The Last updated date at the top of this page records when the current version was published.

#Contact

support@flyder.ai · Flyder, c/o NetMediaOne, LLC, 4101 Tates Creek Centre Drive, Suite 150 – PMB 118, Lexington, KY 40517, USA.