This English version is a translation for your convenience. Only the German version is legally binding. Read the German version
This privacy policy applies to flowconnect.one and mcp.flowconnect.one. It explains which personal data is processed when you visit the website, sign in, manage your account, your team and your billing, connect third party services or use developer keys and MCP, under the EU General Data Protection Regulation (GDPR) and the Brazilian General Data Protection Law (Lei Geral de Proteção de Dados, LGPD, Law No. 13,709/2018).
Last updated: 20 November 2026
1. Controller
The controller within the meaning of the GDPR and the controller (controlador) within the meaning of the LGPD is:
Creative Skyline Ltda.
Postal address:
Winterhuder Weg 29
7. Stock (7th floor)
22085 Hamburg
Germany
Registered office:
Avenida Washington Soares, 55
Sala 516 - Iguatemi Empresarial
Edson Queiroz
60811-341 Fortaleza - CE
Brazil
Authorised representative: Sascha Neumann
Email: contact@creativeskyline.com
Phone: +49 40 729 158 91
Legal notice: https://flowconnect.one/impressum
2. Data protection officer and contact for privacy requests
We have not appointed a data protection officer. Creative Skyline Ltda. is itself responsible for data protection as the controller.
For questions about data protection and to exercise your rights, contact the controller directly: by email to contact@creativeskyline.com or by post to the postal address above. No encarregado has been designated under the LGPD either; the controller's contact details serve as the communication channel for data subjects.
3. What this policy covers
FlowConnect is the central account for the products of Creative Skyline. This policy only describes what happens on flowconnect.one and mcp.flowconnect.one: the public website, registration and sign-in, account and security, teams, the billing pages, connections to Google and Microsoft, developer keys, MCP and OAuth, and the help area.
The products themselves, for example FlowCRM or FlowAI, run on other hosts. AI providers used there are also a matter for those products. For these, the privacy policy of Creative Skyline applies.
On flowconnect.one there is no contact form, no newsletter, no chat, no embedded video and no review or affiliate widget. We serve fonts from our own server. Apps only access your account as OAuth clients. You do not book plans here but on the page of the product concerned; in FlowConnect you only manage payment profiles and invoices.
4. Hosting, server log files and monitoring
flowconnect.one and mcp.flowconnect.one run on servers of our infrastructure provider Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Hetzner processes the data on our behalf.
We provide you with a data processing agreement (DPA) under Art. 28 GDPR on request.
Whenever you open a page, your browser sends data to the server for technical reasons. The server stores in log files the IP address of the requesting device, the date and time, the requested address, the identifier of your browser (user agent) and the previously visited page (referrer), if your browser sends it.
Purpose: to deliver the page, to keep it secure and stable, for example to fend off attacks and overload, and to find errors.
Legal basis: Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is secure and stable operation.
Retention: Log files are kept for no more than 30 days and then deleted or anonymised. Data we need as evidence to investigate a specific incident is deleted only once the incident has been fully resolved.
Monitoring with Laravel Nightwatch
To detect errors and performance problems we use Laravel Nightwatch, a service of Laravel Holdings Inc., 60 Broad Street, 24th Floor, #1559, New York, NY 10004, USA. Nightwatch receives technical events from operations: page requests (address, IP address, status and duration), for signed-in persons the user ID, the name and the email address, error messages with their trace, database queries without the bound parameters, outgoing requests to other services, background jobs, scheduled tasks and commands, cache events, and emails and notifications sent (subject and number of recipients, not their addresses) as well as log entries.
Purpose and legal basis: to find and fix errors and outages (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). In its default setting Laravel keeps this data for up to 90 days. For the transfer to the USA see section 17.
5. Cookies and similar storage
flowconnect.one sets technically necessary cookies and, only with your consent, the cookies of Google Analytics (category “Statistics”, section 6).
| Name | Purpose | Lifetime | When |
|---|---|---|---|
| Session cookie | keeps you signed in and protects forms (HttpOnly, SameSite=Lax, host-only) | 24 hours without activity | as soon as you use the site |
XSRF-TOKEN |
protects forms against forgery | same as the session | as soon as you use the site |
remember_web_* |
“Stay signed in” | 400 days | only if you choose it |
fc_cookie_consent |
stores your cookie choice and a random consent ID | 1 year | after your choice in the notice |
fc_td |
trusted device for two-factor sign-in (section 7) | 30 days | only if you trust the device |
__stripe_mid |
Stripe: fraud prevention for payments | 1 year | only in the payment area |
__stripe_sid |
Stripe: fraud prevention for payments | 30 minutes | only in the payment area |
_ga, _ga_* |
Google Analytics, section 6 | 2 years | only after consent to “Statistics” |
In your browser's local storage we only store your chosen colour scheme (light or dark).
Legal basis of the necessary cookies: Storing and reading them is strictly necessary to provide the function you asked for (§ 25(2) no. 2 TDDDG, the German Telecommunications Digital Services Data Protection Act). No consent is required for this. We base the related processing on Art. 6(1)(b) and (f) GDPR and Art. 7 V and IX LGPD.
Cookie notice: On the public pages (for example the start page, sign-in, registration, legal texts) we ask for your consent with our own notice, without an external service provider. You choose “Accept all”, “Necessary only” or, under “Settings”, each category individually; apart from “Necessary”, nothing is preselected. Before your consent, no request for analytics purposes goes to Google. Cloudflare Turnstile runs on sign-in and registration as protection even without consent (section 7). In the signed-in area no notice appears and we load no analytics tool.
Record of your decision: When you make a choice, fc_cookie_consent stores a random ID and we record the decision on our server: this ID, the time, the kind of decision (consent, change, withdrawal or necessary cookies only), the choice per category, the version of the notice and of this privacy policy, the domain, the language, the identifier of your account if you are signed in, your shortened IP address (for IPv4 the last byte, for IPv6 everything after the first 48 bits is set to zero) and your browser identifier (user agent, shortened). We do not store the full IP address or the page visited. The purpose is to be able to prove that and to what extent you consented. The record can only be viewed by administrators and is not used for analytics or advertising. The legal basis is our legal obligation to provide this proof (Art. 6(1)(c) in conjunction with Art. 7(1) GDPR; Art. 7 II in conjunction with Art. 8 § 2 LGPD). The entries remain after your account is deleted and are deleted after three years.
Changing and withdrawing: You can change or withdraw your choice at any time with “Cookie settings” in the footer of the public pages. If you are signed in, you will find the link on this page, for example. On withdrawal we delete the cookies _ga and _ga_*. You can also delete or block cookies in your browser at any time; without the necessary cookies, however, signing in does not work.
6. Google Tag Manager and Google Analytics
Only if you consent to “Statistics” in the cookie notice do we load Google Tag Manager on the public pages and, through it, Google Analytics 4. Before that, no script from Google is loaded and no connection to Google is made. In the signed-in area, on the password reset pages and on other pages with a token in the address we never load Google Tag Manager.
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
Purpose: We use Google Tag Manager to manage the measurement on the public pages; it sets no cookies itself. Google Analytics measures how the pages are used, for example which pages and sections are viewed, how long a visit lasts and which website you came from, and records technical details of your device and browser. From this we receive aggregated reports that help us improve FlowConnect. Google Analytics does not store IP addresses of users in the EU; only the approximate location (country, region, city) is derived from the IP address.
Google Consent Mode: We first set every storage purpose to “denied” and, after your consent, grant analytics storage only. Advertising storage and personalised advertising stay denied.
Cookies: _ga (2 years) tells visitors apart by a random ID, _ga_* (2 years) keeps the state of the visit.
Retention of analytics data: Independently of the cookie lifetime, Google Analytics keeps event-level data (individual page views and interactions) for 2 months. This is the default setting of Google Analytics 4, which we have not changed; after that, Google deletes this data. Aggregated reports are not affected.
Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG, Art. 7 I LGPD).
Withdrawal: You can withdraw your consent at any time with effect for the future via “Cookie settings” in the footer of the public pages. We then delete the cookies _ga and _ga_* and no longer load Google Tag Manager from the next page view on.
Transfer to the USA: Data may be transferred to Google LLC in the USA (section 17). Under the LGPD this is based on your specific consent (Art. 33 VIII LGPD).
More information: Google's privacy policy, how Google uses data on its partners' websites.
7. FlowConnect: central account and sign-in
Registration and account
For an account we need your name, your email address and a password, which we store only as a hash. In the account you can also set a profile picture, your language, your time zone and notifications.
You confirm the email address by link or with a six-digit code (valid for 60 minutes). Under “Account” you can manage your password, two-factor authentication and sessions and delete your account yourself.
Purpose and legal basis: to provide the account and perform the contract (Art. 6(1)(b) GDPR, Art. 7 V LGPD).
Sign-in ticket and hand-over to the products
Signing in takes place on flowconnect.one. If you open a product on its own domain, FlowConnect issues a one-time sign-in ticket, valid for no more than 60 seconds and only for the target domain. We store only a hash of it, as well as the target domain, the times, the IP address and browser identifier at issue and the IP address at redemption. The entries serve to protect against misuse and are deleted after 7 days. If you open /login as a person who is not signed in, we briefly redirect you once to creativeskyline.de and back to detect a sign-in that still exists there.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD. Our legitimate interest is secure sign-in across several domains and the continuity of existing sessions.
Sessions per domain
Each domain keeps its own session with its own session cookie that applies only to that domain (host-only, so not readable by subdomains or other domains). For each session we store the domain, the IP address, the browser identifier, the last activity and an identifier that links the sessions of one browser across the domains. This lets you see under “Sessions” where you are signed in and sign out everywhere. Sessions expire after 24 hours without activity unless you choose “Stay signed in”.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
Two-factor sign-in and trusted devices (cookie fc_td)
If you use two-factor authentication, we store the secret and the recovery codes in encrypted form. If you choose “Trust this device for 30 days”, we set the encrypted cookie fc_td (host-only, HTTPS only, not readable by JavaScript). For this we store a hash, a device label, the IP address, the browser identifier, the last use and the expiry date. The trust ends after 30 days, when you remove the device in the account settings, when you change your password, when you switch two-factor authentication on or off, when you sign out on all devices and when you generate new recovery codes.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
Sign in with Google
You can sign in or register with your Google account. We request only openid, email and profile from Google and receive the Google identifier, the email address, whether Google has verified it, and the name. If the email address is verified and belongs to an existing account, we link the two. We store the Google identifier, the email address and the time of last use, but no token. This gives us no access to calendar, emails or files; the separate connections exist for that (section 10). If you connect a Google account with a verified email address there, we additionally link it automatically as a sign-in method, unless it already belongs to another account. We inform you about this by email and record the link in the security log. If two-factor authentication is active, it is also requested here.
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
Protection of sign-in and registration (Cloudflare Turnstile)
On sign-in and registration we use Cloudflare Turnstile to tell people from automated programs. The script is loaded from challenges.cloudflare.com even before a cookie decision, because without protection the form stays open to attacks. It evaluates technical signals in the browser and sends them to Cloudflare. These can include the IP address, details of the operating system, device and browser, language settings and the interaction with the page. We check the result (a one-time token) on the server together with your IP address at Cloudflare. We do not use Turnstile for password reset.
If Cloudflare cannot be reached, the form stays usable and is protected by a limit on attempts, a hidden check field and a time check. At registration we also check whether a name looks nonsensical and whether the address comes from a disposable-email provider. We record failed sign-ins, rejections by the check and outages with the time and IP address.
Provider: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA (privacy policy, Turnstile notes). Legal basis: Art. 6(1)(f) GDPR, Art. 7 IX LGPD. Our legitimate interest is protecting the account and the service against misuse and automated attacks.
Sign-in log, place of sign-in and security events
For each sign-in we record the time, the result, the IP address, the browser identifier and the approximate place (for example city and country). We determine the place locally on our own server using the GeoLite database, without sending the IP address to a third party. This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com, which incorporates geographical data from GeoNames (CC BY 4.0).
We also record the outcome of sign-ins and security checks as security events (type, account, IP address, host, time and technical details of the incident). We delete the sign-in log and the security events after 12 months.
We also copy the approximate place of a successful sign-in as the location into your FlowAI profile, unless you have set and locked this location there yourself. FlowAI runs on another host; see section 3.
Purpose and legal basis: to detect suspicious sign-ins, show you your sessions and protect the account (Art. 6(1)(f) GDPR, Art. 7 IX LGPD).
8. Teams, invitations and verified domains
For each team we store members, roles and product permissions. We record invitations, joins, changed permissions and removed members with the time and the acting person in the team protocol, which the team's managers can view. The team protocol stays for as long as the team exists.
If someone invites you to a team or you ask to join, we process your email address and your name for this, even if you do not yet have an account. We send the invitation by email on behalf of the person inviting you.
If someone joins another team, we dissolve their previous own team if it is empty. If it contains data or subscriptions it becomes dormant: the data remains, subscriptions end at the end of the paid period, and credit stays with the dormant team. We inform those concerned about dormant teams by email.
Verified domains
A team can confirm an email domain as its own. For proof via DNS we look up the TXT record flowconnect-verify=… of the domain through the Domain Name System, when the check starts and then daily for as long as the domain is verified. If the record is missing, the verification continues for 14 more days. For proof by email we send a confirmation link to admin@ or postmaster@ of the domain, never to another address; the link is valid for 72 hours, the confirmation for 12 months. For this we process this address, the time of sending and the time of confirmation. The confirmation page /domain-bestaetigen/{token} can be reached without signing in; recipients of this email can therefore be people outside the team.
If someone registers with an address of the verified domain, that person becomes a member of the team after confirming their email address. The managers receive an information email with name and email address. Existing users with an address of the domain receive an offer to join at their next sign-in. Verifications, joins and changes are recorded in the team protocol.
Purpose and legal basis: to manage teams and control access (Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD). Our legitimate interest is that teams can trace who has access.
9. Billing and payment profiles
On the billing pages you manage payment profiles and retrieve invoices, also as PDF and also from our former billing system. Plans are not booked here. For this we process the billing address, invoice data and payment history.
You set up cards and SEPA direct debit through Stripe. You enter the full card or account details directly with Stripe; they do not reach us. We receive and store the card brand and the last four digits with the expiry date, or the last four characters of the IBAN, as well as the identifier of the payment method. On the payment pages Stripe loads its script and sets the cookies __stripe_mid and __stripe_sid.
Provider: Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02FX04, Ireland (privacy policy). Processing by Stripe, Inc. in the USA is possible (section 17).
Purpose and legal basis: to process payments and provide invoices (Art. 6(1)(b) GDPR, Art. 7 V LGPD) and to meet statutory retention duties (Art. 6(1)(c) GDPR, Art. 7 II LGPD).
10. Connections to Google, Microsoft and other services
In the “App catalog” you can connect accounts at Google and Microsoft, also several per provider. For this we redirect you to the provider, where you grant access yourself. We store the access tokens in encrypted form, the connected account (email address), the permissions you actually granted at the provider and the times of connection and last use. You connect Fireflies, Omi and the other services with an API key or other credentials (see below).
When connecting, you choose the services: Gmail (permission gmail.modify or, depending on the package, gmail.readonly), Drive (drive), Google Calendar (calendar) and Contacts (contacts), always with the name and email address of the Google account (userinfo.profile, userinfo.email) and offline access, so that we can update without you being present. For FlowSEO, webmasters.readonly and analytics.readonly are added at your request.
Synchronisation: After connecting, syncs of Gmail, Drive, Calendar and Contacts start if you are allowed to use the related product, and then continue automatically (Gmail, Drive and Calendar every 6 hours, Contacts daily). The data is stored on our servers. How the products use it is governed by the privacy policy of Creative Skyline.
Scope of access: For every connected service, reading, writing and deleting are allowed, for FlowAI as well as for MCP clients. You determine the scope through the services you select when connecting. If you no longer need a service, you disconnect the connection.
Google Limited Use: We use data from your connected Google accounts (Gmail, Drive, Calendar, Contacts) only for the functions you choose yourself. We do not sell it, do not use it for advertising and do not use it to train general AI models. We adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (privacy policy).
Microsoft
There is no sign-in with Microsoft. You can, however, connect one or more Microsoft accounts (Microsoft 365 or Outlook.com) and select Outlook Mail (Mail.ReadWrite, Mail.Send), Outlook Calendar (Calendars.ReadWrite) and OneDrive (Files.ReadWrite), always with User.Read and offline_access. Microsoft is the provider of the service you use and the source of the data; we retrieve it via the Microsoft Graph interface. After connecting we sync the data; it is stored on our servers. Via MCP, authorised applications can read, create, change, send and delete emails, events and files (section 11).
Provider: Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland (privacy statement).
Fireflies and Omi
You connect Fireflies (meeting recordings with summaries, action items, participants and transcripts) and Omi (conversations and memories of your Omi device) with an API key that you create at the provider. We store the key in encrypted form and create a webhook address with a secret token through which the provider reports new data to us. We store the retrieved data on our servers. It is used in FlowBrain and, read-only, by authorised applications via MCP. For Omi you can additionally switch on real-time audio; your Omi device then sends audio to a separate address.
Providers: Fireflies.ai, 5424 Sunol Blvd, Ste 10-531, Pleasanton, CA 94566, USA (privacy policy); Omi: Based Hardware, Inc., USA.
Other services connected with credentials
You connect the following services with credentials that you create at the provider, for example an API key, a token, a client ID with secret or an app-specific password. You can also connect several accounts of these services.
- ElevenLabs (text to speech and speech to text): texts you have spoken and audio files you have transcribed are sent to ElevenLabs.
- MeetGeek (meeting notes): we sync meetings, summaries, transcripts and highlights and store them on our servers. MeetGeek reports new data through a webhook address with a secret token. On your instruction, recordings can also be uploaded, a recording bot can be sent to a meeting or meetings can be deleted.
- Apify (web scrapers and automations): on your instruction we start actors in your Apify account. The inputs are sent to Apify, and we retrieve the results.
- 1Password (credentials): we only connect to the Connect server you run yourself, using its address and token. On your instruction, authorised applications read items including passwords and other secret fields, create items, change or delete them. Every retrieval of an item is logged (see below). Through an MCP key, 1Password can only be reached if you explicitly select it for that key.
- iCloud Mail, Calendar and Contacts: with your Apple ID and an app-specific password we access your emails via IMAP and SMTP and your calendars and contacts via CalDAV and CardDAV. On your instruction, emails are read, sent, moved and deleted, and events and contacts are created, changed and deleted.
- sevDesk and Lexware Office (accounting): vouchers, invoices, contacts and bank transactions are read and, on your instruction, created, sent or finalised. Lexware Office notifies us through a webhook address when a key has been revoked. From the creation date of the key that you enter we calculate its expiry and remind you by email beforehand.
- Personio (HR): employee data including salaries and documents is read and, on your instruction, absences, attendances and employees are created or changed. If you wish, you can hide absence reasons and salary amounts. Every call is logged (see below).
- HeyGen (AI videos): on your instruction, scripts and text prompts, images, avatars and other media as well as videos to be translated are sent to HeyGen. HeyGen creates videos from them in your HeyGen account; we retrieve their status and download links. Billing runs through your own HeyGen account. So that you can see the balance, the spending cap and the permissions of your API key on the app page, we retrieve these details from HeyGen and cache them for up to 10 minutes. If you share the connection with your team, team members can only start paid jobs once you allow this on the app page.
We store the credentials in encrypted form, together with the settings you choose on the app's page and the account the provider names when the credentials are checked. The content stays with the provider. We only retrieve it when an application you authorised calls a tool via MCP. The exception is MeetGeek: we sync and store its meeting data as with Fireflies. Once a day we check with a read-only call whether the credentials are still valid. If the provider rejects them, we mark the connection with “Reconnect”.
Providers: ElevenLabs Inc., USA; MeetGeek; Apify Technologies s.r.o., Czech Republic; Apple Distribution International Ltd., Ireland (iCloud); sevDesk GmbH, Germany; Haufe-Lexware GmbH & Co. KG, Germany (Lexware Office); Personio SE & Co. KG, Germany; HeyGen, Inc., USA. With 1Password, AgileBits Inc. (1Password) receives no data through us, because we only talk to your own Connect server. Processing at the providers is subject to their terms and privacy policies.
Legal basis: the function you set up yourself (Art. 6(1)(b) GDPR, Art. 7 V LGPD). For data of third parties in these accounts, such as contacts, senders of emails, business partners in accounting or employees in Personio, our and your legitimate interest (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). If you connect Personio or an accounting service, please check whether you may use this data in this way in your company.
Access log, temporary files and failure log
Access log: for 1Password we log every retrieval of an item, for Personio every call. We store who carried out which action through which connection and when, the provider's identifier of the item and the names of the fields concerned, never their content. You can see the log on the app's page. We delete the entries after 12 months.
Temporary files: files that a tool creates (for example audio from ElevenLabs or exports from Apify) and files you upload for speech to text are stored on our servers for 24 hours and deleted automatically afterwards. They can be retrieved through a signed link. Anyone who knows this link can open the file within those 24 hours without signing in. Therefore only pass it on if that is acceptable for the file.
Failure log: if a call to a connected service fails, for example when connecting, in the daily check, during a sync, on a webhook or in a tool, we store the app, the operation, the type of error, the HTTP status and the provider's error code, together with the connection, the team and the user concerned. We do not store content, credentials or the provider's message texts. In case of disruptions the log notifies us by email. We delete the entries after 90 days.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD. Our legitimate interest is the traceability of access to sensitive data and the reliable operation of the connections.
Sharing with your team
You can share a connection with your team or connect it for the team right away. Members of your team can then use the account through their own MCP keys or OAuth connections, with full access, that is reading, writing and deleting, for example sending emails or changing events. We store who shared the connection and when, and who used it last, and we log every use by another team member. FlowAI and FlowBrain do not use shared connections for other people. The share ends when you withdraw it, disconnect the connection or leave the team; managers of your team can withdraw it as well. Only share accounts whose content the members of your team may see.
Legal basis: the function you set up yourself (Art. 6(1)(b) GDPR, Art. 7 V LGPD). For data of third parties in a shared account, such as senders of emails or participants of events, our and your legitimate interest in working together as a team (Art. 6(1)(f) GDPR, Art. 7 IX LGPD).
Disconnecting
You can disconnect a connection at any time in the “App catalog” or revoke it at the provider. When you disconnect, we delete the access tokens, the API key or the credentials, stop the syncs and withdraw a team share.
Legal basis: the function you set up yourself (Art. 6(1)(b) GDPR, Art. 7 V LGPD), and your consent at the provider, which you can end at any time by disconnecting or revoking (Art. 6(1)(a) GDPR, Art. 7 I LGPD).
11. Developer keys, MCP and OAuth
API and MCP keys: For a key we store a hash for checking and an encrypted copy so that you can display it again later. Also the name, permissions, creation and last use. Only the person who created the key can see the value; managers and our administrators see the name, permissions and usage data, but never the value. For each call we store the IP address, browser identifier, endpoint, query parameters and response status; the content of requests only if you switch this on. We delete this usage data after 30 days.
MCP and OAuth: On mcp.flowconnect.one, applications you authorise, for example AI assistants such as Claude or ChatGPT, can access your account via an MCP key or OAuth. For the Google and Microsoft services there are tools for reading, writing and deleting, also for sending emails, for Fireflies and Omi tools for reading and for the other services connected with credentials tools to the extent described above. These tools only delete, send or finalise once the application explicitly confirms it. Reachable are your own connections and those that members of your team shared with the team (section 10). You receive an email for each new OAuth connection. We store the registered applications, the authorisations and tokens: authorisation codes are deleted one day after they expire, refresh tokens are valid for 30 days, applications never used are removed after 24 hours and unused ones after 90 days.
The providers of these applications are separate recipients: They receive the data on your instruction, and their terms and privacy policies apply to their further processing. Depending on the key, data of other products can also be reachable via MCP; see section 3.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD. Our legitimate interest is securing the interfaces and detecting misuse.
12. Help area
The help area at /hilfe shows articles about account and team. We store search queries without any link to you, only with the search term, language, number of results and time, to spot missing articles (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). Please do not enter personal details in the search.
13. Emails from FlowConnect
From noreply@flowconnect.one we send emails about confirming the address, resetting the password, a changed password, two-factor authentication being switched on or off, signing out on all devices, a linked Google account, a new MCP OAuth connection, team invitations, access, join requests, dormant teams and domain confirmations. Recipients can also be third parties, for example invited people or the postmasters of a domain. Security emails cannot be unsubscribed from because they serve to protect the account.
Sending runs through SMTP2GO, a service of Sand Dune Mail Ltd, 96-106 Manchester Street, Christchurch 8011, New Zealand (privacy policy). Recipient and sender address, content and delivery data are processed.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD. Our legitimate interest is securing the accounts and reliable delivery.
14. Access by our team
In the administration area, authorised staff of Creative Skyline can see users, teams, security logs and keys (without their value) and can, for example, disconnect connections or revoke keys. We use this for support, security and operations and only as far as necessary for that (Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD).
15. Recipients at a glance
- Hetzner Online GmbH (hosting)
- Laravel Holdings Inc. (monitoring)
- Sand Dune Mail Ltd, SMTP2GO (sending email)
- Cloudflare, Inc. (Turnstile)
- Stripe Payments Europe, Limited (payments)
- Google Ireland Limited (Sign in with Google, connections, Analytics after consent)
- Microsoft Ireland Operations Limited (connections)
- Fireflies.ai and Based Hardware, Inc. (Omi), if you connect them
- ElevenLabs, MeetGeek, Apify, Apple (iCloud), sevDesk, Lexware Office, Personio, HeyGen and the 1Password Connect server you run, if you connect them
- Members of your team with whom you share a connection
- Providers of applications you authorise, for example AI assistants via MCP, on your instruction
- Managers of your team to the extent described above
- Authorities and courts where we are legally obliged
16. Retention at a glance
| Data | Period |
|---|---|
| Server log files | no more than 30 days |
| Operational data in Nightwatch | up to 90 days (default setting) |
| Sign-in tickets | valid for 60 seconds, deleted after 7 days |
| Sessions | expire after 24 hours without activity or on sign-out |
| Trusted devices | 30 days or until removed |
| Sign-in log and security events | 12 months |
| API and MCP call data | 30 days |
| Credentials of connected services | until the connection is disconnected |
| Access log (1Password, Personio) | 12 months |
| Failure log of the connections | 90 days |
| Temporary files of the tools | 24 hours |
| Confirmation codes by email | 60 minutes |
| Confirmation link for domains | 72 hours, confirmation 12 months |
| Consent record | 3 years, also after the account is deleted |
| Team protocol | as long as the team exists |
| Account and team data | until the account or team is deleted |
| Invoices and accounting vouchers | 8 years (§ 147 AO, § 257 HGB) |
| Books and records | 10 years (§ 147 AO, § 257 HGB) |
If you delete your account, we delete the related data, unless a statutory retention duty applies. Data belonging to a team that continues to exist stays with the team.
17. Transfers to third countries
Brazil
Our servers are located in Germany at Hetzner Online GmbH, where the data is stored and processed. Creative Skyline Ltda. is a company under Brazilian law with its registered office in Fortaleza. If we access data from Brazil for operations and support, this is a transfer to a third country. On 26 January 2026, the EU Commission adopted an adequacy decision for Brazil under Art. 45 GDPR. The transfer is therefore permitted without additional safeguards. In Brazil, the LGPD additionally protects the data.
USA
With Google, Cloudflare, Stripe and Microsoft, data may be transferred to the USA. Google LLC is certified under the EU-US Data Privacy Framework. Cloudflare, Inc., Stripe, LLC and Microsoft Corporation state in their privacy notices that they comply with the EU-US Data Privacy Framework. These transfers are based on the adequacy decision of the European Commission of 10 July 2023 (Art. 45 GDPR).
Fireflies.ai and Based Hardware, Inc. (Omi) have their registered offices in the USA. If you connect them, we retrieve data there that you stored with them and transmit your API key for this. You set up the connection yourself and can disconnect it at any time.
ElevenLabs Inc. has its registered office in the USA. If you connect ElevenLabs, we transmit the texts and audio files you have processed and your API key there. With MeetGeek and Apify, data may be processed outside the EU, depending on the provider and the storage location of your account; MeetGeek offers an EU and a US region. Apple may transfer iCloud data to Apple Inc. in the USA. The safeguards these providers rely on are set out in their privacy policies. You set up the connection yourself and can disconnect it at any time.
HeyGen, Inc. has its registered office in the USA. If you connect HeyGen, we transmit there, on your instruction, the scripts and text prompts, images, avatars and other media and the videos to be translated that you have processed, and your API key. HeyGen states in its privacy policy that it is certified under the EU-US Data Privacy Framework and additionally names standard contractual clauses for certain transfers. You set up the connection yourself and can disconnect it at any time.
Laravel Holdings Inc. has its registered office in the USA and, according to its own statements, bases cross-border transfers on contractual protections; Nightwatch offers storage locations in the USA, the EU and Australia.
New Zealand
SMTP2GO is operated from New Zealand, for which an adequacy decision of the EU Commission exists (Decision 2013/65/EU). According to its own statements, SMTP2GO stores personal data of users in the EEA within the EEA.
Under the LGPD
Under the LGPD we base international transfers on Art. 33 LGPD, depending on the case on the need to perform the contract (Art. 33 IX in conjunction with Art. 7 V LGPD) or on your consent (Art. 33 VIII LGPD).
18. Obligation to provide data
Name, email address and password are required for an account; without them we cannot set one up. For invoices we need the billing details, for payments a payment method. Everything else, such as a profile picture, connections, keys or consent to “Statistics”, is voluntary. There is no statutory obligation to provide data to us.
19. No automated decisions
No automated decision within the meaning of Art. 22 GDPR that produces legal effects for you or similarly significantly affects you takes place on flowconnect.one (nor within the meaning of Art. 20 LGPD). Protection checks such as Turnstile, the limit on attempts or the check for disposable addresses can reject a single entry. If this stops you from getting further, write to us and we will check it by hand.
20. Your rights
Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You may object at any time, on grounds relating to your particular situation, to processing based on Art. 6(1)(f) GDPR (Art. 21). You can withdraw a consent at any time with effect for the future (Art. 7(3) GDPR): the statistics consent via “Cookie settings” in the footer of the public pages, a connection by disconnecting it in the “App catalog”.
Under the LGPD (Art. 18) you as the data subject (titular) have in particular the right to confirmation that data is processed, to access the data, to correction, to anonymisation, blocking or deletion of unnecessary, excessive or unlawfully processed data, to data portability, to information about the entities the data is shared with, and to object.
To exercise your rights, an email to contact@creativeskyline.com is enough. You can also change or delete much of the data yourself under “Account”.
21. Right to lodge a complaint
You have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement (Art. 77 GDPR). Under the LGPD you can turn to the Brazilian data protection authority, the Autoridade Nacional de Proteção de Dados (ANPD).
22. Changes
We update this privacy policy when FlowConnect or the legal situation changes. The version published here applies.