FlowMT public policy
Privacy Policy
FlowMT ยท PERFECT GLASS SRL
Last updated: 2026-03-31
FlowMT is a Software-as-a-Service platform owned and operated by PERFECT GLASS SRL. This Privacy Policy explains how we access, collect, use, store, share and delete personal data and social-platform API data when users connect accounts or use FlowMT for social media management, content publishing, advertising, analytics, messaging, live streaming and multi-account operations.
Effective date: 2026-03-31
Company and controller information
- Product: FlowMT
- Company: PERFECT GLASS SRL
- Registered country / governing law: Moldova
- Address: Chisinau
- Company registration number: 1025600066734
- Website: https://flowmt.com/company
- Official contact: contact@flowmt.com
What FlowMT does
FlowMT helps businesses, agencies and creators manage official social-platform integrations from one workspace. Depending on the features selected by the user, FlowMT may connect to Facebook, Instagram, YouTube, Google, LinkedIn, LinkedIn Live, TikTok, Twitch, X, Pinterest and manually configured RTMP destinations.
FlowMT is not affiliated with, endorsed by, or controlled by those third-party platforms. Each connected platform remains governed by its own terms, privacy policy and developer policies.
Data we collect directly from users
- Account information such as name, email address, username, workspace membership and login identifiers.
- Business, agency or creator profile information added by the user inside the workspace.
- Content prepared in FlowMT, including post text, captions, media files, thumbnails, scheduling choices and campaign details.
- Live-streaming information such as live title, description, selected destinations, comments, reactions and basic stream-health information.
- Support messages, contact-form submissions and operational communications.
- Technical data such as device type, browser, IP address, logs, timestamps and security events needed to operate and protect the service.
Creator monetization data
When FlowMT offers creator monetization, we process additional data to calculate qualified views, apply the current configured rate of 3.00 USD per 1,000 qualified views, enforce the minimum payout of 10.00 USD and manage payout operations.
- We process creator account status, payout method, payment country, payment currency, approval status, hold reasons and account timestamps.
- We process payout details submitted by creators, such as payout email, account-holder name, payment notes or other payout instructions.
- We process qualified-view events for eligible videos, shorts and live streams, including content ID, creator ID, viewer/session identifiers when available, watch duration, qualification status, disqualification reason, calculated amount and timestamps.
- Hashed IP, device or browser information and session identifiers may be used for deduplication, abuse prevention, security review and payout integrity.
- Monthly summaries, payout requests, adjustments, payment references and review records are retained for accounting, fraud prevention, disputes and legal compliance.
- Fraudulent, artificial, automated, incentivized, recycled, purchased or manipulated views are excluded from payment eligibility.
Data received from connected social platforms
FlowMT receives platform data only after the user authorizes access through OAuth, an official API flow or a manual RTMP/live-destination configuration. The exact data depends on the platform, scopes approved by the user and features enabled in FlowMT.
- Google and YouTube: channel identifiers, metadata, access and refresh tokens, video/live metadata, upload or live-broadcast settings, comments, analytics and other YouTube API data needed for user-authorized features.
- Meta, Facebook and Instagram: account, page or business identifiers, profile/page metadata, approved permissions, post/media metadata, comments, reactions, insights and publishing/live information.
- LinkedIn and LinkedIn Live: member or organization identifiers, metadata, publishing permissions, post metadata, analytics and live-stream configuration.
- TikTok: account identifiers, profile metadata, publishing or analytics data available through approved API access. Manual live destinations use the server URL and stream key supplied by the user.
- Twitch: channel identifiers, profile metadata, chat/comment data, stream-key data where authorized, live status and engagement data.
- X, Pinterest and other integrations: account identifiers, profile/board/page metadata, content metadata, publishing status and analytics available through user-authorized access.
Scope-by-scope disclosures for connected platforms
FlowMT requests platform permissions only to operate user-facing features visible inside the product. A user may connect one platform without connecting another. Permissions may include:
email,profile,openidfor account identity, login and connected-account display.youtube,youtube.uploadandyoutube.readonlyfor authorized YouTube channel management, live broadcasts, uploads, comments, status, metadata and analytics.adwordsfor Google Ads accounts, campaign management and reporting selected by the user.business_management,pages_show_list,pages_manage_metadata,pages_read_engagement,pages_manage_postsandread_insightsfor authorized Meta/Facebook Page assets, publishing, engagement and insights.instagram_business_basic,instagram_basicand content-publishing permissions for connected Instagram professional accounts.w_member_social,r_member_liveandw_member_livefor authorized LinkedIn publishing and LinkedIn Live operations.user.info.basic,video.list,video.publishandvideo.uploadfor selected TikTok workflows.user:read:email,channel:read:stream_keyandchat:readfor selected Twitch workflows.tweet.read,tweet.write,users.read,media.writeandoffline.accessfor selected X workflows.user_accounts:read,boards:read,boards:write,pins:readandpins:writefor selected Pinterest workflows.
Google account sign-in
email identifies the account, supports login and verification messages and helps prevent duplicate accounts. profile displays the user's basic name or avatar when Google login is used.
YouTube API Services
youtube manages user-authorized YouTube resources, including live broadcasts, stream metadata, video metadata, channel status, comments and related actions. youtube.upload uploads videos selected by the user. youtube.readonly reads channel information, video/live status, comments and basic analytics-related metadata needed to show the authorized account.
Google Ads
openid, email and profile verify the Google identity connecting advertising accounts. adwords lists and manages accessible Google Ads customer accounts, campaigns and reporting workflows selected by the user.
Meta and Facebook Pages
business_management discovers and manages authorized business assets and page relationships. pages_show_list shows available Pages. pages_manage_metadata maintains connection metadata, webhooks and technical configuration. pages_read_engagement reads comments, reactions and basic performance data. pages_manage_posts creates, schedules, edits or deletes Page posts only when requested. read_insights displays Page, post, campaign or content performance analytics.
Instagram Business
instagram_business_basic or instagram_basic identifies the connected professional account and verifies eligibility for FlowMT features. instagram_business_content_publish or instagram_content_publish publishes content selected by the user when platform approval allows it. For manually configured Instagram live destinations, FlowMT uses only the server URL and stream key supplied by the user.
LinkedIn and LinkedIn Live
openid, profile and email identify the connected member. w_member_social publishes posts and media selected by the user. r_member_live reads live eligibility and broadcast status, while w_member_live creates, configures, starts, updates or ends selected LinkedIn Live broadcasts. These authorizations are separate.
TikTok
user.info.basic identifies the account. video.list reads the user's video list and metadata. video.publish publishes selected videos, and video.upload supports approved upload workflows. For manually configured TikTok Live destinations, the user supplies the server URL and stream key.
Twitch
user:read:email identifies the connected account. channel:read:stream_key retrieves the authorized channel stream key for selected restreaming, and chat:read reads Twitch live chat for the broadcaster's FlowMT interface.
X
tweet.read reads post metadata and performance fields; tweet.write publishes user-created or scheduled posts; users.read identifies the account; media.write uploads user-selected media; and offline.access maintains the connection through refresh tokens for scheduled posts and account status.
user_accounts:read identifies the account. boards:read lists boards, boards:write creates or updates boards, pins:read reads pin status and performance information, and pins:write creates or updates pins selected by the user.
FlowMT does not ask for social-platform passwords and does not use Google, YouTube or other platform API data to train generalized AI models.
How we use data
- To create and secure FlowMT accounts and workspaces.
- To connect social accounts after user authorization and keep selected integrations working.
- To publish, schedule, update or delete content only when requested by the user or an authorized workspace member.
- To start, maintain, monitor and stop live streams and restreams selected by the user.
- To display comments, reactions, messages, campaign performance, analytics and social-account status inside FlowMT.
- To diagnose technical issues, prevent abuse, protect accounts and comply with legal obligations.
What FlowMT does not do with platform data
- FlowMT does not sell personal data, OAuth tokens, stream keys, comments, messages, analytics or platform API data.
- FlowMT does not publish, delete, update, start a live stream or spend advertising budget without a user action, schedule, workspace permission or explicit configuration.
- FlowMT does not use connected platform data to build hidden profiles outside the FlowMT product experience.
- FlowMT does not transfer Google or YouTube user data to third parties except as needed to provide user-facing features, for security, legal compliance or with user consent.
- FlowMT does not use Google, YouTube, Meta, TikTok, LinkedIn or Twitch API data to train generalized AI or machine-learning models.
Google and YouTube API Services disclosure
FlowMT uses YouTube API Services and Google APIs only to provide user-authorized features such as connecting a YouTube channel, creating or managing live broadcasts, publishing video metadata, displaying comments and analytics and showing account status.
FlowMT's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Users can review the Google Privacy Policy and YouTube Terms of Service.
- We do not sell Google or YouTube user data.
- We do not use Google or YouTube user data for unrelated advertising targeting.
- We store tokens and API data only as needed to provide connected features and maintain security, auditability and reliability.
Sharing and third parties
We share data only when necessary to provide FlowMT, when the user instructs us to send content to a connected platform, when a service provider processes data for us or when required by law.
- Connected platforms receive the content, metadata and actions that the user chooses to send to them.
- Infrastructure, hosting, email, analytics, security and support providers may process limited data on our behalf.
- We may disclose data to comply with legal obligations, enforce our terms, prevent abuse or protect rights and safety.
- We do not sell personal data or platform API data.
Storage, security and retention
FlowMT uses technical and organizational safeguards designed to protect user data, including HTTPS, access controls, encrypted storage for sensitive tokens/keys where supported by the backend, monitoring and restricted administrative access.
We keep account, workspace, content, integration and operational records for as long as needed to provide FlowMT, meet legal obligations, resolve disputes, prevent abuse and keep backups. OAuth tokens and connected account data are deleted or disabled when no longer needed, when a user disconnects an account or when a deletion request is completed, subject to legal and security retention requirements.
Detailed retention practices
- Account records: kept while the FlowMT account is active and for a reasonable period afterward for legal, security and audit purposes.
- OAuth tokens: kept only while the integration is connected or needed for scheduled/user-requested actions. Tokens are removed or invalidated when an account is disconnected or deletion is completed, subject to backup and security retention.
- Stream keys and manual RTMP destinations: stored only to send live streams to destinations configured by the user. They are treated as sensitive credentials and should be deleted when no longer needed.
- Uploaded media and prepared content: kept while needed for drafts, schedules, publishing history, live workflows, analytics or user access, unless deleted earlier by the user or by request.
- Comments, reactions and messages: kept to display engagement, moderation and reporting views, and may be refreshed or removed when the connected platform no longer provides access.
- Logs and security events: kept for troubleshooting, anti-abuse, reliability, audit and legal compliance. Logs are limited where possible and sensitive values are masked.
- Backups: deleted according to backup rotation. Data removed from production systems may remain in encrypted backups for a limited time until those backups expire.
Security controls
- HTTPS is used for production web access and API communication.
- OAuth callback state values are signed to reduce the risk of forged authorization callbacks.
- Sensitive tokens, stream keys and destination secrets are encrypted or masked where supported by backend storage and logs.
- Administrative access is restricted to authorized personnel and used only for operations, support, security, billing, compliance or abuse investigation.
- Rate limiting, input validation and authentication checks are used on backend endpoints.
- Operational logs are reviewed to diagnose delivery, publishing, live streaming, OAuth and SMTP issues without exposing passwords or secret tokens to users.
- When we become aware of a security incident affecting personal data, we will investigate, mitigate and notify affected users or authorities where required by law.
Workspace access and agency use
FlowMT may be used by teams, agencies and businesses. A workspace owner or administrator may invite other users, assign permissions and allow them to manage connected social accounts. Users should invite only trusted people and should remove access when a team member no longer needs it.
Child Safety Standards
FlowMT strictly prohibits Child Sexual Abuse and Exploitation (CSAE) and Child Sexual Abuse Material (CSAM).
FlowMT has zero tolerance for child sexual abuse or exploitation and for any attempt to use FlowMT to facilitate it.
Prohibited conduct
Users must not use FlowMT to create, publish, upload, transmit, distribute, request, store, promote or facilitate CSAE, CSAM or any related sexual exploitation of children.
- Creating, generating, requesting, uploading, publishing, streaming, transmitting, storing or possessing CSAE or CSAM, including images, video, audio, text or links.
- Distributing, sharing, exchanging, selling, promoting or otherwise making available sexual content involving children.
- Grooming or manipulating a child or another person to enable sexual abuse or exploitation of a child.
- Sextortion, blackmail, threats or coercion involving a child or sexual content involving a child.
- Trafficking or otherwise exploiting children for sexual purposes.
- Soliciting, arranging or facilitating sexual contact with a child, or soliciting or exchanging sexual content involving a child.
- Any attempt to assist, encourage, finance, organize or otherwise facilitate child sexual abuse or exploitation.
Reporting child-safety concerns
Users can also access profile reporting and blocking actions from supported comments and conversations. Child-safety concerns can additionally be submitted through the official Child Safety contact and public FlowMT contact form.
Child Safety contact
Child Safety contact: contact@flowmt.com
Read the full FlowMT Child Safety Standards: /child-safety
How FlowMT responds
- Remove or restrict access to content.
- Restrict, suspend or terminate accounts or access where permitted by our policies and applicable law.
- Preserve information when legally necessary or appropriate.
- Cooperate with competent authorities and lawful investigations.
- Report confirmed CSAM or other suspected child sexual exploitation to competent authorities or legally recognized organizations when required or permitted by applicable law.
Scope
These standards apply to all users and all content and interactions available through FlowMT, including social profiles, photos, videos, shorts, live streams and social interactions. They apply regardless of whether conduct occurs on or off the platform when it relates to FlowMT.
Children
FlowMT is intended for users aged 18 and over. Users under 18 may not create or use a FlowMT account. We do not knowingly collect personal data from users under 18.
User choices, account deletion and international transfers
Users can disconnect social accounts where available, revoke access from connected-platform settings and request access, correction, export or deletion of personal data by contacting the official email above. Data-deletion instructions are available at /data-deletion.
FlowMT may process data in countries where we, our service providers or connected platforms operate. When required, we rely on appropriate safeguards and contractual protections for international transfers.
Changes and contact
We may update this Privacy Policy when FlowMT features, integrations, laws or platform requirements change. For privacy questions, complaints, data requests or platform-review inquiries, use the official contact details above or the public contact form.