Privacy Policy
Last updated: October 20, 2026
This policy describes how Flowmatic handles information when you use its RSS, workflow, AI-content, approval, and social-publishing features. Some integrations are optional and may not be enabled in every deployment. If you operate a self-hosted instance, your organization controls its hosting, database, backups, and retention settings.
1. Information processed
- Account and sign-in information: name, email address, password hash for password sign-in, profile image, and account identifiers or tokens returned by an identity provider such as Google when enabled.
- Workspace and workflow information: workspace membership and roles, workflow definitions, settings, prompts, schedules, and configuration you provide.
- RSS and content information: feed URLs, article titles, links, summaries and other feed fields, generated drafts, approval decisions, publishing settings, and execution results or error messages.
- Connected services: account identifiers, permissions, connection metadata, and authorization credentials needed for integrations. The application encrypts tokens stored in its social-account records with AES-256-CBC. Other identity-provider credentials may be stored through the authentication adapter; do not assume every provider token uses the same storage protection.
- Technical information: authentication/session and temporary OAuth state cookies, plus service logs needed to operate and troubleshoot the application. This codebase does not include an advertising or analytics tracker.
2. How information is used
- To authenticate users and administer workspaces.
- To fetch feeds, execute workflows, create drafts, request approvals, and publish content when you configure and authorize those actions.
- To send the article text, your prompt, and related workflow context to the AI provider selected for a generation request.
- To maintain the service, troubleshoot errors, protect accounts, and enforce workspace settings.
Flowmatic does not sell personal information or use it for targeted advertising.
3. AI and connected providers
When you enable an AI integration, relevant article text, prompts, and workflow context are sent to the configured provider, which may include Google Gemini, OpenAI, or Anthropic. The provider processes that information under its own terms and privacy practices. Review the provider’s current terms before enabling it; Flowmatic does not control the provider’s retention or model-training practices.
When you connect an identity or social service, the application exchanges information with that provider to authenticate, retrieve account details, or carry out the action you requested. Depending on the configuration, integrations may include Google sign-in, Meta platforms, X, Buffer, LinkedIn, Bluesky, Mastodon, or messaging webhooks. The provider’s own policy applies to its handling of data.
Only connect accounts and enable workflow actions that you are authorized to use. Review generated or queued content before allowing a workflow to publish it.
4. Security
Password sign-in passwords are hashed with bcrypt. Social-account tokens stored in the application’s social-account records are encrypted using the configured `ENCRYPTION_KEY`. Access to data also depends on the security of the deployment, database, environment variables, and backups. HTTPS/TLS must be configured by the operator for hosted deployments; local development may use unencrypted localhost connections. No method of storage or transmission is completely secure.
5. Cookies
The application uses authentication/session cookies and short-lived OAuth state cookies when you sign in or connect an integration. Cookie names and security attributes can vary by authentication provider and deployment. This codebase does not add advertising or analytics cookies.
6. Retention and deletion
Account, workspace, workflow, RSS, content, and execution records are stored in the configured database. This codebase does not currently implement automatic 30-day or 90-day deletion for those records. Retention therefore depends on the service operator’s policies and database/backups configuration. For a hosted service, contact the operator to request access, correction, export, or deletion. For a self-hosted instance, contact its administrator.
Disconnecting an integration should be done through the application where available; deleting a connection does not necessarily remove data held by the external provider. Deletion from backups may take longer than deletion from the active database.
7. Children
Flowmatic is not designed for children under 13, and the service does not knowingly seek to collect their personal information.
8. Changes and contact
This policy may be updated as the application or its integrations change. For privacy questions about the hosted service, contact privacy@flowmatic.app. For a self-hosted instance, contact its operator.