Cookie policy
On this page
1. Introduction
This Cookie Policy explains how Flob Inc. ("Company," "we," "us," or "our") uses cookies and similar tracking technologies when you visit or use our Reos platform ("Research Operating System") and related services (collectively, the "Service").
This policy should be read in conjunction with our Privacy Policy, which provides more information about how we collect and use personal data.
Essential and functional cookies (those strictly necessary for the Service to work correctly, such as authentication, security, and preference cookies) are used whenever you use the Service and cannot be switched off. For analytics and diagnostics cookies and advertising cookies, it depends on where you are (Section 6):
- In the EEA, the UK, Switzerland, Brazil and Quebec we use them only with your consent, which you can give, refuse or withdraw at any time in our cookie banner and with "Cookie settings".
- Everywhere else they are on by default, and you can turn them off at any time with "Your privacy choices".
- A Global Privacy Control signal from your browser always turns advertising cookies off (Section 7).
In this policy, "advertising consent" means your yes in the first case, and advertising cookies being on (by default, and not turned off by you or by GPC) in the second.
With your advertising consent we use Google Ads, LinkedIn Ads and Meta Ads (Facebook and Instagram) to measure which of our ads bring people to Reos (Section 3.4). We do not use advertising cookies for personalised advertising or remarketing, and we do not use third-party marketing analytics services. The cookies we actually set are listed below.
2. What Are Cookies?
Cookies are small text files that are placed on your computer, smartphone, or other device when you visit a website. Cookies are widely used to make websites work more efficiently, provide information to website owners, and enable certain features.
2.1 Types of Cookies by Duration
Session Cookies: These cookies are temporary and are deleted when you close your browser. They are used to maintain your session as you navigate the Service.
Persistent Cookies: These cookies remain on your device for a set period or until you delete them. They are used to remember your preferences and choices across visits.
2.2 Types of Cookies by Origin
First-Party Cookies: These cookies are set by us (the website you are visiting).
Third-Party Cookies: These cookies are set by third parties, such as security or diagnostics providers, and, only with your advertising consent, Google for ad measurement (Section 3.4).
3. How We Use Cookies
We use cookies and similar technologies for the following purposes:
3.1 Essential Cookies (Strictly Necessary)
These cookies are necessary for the Service to function and cannot be switched off. They are usually only set in response to actions made by you, such as logging in or setting your privacy preferences.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
better-auth.session_token | Reos | Authentication session | Session |
better-auth.session_data | Reos | Session data | Session |
oauth_state | Reos | Protects sign-in flows against cross-site request forgery | Duration of sign-in flow |
reos-cookie-consent | Reos | Stores your cookie choice, the date you made it and the policy version (browser local storage) | 12 months, then we ask again |
__cf_bm | Cloudflare | Bot management and security | 30 minutes |
cf_clearance | Cloudflare | Security verification | 1 year |
Without these cookies:
- You would not be able to log in or stay logged in
- Your cookie preferences would not be remembered
- Security features would not function properly
3.2 Functional Cookies (Preferences)
These cookies enable the Service to provide enhanced functionality and personalization. Because they are needed for the Service to behave correctly (for example, to route your requests to the right data region and remember choices you have made), they are set as part of the Service's core operation and, like essential cookies, do not have a separate on/off toggle in the consent banner.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
reos-theme | Reos | Remembers your theme preference (light/dark/system) | 1 year |
| Last-active-organization cookie | Reos | Remembers which organization you last worked in | Persistent |
| Region routing cookie | Reos | Routes your requests to your organization's data region | Persistent |
reos_ref | Reos | If you reached us through a personal invitation link we sent you, remembers the reference code in that link so that your sign-up can be recognised as coming from it. The code is a random string we generated; it holds no information about you and is not shared with anyone else | 90 days |
Without these cookies:
- Your theme preference would reset on each visit
- Interface and routing preferences would not be remembered
- A sign-up would not be recognised as coming from an invitation we sent you
3.3 Analytics and Diagnostics (Performance)
We do not currently use third-party product analytics or web analytics services (such as Google Analytics or PostHog), and no such cookies are set. We measure aggregate usage of the Service using first-party, privacy-preserving infrastructure (Cloudflare analytics), which does not build individual profiles.
With your consent, we use Sentry for error tracking and diagnostics:
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| Sentry session identifiers | Sentry | Correlating errors within a session for debugging | Session |
Sentry Error Tracking: When errors occur, Sentry automatically collects:
- Error messages and stack traces
- Browser and device information
- User actions leading to the error (session replay on errors; text inputs and sensitive fields are masked, and automated PII scrubbing is applied)
- Network request information and performance metrics
This data helps us quickly identify and fix bugs to improve your experience.
Without this:
- We would have difficulty identifying and fixing errors in the Service
3.4 Advertising Cookies (Marketing)
We use these cookies only with your advertising consent (Section 1): in the EEA, the UK, Switzerland, Brazil and Quebec only once you accept them in our cookie banner; elsewhere unless you turn them off with "Your privacy choices" or your browser sends a GPC signal. They let us measure which of our ads bring people to Reos (conversion measurement). Today the ad platforms that receive data are Google Ads, LinkedIn Ads and Meta Ads (Facebook and Instagram), each only for visits that came from one of its own ads. We remember the ad you came from, Google sets its click cookies (LinkedIn and Meta set no cookies on our website), and we tell the platform whose ad you clicked when that visit leads to a finished demo, a sign-up, a booked call or a payment (with its value). We do not use them to show you personalised ads, to build remarketing audiences, or for Google Analytics.
What we report to Google. For each of these conversions we send Google Ads the ad click identifier of your visit (gclid, gbraid or wbraid), the time of the conversion, a random transaction identifier, the consent signals for ad user data and ad personalisation (personalisation always denied), and, for a payment, its value and currency. To match a conversion to the ad click, we may also send Google a one-way hashed (SHA-256) version of the email address you sign up or book a call with, only with your advertising consent. We do not send your name or phone number.
What we report to LinkedIn. If you came from one of our LinkedIn ads, the link you clicked may carry LinkedIn's ad click identifier (li_fat_id). We read it from the link and keep it with your reos_gv visitor record. We do not load the LinkedIn Insight Tag or any other LinkedIn script, and LinkedIn sets no cookies on our website. For each of the conversions above we send LinkedIn, from our servers, that click identifier, the time of the conversion, a random event identifier, and, for a payment, its value and currency. To match a conversion to the ad click, we may also send LinkedIn a one-way hashed (SHA-256) version of the email address you sign up or book a call with, only with your advertising consent. We do not send your name or phone number.
What we report to Meta. If you came from one of our Meta ads (on Facebook or Instagram), the link you clicked may carry Meta's ad click identifier (fbclid). We read it from the link and keep it with your reos_gv visitor record. We do not load the Meta Pixel or any other Meta script, and Meta sets no cookies on our website. For each of the conversions above we send Meta, from our servers through its Conversions API, that click identifier with the time of your first visit, the time of the conversion, a random event identifier, and, for a payment, its value and currency. To match a conversion to the ad click, we may also send Meta a one-way hashed (SHA-256) version of the email address you sign up or book a call with, only with your advertising consent. We do not send your name or phone number.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
reos_gv | Reos | A random visitor identifier. It links your first visit from an ad or a tagged link (the ad click identifier, the campaign tags in the link, the landing page, the referring website and the country derived from your IP address) to your account if you sign up | 90 days |
_gcl_aw, _gcl_gb, _gcl_au | Google (set on our domain) | Store the Google Ads click identifier (gclid, gbraid or wbraid) so that a later conversion can be attributed to the ad click | 90 days |
Cookies on Google's own domains (for example IDE and test_cookie on doubleclick.net) | Conversion measurement and fraud prevention in Google Ads | Up to 13 months (IDE), 15 minutes (test_cookie) |
Google Consent Mode v2. The Google tag is loaded only on our public website pages (not inside the product), and only with your advertising consent. Before it loads, Google's consent defaults are set by region: in the EEA, the UK, Switzerland, Brazil and Quebec every signal (ad_storage, ad_user_data, ad_personalization, analytics_storage) defaults to denied; elsewhere ad_storage and ad_user_data default to granted. Your own setting is then applied, and it grants at most ad_storage and ad_user_data: ad_personalization and analytics_storage stay denied everywhere, and ad personalisation signals are switched off. If you withdraw consent, the signals are set back to denied, we delete the reos_gv cookie and Google's click cookies (_gcl_aw, _gcl_gb, _gcl_au), no further Google Ads data is collected, and no further conversion is reported to Google, LinkedIn or Meta for your visit. The same applies if your browser sends a Global Privacy Control signal (Section 7).
Recipient. Google (Google Ireland Limited for users in the EEA, UK and Switzerland, otherwise Google LLC) receives the ad click identifier, the public pages you view, your IP address and browser information, and, when we report a conversion to Google Ads, the fact that it happened, its value and possibly the hashed email address described above. Google acts as an independent controller under the Google Ads Controller-Controller Data Protection Terms. Google may process this data outside your country, including in the United States. Google LLC is certified under the EU-US, UK Extension and Swiss-US Data Privacy Frameworks, and Google's terms include Standard Contractual Clauses. Google's privacy policy: https://policies.google.com/privacy
Recipient: LinkedIn. LinkedIn (LinkedIn Ireland Unlimited Company for users in the EEA and Switzerland, otherwise LinkedIn Corporation) receives, only when we report a conversion for a visit that came from one of our LinkedIn ads, the ad click identifier, the fact that the conversion happened and when, for a payment its value, and possibly the hashed email address described above. LinkedIn does not receive the pages you view, your IP address or your browser information from us, because no LinkedIn code runs on our website. LinkedIn acts as an independent controller under the LinkedIn Independent Controller Addendum. LinkedIn may process this data outside your country, including in the United States, and LinkedIn's terms include Standard Contractual Clauses. LinkedIn's privacy policy: https://www.linkedin.com/legal/privacy-policy
Recipient: Meta. Meta (Meta Platforms Ireland Limited for users in the EEA and Switzerland, otherwise Meta Platforms, Inc.) receives, only when we report a conversion for a visit that came from one of our Meta ads, the ad click identifier, the fact that the conversion happened and when, for a payment its value, and possibly the hashed email address described above. Meta does not receive the pages you view, your IP address or your browser information from us, because no Meta code runs on our website. Meta processes this data under the Meta Business Tools Terms. Meta may process this data outside your country, including in the United States. Meta Platforms, Inc. is certified under the EU-US, UK Extension and Swiss-US Data Privacy Frameworks, and Meta's terms include Standard Contractual Clauses. Meta's privacy policy: https://www.facebook.com/privacy/policy
Without advertising consent. The Google tag is not loaded and nothing is stored on your device for advertising. We still count visits to our public pages and demos in aggregate (with the campaign and source named in the link, if any, the referring website and the country, but without any identifier) to see how many people reach each step. As part of running the Service we also record which sign-up and onboarding steps an account completes (account created, email verified, workspace created, first upload or study, first payment); without your advertising consent this record is not linked to any ad click.
We do not use other advertising technologies: we do not load the Meta Pixel or the LinkedIn Insight Tag, and Meta and LinkedIn set no cookies on our website. If we add one, we will update this Cookie Policy first, and it will only run with your advertising consent.
4. Third-Party Cookies
The only third parties that may set cookies or similar identifiers through the Service today are Cloudflare, Sentry (with analytics consent) and Google (with advertising consent):
4.1 Cloudflare
Cloudflare may set cookies for:
- Security and bot protection
- Performance optimization
Cloudflare's privacy policy: https://www.cloudflare.com/privacypolicy/ Cloudflare's cookie policy: https://www.cloudflare.com/cookie-policy/
4.2 Sentry
Sentry may set cookies or use browser storage for:
- Error tracking and monitoring
- Performance monitoring
- Session correlation for debugging
Sentry's privacy policy: https://sentry.io/privacy/
4.3 Google
Only with your advertising consent, and only on our public website pages, Google may set cookies for:
- Google Ads conversion measurement (see Section 3.4)
- Fraud and invalid-click prevention
Google's privacy policy: https://policies.google.com/privacy How Google uses information from sites that use its services: https://policies.google.com/technologies/partner-sites
5. Similar Technologies
In addition to cookies, we may use other similar technologies:
5.1 Local Storage
We use browser local storage to store:
- User preferences
- Cookie consent preferences (
reos-cookie-consent) - Cached application data
Local storage data persists until explicitly cleared by you or the application.
5.2 Email Delivery Tracking
Emails sent through the Service (such as study invitations and notifications) may include standard delivery instrumentation so that we and the sender can detect bounces and delivery failures. We do not use email tracking for advertising.
5.3 JavaScript
Our Service uses JavaScript to enable interactivity. Disabling JavaScript will significantly impair the functionality of the Service.
6. Managing Cookies
You have several options for managing cookies:
6.1 Our Cookie Consent Banner
In the EEA, the UK, Switzerland, Brazil and Quebec, when you first visit the Service you will see a cookie consent banner that allows you to:
- Accept All: Enable all cookie categories
- Reject All: Disable all non-essential cookies
- Customize: Choose which categories of cookies to enable
Nothing optional runs until you choose. You can change your preferences at any time with "Cookie settings": in the footer of our website, and in the account menu inside the app. Withdrawing consent is as easy as giving it.
Everywhere else, no banner is shown: analytics and advertising cookies are on by default. "Your privacy choices", in the footer of our website and in the account menu inside the app, opens the same settings, where you can turn either off. Your choice is stored like a consent (Section 11). If we cannot tell where you are, we treat you as being in a region where we ask first.
6.2 Browser Settings
Most web browsers allow you to control cookies through their settings. You can typically:
- View what cookies are stored on your device
- Delete some or all cookies
- Block all cookies or certain types of cookies
- Set preferences for specific websites
Browser-specific instructions:
- Chrome: Settings > Privacy and security > Cookies
- Firefox: Settings > Privacy & Security > Cookies
- Safari: Preferences > Privacy > Cookies
- Edge: Settings > Cookies and site permissions
Note: Blocking or deleting cookies may impact the functionality of the Service. Essential cookies are required for the Service to function properly.
7. Do Not Track and Global Privacy Control
Some web browsers transmit "Do Not Track" (DNT) signals to websites. Because there is no common understanding of how to interpret DNT signals, the Service does not currently respond to DNT signals.
Global Privacy Control (GPC): If your browser sends a GPC signal, we treat it as a refusal of advertising cookies. The Google tag is not loaded and no conversion is reported to Google, LinkedIn or Meta for your visit, whatever you chose in the banner.
We do not sell personal information for money. With your advertising consent, Google, LinkedIn and Meta receive ad click identifiers and conversion events (possibly with a hashed email address) to measure our ads, which some US state laws may treat as a sale or sharing. You can opt out at any time with "Your privacy choices", which is our "Do Not Sell or Share My Personal Information" link, with Reject all in Cookie settings, or by sending a GPC signal.
8. Cookies on Mobile Devices
When you access the Service through a mobile browser, cookies function similarly to desktop browsers, and you can manage them through your mobile browser settings. We do not use mobile advertising identifiers (such as Apple's IDFA or Google's Advertising ID).
9. Changes to This Cookie Policy
We may update this Cookie Policy from time to time to reflect changes in technology, law, our business operations, or for other reasons. If we make material changes, we will notify you by:
- Updating the "Last Updated" date at the top of this policy
- Posting a notice on the Service
- Resetting cookie consent preferences (for significant changes, including any introduction of new non-essential cookie categories)
We encourage you to review this Cookie Policy periodically.
10. Contact Us
If you have any questions about our use of cookies or this Cookie Policy, please contact us:
Flob Inc. 1111B S Governors Ave STE 49827 Dover, DE 19904 United States
Email: support [at] reos [dot] ai
11. Cookie Consent Record
We store your choice, the date you made it and the policy version in your browser, and ask again after 12 months or when we add a new kind of cookie or a new ad platform. An opt-out made with "Your privacy choices" is stored the same way.
This Cookie Policy was last updated on November 13, 2026.








