Privacy policy
On this page
1. Introduction
Welcome to the Privacy Policy of Flob Inc. ("Company," "we," "us," or "our"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Reos platform ("Research Operating System") and related services (collectively, the "Service").
This Privacy Policy covers both the personal data of our customers and website visitors, for which Flob Inc. is the data controller, and the personal data of Research Participants — the people our customers invite to studies, interviews, and calls through the Service — which we process on behalf of our customers as a data processor. If you are a Research Participant, Sections 2 and 3 explain who is responsible for your data and how to exercise your rights.
We are committed to protecting your privacy and ensuring you understand how your personal data is processed. Please read this Privacy Policy carefully. By accessing or using the Service, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy.
If you do not agree with the terms of this Privacy Policy, please do not access or use the Service.
2. Who Is Responsible for Your Data: Our Two Roles
We process personal data in two distinct roles, and your rights and the party responsible depend on which role applies:
(a) Flob Inc. as data controller. For personal data relating to our customers and website visitors — account information, billing information, usage data, and marketing data — Flob Inc. is the data controller (or "business" under the California Consumer Privacy Act) and this Privacy Policy describes that processing in full.
(b) Flob Inc. as data processor (Research Participants). Our customers use Reos to conduct research with their own users, customers, and other individuals ("Research Participants"). When you receive a study invitation through Reos, complete a form or survey, book a session, or join a live or AI-conducted interview or call, the organization that invited you (our customer, the "Research Organizer") decides why and how your data is used. The Research Organizer is the data controller of that data, and Flob Inc. processes it only on the Research Organizer's instructions as a data processor (or "service provider"). Section 3 describes this processing in more detail.
Contact details of the controller (where Flob Inc. is the controller):
Flob Inc. 1111B S Governors Ave STE 49827 Dover, DE 19904 United States
Data Protection Contact: support [at] reos [dot] ai
Privacy Lead (data protection inquiries): Rob Manzano Email: rob [at] reos [dot] ai
For European Union residents, where Flob Inc. acts as the data controller under the General Data Protection Regulation (GDPR), our privacy lead oversees compliance with data protection requirements and can be contacted directly for any GDPR-related inquiries.
3. Research Participants: Data We Process on Behalf of Research Organizers
This section is written for Research Participants — the people our customers invite into their research — as well as for our customers.
3.1 What We Collect About Research Participants
Depending on how the Research Organizer configures their study, the Service may process the following about you as a Research Participant:
- Contact and profile information: Name, email address, and other details provided by you or by the Research Organizer (for example, when they import a participant list, connect a recruitment platform such as Prolific, or recruit you through Respondent as described in Section 3.6)
- Communications: Study invitations, scheduling emails, reminders, and other messages sent to you through the Service at the Research Organizer's direction, and related delivery metadata (such as whether an email bounced)
- Form and survey responses: Answers you submit through forms, surveys, and screeners hosted by the Service
- Scheduling information: Session bookings, RSVP responses, and availability you provide
- Consent records: Records of the consents you grant (including their version, date, and time)
- Session recordings and transcripts: Audio and video of live research sessions, calls, and interviews — including sessions conducted by an AI interviewer — together with automatically generated transcripts, captions, and speaker attributions
- AI-generated analysis: Observations, insights, summaries, and other analyses derived from your contributions
- Incentive information: If the Research Organizer offers you a reward, the details needed to deliver it (such as your name, email address, and reward amount) are shared with the incentive provider the Research Organizer has connected for that purpose
- Technical data: IP address, browser and device information, and usage data collected when you use participant-facing pages of the Service
3.2 How This Data Is Used
We process Research Participant data solely to provide the Service to the Research Organizer and on their documented instructions — for example, to send the invitations they compose, host their forms, run and record their sessions, transcribe recordings, and generate the analyses they request. We do not use Research Participant data for our own marketing, we do not sell it, and we do not use it to train AI models (see Section 7.1).
3.3 AI Interviews and AI Processing
Some sessions are conducted or assisted by an AI interviewer, and research content is analyzed by third-party AI providers listed in Section 7. The Service presents notices when you are interacting with an AI system, and Research Organizers are contractually required to inform you when AI conducts or analyzes your session and to obtain any legally required consents (including recording consents) before the session begins.
A Research Organizer can also connect their own AI assistant, such as Claude or ChatGPT, to their workspace (see Section 7.5c). When they do, content from their research, including what you said in a session, can be sent to that assistant's provider at the Research Organizer's direction and under their responsibility.
3.4 Your Rights as a Research Participant
Because the Research Organizer is the data controller of your data, requests to access, correct, delete, or object to the processing of your research data should be directed to the organization that invited you to the study. Their contact details are typically included in the study invitation or consent form.
If you contact us directly, we will refer your request to the relevant Research Organizer and notify them, and we will provide reasonable assistance so they can respond. Where we are legally required to act on your request directly, we will do so. You can reach us at support [at] reos [dot] ai. You can opt out of further emails sent through the Service at any time using the unsubscribe link included in those emails.
3.5 Retention of Research Participant Data
We retain Research Participant data for as long as the Research Organizer instructs us to (typically for the duration of their account and their research projects), after which it is deleted in accordance with Section 9. Research Organizers can delete participant data at any time using the Service's deletion tools.
3.6 Research Participants Recruited Through Respondent
If you joined a study through the research panel of Respondent, Inc. ("Respondent"), Respondent holds your Respondent account and profile as its own controller, under its own privacy policy. Research Organizers recruit through an account we hold with Respondent, and we receive from Respondent only what the study needs: your first name and last initial, your screener answers, how you match the study's criteria, session times, and messages you exchange with the Research Organizer. We do not receive your email address or other contact details from Respondent. We send Respondent your session status, booking times, payment confirmations and messages from the Research Organizer, so that Respondent can schedule you and pay your incentive.
Your research data in Reos is handled as described in Sections 3.1 to 3.5. For your Respondent profile and incentive payments, contact Respondent. When your data is deleted from Reos at your request, we also ask Respondent to hide your screener response for that study. Data received from Respondent may be deleted earlier than other research data where Respondent's terms require it.
4. Information We Collect
We collect information in several ways when you use our Service:
4.1 Information You Provide to Us
Account Information:
- Email address
- Full name
- Profile picture/avatar
- Password (stored in encrypted/hashed form)
- Two-factor authentication settings and backup codes
- Passkey/WebAuthn credentials for passwordless authentication
Organization Information:
- Organization name
- Organization logo
- Member roles and permissions
Billing Information:
- Billing name (individual or company)
- Billing email address
- Billing address (street, city, state/province, postal code, country)
- Tax identification number (VAT ID, if applicable)
Note: Payment card information is collected and processed directly by our payment processor (Stripe) and is not stored on our servers.
Research Content:
- Video and audio interview files
- Documents and transcripts
- Notes and annotations
- Observations and insights
- Personas and customer profiles
- Reports and summaries
- Any other content you upload or create through the Service
Guides and Newsletter:
- Email address and, if you give it, first name when you request a free guide or subscribe to our newsletter
- Whether you asked for the newsletter
Demo Requests:
- Name, work email, company and team size when you book or request a demo on /demo, and your time zone and chosen time if you book a call
Communications:
- Support requests and correspondence
- Feedback and suggestions
- Survey responses
4.2 Information Collected Automatically
Device and Technical Information:
- IP address
- Browser type and version
- Operating system
- Device identifiers
- Screen resolution and device capabilities
Session Information:
- Session tokens
- Login timestamps
- User agent strings
- Referring URLs
Usage Information:
- Features accessed and actions taken within the Service
- AI model usage (models used, processing volume)
- Units consumed and the activities that consumed them
- Time spent on pages
- Click patterns and navigation paths
- Search queries within the Service
Log Data:
- Server logs recording requests to our Service
- Error logs and diagnostic data
- Performance metrics
4.3 Information from Third Parties
OAuth Providers: If you choose to sign in using third-party authentication providers, we may receive:
- Basic profile information (name, email, profile picture)
- OAuth tokens for authentication purposes
Payment Processor: Our payment processor (Stripe) may share:
- Transaction status and confirmation
- Subscription status
- Customer identifiers
4.4 Research Data Processing
When you use our AI-powered analysis features, the following data may be processed:
- Transcripts of uploaded audio/video content
- Text content from documents
- User-generated prompts and queries
- AI-generated outputs (observations, insights, summaries)
This data is processed by our third-party AI providers as described in Section 7.
5. How We Use Your Information
We use the information we collect for the following purposes:
5.1 Providing and Maintaining the Service
- Creating and managing your account
- Authenticating your identity and securing your account
- Processing your research content through AI analysis
- Generating insights, observations, and reports
- Enabling collaboration features
- Processing payments and managing subscriptions
5.2 Improving and Developing the Service
- Analyzing usage patterns to improve features
- Developing new features and functionality
- Debugging and fixing errors
- Conducting research and analysis
- Testing new features
5.3 Communications
- Sending service-related notifications (account verification, security alerts, billing)
- Responding to your inquiries and support requests
- Sending product updates and announcements (with your consent where required)
5.4 Security and Fraud Prevention
- Detecting and preventing fraud, abuse, and security threats
- Monitoring for suspicious activity
- Enforcing our Terms of Service
- Protecting our rights and property
5.5 Legal Compliance
- Complying with applicable laws and regulations
- Responding to legal requests and court orders
- Establishing, exercising, or defending legal claims
5.6 Advertising and Marketing (Consent-Based)
Ad measurement (with your advertising consent). We advertise Reos on Google Ads, LinkedIn Ads and Meta Ads (Facebook and Instagram), today the only ad platforms that receive data from us, each only for visits that came from one of its own ads. In the EEA, the UK, Switzerland, Brazil and Quebec we do this only once you accept advertising cookies in our cookie banner. Everywhere else advertising cookies are on by default and you can turn them off at any time with "Your privacy choices"; a Global Privacy Control signal always turns them off. In this policy "advertising consent" covers both: your yes, or advertising cookies being on by default and not turned off. With it, our public website pages load the Google tag and we keep a first-party visitor cookie, so that we can measure which of our ads bring people to Reos. No LinkedIn or Meta script is loaded: we read LinkedIn's and Meta's ad click identifiers from the link of the ad you clicked. We remember the ad you came from, Google sets its click cookies, 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). For each such conversion that platform receives the ad click identifier of your visit, the time, a random transaction identifier, for Google the consent signals and, for a payment, its value. To match the conversion to the ad click, we may also send that platform 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. For EEA, UK, and Swiss users the legal basis is your consent (Article 6(1)(a) GDPR); you can withdraw it at any time, and withdrawal does not affect the lawfulness of processing before it. We do not use your data for personalised advertising or remarketing. If your browser sends a Global Privacy Control signal, we treat it as a refusal of this consent (Section 14). The cookies, Google's, LinkedIn's and Meta's roles and Consent Mode are described in Section 3.4 of our Cookie Policy.
Acquisition records without that consent. To understand how people find and start using Reos, we record which sign-up and onboarding steps an account completes (account created, email verified, workspace created, first upload or study, first payment, and, if you book or attend a sales call with us, that call) and count visits to our public pages and demos in aggregate, without any identifier. Our legal basis is our legitimate interest in understanding and improving how we acquire customers (Article 6(1)(f) GDPR). Without your advertising consent this record is not linked to any ad click, and none of it is shared with advertising partners.
We may send you product updates and marketing emails about our own services, with your consent where required; you can unsubscribe at any time.
Booking a demo. When you book a call on /demo, we keep your name, email, company and team size in our sales records, and Calendly (Calendly LLC, United States, our processor) receives your name, email and time zone to schedule it. If you start but do not finish booking, our sales team may email you once about your request. Legal basis: steps at your request before a contract and our legitimate interest in answering it (Art. 6(1)(b) and (f) GDPR).
Free guides. When you request a free guide, we use your email address and, if you give it, your first name to send it to you, and the IP address of the request to limit abuse of the form. Requesting a guide does not subscribe you to anything.
Our newsletter. The newsletter is optional and separate from the guide. You receive it only if you confirm it on the download page, which the guide email links to. Ticking the box on the form does not subscribe you on its own. You can unsubscribe at any time with one click, and you keep the guide.
How guides perform. We count page views, form starts, requests, downloads and newsletter sign-ups per guide, with the campaign and source named in the link, the referring website and the country. Page views and form starts carry no identifier and set no cookie. Requests, downloads and sign-ups are linked to the request they belong to and, if you subscribe, to your subscription. The first download of a request also counts as a lead in the acquisition records described above; these records do not hold your email address. If you ask us to delete your subscription, we also clear your address, first name and IP address from your guide requests.
6. Legal Bases for Processing (GDPR)
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we process your personal data based on the following legal grounds under Article 6 of the GDPR:
6.1 Contract Performance (Article 6(1)(b))
Processing necessary for the performance of our contract with you, including:
- Account creation and authentication
- Providing the core Service features
- Processing payments
- Sending you a free guide you requested
- Scheduling a demo call you book with us
6.2 Legitimate Interests (Article 6(1)(f))
Processing necessary for our legitimate interests, including:
- Improving and developing the Service
- Ensuring security and preventing fraud
- Analyzing usage and performance
- Preventing abuse of our public forms and measuring how our guides perform
- Answering a demo request, including one follow-up email if you did not finish booking
We have conducted balancing tests for each legitimate interest processing activity. In each case, we have determined that: (a) the processing is necessary to achieve our legitimate interest; (b) the processing does not override your fundamental rights and freedoms; and (c) you would reasonably expect such processing given your relationship with us. For service improvement and security purposes, we process only aggregated or pseudonymized data where possible, minimizing any impact on your privacy. You have the right to object to processing based on legitimate interests at any time by contacting our privacy lead (see Section 2).
6.3 Consent (Article 6(1)(a))
Where you have given consent, including:
- Marketing communications (where consent is required), including our newsletter
- Analytics cookies and advertising cookies
- Certain data sharing with third parties
You may withdraw consent at any time.
6.4 Legal Obligation (Article 6(1)(c))
Processing necessary to comply with legal obligations, including:
- Tax and accounting requirements
- Responding to lawful government requests
7. Data Sharing and Third Parties
We may share your information with the following categories of third parties:
7.1 AI Service Providers
To provide AI-powered analysis features, we transmit your research content to the following third-party AI providers:
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Anthropic | AI analysis, content generation | Prompts, transcripts, documents | United States |
| OpenAI | AI analysis, content generation, transcription | Prompts, transcripts, documents, audio | United States |
| Google (Gemini / Vertex AI) | AI analysis, content generation | Prompts, transcripts, documents | United States |
| Amazon Web Services (Bedrock) | AI analysis, content generation | Prompts, transcripts, documents | EU (eu-central-1) or US (us-east-1), matching your data region |
| Cloudflare Workers AI | AI analysis, embeddings, speech synthesis, live translation | Prompts, transcripts, documents | Global (Cloudflare network) |
| Fireworks AI | Open-model inference | Prompts, transcripts, documents | United States |
| Together AI | Open-model inference | Prompts, transcripts, documents | United States |
| Cerebras | Low-latency open-model inference | Prompts, transcripts, documents | United States |
| OpenRouter | AI model routing (fallback) | Prompts, transcripts, documents | United States (routes to upstream providers) |
| CoreWeave | Open-model inference | Prompts, transcripts, documents | United States |
| Baseten | Open-model inference | Prompts, transcripts, documents | United States |
| Nebius | Open-model inference | Prompts, transcripts, documents | European Union and United States |
| Mistral AI | Open-model inference | Prompts, transcripts, documents | European Union and United States |
| AssemblyAI | Audio/video transcription | Audio/video files | European Union (Dublin, Ireland) |
| Cartesia | Speech synthesis for AI interviews, spoken live translation and voice replacement in anonymisation | AI-generated response text; machine translations of what call participants say; redacted transcripts of recordings whose voices are replaced | United States |
These providers process your data according to their respective privacy policies and data processing agreements. If your organization brings its own API keys for a provider ("BYOK"), that provider processes your data under your organization's own agreement with the provider.
AI Model Training Policy
We have selected AI providers that commit to not using your data for model training. We do not and will never explicitly opt-in to allow any provider to use your data for training purposes. Below are the specific commitments from each provider:
| Provider | Training Policy | Source | Accessed |
|---|---|---|---|
| Anthropic | "Anthropic may not train models on Customer Content from Services." | Commercial Terms | January 2026 |
| OpenAI | "Data sent to the OpenAI API is not used to train or improve OpenAI models (unless you explicitly opt in)." | API Data Usage | January 2026 |
| Google (Vertex AI) | "Google won't use your data to train or fine-tune any AI/ML models without your prior permission or instruction." | Vertex AI Data Governance | January 2026 |
| Cloudflare Workers AI | "Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services." | Workers AI Data Usage | January 2026 |
| AssemblyAI | "We will not use files you submit for model training if you [...] are utilizing our European servers." We use exclusively EU servers. | Model Training FAQ | January 2026 |
For providers not listed in the table above (including Amazon Bedrock, Fireworks AI, Together AI, Cerebras, OpenRouter, CoreWeave, Baseten, Nebius, Mistral AI, and Cartesia), our data processing agreements with those providers prohibit the use of customer data for model training, and several additionally commit to deleting data after processing.
Important Disclaimer: While we have taken reasonable steps to select providers that commit to not using customer data for training and we do not explicitly authorize such use, we cannot guarantee that providers will not violate their stated commitments. We are not responsible for any unauthorized use of data by third-party providers that occurs in violation of their stated policies; if we become aware of such a violation, we will notify affected customers and take reasonable steps to enforce our agreements.
Automated Decision-Making and AI Processing (Article 22 GDPR)
Our AI-powered features assist you in analyzing research content, generating insights, and creating summaries. We want to be transparent about how this processing works:
Nature of AI Processing: The AI analysis features are tools that support your research workflow. They generate suggestions, summaries, and observations based on content you provide. These outputs are intended to assist your work, not to make autonomous decisions about you or produce legal or similarly significant effects on you.
Human Oversight: All AI-generated outputs are presented to you for review. You retain full control over whether to accept, modify, or reject any AI-generated content. No decisions affecting your rights or access to the Service are made solely by automated means.
7.2 Infrastructure Providers
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Cloudflare | Hosting, CDN, security, file storage (R2), AI Gateway, real-time calls, video transcoding | All Service data, uploaded files | US-based company; file storage and workers are regionalized to your selected data region (EU by default) |
| PlanetScale | Database hosting | All structured data | EU (Frankfurt, eu-central-1) by default; US (us-east-1) for organizations that select US data residency |
| Turbopuffer | Vector search indices for semantic search | Embeddings derived from research content | EU (eu-central-1) or US (us-east-1), matching your data region |
| Amazon Web Services | General cloud hosting and compute, email delivery (SES), media processing, backup storage (S3) | Email addresses and names; uploaded media files; backup copies of Service data | EU (eu-central-1) or US (us-east-2), matching your data region |
Data residency: Customer research data at rest (database records, uploaded files, vector indices) is stored in the customer's selected region — EU (Frankfurt) by default, or the United States for customers who choose US residency. Account, authentication, and organization registry data is stored in the EU (Frankfurt). Transient AI processing may occur outside your region as described in Sections 7.1 and 8.
7.3 Analytics and Monitoring Providers
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Sentry | Error tracking, performance monitoring, session replay on errors | Error logs, stack traces, device info, IP address | United States |
| Cloudflare | First-party, aggregated usage analytics | Aggregated usage metrics | Global (Cloudflare network) |
Sentry Error Tracking and Session Replay: When errors occur in the Service, we automatically collect diagnostic information including:
- Error messages and stack traces
- Browser and device information
- User actions leading to the error (session replay; text inputs and sensitive fields are masked, and we apply automated PII scrubbing before transmission)
- Performance metrics
This data helps us identify and fix bugs to improve the Service. You can control analytics collection through our cookie consent manager.
We do not currently use third-party product analytics or web analytics services (such as Google Analytics or PostHog). If we introduce such a service in the future, we will update this Privacy Policy and, where required, request your consent through our cookie consent manager first.
7.4 Payment Processing
| Provider | Purpose | Data Shared |
|---|---|---|
| Stripe | Subscription and payment processing | Billing information, transaction data |
7.5 Email Services
| Provider | Purpose | Data Shared |
|---|---|---|
| Amazon Web Services (AWS SES) | Transactional emails, notifications, participant communications | Email addresses, names |
| Cloudflare | Email delivery | Email addresses, names |
7.5a Meeting Recording Services
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Recall.ai | Meeting bot for recording video conferences (Zoom, Google Meet, Microsoft Teams) | Meeting audio/video, participant information | EU (eu-central-1) endpoint, operated by a US entity |
7.5b Integrations and Connected Accounts
The Service lets our customers connect their own accounts with third-party services and platforms. When a customer connects such an integration, personal data may be exchanged between the Service and that provider at the customer's direction and under the customer's own agreement with that provider. We are not the controller of the data you hold in those third-party services, and their handling of your data is governed by their own terms and privacy policies. Respondent is the exception: we hold the Respondent account and run the integration for workspaces that use it (see Section 3.6 and our subprocessor list). Examples of integrations a customer may connect include:
- Participant recruitment platforms (such as Prolific), used to source Research Participants
- Incentive and reward payout providers, used to send rewards to Research Participants
- Calendar and scheduling (such as Google Calendar)
- Storage and productivity tools (such as Google Drive, Microsoft Teams, GitHub, Linear, and Jira/Atlassian), used to import research material or export results
Data flows through these integrations only when a customer connects and configures them.
7.5c AI Assistant Connections (Claude, ChatGPT and Other MCP Clients)
You can connect the Service to an AI assistant that supports the Model Context Protocol (MCP), such as Claude by Anthropic or ChatGPT by OpenAI, so that the assistant can search and work with your research data on your behalf. This section explains what happens when you do.
How a connection is made. You add Reos to your assistant and sign in to Reos. Our consent screen shows which app is asking, where it will send you back to, what it will be able to do, and asks you to choose one organization. Nothing is shared until you select Allow. The connection then acts as you, with the permissions your role gives you in that organization, and only for the projects you can access. A Viewer's connection can only read; a connection never has more access than you have in the Service yourself.
What the assistant can receive. When you ask your assistant something, it calls Reos tools and receives their results. Depending on your request and your permissions, results can contain:
- Your account details: your name and email address
- Organization and project information: names, descriptions, status and counts
- Research content: raw data such as interview recordings' transcripts, documents, notes and imported data sets; observations, insights, solutions, tags, comments and documents; still images taken from your video recordings
- Research Participant data contained in that content, such as participant names, quotes, and what they said or showed in an interview
- Names of the teammates who wrote comments or created items
What we receive from the assistant. We receive only what the assistant sends to a tool: the request itself (for example, a search query, a project or item identifier, or text you ask it to save). We do not request or receive your conversation history, your other chats, the assistant's memory, or files you have not asked it to send to Reos. When you ask the assistant to add data or create documents, projects or analyses, that content is stored in your workspace like any other content you create in the Service.
Purposes. We process this data only to answer the assistant's requests on your behalf, to enforce your permissions, to keep the connection secure (including rate limiting and abuse prevention), and to troubleshoot problems with the connection. We do not use it for advertising and do not use it to train AI models.
Recipients. Results are sent to the AI assistant provider you connected (for example, Anthropic for Claude or OpenAI for ChatGPT). That provider is an independent recipient chosen by you or your organization, not a subprocessor of ours, and processes what it receives under its own terms and privacy policy and the settings of your account with it, including how long it keeps your conversations and whether it may use them to improve its models. If you connect an assistant to an organization that holds Research Participant data, your organization, as the data controller, is responsible for making sure that sharing this data with that provider is permitted, for example under your consent forms, data processing agreements and internal policies.
What we keep. We store a record of each connection: the app's registered name and callback address, your user account, the organization you chose, and when you allowed it. Access and refresh tokens are stored only in hashed or encrypted form. An access token is valid for one hour; a connection that goes unused for 90 days expires and has to be authorized again. The connection record itself is kept until you revoke the connection or your account is deleted, so that you can see it under AI assistants. Requests made through a connection are recorded in our usage and security logs, which are kept for 90 days (see Section 9). Content an assistant adds to your workspace follows the retention of your other research content.
Your controls. You can see and revoke your connections at any time under AI assistants in your profile menu. Revoking takes effect immediately: the assistant can no longer read or change anything in Reos. You can also remove the connection in your assistant's own settings, and you can ask us to delete your data as described in Section 10. Deleting your Reos account ends all of its connections.
7.5d Sales Scheduling
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Calendly (Calendly LLC) | Scheduling demo calls booked on /demo (our processor) | Name, email address, time zone, chosen time | United States |
7.6 Advertising Partners
Google Ads. Only with your advertising consent (Section 5.6; for EEA, UK, and Swiss users, consent is the sole legal basis for this), Google receives, through the Google tag on our public website pages, the ad click identifier, the public pages you view, your IP address and browser information, and, when we report a conversion to Google Ads (a finished demo, a sign-up, a booked call or a payment), the ad click identifier, the time, a random transaction identifier, the consent signals, for a payment its value, and possibly a one-way hashed (SHA-256) version of the email address you signed up or booked with. Google acts as an independent controller under the Google Ads Controller-Controller Data Protection Terms. 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. How Google uses information from sites that use its services: https://policies.google.com/technologies/partner-sites. If you withdraw your consent, or your browser sends a Global Privacy Control signal, no further data is sent to Google.
LinkedIn Ads. Only with your advertising consent (Section 5.6; for EEA, UK, and Swiss users, consent is the sole legal basis for this), LinkedIn (LinkedIn Ireland Unlimited Company for users in the EEA and Switzerland, otherwise LinkedIn Corporation) receives, when we report a conversion for a visit that came from one of our LinkedIn ads (a finished demo, a sign-up, a booked call or a payment), the ad click identifier from the ad's link, the time, a random event identifier, for a payment its value, and possibly a one-way hashed (SHA-256) version of the email address you signed up or booked with. We send this from our servers. We do not load the LinkedIn Insight Tag, LinkedIn sets no cookies on our website, and LinkedIn does not receive the pages you view, your IP address or your browser information from us. 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. If you withdraw your consent, or your browser sends a Global Privacy Control signal, no further data is sent to LinkedIn.
Meta Ads. Only with your advertising consent (Section 5.6; for EEA, UK, and Swiss users, consent is the sole legal basis for this), Meta (Meta Platforms Ireland Limited for users in the EEA and Switzerland, otherwise Meta Platforms, Inc.) receives, when we report a conversion for a visit that came from one of our Meta ads on Facebook or Instagram (a finished demo, a sign-up, a booked call or a payment), the ad click identifier from the ad's link with the time of your first visit, the time, a random event identifier, for a payment its value, and possibly a one-way hashed (SHA-256) version of the email address you signed up or booked with. We send this from our servers through Meta's Conversions API. We do not load the Meta Pixel, Meta sets no cookies on our website, and Meta does not receive the pages you view, your IP address or your browser information from us. 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. If you withdraw your consent, or your browser sends a Global Privacy Control signal, no further data is sent to Meta.
We do not share personal data with any other advertising partner.
7.7 Other Disclosures
We may also share your information:
- With your consent: When you direct us to share information with third parties
- For legal reasons: To comply with laws, legal processes, or government requests
- For safety and security: To protect the rights, property, or safety of Flob Inc., our users, or others
- In business transfers: In connection with a merger, acquisition, bankruptcy, or sale of assets
- With service providers: Contractors and agents who perform services on our behalf, bound by confidentiality obligations
8. International Data Transfers
Your information may be transferred to and processed in countries other than your country of residence, including the United States. These countries may have different data protection laws than your home country.
8.1 Data Residency
Customer research data at rest is stored in the customer's selected region — EU (Frankfurt) by default, or the United States for customers who choose US data residency. Account, authentication, and organization data is stored in the EU (Frankfurt). However, to provide AI analysis and related features, research content is transmitted to third-party providers for transient processing, several of which are US-based companies; this processing is covered by the transfer mechanisms below.
8.2 Transfer Mechanisms
For transfers from the EEA, UK, or Switzerland to the United States and other countries without an adequacy decision, we rely on:
- Standard Contractual Clauses (SCCs): EU Commission-approved contractual terms, executed with all subprocessors that receive such transfers
- EU-US Data Privacy Framework (DPF): For transfers to DPF-certified US companies
- Your consent: Where appropriate and where you have provided explicit consent
We maintain a Transfer Impact Assessment covering these transfers, following the European Data Protection Board's recommendations, and re-evaluate it at least every six months.
8.3 Safeguards
We implement appropriate safeguards to protect your data during international transfers, including:
- Encryption in transit and at rest
- Zero- or minimal-retention processing by AI providers (data is processed and discarded, not stored)
- Access controls and authentication
- Contractual protections with service providers, including prohibitions on model training and data-deletion obligations
9. Data Retention
We retain your personal data for as long as necessary to fulfill the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.
9.1 Retention Periods
| Data Category | Retention Period |
|---|---|
| Account data | Duration of account + 30 days after deletion request |
| Research content | Duration of account + 30 days after deletion |
| Research Participant data | Per the Research Organizer's instructions; deleted with the associated research content |
| Research Participant data received from Respondent | As above, or earlier where Respondent's terms require; event notifications received from Respondent are cleared after 30 days |
| Billing records | 7 years (legal requirement) |
| Usage logs | 90 days |
| AI assistant connections: access and refresh tokens | Access tokens 1 hour; refresh tokens expire after 90 days without use, or immediately when you revoke the connection |
| AI assistant connections: connection record (app, your account, chosen organization) | Until you revoke the connection or your account is deleted |
| Support communications | 3 years |
| Marketing consent records | Duration of consent + 3 years |
| Free guide requests: email address and first name | 30 days after the request |
| Free guide requests: IP address | 24 hours |
| Delivery records of guide and newsletter emails | While a guide request or a subscription holds your address; your address is then removed within about a day |
| Guide statistics, without your address | Kept for reporting |
| Ad measurement: visitor identifier and ad click data | 90 days after the click if you do not sign up (removed by a daily clean-up, so within a day after that); otherwise until your account is deleted |
| Sign-up and onboarding steps (acquisition records) | Until your account is deleted |
9.2 Deletion
When you delete your account or request data deletion:
- Your personal data will be deleted or anonymized within 30 days
- Backup copies may be retained for up to 90 days
- We may retain certain data as required by law or for legitimate business purposes
10. Your Privacy Rights
Depending on your location, you may have the following rights regarding your personal data.
Research Participants: if your data was collected as part of a study run by one of our customers, the Research Organizer is the data controller — please direct your request to them as described in Section 3.4. We will assist them in fulfilling it. The rights below apply where Flob Inc. is the data controller.
10.1 Rights Under GDPR (European Union, EEA, UK)
If you are located in the European Union, European Economic Area, or United Kingdom, you have the following rights under the General Data Protection Regulation:
Right of Access (Article 15): You have the right to obtain confirmation of whether we process your personal data and to receive a copy of that data.
Right to Rectification (Article 16): You have the right to correct inaccurate personal data and to complete incomplete data.
Right to Erasure ("Right to be Forgotten") (Article 17): You have the right to request deletion of your personal data in certain circumstances.
Right to Restriction of Processing (Article 18): You have the right to request that we restrict processing of your personal data in certain circumstances.
Right to Data Portability (Article 20): You have the right to receive your personal data in a structured, commonly used, machine-readable format and to transmit it to another controller.
Right to Object (Article 21): You have the right to object to processing based on legitimate interests, including profiling and direct marketing.
Rights Related to Automated Decision-Making (Article 22): You have the right not to be subject to decisions based solely on automated processing that produce legal or similarly significant effects.
Right to Withdraw Consent: Where processing is based on consent, you may withdraw consent at any time without affecting the lawfulness of processing based on consent before its withdrawal.
Right to Lodge a Complaint: You have the right to lodge a complaint with a supervisory authority, particularly in the EU member state of your habitual residence, place of work, or place of the alleged infringement.
Response Time: We will respond to your requests within 30 days, which may be extended by two further months where necessary.
10.2 Rights Under CCPA (California)
If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA):
Right to Know: You have the right to request disclosure of the categories and specific pieces of personal information we have collected about you, the sources of collection, the purposes of collection, and the categories of third parties with whom we share your information.
Right to Delete: You have the right to request deletion of your personal information, subject to certain exceptions.
Right to Correct: You have the right to request correction of inaccurate personal information.
Right to Opt-Out of Sale/Sharing: You have the right to opt out of the "sale" of your personal information and the "sharing" of your personal information for cross-context behavioral advertising.
Right to Limit Use of Sensitive Personal Information: You have the right to limit the use and disclosure of sensitive personal information.
Right to Non-Discrimination: We will not discriminate against you for exercising your privacy rights.
Categories of Personal Information Collected: In the past 12 months, we have collected the following categories of personal information: identifiers, commercial information, internet activity, geolocation data, professional information, and inferences.
"Sale" and "Sharing" of Personal Information: 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 (in the footer of our website and in the account menu inside the app), with Reject all in Cookie settings, or by sending a GPC signal.
10.3 Rights Under LGPD (Brazil)
If you are located in Brazil, you have the following rights under the Lei Geral de Proteção de Dados:
- Confirmation of the existence of processing
- Access to personal data
- Correction of incomplete, inaccurate, or outdated data
- Anonymization, blocking, or deletion of unnecessary or excessive data
- Data portability
- Deletion of data processed with consent
- Information about sharing with third parties
- Information about the possibility of denying consent
- Revocation of consent
10.4 Rights Under Other Jurisdictions
Canada (PIPEDA): Canadian residents have rights to access and correct personal information, and to withdraw consent subject to legal restrictions.
Australia (Privacy Act): Australian residents have rights to access and correct personal information under the Privacy Act 1988.
10.5 Exercising Your Rights
To exercise any of your privacy rights, please contact us at:
Email: support [at] reos [dot] ai
Mail: Flob Inc. Attn: Privacy Request 1111B S Governors Ave STE 49827 Dover, DE 19904 United States
We may need to verify your identity before processing your request. We will respond to verified requests within the timeframes required by applicable law.
11. Data Security
We implement appropriate technical and organizational measures to protect your personal data against unauthorized or unlawful processing, accidental loss, destruction, or damage.
11.1 Security Measures
- Encryption: Data is encrypted in transit (TLS 1.3/HTTPS) and at rest (AES-256)
- Access Controls: Role-based access controls, two-factor authentication (TOTP and passkeys), and configurable MFA enforcement
- Infrastructure Security: Secure cloud infrastructure with Cloudflare WAF, DDoS protection, and rate limiting
- Credential Protection: API keys and sensitive credentials are encrypted at the application level before storage
- Monitoring: Security monitoring, audit logging, and alerting for suspicious activity
- Vendor Security: Third-party vendors are evaluated for security certifications and practices, with data processing agreements in place
11.2 Certifications and Independent Audits
Flob Inc. maintains:
- SOC 2 Type II attestation (independent audit of our security, availability, and confidentiality controls over time)
- ISO/IEC 27001 certification (information security management system)
- ISO/IEC 42001 certification (AI management system, covering the responsible development and operation of our AI features)
- A GDPR compliance program, including records of processing activities, transfer impact assessments, and data protection reviews
Audit reports and certificates are available to customers on request, subject to confidentiality obligations.
While we maintain these certifications and safeguards, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
11.3 Your Responsibilities
You are responsible for:
- Maintaining the security of your account credentials
- Using strong, unique passwords
- Enabling two-factor authentication
- Notifying us promptly of any unauthorized access
11.4 Breach Notification
In the event of a personal data breach that poses a risk to your rights and freedoms, we will notify you and relevant supervisory authorities as required by applicable law.
12. Children's Privacy
The Service is not intended for use by individuals under the age of 18, and we do not knowingly collect personal information directly from children under 18 as account holders. If we become aware that we have collected such information, we will take steps to delete it promptly.
Research Organizers may only involve minors as Research Participants where they have obtained verifiable parental or guardian consent and comply with all applicable children's privacy laws, as required by our Terms of Service; the Research Organizer is the data controller for such data.
If you are a parent or guardian and believe your child has provided us with personal information, please contact us at support [at] reos [dot] ai.
13. Cookies and Tracking Technologies
We use cookies and similar tracking technologies to collect and track information about your use of the Service. For detailed information about our use of cookies, please see our Cookie Policy.
13.1 Types of Cookies
- Essential Cookies: Required for the Service to function (authentication, security)
- Functional Cookies: Remember your preferences (theme, settings)
- Analytics Cookies: Help us understand how you use the Service (error tracking and diagnostics)
- Advertising Cookies: Google Ads, LinkedIn Ads and Meta Ads conversion measurement and our first-party visitor cookie: in the EEA, the UK, Switzerland, Brazil and Quebec only with your prior consent; elsewhere on by default until you turn them off, and always off under Global Privacy Control
13.2 Your Choices
You can manage your cookie preferences through our cookie consent banner, with "Cookie settings" (in the EEA, the UK, Switzerland, Brazil and Quebec) or "Your privacy choices" (everywhere else) in the footer of our website or in the account menu inside the app, or by adjusting your browser settings. Note that disabling certain cookies may affect the functionality of the Service.
14. Do Not Track Signals
Some browsers transmit "Do Not Track" (DNT) signals. Our Service does not currently respond to DNT signals, as there is no industry standard for handling such signals. You can manage tracking through our cookie consent manager.
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.
15. Third-Party Links
The Service may contain links to third-party websites or services. We are not responsible for the privacy practices of these third parties. We encourage you to read the privacy policies of any third-party websites you visit.
16. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by:
- Posting the updated Privacy Policy on the Service
- Updating the "Last Updated" date
- Sending you an email notification (for material changes)
Your continued use of the Service after any changes indicates your acceptance of the updated Privacy Policy.
We encourage you to review this Privacy Policy periodically.
17. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact us:
Flob Inc. 1111B S Governors Ave STE 49827 Dover, DE 19904 United States
Email: support [at] reos [dot] ai
Data Protection Contact: For GDPR-related inquiries, you may contact our data protection point of contact at the same address.
17.1 Complaints
If you are not satisfied with our response to your privacy concerns, you have the right to lodge a complaint with your local data protection authority:
- EU Residents: Contact your local Data Protection Authority (DPA). A list of all EU DPAs is available at: https://edpb.europa.eu/about-edpb/about-edpb/members_en
- UK Residents: Information Commissioner's Office (ICO) - https://ico.org.uk
- Swiss Residents: Federal Data Protection and Information Commissioner (FDPIC) - https://www.edoeb.admin.ch
- California Residents: California Attorney General - https://oag.ca.gov/privacy
- Brazilian Residents: Autoridade Nacional de Proteção de Dados (ANPD)
18. California Privacy Notice
This section provides additional information for California residents pursuant to the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA).
18.1 Categories of Personal Information
In the preceding 12 months, we have collected the following categories of personal information:
| Category | Examples | Collected |
|---|---|---|
| Identifiers | Name, email, IP address, account ID | Yes |
| Personal Information (Cal. Civ. Code 1798.80) | Name, address, phone number | Yes |
| Protected Classification Characteristics | None intentionally collected | No |
| Commercial Information | Purchase history, subscription records | Yes |
| Biometric Information | None collected for identification purposes | No |
| Internet Activity | Browsing history, interactions with Service | Yes |
| Geolocation Data | IP-based approximate location | Yes |
| Sensory Data | Audio/video files you upload | Yes |
| Professional Information | Job title (if provided) | Yes |
| Education Information | None intentionally collected | No |
| Inferences | Usage patterns, preferences | Yes |
| Sensitive Personal Information | Account credentials | Yes |
18.2 Sources of Personal Information
We collect personal information from:
- You directly (account creation, content upload)
- Automatically (usage data, device information)
- Third parties (OAuth providers, payment processor)
18.3 Business or Commercial Purposes
We use personal information for the purposes described in Section 5 of this Privacy Policy.
18.4 Disclosure for Business Purposes
We disclose personal information to the categories of third parties described in Section 7 of this Privacy Policy.
| Recipient | Categories of Personal Information | Purpose |
|---|---|---|
| Google (only with your advertising consent) | Identifiers (including a hashed email address), Internet activity | Advertising measurement |
| LinkedIn (only with your advertising consent) | Identifiers (including a hashed email address) | Advertising measurement |
| Meta (only with your advertising consent) | Identifiers (including a hashed email address) | Advertising measurement |
18.5 Sale and Sharing of Personal Information
Note for EEA/UK/Swiss Users: The terms "sale" and "sharing" used in this section are specific legal definitions under California law (CCPA/CPRA) and do not reflect how we process data for users in the EEA, UK, or Switzerland.
For California Residents: 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 (in the footer of our website and in the account menu inside the app), with Reject all in Cookie settings, or by sending a GPC signal.
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.
You may contact us about your rights at any time by emailing support [at] reos [dot] ai with the subject line "California Privacy Request."
18.6 Retention
We retain personal information as described in Section 9 of this Privacy Policy.
This Privacy Policy was last updated on November 13, 2026.







