This is a translation for your convenience. The German version is binding and prevails in the event of any discrepancy.
This privacy policy applies to FlowData on flowdata.one, including the application at flowdata.one/dashboard, the programming interface at https://api.flowdata.one/v1 and MCP access at https://mcp.flowconnect.one/flowdata. It explains which personal data is processed when you visit the website, send an inquiry or use FlowData, under the General Data Protection Regulation (GDPR) and the Brazilian data protection law (Lei Geral de Proteção de Dados, LGPD, Law No. 13.709/2018).
FlowData is a service of Creative Skyline.
Last updated: 16 November 2026
1. Controller
The controller under the GDPR and the controlador under the LGPD is:
Creative Skyline Ltda.
Postal address:
Winterhuder Weg 29
7th floor
22085 Hamburg
Germany
Registered office:
Avenida Washington Soares, 55
Sala 516 - Iguatemi Empresarial
Edson Queiroz
60811-341 Fortaleza - CE
Brazil
Authorized representative: Sascha Neumann
Email: contact@creativeskyline.com
Phone: +49 40 729 158 91
Legal notice: https://flowdata.one/en/legal-notice
2. Data protection officer and privacy contact
We have not appointed a data protection officer. Creative Skyline Ltda., as controller, is itself responsible for data protection. No encarregado has been appointed under the LGPD either; the controller's contact details serve as the communication channel for data subjects.
For privacy questions and to exercise your rights, write to contact@creativeskyline.com or to the postal address above.
3. What this policy covers
This policy describes what happens on flowdata.one and api.flowdata.one: the public website with the documentation at flowdata.one/docs, the inquiry form, the application with its Playground, the data areas of the interface (IP geolocation, Client Info, Maps, email verification, YouTube), media processing, payment and access through MCP. It also applies to the older addresses of the same interface at creativeskyline.de/api.
Sign-in, account, team, security and connections are handled by FlowConnect. The FlowConnect privacy policy applies to them. Other Creative Skyline products have their own privacy notices.
Sections 10 to 16 describe the data you send us through the interface. This is often data about other people, such as email addresses, IP addresses or postal addresses.
4. Hosting, server log files and monitoring
flowdata.one, api.flowdata.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. Not all processing stays on these servers: the services named in sections 13 to 15 and 17 receive the data described there, and the servers are also accessed from Brazil (section 25).
Each time you visit, your browser or application transmits data to the server for technical reasons. The server stores in log files the IP address of the requesting device, date and time, the address requested, your browser or application identifier (user agent) and the previously visited page (referrer), if it is sent. For calls to the interface, the address requested may contain a verified email address, a queried IP address or a search term.
Purpose and legal basis: to deliver the page and the interface, ensure their secure and stable operation and find errors (Art. 6(1)(f) GDPR, Art. 7 IX LGPD).
Retention: Log files are kept for at most 30 days and then deleted or anonymized. Data we need as evidence to investigate a specific incident is deleted only once the incident has been finally resolved.
Operational 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 operating events: page requests and calls to the interface (address, IP address, status and duration), for signed-in persons the user ID, name and email address, error messages with stack traces, database queries without their parameters, outgoing requests to other services, background jobs, emails sent (subject and number of recipients, not their addresses) and log entries. Here too, the address of a call may contain a verified email address or a queried IP address.
Purpose and legal basis: to find and fix errors and outages (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). By default, Laravel keeps this data for up to 90 days.
5. Cookies and similar storage
The cookie notice on flowdata.one has two categories: "Necessary" and "Statistics". Statistics cookies are set only with your consent.
| Name | Purpose | Lifetime | When |
|---|---|---|---|
| Session cookie | keeps your session and protects forms | limited, ends without activity | as soon as you use the page |
XSRF-TOKEN |
protects forms against forgery | same as the session | as soon as you use the page |
fd_cookie_consent |
stores your cookie choice and a random consent ID | 1 year | after your choice in the notice |
remember_web_* |
"Remember me" | 400 days | only if you choose it |
fc_td |
trusted device for two-factor sign-in | 30 days | only if you trust the device at sign-in |
__stripe_mid, __stripe_sid |
Stripe: fraud prevention for payments | 1 year, 30 minutes | only on the payment page |
_ga, _ga_* |
Google Analytics, section 6 | 2 years | only after consent to "Statistics" |
Your chosen color scheme (light or dark) may be stored in your browser's local storage. While the tab stays open, the Playground uses session storage to remember that you confirmed paid calls. No API key is kept there.
Legal basis for necessary cookies: Storing and reading them is strictly necessary to provide the function you request (Section 25(2) No. 2 TDDDG). 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 we ask for your consent with our own notice, without an external provider. Nothing except "Necessary" is preselected.
Record of your decision: When you make a choice, we log on our server the random ID, the time, the type of decision, the choice per category, the version of the notice and of this policy, the domain, the language, your account ID if you are signed in, your truncated IP address and your truncated browser identifier. The purpose is to prove your consent (Art. 6(1)(c) in conjunction with Art. 7(1) GDPR; Art. 7 II in conjunction with Art. 8 § 2 LGPD). The entries are deleted after three years.
Change and withdraw: Via "Cookie settings" in the footer you can change or withdraw your choice at any time. On withdrawal we delete the _ga and _ga_* cookies.
6. Google Tag Manager and Google Analytics
Only if you consent to "Statistics" in the cookie notice do we load Google Tag Manager (container GTM-KFHTLXPV) on the public pages and, through it, Google Analytics 4. The container contains statistics tags only. Before that, no Google script is loaded and no connection to Google is established.
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
Purpose: Aggregated reports show us how the pages are used, for example which pages are viewed, how long a visit lasts and which website you came from. Google Analytics does not store IP addresses for users in the EU; only the approximate location is derived from the IP address.
Google Consent Mode: All storage purposes start as "denied". After your consent we grant analytics storage only. Ad storage and personalized advertising remain denied.
Cookies: _ga (2 years) distinguishes visitors by a random identifier, _ga_* (2 years) stores the state of the visit.
Retention of analytics data: Google Analytics keeps event-level data for 2 months.
Legal basis: your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG, Art. 7 I LGPD). You can withdraw it at any time with effect for the future via "Cookie settings".
Transfer to the USA: Data may be transferred to Google LLC in the USA (section 25).
7. Inquiries
If you send us an inquiry through the form on flowdata.one, we process the details in the form, for example your name, email address, company and message.
These details are used as follows: we receive them by email, you get a confirmation email, and we create a contact in our own CRM (FlowCRM) to handle your inquiry.
Legal basis: steps taken at your request (Art. 6(1)(b) GDPR, Art. 7 V LGPD) and our legitimate interest in answering inquiries and looking after prospective customers (Art. 6(1)(f) GDPR, Art. 7 IX LGPD).
Retention: We keep inquiries as long as needed to handle them, at most 12 months after receipt. We delete them earlier if you ask us to, unless a retention obligation applies. We keep the contact created in FlowCRM beyond that for as long as we look after you as a prospect or customer. We delete it if you ask us to, unless a retention obligation applies.
Protection of the forms (Cloudflare Turnstile)
On the forms we use Cloudflare Turnstile to distinguish humans from automated programs. The script is loaded from challenges.cloudflare.com and sends technical signals to Cloudflare. These may include the IP address, details of the operating system, device and browser, language settings and interaction with the page. We verify the result on our server together with your IP address at Cloudflare.
Provider: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA (privacy policy, Turnstile notice). Legal basis: Art. 6(1)(f) GDPR, Art. 7 IX LGPD. Our legitimate interest is protection against abuse and automated attacks.
8. Sign-in through FlowConnect
Sign-in takes place on flowconnect.one. FlowConnect then hands you over to flowdata.one with a one-time sign-in ticket, where a separate session for this domain is created. For each session we store the domain, the IP address, the browser identifier and the last activity. Details are in the FlowConnect privacy policy.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
9. Your data in FlowData
In FlowData we process what you and your team create and what use of the service produces:
- API keys (name, permissions, spending limits, timestamps),
- team settings, media processing presets and watermarks, callback addresses,
- the request log and usage counters (section 10),
- the input and results of the individual areas (sections 11 to 16),
- balance, ledger entries, usage and invoices (section 17).
Purpose and legal basis: to provide FlowData and perform the contract (Art. 6(1)(b) GDPR, Art. 7 V LGPD).
Third-party data: If you send us data about other people, such as your contacts' email addresses, your visitors' IP addresses or videos showing people, we process it for you. You are responsible for being allowed to give it to us. Where we process only on your instructions, you are the controller and we are the processor. We will send you a data processing agreement under Art. 28 GDPR on request to contact@creativeskyline.com. The services named in sections 13 and 14 are then sub-processors.
Shared result stores: We operate the result stores named in sections 11, 13, 14 and 15 under our own responsibility. They are not assigned to a team. A stored result may also answer the same request from another customer.
10. Request log and usage counters
Request log: For each call to the interface we store the key, the user ID, the path, the method, the caller's IP address, the user agent, the URL parameters (query string), the response status and the response time. For failed calls we also store the error response; this does not apply to media processing. Your API key is removed before storage. Members of your team with access to FlowData can see this log. We delete the entries after 30 days.
Usage counters: In addition, we count calls, response time and cost per key, user, path, method and day. The path is stored as it was called; we only remove API keys from it. For email verification the verified email address is therefore in the path, for IP geolocation the queried IP address or domain, for YouTube the channel identifier.
There is no fixed deletion date for the usage counters. We do not delete them automatically, including the email addresses and IP addresses they contain.
Purpose and legal basis: to bill usage and show it to you in a traceable way (Art. 6(1)(b) GDPR, Art. 7 V LGPD), to find errors and detect misuse (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). We base the indefinite retention of the counters on Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is to be able to evaluate usage over long periods and to trace earlier billing. Your rights under section 28, including erasure and objection, remain unaffected.
11. IP geolocation
You send us an IP address or domain. If you give none, we use the caller's IP address. We resolve domains to an IP address by DNS. We determine the approximate location, time zone and network operator locally on our own server from GeoLite database files. IP addresses are not sent to MaxMind or any other geodata service in this process.
This product includes GeoLite data created by MaxMind, available from https://www.maxmind.com, which includes geographic data from GeoNames (CC BY 4.0).
Result store: We store successful lookups with the queried IP address and the result (country, region, city, postal code, coordinates, time zone, currency, network operator) in the table data_ip_addresses. There is no fixed deletion date for this table. We do not delete it automatically.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD for the lookup. We base retention on Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is traceable and stable operation of the service.
12. Client Info
Client Info evaluates only the headers of the respective call (IP address, user agent, language settings, indications of a proxy) and sends the result back to the caller. No external service is asked and the result is not stored separately. As with every call, an entry is created in the request log (section 10).
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
13. Maps
For address search, geocoding and directions we query one of the following services, unless a suitable stored result already exists. Which service is asked depends on priority and free quota. You can also choose one yourself with the provider parameter. Directions are calculated by Mapbox.
| Service | Provider | Privacy notice |
|---|---|---|
| Mapbox | Mapbox, Inc., 740 15th St NW, Suite 500, Washington, DC 20005, USA | mapbox.com/legal/privacy |
| Google Maps Platform | Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland | policies.google.com/privacy |
| MapTiler | MapTiler AG, Zugerstrasse 22, 6314 Unterägeri, Switzerland | maptiler.com/privacy-policy |
| Nominatim | OpenStreetMap Foundation, St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdom | osmfoundation.org/wiki/Privacy_Policy |
Radar, only if you expressly choose it with provider |
Radar Labs, Inc., 111 5th Ave, 12th Floor, New York, NY 10003, USA | radar.com/privacy |
The search term or address, coordinates, country, language and, for directions, start, destination and waypoints are transmitted from our server, without your account or payment data. Personal reference arises if the search term or coordinates point to a person's address.
Result store: We store search queries with their parameters (data_maps_search_logs), addresses found with coordinates (data_maps_addresses), directions with start, destination, waypoints and result (data_maps_directions) and the request and response of the respective service (data_maps_provider_logs). There is no fixed deletion date for these tables. We do not delete them automatically.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD for the query. We base retention on Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is to answer repeated requests quickly and without querying a service again.
14. Email verification
You send us an email address. First we check it ourselves: syntax, the domain's mail server by DNS, disposable domains, role addresses and known catch-all domains. Only if that is not enough does the full email address go to the following services, in this order, until one gives a definite answer:
| Service | Provider | Privacy notice |
|---|---|---|
| LeadRocks | interface at api.leadrocks.io | leadrocks.io/privacy-policy.html |
| Hunter | Hunter Web Services, Inc., 2810 N Church St #50754, Wilmington, DE 19802, USA | hunter.io/privacy-policy |
| Emailable | EMAILABLE LLC, 400 Rella Blvd, Montebello, NY 10901, USA | emailable.com/privacy-policy |
You can limit the check to one of these services with the type parameter.
Result store: In the table email_verifier we store the email address, the result (for example safe, risky, invalid), the reason, the individual checks, the source and the complete response of the respective service. This response may contain further details the service returns about the address. A stored result answers repeated requests for 3 to 90 days depending on the result, including in FlowSend list cleaning and other Creative Skyline products. After that time the row is not deleted. There is no fixed deletion date for this table.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD for the verification. We base retention on Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is to avoid repeated checks and to detect undeliverable addresses.
15. YouTube
You give us a channel ID or handle. We fetch the public channel data through a script on our server from the official YouTube Data API. Only the channel ID or handle is transmitted.
Provider: YouTube LLC, 901 Cherry Ave., San Bruno, CA 94066, USA, a Google company (Google privacy policy).
Result store: In the table data_youtube we store channel ID, handle, title, description, subscriber, video and view counts and the address of the thumbnail. A stored result answers requests for 24 hours. After that we update it on the next request. There is no fixed deletion date for this table. We do not delete it automatically. If a channel belongs to an individual, this may be personal data.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD for the query. We base retention on Art. 6(1)(f) GDPR and Art. 7 IX LGPD. Our legitimate interest is to answer repeated requests quickly.
16. Media processing
You give us a file by naming an HTTPS address from which our server fetches it, or by uploading it directly through a time-limited link. We process video, audio and images with ffmpeg and ImageMagick on our own servers. We use no external processing service and no AI providers for this. If the files contain people or voices, we process them as a processor (section 9).
Storage location: Uploaded files, finished outputs and watermarks are kept in our own S3-compatible object storage at s3.creativeskyline.com, which also runs at Hetzner. You can instead have outputs uploaded to an address of your own. We store input addresses and callback addresses only in encrypted form.
Callbacks (webhooks): If you set up callbacks, we send the status of a job to the address you name, where applicable with download links. We store the contents of these callbacks in encrypted form. The recipient is you or the party you name; you are responsible for the processing there.
Retention:
| Data | Period |
|---|---|
| Working files on the server | until the end of the job |
| Directly uploaded files | 24 hours after the upload was created, deleted in the daily run |
| Finished outputs stored by us | 7 days |
| Jobs including output data and callbacks | 90 days |
| Watermarks | until you replace or delete them |
| Billing lines | permanently, see section 17 |
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
17. Payment and billing
You pay for FlowData through a balance in euros, which you top up in amounts of 20 euros or more. For each top-up we create an invoice in FlowAccounting, which you pay by Stripe or by bank transfer. Only if we approve it for your team do you pay monthly in arrears on invoice instead.
What we process: billing address, team name, tax details if you provide them, amounts, invoice numbers, payment method and payment status, ledger entries on the balance and usage per area, key and period. We keep invoices and customer master data in our own systems FlowAccounting and FlowCRM.
Business confirmation: FlowData is aimed exclusively at businesses and self-employed professionals (§ 11 of the terms). With every top-up we therefore store your confirmation that you use FlowData exclusively for commercial or independent professional purposes and accept the terms, with the time, the acting person and the version of the terms it refers to. The purpose is proof that you booked as a business. If we ask you for proof, such as your VAT identification number or details of your business, we process these details for the same purpose. The legal basis is the contract with you (Art. 6(1)(b) GDPR, Art. 7 V LGPD) and our legitimate interest in being able to prove that we offer FlowData to businesses only (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). We do not automatically delete these records.
Stripe: When you pay by Stripe, you enter the full card or account details directly at Stripe; they do not reach us. Stripe loads its script on the payment page and sets the cookies named in section 5.
Provider: Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02FX04, Ireland (privacy policy). Processing by Stripe companies in the USA is possible (section 25).
Legal basis: Art. 6(1)(b) and (c) GDPR, Art. 7 II and V LGPD. We keep invoices and accounting records for 8 years (Section 147 AO, Section 257 HGB). We do not automatically delete billing lines for usage.
18. Playground
After signing in, you can try out the interfaces at flowdata.one/dashboard/playground. Your browser calls https://api.flowdata.one/v1 directly, either with a key of your own that you enter or with a temporarily issued key that is valid for two hours and has its own spending limit. The key is held only in the memory of the open page and is not kept in your browser. FlowData stores the outputs of media jobs started from the Playground (section 16); your own storage targets and callbacks are not available there. The calls are logged (section 10), processed and billed like all others.
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
19. MCP and AI agents
Through https://mcp.flowconnect.one/flowdata, applications you authorize, such as AI assistants like Claude or ChatGPT, can access the areas of FlowData with an MCP key or OAuth (IP geolocation, Client Info, Maps, email verification, YouTube statistics), trigger queries or media jobs on your behalf and check their status. Through MCP, media jobs accept only a publicly reachable HTTPS address as the source, and FlowData stores all outputs (section 16). Direct uploads, your own storage targets and callbacks are not available through MCP. These calls are logged and billed like all others.
The application you choose is a separate recipient. It receives the data on your instruction. The relationship with its provider, including any data processing agreement that may be required, exists between you and that provider. Its terms and privacy policies apply to further processing.
How keys are stored and calls are logged is described in the FlowConnect privacy policy.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD. Our legitimate interest is to secure the interfaces.
20. Emails from FlowData
We send emails about inquiries, invoices and notices about your account and balance. They are sent through SMTP2GO, a service of Sand Dune Mail Ltd, 96-106 Manchester Street, Christchurch 8011, New Zealand (privacy policy). Recipient and sender addresses, content and delivery data are processed.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD.
21. Access by our team
Authorized Creative Skyline staff can access keys, billing data, logs and jobs to the extent necessary for support, billing, security and operations (Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD).
22. Recipients at a glance
- Hetzner Online GmbH (hosting, object storage)
- Laravel Holdings Inc. (operational monitoring)
- Sand Dune Mail Ltd, SMTP2GO (email delivery)
- Cloudflare, Inc. (Turnstile)
- Stripe Payments Europe, Limited (payments)
- Google Ireland Limited (Analytics after consent, Google Maps Platform)
- YouTube LLC (YouTube Data API)
- Mapbox, Inc., MapTiler AG, OpenStreetMap Foundation and, at your choice, Radar Labs, Inc. (Maps)
- LeadRocks, Hunter Web Services, Inc., EMAILABLE LLC (email verification)
- providers of the applications you authorize and targets you name for outputs and callbacks, on your instruction
- members of your team within their permissions
- authorities and courts where we are legally obliged
23. Retention at a glance
| Data | Period |
|---|---|
| Server log files | at most 30 days |
| Operating data in Nightwatch | up to 90 days (default) |
| Consent log | 3 years |
| Event data in Google Analytics | 2 months |
Interface request log (api_usages) |
30 days |
Usage counters with path, including email address or IP address (api_usage_counters) |
no fixed deletion date |
IP geolocation result store (data_ip_addresses) |
no fixed deletion date |
Maps result store (data_maps_search_logs, data_maps_addresses, data_maps_directions, data_maps_provider_logs) |
no fixed deletion date |
Email verification result store (email_verifier) |
no fixed deletion date; used as an answer for 3 to 90 days |
YouTube result store (data_youtube) |
no fixed deletion date; used as an answer for 24 hours |
| Media: working files, uploads, outputs, jobs | see section 16 |
| API keys, settings, webhook addresses | as long as the account, team or entry exists |
| Inquiries | at most 12 months after receipt; the contact created in FlowCRM for as long as we look after you as a prospect or customer; details: see section 7 |
| Billing lines for usage | no fixed deletion date |
| Business confirmation at top-up (section 17) | no fixed deletion date |
| Invoices and accounting records | 8 years (Section 147 AO, Section 257 HGB) |
The end of the contract or the deletion of individual API keys does not automatically cause the items marked "no fixed deletion date" to be deleted.
24. Legal basis for indefinite storage
We keep the tables and counters without a fixed deletion date because they allow us to answer repeated requests without querying a service again, to evaluate usage over long periods and to trace earlier billing (Art. 6(1)(f) GDPR, Art. 7 IX LGPD). We have not set a maximum period for this. You can object to this storage and request access or erasure (section 28). We review such requests individually.
25. Transfers to third countries
Brazil
The application runs on servers in Germany at Hetzner Online GmbH. Creative Skyline Ltda. is a company under Brazilian law with its registered office in Fortaleza. When we access data from Brazil for operations and support, this is a transfer to a third country. The EU Commission adopted an adequacy decision for Brazil under Art. 45 GDPR on 26 January 2026. The transfer is therefore permitted without additional safeguards. Brazil recognizes the EU in return through Resolução CD/ANPD 32/2026. In Brazil the LGPD additionally protects the data.
USA
With Google (including YouTube) and Cloudflare, data may be transferred to the USA. These transfers rely on the EU-US Data Privacy Framework and the adequacy decision of the EU Commission of 10 July 2023 (Art. 45 GDPR). Mapbox, Inc., EMAILABLE LLC and Radar Labs, Inc. state in their privacy notices that they comply with the EU-US Data Privacy Framework; this also relies on the decision named above. Stripe states the same for its US companies. Hunter Web Services, Inc. states that it operates its servers in Belgium and bases transfers outside the EEA on standard contractual clauses (Art. 46(2)(c) GDPR). Laravel Holdings Inc. states that it bases cross-border transfers on contractual safeguards.
LeadRocks
LeadRocks states in its privacy policy that it operates its servers in the USA and uses standard contractual clauses for transfers from the EEA.
Other countries
There are adequacy decisions of the EU Commission for Switzerland (MapTiler), New Zealand (SMTP2GO) and the United Kingdom (OpenStreetMap Foundation).
Under the LGPD
Under the LGPD we base international transfers on Art. 33 LGPD, depending on the case on the necessity to perform the contract (Art. 33 IX in conjunction with Art. 7 V LGPD) or on your consent (Art. 33 VIII LGPD).
26. Obligation to provide data
For inquiries we need the details marked as required, for FlowData a FlowConnect account and, for the paid areas, a balance or approval for invoicing. There is no legal obligation to provide us with data.
27. No automated decisions
No automated decision within the meaning of Art. 22 GDPR that produces legal effects concerning you or similarly significantly affects you takes place in FlowData (nor within the meaning of Art. 20 LGPD). Email verification provides an assessment; what you do with it is your decision. Protective checks such as Turnstile may reject a single entry. If this stops you from proceeding, write to us and we will check it manually.
28. 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 may withdraw consent at any time with effect for the future (Art. 7(3) GDPR).
Under the LGPD (Art. 18) you, as a data subject (titular), have in particular the right to confirmation that data is being processed, access to the data, correction, anonymization, blocking or deletion of unnecessary, excessive or unlawfully processed data, data portability, information about the entities with which data is shared, and objection.
You have these rights even if you have never been a FlowData customer but your email address or IP address reached our result stores through a customer. To exercise your rights, an email to contact@creativeskyline.com is sufficient.
29. 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, place of work or place of the alleged infringement (Art. 77 GDPR). Under the LGPD you may contact the Brazilian data protection authority, the Autoridade Nacional de Proteção de Dados (ANPD).
30. Changes
We adapt this privacy policy when FlowData or the legal situation changes. The version published here applies.