FloPayFloPay
  • Playground
  • Docs
  • Contact
Legal

Cookies

Effective
May 26, 2026
Version
1.0
On this page
  1. 1. Introduction
  2. 2. Scope
  3. 3. What Are Cookies
  4. 4. Cookies On flopay.com Today
  5. 5. Third-Party Resources
  6. 6. Categories We Use If Cookies Are Added
  7. 7. How To Manage Cookies
  8. 8. Consent & Future Changes
  9. 9. Related Policies
  10. 10. Changes To This Policy
  11. 11. Contact

This Cookie Policy explains how FloPay LLC, a Wyoming limited liability company (“FloPay”, “we”, “us”, or “our”), uses cookies and similar technologies on flopay.com, what third-party resources we load on your behalf, and the choices you have to control them.

flopay.com does not set any first-party tracking cookies today and does not load analytics, advertising, or marketing tags. This policy describes our current practice and the framework we will use if that changes.

1. Introduction

We publish this policy so that visitors to flopay.com can see exactly what runs in their browser when they land on the site, what it implies for their data, and what choices they have. It complements our Privacy Policy, which describes how FloPay handles personal information more broadly.

2. Scope

This policy applies to the FloPay marketing website at flopay.com. Our developer and demo subdomains — including docs.flopay.com, api.flopay.com, and demo.flopay.com — and the FloPay platform, SDKs, APIs, dashboards, the Agent Vault, and the MCP Server may use cookies and similar technologies for authentication, security, and product functionality. Those uses are described in the documentation and notices for each Service.

3. What Are Cookies

Cookies are small text files that a website asks your browser to store on your device. They are used to remember information between page loads and visits — for example, to keep you signed in, remember a preference, or measure how the site is used.

“Similar technologies” we treat the same way as cookies for this policy include:

  • Local storage and session storage — browser-side key/value stores scoped to a site.
  • Pixels and tracking beacons — small images or scripts used to record that a page or email was opened.
  • SDKs and tag managers — third-party libraries that may set their own cookies or local storage entries when loaded.

Cookies can be first-party (set by flopay.com) or third-party (set by another domain whose resources we load). They can be session cookies that expire when you close your browser, or persistent cookies that remain until they expire or you delete them.

4. Cookies On flopay.com Today

flopay.com does not set any first-party cookies. We do not run analytics, advertising, marketing, retargeting, A/B-testing, or session-replay tools on the marketing site. We do not use a tag manager, and we do not store identifiers in local storage or session storage from the marketing site itself.

The result is that, in a typical visit to flopay.com, no cookie is written by us and no identifier is persisted in your browser by our code.

5. Third-Party Resources

flopay.com loads one third-party resource that is relevant to this policy:

  • Google Fonts. We load web fonts from Google’s font-hosting service to render typography on the site. Google does not receive cookies from this request when it is made to fonts.googleapis.com, but as with any HTTP request your IP address, user-agent string, and the referring URL are visible to Google as part of normal network delivery. Google’s use of that information is governed by Google’s own privacy terms.

We do not currently load any other third-party analytics, advertising, social, video, or tag-management resources on flopay.com. If we add one in the future, we will update this page before that change ships, and any cookies it requires will be handled as described in Section 8.

External links from flopay.com to FloPay’s other surfaces — for example, docs.flopay.com, api.flopay.com, and demo.flopay.com — or to third-party sites are not in scope for this policy; once you follow such a link, the destination site’s own cookie practices apply.

6. Categories We Use If Cookies Are Added

If we introduce cookies in the future, we will classify them using the categories below. These are the same categories most consent-management frameworks use, so they should be familiar if you have managed cookie preferences on other sites.

  • Strictly necessary. Required for the site to function — for example, preserving a security token across a navigation. These cannot be switched off in a consent banner because the site relies on them.
  • Preferences. Remember choices you make to personalize the experience — for example, language, theme, or whether you have dismissed a banner.
  • Analytics. Help us understand how visitors use the site so we can improve it. We treat analytics cookies as non-essential and will gate them on consent where required by law.
  • Marketing. Used to measure the effectiveness of marketing campaigns or to deliver advertising. We treat marketing cookies as non-essential and will gate them on consent where required by law.

7. How To Manage Cookies

Because flopay.com does not set cookies today, there is nothing to opt out of on this site at the moment. You can still control how your browser handles cookies generally, which will apply automatically to any cookies we introduce later.

  • Browser settings. Every major browser — including Chrome, Safari, Firefox, and Edge — lets you view stored cookies, block third-party cookies, clear cookies for a specific site, or block all cookies. Look in your browser’s privacy or site-settings panel.
  • Private or incognito mode. Most browsers offer a private-browsing mode that discards cookies and local storage when you close the window.
  • Do Not Track / Global Privacy Control. If your browser sends a Do Not Track or Global Privacy Control signal, we treat it as a request not to use non-essential cookies, in addition to any consent choice you make in a future banner.

Blocking strictly necessary cookies for sites that rely on them — for example, an authenticated dashboard on another FloPay subdomain — may break functionality on those sites.

8. Consent & Future Changes

We will not introduce analytics, marketing, or other non-essential cookies on flopay.com without first updating this policy and, where required by law, surfacing a consent mechanism that lets you accept or reject those categories before they load.

For visitors in the European Economic Area, the United Kingdom, and Switzerland, that means non-essential cookies will be off by default and will only run after you give consent. Where you have given consent, you can withdraw it at any time using the same mechanism, and withdrawal will not affect any processing that already took place.

9. Related Policies

This policy should be read together with our other legal documents:

  • Privacy Policy — describes how FloPay collects, uses, shares, and protects personal information.
  • Terms — govern your use of flopay.com and the FloPay Services.

10. Changes To This Policy

We may update this policy from time to time — for example, when we add or remove a third-party resource, change the categories we use, or introduce a consent mechanism. When we do, we will revise the “Effective” date above and, for material changes, give prominent notice on the Website. Your continued use of flopay.com after the effective date constitutes acceptance of the updated policy.

11. Contact

Questions, requests, or complaints about this policy can be sent to hello@flopay.com.

FloPayFloPay

The Financial Rails for the Agentic Economy

Product

  • Agent-Assisted Commerce
  • The Agent Vault
  • Agentic Discovery Network
  • Smart Agentic Orchestration

Development

  • Documentation
  • MCP Server
  • API Reference
  • Demo Playground

Company

  • Mission
  • Values
  • War Room
  • Contact

© 2026 FloPay LLC. All rights reserved.

PrivacyTermsCookies