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 FlowModels on flowmodels.one, including the application at flowmodels.one/dashboard, the API at api.flowmodels.one and MCP access at https://mcp.flowconnect.one/flowmodels. It explains which personal data is processed when you visit the website, send an inquiry or use FlowModels, 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).
FlowModels is a service of Creative Skyline.
Last updated: 13 November 2026
1. Controller
Unless section 9 says otherwise, 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://flowmodels.one/en/legal-notice
2. Data protection officer and contact for privacy requests
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 flowmodels.one and api.flowmodels.one: the public website, the inquiry form, the application, the API with the connected AI models, billing and access via MCP.
Login, account, team, security and API keys run through FlowConnect. The FlowConnect privacy policy applies to those. Other Creative Skyline products have their own privacy notices.
4. Hosting, server log files and monitoring
flowmodels.one, api.flowmodels.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 AI providers receive the data described in sections 11 and 12, and the servers are also accessed from Brazil (section 23).
With every request, your browser or application technically transmits data to the server. The server stores in log files the IP address of the requesting device, date and time, the requested address, the browser or program identifier (user agent) and the previously visited page (referrer), if transmitted.
Purpose and legal basis: to deliver the site and the API, to ensure their secure and stable operation and to 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 clarify 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. Technical events from operations go to Nightwatch: page requests (address, IP address, status and duration), for signed-in persons the user ID, name and email address, error messages with their stack trace, database queries without the inserted parameters, outgoing requests to other services, background tasks, sent emails (subject and number of recipients, not their addresses) and log entries.
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 flowmodels.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 |
| Consent cookie | stores your cookie choice and a random consent ID | 1 year | after your choice in the notice |
remember_web_* |
"Stay signed in" | 400 days | only if you choose it |
fc_td |
trusted device for two-factor login | 30 days | only if you trust the device at login |
__stripe_mid, __stripe_sid |
Stripe: fraud prevention for payments | 1 year, 30 minutes | only on the payment pages |
_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.
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-MPKD6B7H) 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 may 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 23).
7. Inquiries via the contact form
When you send an inquiry, for example about volume or invoiced billing, we process the details in the form: name, email address, topic, message and, if you provide it, your company.
This is what happens with these details: we store the inquiry, we receive it by email, you receive a confirmation by email, and we create a contact in our own CRM (FlowCRM, the Creative Skyline team) 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 prospects (Art. 6(1)(f) GDPR, Art. 7 IX LGPD).
Retention: We store inquiries as long as needed to handle them, for at most 12 months after receipt. At your request we delete them earlier, unless a retention duty applies. We keep the contact created in FlowCRM beyond that for as long as we look after you as a prospect or customer. At your request we delete it, unless a retention duty applies.
Contact form protection (Cloudflare Turnstile)
On the contact form 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 IP address, details of the operating system, device and browser, language settings and interaction with the page. We verify the result server-side together with your IP address at Cloudflare.
Provider: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA (privacy policy, Turnstile notices). Legal basis: Art. 6(1)(f) GDPR, Art. 7 IX LGPD. Our legitimate interest is protection against abuse and automated attacks.
8. Login via FlowConnect
Login takes place on flowconnect.one. FlowConnect then hands you over to flowmodels.one with a one-time login 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. Who is responsible for what
We are the controller for your account, contract and billing data, the logs for security and billing, the website, the inquiry form and support.
You are the controller for the personal data you pass to FlowModels through the API or the application, in particular data of your own customers and end users in prompts, files, images, audio recordings, conversations and memories. For this data we act as your processor (Art. 28 GDPR, Art. 39 LGPD) and process it according to your instructions, which you give through your use of the API and our contract terms. The AI providers named in sections 11 and 12 are sub-processors in this context, as is Hetzner.
We will send you a data processing agreement (DPA) under Art. 28 GDPR on request to contact@creativeskyline.com.
As controller you inform your end users about this processing yourself, ensure a legal basis and answer their requests. End users of your application should contact you first. Please enter only personal data you really need in prompts, and use a neutral value as your end user identifier (external_identifier) rather than an email address or a name.
10. What we ourselves store about API calls
The retention periods are listed together in section 22.
Call log: For each call we store the time, team, user, key, request ID, the called model and the provider, token counts, duration, status and any error code and, if you use an end user identifier, the assignment to that end user. The log serves billing, proof of usage and support.
Request and response content: For calls to /v1/chat/completions and /v1/responses we additionally store the text of your request and the model's response for troubleshooting by support. We remove attachments (files and images) before storing, as well as the query parts of addresses. You do not see this content anywhere in the interface; only authorized staff can access it (section 20). The content is automatically cleared after 30 days. You can have the storage of content turned off for your team: write to contact@creativeskyline.com. An administrator of Creative Skyline then turns it off in your team's administration and records the change with a reason. For all calls after that, the log contains only the technical details. Content already stored is cleared within the 30-day period.
Background runs and stored responses: If you start a run in the background or store a response (/v1/responses), we keep the input and the result until 24 hours after completion. For background runs the call log contains no content.
Replay protection: If you send an Idempotency-Key, we store the response to that request for 24 hours so that a repeat is not charged again.
API access log: For each call we store IP address, browser or program identifier, path, method, status and duration, without request or response text. These entries are deleted after 30 days; aggregated counters remain.
Files: Files you upload through /v1/files stay in our private object storage until you delete them. There is no automatic period for this. Attachments intended only for a single call are deleted after the call. We remove leftovers after a crash after at most 24 hours.
Images and videos: If you generate images (/v1/images) or videos (/v1/videos), we store for each job the model, settings, status and cost as well as your prompt, the prompt in encrypted form. Finished images and videos are kept in our private object storage and can only be reached through retrieval addresses that are valid for 15 minutes. After 7 days we automatically delete the file and the prompt; you can delete both yourself earlier. If the billing of a job has not yet been settled, the details are kept until it is settled. Images you provide by address as a source or start image are downloaded by us and passed on only to the recipient named in section 12.
Usage and billing data: For billing and proof we store per call the time, model, provider, quantities and amounts, as well as balance movements. There is no automatic deletion of this data. It is kept during the contract and beyond that within the statutory retention duties (section 22).
Purpose and legal basis: to provide and bill the API and to help with disruptions (Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD), and for billing data additionally the retention duties (Art. 6(1)(c) GDPR, Art. 7 II LGPD).
11. AI providers as sub-processors
FlowModels forwards your calls through the programming interfaces of the following providers. You choose the model that executes a call yourself through the model field. We do not automatically forward a call to another model or another provider.
| Provider | Seat | Purpose |
|---|---|---|
| OpenAI Ireland Ltd | 117-126 Sheriff Street Upper, D01 YC43 Dublin 1, Ireland | language models, embeddings, audio transcription, image generation |
| Anthropic Ireland, Limited (parent company: Anthropic PBC, USA) | 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland | Claude language models |
| Google Cloud EMEA Limited (Gemini) | 70 Sir John Rogerson's Quay, Dublin 2, Ireland | Gemini language models, image generation |
| X.AI LLC (Grok) | 1450 Page Mill Road, Palo Alto, CA 94304, USA | Grok language models |
| Groq LLC | P.O. Box 1778, Mountain View, CA 94042, USA | open language models, audio transcription (Whisper) |
| Perplexity AI, Inc. | 575 Market St. Fl 4, 94105 San Francisco, USA | Sonar language models with web search |
| Higgsfield Inc. | 550 Montgomery St, 3rd Floor, San Francisco, CA 94111, USA | video generation with the models of ByteDance, MiniMax and Alibaba |
Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD for the calls you start. Where you bring in third-party data, we process it on your behalf (section 9). For transfers to third countries see section 23.
12. Which data goes where
As a rule, the prompt, files and audio of a call go only to the provider of the model you choose for that call:
Model family (model) |
Provider | What is transmitted |
|---|---|---|
OpenAI: openai/gpt-… |
OpenAI | messages, system instruction, attachments, tool definitions, response format |
OpenAI embeddings: openai/text-embedding-… |
OpenAI | the texts passed in |
OpenAI audio: openai/gpt-transcribe |
OpenAI | the audio file and the language setting |
Anthropic: anthropic/claude-… |
Anthropic | messages, system instruction, attachments, tool definitions |
Google: gemini/gemini-… |
Google (Gemini) | messages, system instruction, attachments including audio and video, tool definitions |
xAI: xai/grok-… |
xAI | messages, system instruction, attachments, tool definitions |
Groq, open models: groq/openai/gpt-oss-…, groq/qwen/… |
Groq, not the developers of the models | messages, system instruction, tool definitions |
Groq, Whisper: groq/whisper-… |
Groq | the audio file and the language setting |
Perplexity: perplexity/sonar… |
Perplexity | messages, system instruction; web searches arise from the request |
OpenAI images: openai/gpt-image-… |
OpenAI | the prompt, size and quality, for edits the source image |
Google images: google/gemini-…-image… |
Google (Gemini) | the prompt and the size |
Video: bytedance/seedance-…, minimax/h3/…, alibaba/wan-… |
Higgsfield, not the developers of the models (ByteDance, MiniMax, Alibaba) | the prompt, settings such as duration, resolution and aspect ratio, for videos from images the start image and, where applicable, the end image |
Exceptions. In the following cases, data of a call also goes to another of the providers named above. Each case occurs only if you use the relevant function:
| Case | What is transmitted | Additional provider |
|---|---|---|
| Audio in a message to a model that cannot process audio itself | the audio file is transcribed, and the transcript then goes to the selected model | Groq (Whisper) |
History compression: for conversations with external_identifier and on request with context_compression |
older parts of the conversation, condensed into a summary | Groq |
Automatic memories for conversations with external_identifier |
the end user's message and the memories derived from it | Groq (classification), OpenAI (embeddings) |
| Files for end users (upload and search) | text passages of the file and search texts; images in files for image analysis | OpenAI (embeddings, image analysis) |
We transfer finished videos to our storage and then ask Higgsfield to delete its copy.
We read text from files on our own servers. If you use web search (web_search), the provider of the selected model carries it out and uses content of your request for it.
Model responses can be wrong; please check them before use.
13. Provider terms
How long the providers keep data, whether they use inputs for their own purposes and how they secure the data depends solely on their own terms and privacy notices. We make no commitment of our own on this.
- OpenAI: business terms, privacy
- Anthropic: commercial terms, privacy
- Google (Gemini): Gemini API terms, privacy
- xAI: business terms, privacy
- Groq: terms of use, privacy
- Perplexity: API terms, privacy
- Higgsfield: terms of use, privacy
14. Conversations, memories and files per end user
If you pass an end user identifier (external_identifier) with a call, we store conversations, memories and uploaded files for that end user. You set the identifier, metadata and settings yourself. Without an identifier we keep no history.
Automatic memories are turned on for new end users. FlowModels then derives memories from the end user's messages and uses them in later responses. You turn this off per end user by setting memory_extraction_enabled to false.
This data stays stored until you delete it or the end user. There is no automatic period for this.
Erasure and erasure receipt: You can delete individual memories and files or delete an end user completely, in the application or through the API. When deleting an end user we remove their conversations, memories, files, the related embeddings and the call logs for that end user. Stored files are then removed in the background.
You receive an erasure receipt with status, timestamps and the number of deleted entries per data type. The receipt contains no texts and no file names; we keep your identifier in it only as a hash value. We do not delete receipts automatically, so that you can prove the erasure.
Billing and usage rows remain so that invoices stay traceable. On erasure we replace their assignment to the end user with a pseudonym.
15. Audio transcription
We store audio files for /v1/audio/transcriptions only temporarily on our server and delete them as soon as the job has completed, been cancelled or failed; leftovers after a crash are removed automatically shortly afterwards. The result is kept encrypted with us and is deleted 24 hours after completion. You can delete it yourself earlier. For live sessions the same period applies to confirmed segments.
The provider receives the recording as described in section 12.
16. Webhooks
If you set up webhooks, we send events to the address you specify. For each delivery we store the event type, identifiers, status, number of attempts, your server's HTTP code and timestamps. For finished background runs the message contains only the identifier and status, no response text. We store the signing secret encrypted.
There is no automatic period for the delivery log. If you delete an address through the interface, we also remove its log.
The recipient is you or the party you name. Legal basis: Art. 6(1)(b) GDPR, Art. 7 V LGPD.
17. Payment and billing
You top up your balance through an invoice with a payment link. Payment and, if you turn on automatic top-up, the storage of your card run through Stripe, a service of Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02FX04, Ireland (privacy). Stripe receives the payment data directly from you; we do not store full card numbers. Processing by Stripe, Inc. in the USA is possible (section 23).
We store your billing details, invoices, top-ups and, if you turn on automatic top-up, your consent with the time and the acting person. You can turn off automatic top-up at any time.
FlowModels is aimed exclusively at businesses and self-employed professionals (§ 2 of the terms). With every top-up we therefore store your confirmation that you use FlowModels 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; for automatic top-ups, the confirmation you gave when turning them on. 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.
Legal basis: Art. 6(1)(b), (c) and (f) GDPR, Art. 7 II, V and IX LGPD. For the business confirmation, these are the contract with you (point (b)) and our legitimate interest in being able to prove that we offer FlowModels to businesses only (point (f)). For retention see section 22.
18. MCP and AI agents
Through https://mcp.flowconnect.one/flowmodels, applications you authorize, such as AI assistants, can read FlowModels data using an MCP key or OAuth: models, prices, usage and balance.
The application you choose is a separate recipient. It receives the data on your instruction. The relationship with its provider, including any necessary data processing agreement, exists between you and that provider. Its terms and privacy notices 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 securing the interfaces.
19. Emails from FlowModels
We send emails about inquiries, balance, warning thresholds, invoices, failed top-ups and webhooks from noreply@flowmodels.one. Sending runs 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 sending data are processed in this context.
Legal basis: Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD.
20. Access by our team
Authorized staff of Creative Skyline can access logs, stored content and billing data where necessary for support, security and operations (Art. 6(1)(b) and (f) GDPR, Art. 7 V and IX LGPD).
21. Recipients at a glance
- Hetzner Online GmbH (hosting)
- Laravel Holdings Inc. (operational monitoring)
- Sand Dune Mail Ltd, SMTP2GO (email delivery)
- Cloudflare, Inc. (Turnstile)
- Stripe Payments Europe, Limited (payment)
- Google Ireland Limited (Analytics after consent)
- OpenAI Ireland Ltd, Anthropic Ireland, Limited, Google Cloud EMEA Limited, X.AI LLC, Groq LLC, Perplexity AI, Inc., Higgsfield Inc. (AI models, sections 11 and 12)
- Providers of the applications you authorize and the webhook recipients you name, on your instruction
- Members of your team within the scope of their rights
- Authorities and courts, where we are legally required
22. Retention at a glance
| Data | Period |
|---|---|
| Server log files | at most 30 days |
| Operational data in Nightwatch | up to 90 days (default setting) |
| Consent log | 3 years |
| Event data in Google Analytics | 2 months |
| Call log (technical details) | 400 days |
| Request and response text in the call log | 30 days |
| API access log (IP address, identifier, path, status) | 30 days |
| Background runs and stored responses | 24 hours after completion |
Responses for an Idempotency-Key |
24 hours |
| Attachments for a single call | until the end of the call, leftovers at most 24 hours |
| Audio files for transcriptions | until the job is completed |
| Transcription results | 24 hours after completion, or until you delete them |
Files through /v1/files |
until you delete them |
| Generated images and videos including the prompt | 7 days, or until you delete them; if billing is unsettled, until it is settled |
| Conversations, memories and files per end user | until you delete them or the end user |
| Erasure receipts | no automatic period |
| Webhook delivery log | no automatic period; removed when the address is deleted through the interface |
| Usage and balance movements | no automatic deletion; during the contract and within statutory retention duties |
| Business confirmation at top-up | as long as the top-up it belongs to, that is with the contract and within statutory retention duties |
| Inquiries through the form | at most 12 months from receipt; the contact created in FlowCRM for as long as we look after you as a prospect or customer |
| Invoices and accounting records | 8 years (Section 147 AO, Section 257 HGB) |
After the end of the contract, we delete your FlowModels data manually within 30 days of a request to contact@creativeskyline.com, unless a statutory retention duty prevents this (§ 18.2 of the terms). There is no automatic deletion at the end of the contract. You can delete end users and their data yourself at any time (section 14).
23. Transfers to third countries
Brazil
Our servers are located 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, Cloudflare and Perplexity, 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). With OpenAI, Anthropic, Groq and xAI, transfers to the USA rely on standard contractual clauses (Art. 46(2)(c) GDPR). Laravel Holdings Inc. states that it bases cross-border transfers on contractual safeguards. With Stripe, processing by Stripe, Inc. in the USA is possible. For video generation, data goes to Higgsfield Inc. in the USA. Higgsfield states that it bases transfers from the EU to countries without an adequacy decision on standard contractual clauses approved by the EU Commission (Art. 46(2)(c) GDPR).
Other countries
There is an adequacy decision of the EU Commission for New Zealand (SMTP2GO).
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).
24. Obligation to provide data
For inquiries we need the details marked as required, for FlowModels a FlowConnect account, billing details and a balance. Everything else, such as end user identifiers or automatic top-up, is voluntary. There is no legal obligation to provide us with data.
25. 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 FlowModels (nor within the meaning of Art. 20 LGPD). Calls may be refused for lack of balance or reached limits, and 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.
26. 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.
To exercise your rights, an email to contact@creativeskyline.com is sufficient. For data we process as a processor for one of our customers, please contact that customer.
27. 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).
28. Changes
We adapt this privacy policy when FlowModels or the legal situation changes. The version published here applies.