Flamingo

Privacy Policy.

Last Updated: 06/12/2026Source: SECURITY.md

Flamingo AI Privacy Policy

Effective Date: 2025
Applies to: All Flamingo AI products, including OpenFrame, OpenMSP, and the Flamingo Website

1. Definitions

“Flamingo Software” means all software products developed and released by Flamingo AI, Inc., including but not limited to OpenFrame, 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.

“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.cx and related domains controlled by Flamingo AI.

2. Scope

This Privacy Policy explains how Flamingo AI, Inc. (“Flamingo AI”) collects, uses, and protects personal data in connection with Flamingo Software, including OpenFrame, OpenMSP, and the Flamingo Website.

3. Data Collection

  • Self-Hosted Deployments (OpenFrame): Flamingo AI does not access or collect customer data. All data remains fully under customer control.
  • OpenMSP (Community): Flamingo AI collects account registration details (username, email), and any content you voluntarily submit (posts, documentation, comments). Metadata (such as IP addresses and logs) may be collected for security, fraud prevention, and moderation.
  • Website: Limited analytics (IP addresses, device/browser data, cookies) are collected for performance, security, and improvements.
  • Support Engagements: Customers may voluntarily provide logs or diagnostic data for troubleshooting. Such data is deleted promptly after resolution.

4. Legal Basis for Processing (GDPR)

Flamingo AI processes personal data only when:

  • You have given consent (e.g., submitting community contributions to OpenMSP, website cookies).
  • Processing is necessary for the performance of a contract (e.g., account creation, support requests).
  • Processing is required by law.
  • Processing is necessary for legitimate interests (e.g., community moderation, improving security and services).

5. Data Subject Rights

Depending on your location (EU/UK under GDPR, California under CCPA, or similar laws), you may have the right to:

  • Access your personal data.
  • Rectify inaccurate data.
  • Request deletion (“right to be forgotten”).
  • Restrict or object to processing.
  • Request portability of your data.
  • Withdraw consent at any time.
  • Opt out of sale or sharing of personal data (CCPA).
  • Lodge a complaint with a supervisory authority (for EU/UK residents).

Requests can be submitted to privacy@flamingo.so.

6. Data Transfers

  • Flamingo AI does not transfer customer data from self-hosted deployments.
  • If personal data must cross borders (e.g., for support or OpenMSP account services), Flamingo AI uses safeguards such as Standard Contractual Clauses.

7. Data Retention

  • Customer-controlled data in OpenFrame remains under customer control.
  • Support data is retained only for resolution, typically deleted within 24 hours.
  • Website analytics are retained no longer than necessary for stated purposes.
  • OpenMSP contributions remain public unless removed by you or as part of community moderation. Account data may be deleted upon request.

8. Children’s Privacy

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.

9. Security

Flamingo AI implements reasonable technical and organizational safeguards, but customers remain fully responsible for the security of their own infrastructure.

10. Responsibility Disclaimer

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.

11. Text Messaging Opt-In Data

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.

12. Contact Information

Privacy Inquiries: privacy@flamingo.so
General Information: info@flamingo.so

By using Flamingo AI products, you acknowledge and agree to this Privacy Policy.

AI MSP

Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.
Most MSPs start with AI features inside their existing PSA, RMM, and ticketing systems rather than standalone products. Common categories include AI ticket triage, alert correlation, scripting assistants, and AI-native all-in-one platforms like OpenFrame that run intelligence across the whole stack.
Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.

AI Safety

It can be, with governance. Keep a human in the loop on high-risk actions, log every automated step for audit, and choose platforms that keep your data yours with no vendor lock-in. Pilot on internal data first so you catch issues before client systems are involved.

MSP AI Agents

An AI agent for an MSP is software that reads a ticket, decides the action, performs it across your tools, and records the result without a technician driving each step. It differs from a chatbot or copilot by taking action, not just suggesting one.
Yes, for low-risk categories. MSPs report 10% to 25% of tickets closed without a tech opening them, covering password resets, MFA enrollment, and known installs. Anything needing judgment or touching production data still escalates to a human.

AI for MSPs

No. AI automates routine tickets, patching, and monitoring, but trust, accountability, and complex business judgment still need people. The future of managed services moves technicians from closing tickets to advising clients, which makes the human role more valuable, not obsolete.

AI Infrastructure

AI-powered infrastructure managed services apply machine learning to infrastructure telemetry so providers can predict failures, automatically remediate known issues, and forecast capacity needs. They replace static-threshold monitoring and manual firefighting with predictive, largely automated operations overseen by technicians.