Get the most out of OpenFrame · Book 30 minutes with Conrad, 25 years in IT. He'll show you what Mingo and Fae can take off your list.
Version 2.2 · Effective December 1, 2026
Version: 2.2
Effective date: December 1, 2026
Applies to: All Flamingo AI products, including OpenFrame, OpenFrame SaaS, OpenMSP, and the Flamingo Website
“Flamingo Software” means all software products developed and released by Flamingo AI, Inc., including but not limited to OpenFrame, OpenFrame SaaS, OpenMSP, related agents, integrations, orchestration layers, user interfaces, binaries, and documentation.
“OpenFrame” refers to the self-hosted remote monitoring and management (RMM) platform released by Flamingo AI.
“OpenFrame SaaS” refers to the hosted version of OpenFrame operated by Flamingo AI at openframe.ai, where Flamingo AI processes customer data on the customer’s behalf. This is distinct from self-hosted OpenFrame deployments, which Flamingo AI does not operate and cannot access.
“OpenMSP” refers to the community knowledge base, documentation, and related collaborative content contributed by users and curated by Flamingo AI.
“Flamingo Website” refers to flamingo.run, openframe.ai, openmsp.ai and related domains controlled by Flamingo AI.
This Privacy Policy explains how Flamingo AI, Inc. (“Flamingo AI”) collects, uses, and protects personal data in connection with Flamingo Software, including OpenFrame, OpenFrame SaaS, OpenMSP, and the Flamingo Website.
Where a customer uses OpenFrame SaaS, Flamingo AI processes the data below. Operational data, remote session recordings, AI requests and connected directory data are processed on the customer’s behalf. Account, sign-up, customer relationship, product analytics and billing data are also used by Flamingo AI for its own purposes: managing accounts and billing, communicating with customers, measuring advertising and understanding how the product is used.
Each customer's data is logically separated from other customers' data, and customer records are scoped to that customer.
Data is encrypted in transit and at rest. Connections over the internet use TLS. OpenFrame SaaS runs on Google Cloud, which encrypts traffic between servers inside its network and encrypts stored data.
Flamingo AI does not sell customer data and does not use it to train artificial intelligence or machine learning models.
What we access. When a Google Workspace super administrator grants consent for their tenant, we access data through Google's Admin SDK Directory, Reports and Licensing APIs:
The consent request also includes the OpenID and email scopes, so that we can confirm which administrator granted it, and write permissions for users, groups and group members. Two of the permissions Google grants are wider than our use of them: the licensing permission and the user security permission both allow changes, and OpenFrame uses them only to read. We do not request or access Gmail, Google Drive, Google Calendar, Google Chat, Google Meet, or Google Photos data.
How we use it. To provide IT administration features to the administrators who manage that tenant, including through OpenFrame's AI assistant when an administrator asks it to retrieve or act on that data.
Actions we take on the customer's behalf. OpenFrame can make no change unless the super administrator has granted the write permissions. An administrator can also switch write-back off for a connection, which stops OpenFrame making any change while directory data continues to synchronize. Where write-back is on, OpenFrame can:
OpenFrame does not assign or remove licences, delete user accounts, grant administrative roles, or perform any action on a device. It does not reset the password of an existing account. Google may assign a licence itself when a user is created or moved, under the customer's own settings. Changes are made only in response to a request from an OpenFrame user: no scheduled or background process modifies your users, groups, group memberships or organizational units. Where OpenFrame registers notification channels with Google to receive directory updates, a background job maintains them; those channels are OpenFrame's own subscriptions, and they are stopped when the connection is deleted. OpenFrame records each change with the identity of the OpenFrame user who requested it. Google's own administrative audit log records the same action under the administrator who granted consent.
Who we share it with. To generate a response to an administrator's request, the relevant data is sent to the AI provider selected for the assistant: Anthropic (Claude API) or OpenAI. Whichever provider is selected, some supporting functions use a fixed provider. Anthropic is used to shorten long conversations, to name conversations and to search the web. OpenAI is used to extract facts the assistant should remember, to review the quality of the assistant's answers, to check commands before they run, and to decide when an end-user conversation should be handed to a technician. Conversation content, which can include directory data the assistant retrieved, is therefore sent to both providers. Under those providers' commercial API terms, customer content is not used to train their models. Each provider may retain requests and responses for up to 30 days to detect abuse and misuse, and OpenAI may review retained content for that purpose.
Flamingo AI records AI requests and responses in its operational logs for up to 90 days. Flamingo AI engineers read those logs only where it is necessary to investigate a bug or abuse, or to comply with applicable law. They read a specific conversation for any other reason only after an administrator of that customer has agreed to it, for example in a support request. To find faults in the assistant, an automated review reads technician conversations and sends findings to an internal Flamingo AI Slack channel. A finding contains a description of the problem written by the AI model and a link to the conversation, which only users of that customer can open; the description is not anonymized. We may also publish anonymized descriptions of how the AI assistant is used, including in our Slack community, with customer, client and personal identifiers removed by our team. We do not sell Google Workspace data, and we do not transfer it to advertising platforms, data brokers, or resellers. Apart from the AI providers and the internal channel described above, it is not shared with any third party, except where an administrator asks us to include information in a support request.
How we protect it. Google user data is encrypted in transit between Google and OpenFrame. The OAuth refresh token issued for a connected tenant is encrypted with Google Cloud Key Management Service under a key created for the OpenFrame customer that owns the connection, and is stored only in encrypted form.
How long we keep it, and how it is deleted. Directory data is retained for as long as the connection exists. A connection can be disconnected or deleted. When it is disconnected, we delete the stored refresh token and keep the synchronized directory data. When it is deleted, we delete the stored refresh token and the directory data synchronized through it. Audit events already received remain in our logs for up to 90 days. In neither case do we revoke the grant at Google: to end OpenFrame's access, remove it in the Google Admin console or in your Google Account's third-party access settings. Conversations with the AI assistant, facts derived from them and review findings are kept until the customer's data is deleted (section 10). You can request deletion by contacting privacy@flamingo.run. Copies remain in backups for the periods in section 10.
Limited Use. OpenFrame's use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. Data received from Google Workspace APIs is not used to develop, improve, or train non-personalized artificial intelligence or machine learning models, whether by Flamingo AI or by any third party.
What we access. When a Global Administrator grants tenant-wide admin consent, we access data through the Microsoft Graph API. Consent is granted separately for each set of permissions we use, and each set is a separate OpenFrame application in your Entra directory.
We do not access Exchange Online mailboxes, OneDrive or SharePoint files, calendars, Teams chats or meetings, or Intune device management. We do not read sign-in log records; we read only the date of each user's last sign-in.
How we use it. To provide IT administration features to the administrators who manage that tenant, including through OpenFrame's AI assistant when an administrator asks it to retrieve or act on that data.
Actions we take on the customer's behalf. Making changes requires a further, separate admin consent for the write permissions, and write-back must be on for the connection; otherwise OpenFrame attempts no change. Where both hold, OpenFrame can:
OpenFrame does not change licence assignments, reset passwords for existing accounts, delete user accounts, perform any action on a device, or assign administrative roles. Changes are made only in response to a request from an OpenFrame user; no scheduled or background process modifies your users, groups or group memberships. Where OpenFrame registers change-notification subscriptions with Microsoft to receive directory updates, a background job maintains them. OpenFrame records each change with the identity of the OpenFrame user who requested it. Microsoft's own audit log records the same action under the OpenFrame application.
Who we share it with. As described in section 5 for Google Workspace data: the relevant data is sent to the AI providers named there, is retained by them and recorded in Flamingo AI's operational logs as described there, and is not sold, transferred to advertising platforms, data brokers or resellers, or otherwise shared with any third party except where an administrator asks us to include information in a support request.
How we protect it. Microsoft 365 data is encrypted in transit between Microsoft and OpenFrame. We store no credential of yours: access is granted as service principals of OpenFrame's own applications inside your Entra directory, and OpenFrame's own application credentials are held in our secret store, never in the customer database.
How long we keep it, and how it is deleted. Directory data is retained for as long as the connection exists. When the connection is disconnected, we remove the change-notification subscriptions and keep the synchronized directory data. When the connection is deleted, we remove the subscriptions and delete the directory data synchronized through it. Audit events already received remain in our logs for up to 90 days. Because the authorization lives in your own directory rather than as a token held by us, access ends fully when you remove the OpenFrame applications from your Entra portal.
Flamingo AI processes personal data only when:
Depending on your location (EU/UK under GDPR, California under CCPA, or similar laws), you may have the right to:
Requests can be submitted to privacy@flamingo.run.
An OpenFrame SaaS user can delete their own account in Settings. We then remove the user's name, email address, password, profile picture and sign-in links from the account. Tickets, conversations and activity records the user created remain with the customer's workspace, and the user's contact record remains in HubSpot until you ask us to delete it.
Flamingo AI products are not directed to children under 16 in the EU/UK or under 13 in the US. Flamingo AI does not knowingly collect data from minors.
Flamingo AI implements reasonable technical and organizational safeguards, but customers remain fully responsible for the security of their own infrastructure.
Use of Flamingo AI products is entirely at your own risk. Customers are solely responsible for compliance with applicable data protection laws when deploying Flamingo AI software or participating in OpenMSP.
Text messaging originator opt-in data and consent will not be shared with any third parties, excluding aggregators and providers of the Text Message services.
We use service providers that process personal data on our behalf, each under a contract that limits what it may do with the data. Advertising and visitor-identification providers also use the data they receive for their own purposes, under their own terms:
| Purpose | Provider |
|---|---|
| Hosting of OpenFrame SaaS, encryption key management | Google Cloud |
| Single sign-on | Google, Microsoft, Apple |
| Push notifications | Google Firebase, Apple |
| Hosting and database of the Website and of the OpenFrame help centre | Vercel, Supabase |
| AI responses, AI supporting functions, web search | Anthropic, OpenAI |
| Payments and invoicing | Stripe |
| Customer relationship management, marketing and account email, support tickets, meeting booking | HubSpot |
| Product and Website analytics, session recording | PostHog, Google Analytics, Ahrefs |
| Tag management | |
| Advertising measurement | Google Ads, Meta, Reddit, LinkedIn |
| Identifying the company a Website visitor comes from | Snitcher, Leadsy |
| Internal notifications; community | Slack |
| Meeting recording | Google Workspace (Google Meet), Fireflies |
| Transcription and video processing of recorded calls | AssemblyAI, Shotstack, Vizard |
| Video hosting | Mux |
The current list of subprocessors is published in our Trust Center.
Analytics and advertising cookies are set when you open the Website. You can block or delete cookies in your browser settings or through the opt-out tools each provider offers. Blocking necessary cookies may stop sign-in or chat history from working.
The version and effective date of this Privacy Policy are stated at the top. When we make a change that materially affects how we use personal data, we announce it on the Website or by email before it takes effect.
Privacy Inquiries: privacy@flamingo.run
General Information: hello@flamingo.run
By using Flamingo AI products, you acknowledge and agree to this Privacy Policy.