FlowMeta
Legal

Privacy Policy

Last updated: 27 October 2026

1. Who we are and what this policy covers

This policy explains how Savaş Türkoğlu ("FlowMeta", "we", "us") handles personal data in the FlowMeta website, dashboard, MCP gateway, worker, management MCP and optional Telegram bot. For account, billing and website data we are the controller.

It does not cover a customer's own website or the MCP client you use. Those are governed by their own terms and privacy policies.

Postal address: Kalkan Mah. Nilüfer Sok 33/1 Kaş, Antalya, Türkiye. Privacy contact: privacy@use2mind.com.

2. Controller and processor roles

For your account, organisation, billing relationship and use of the FlowMeta website, we are the controller.

When we explore, call or run automations against a website you connect, we process the personal data in that site on your instructions. You are the controller of that data and FlowMeta is the processor. The Data Processing Agreement sets out those roles.

If you are an end customer of one of our customers, please contact that customer first. We will assist them with your request.

3. What we collect

Account and organisation data: your e-mail address, name, authentication identifiers, organisation name and slug, role, invitations and account settings. Authentication is handled through Supabase; we do not store your password in plain text.

Site data: the site's address, name, verification method and token, site kind (public or admin), login state, manifests, tools, tool descriptions, site events, onboarding reports and recordings. Tool-call logs include the tool name, status, duration, caller type and arguments with sensitive keys redacted.

Credentials: a site username, password and optional authenticator (TOTP) key are stored encrypted with AES-256-GCM. They are used only to sign in to that site. They are never shown to an MCP client.

Automation data: your request, the compiled spec, schedule, time zone, output formats, delivery channels, run results, report files, delivery status, and the Telegram chat identifier and username if you link a chat.

Billing data: plan, subscription status, period dates, Paddle customer and subscription identifiers, and cancellation reason. Paddle handles card data; we never receive your card number.

Technical data: server logs, IP address, user agent, error reports through Sentry, and product events through PostHog (for example signup, site created, onboarding finished, published, upgrade started). Product events do not include site content or credentials.

Support data: the messages you send to our support addresses and your e-mail address.

4. What we do not collect or do

We do not receive or store card numbers. Payment data is handled by Paddle as merchant of record.

We do not sell personal data, use it for advertising, or send it to advertising networks or data brokers.

We do not use your site content, credentials or reports to train AI models.

The marketing site does not use analytics, advertising or tracking cookies. The dashboard uses the cookies needed for sign-in and language; see the Cookie Policy.

5. Why we process it

We process personal data to perform our contract with you: create and secure your account, run the service, serve your MCP endpoints, execute automations and provide support.

We rely on legitimate interests to keep the service secure, prevent abuse, diagnose errors, enforce quotas and improve how the service works. We use aggregated, de-identified operational data for improvement where possible.

We process billing and tax records to comply with legal obligations.

Where we ask for consent, for example before you link a Telegram chat or before an optional feature processes data, you can withdraw it at any time. Withdrawing consent does not affect processing that already happened.

6. AI providers and your site data

FlowMeta uses AI providers to choose actions during onboarding and drift, to generate tool descriptions and to compile automation requests. The current providers are OpenAI, DeepSeek, and OpenRouter/TypeSafe Jev; heuristics are used as a fallback.

For onboarding, drift and tool healing, a decision provider may receive page structure and visible page text or state so it can choose the next action. Do not connect a site whose pages contain data you are not allowed to send to a processor.

For automations, the compile model receives your request, the site's tool names, descriptions and parameter schemas, and response shapes (keys and types), not the values in your site. A scheduled run executes the saved spec with code and does not send the rows to a model. A Telegram question is compiled the same way.

We instruct AI providers not to train their models on the data we send and to process it only to return a result to us. Where a provider is outside Türkiye or the EEA, we rely on Standard Contractual Clauses or another lawful transfer mechanism.

7. Who else is involved

We use a small number of processors to run the service. They are listed with their purpose, data and location on the Sub-processors page. They include Supabase for database, authentication and storage; Browserbase for browser sessions; Resend for e-mail; Sentry for errors; PostHog for product analytics; Paddle for billing; OpenAI, DeepSeek and OpenRouter/TypeSafe for AI processing; and Telegram if you link a chat.

Our application hosting provider runs the FlowMeta containers. Our DNS provider resolves our domains.

We may disclose data if the law requires it, and we will tell you where we are permitted to.

8. International transfers

Some of our providers process data outside Türkiye and the EEA, including in the United States, the United Kingdom and China (for DeepSeek). Where required, transfers are covered by the European Commission's Standard Contractual Clauses or another recognised mechanism, together with the corresponding safeguards under Turkish law.

You can ask us for more information about the transfer mechanism for a particular provider.

9. How long we keep it

Account and organisation data stays until you delete your account. Deleting an owner account disables the organisation's sites at once and permanently deletes the organisation and its data after 7 days. Backup copies expire according to the database provider's backup retention.

Raw tool-call logs are kept for 90 days and then aggregated into daily counts without arguments. Recordings are deleted after 30 days. Automation report files are kept for 7 days; preview rows for 24 hours; unsaved automation drafts for 7 days.

Site deletion is a soft delete first; browser contexts, recordings and the site's data are hard-deleted after 7 days.

Error reports in Sentry and server logs are kept for a limited operational period configured in those systems. Support correspondence is kept for up to 24 months. Billing and tax records are kept for the period required by law.

10. Security

Data is encrypted in transit with TLS and at rest by our infrastructure providers. Site credentials and authenticator keys use AES-256-GCM envelope encryption with a key held outside the database. API keys and OAuth tokens are stored as hashes.

Access to production systems is restricted. Sensitive keys stay on the server and never reach the browser or an MCP client. Tool-call arguments, logs and Sentry events are scrubbed for authorization, cookie, password, token and OTP keys.

Browser sessions run in isolated remote browsers; a compromised browser session does not expose the database or the master key.

No system is perfectly secure. If a breach affects your data and creates a risk to you, we will notify you and the relevant authority within the deadlines the law sets.

11. Your rights

You can ask us for a copy of your data, correct it, delete it, restrict or object to processing, or receive it in a portable format. Under the GDPR these are Articles 15 to 22; under the KVKK they are Article 11.

You can delete individual sites, automations or your account in the dashboard. The Delete account and data page explains the steps and what remains.

Write to privacy@use2mind.com. We answer within one month under the GDPR and within 30 days under the KVKK. We may ask for enough information to confirm that the account is yours, but never for your password.

If you are not satisfied, you can complain to your national supervisory authority. In Türkiye that is the Personal Data Protection Authority (KVKK); in the EU it is the authority in your country of residence.

12. Cookies and the marketing site

The marketing site uses a language cookie and the dashboard uses authentication cookies. We do not use advertising or analytics cookies. See the Cookie Policy for details.

13. Children

FlowMeta is a business service and is not directed at children under 18. We do not knowingly collect their data. If you believe a child has created an account, write to privacy@use2mind.com and we will delete it.

14. Changes and contact

If we change this policy in a way that materially affects you, we will announce it in the dashboard or by e-mail before it takes effect. The date at the top of this page reflects the current version.

Privacy questions and requests: privacy@use2mind.com. Everything else: hello@use2mind.com. Postal address: Savaş Türkoğlu, Kalkan Mah. Nilüfer Sok 33/1 Kaş, Antalya, Türkiye.

Contact

Questions about this document? Write to us.

hello@use2mind.comprivacy@use2mind.comsupport@use2mind.com

Savaş Türkoğlu · Kalkan Mah. Nilüfer Sok 33/1 Kaş, Antalya, Türkiye

This document describes how FlowMeta operates today. It is not legal advice.