SYNAC FLOW

Privacy policy

Last updated: 19 November 2026

1. Controller

(1) The controller within the meaning of the General Data Protection Regulation (GDPR) is Khondakar Readul Islam (SYNAC.IO), HUB31 Accelerator, Hilpertstraße 31, 64295 Darmstadt, Germany. You can contact us at privacy@synac.io.
(2) We have not appointed a data protection officer, as we are not legally required to do so.

2. Scope

(1) This privacy policy applies to the website synacflow.com with its checkout, its student check and its Marketplace, the SYNAC FLOW Workspace, which we operate, and the SYNAC FLOW connect service.
(2) Organisations may also operate SYNAC FLOW on their own infrastructure (installations). The operating organisation is the controller for all data processed in its installation. We have no access to installations.

3. Visiting this website

(1) When you visit this website, your browser transmits technical data, in particular your IP address, the date and time of access, the requested page and the name and version of your browser. We process this data only to deliver the website and, at the checkout, the student check, the Marketplace and when you save your cookie settings, to limit the number of requests (paragraphs 2, 4 and 7 and section 10 (2)); we do not store it in log files. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in providing the website and keeping the checkout, the student check, the Marketplace and the cookie settings available for everyone.
(2) The website uses only technically necessary cookies: the cookie of the checkout described in paragraph 4, a cookie that keeps the language you chose with the language switch of the Marketplace for one year, a cookie that keeps the display you chose with the light and dark switch or in the accessibility settings (light or dark, high contrast, larger text) for one year after your last change, and a cookie that keeps your choice in the cookie settings for one year, so that we do not ask again on any of our pages. They do not require consent (§ 25(2) No. 2 TDDDG). So that we can prove your choice in the cookie settings, this cookie also contains a random number, and we store a record with this number, your choice for each category, the version of the text you were shown and the time of your choice. The record contains no name, no IP address and no details of your browser and is not linked to an account, a purchase or a comment; your IP address is used only to limit the number of requests and is not stored with the record. If you change or withdraw your choice, we add a new record under the same number. We delete each record three years after it was made. Only our administrators can access the records. The legal basis is Art. 6(1)(c) in conjunction with Art. 7(1) GDPR where you consent, and otherwise Art. 6(1)(f) GDPR; our legitimate interest lies in being able to prove which choice applied at what time. We set the display cookie only when you use one of these controls; it contains only the display you chose and no identifier, and we do not store its content. Without it, the website follows the light or dark setting of your device. The website does not use tracking, analytics or advertising tools and does not load content from third-party servers; the cookie settings already show these categories so that you decide before any such tool is ever used. If you are signed in to the SYNAC FLOW Workspace, the pricing page asks the Workspace for the current plan of your organisation to show it to you when you change your plan, and the Marketplace asks the Workspace for your display name so that you can comment; your browser sends the Workspace's sign-in cookie with these requests, and the answers are not stored (Art. 6(1)(b) GDPR).
(3) If you contact us by email, we process your email address and your message solely to handle your enquiry and delete them once it has been dealt with, unless statutory retention obligations apply. The legal basis is Art. 6(1)(b) and (f) GDPR.
(4) If you buy a plan, the checkout stores the plan you chose, the number of people, the language, the price shown to you, the status and the times of the purchase and, once you have signed in to the SYNAC FLOW Workspace, your organisation, the number of its members, your user ID and the email address of your account and, for a change of your plan, your current plan. We use this data to assign the purchase to your organisation, to provide the plan once, to refuse a plan for fewer people than your organisation has and, for a plan for your own installation, to send the activation key to that email address. Your password is checked only by the Workspace. So that the checkout finds your purchase again after you sign in, it sets one technically necessary cookie that contains only the identifier of the purchase and expires after 30 minutes; this cookie does not require consent (§ 25(2) No. 2 TDDDG). The links from the checkout to the sign-in and registration pages of the Workspace carry a code that works only once and only for 10 minutes; we store it only as a non-reversible hash with the purchase. With this code, the Workspace receives the identifier of the purchase and keeps it with your account, for a new account already before you confirm your email address, so that it takes you back to the checkout after this confirmation and reminds you on the dashboard of a purchase that is not completed. It deletes the identifier when you close the reminder, the next time the dashboard is opened after the plan has been bought or the purchase has been deleted (paragraph 6), and otherwise together with your account. The checkout counts the requests from each IP address to stay available for everyone; these counts are deleted after at most one hour and, for an address that exceeded the limits, after 24 hours. Your IP address is not stored with the purchase.
(5) Payment is handled by our payment service provider, which sells the plan to you in its own name as merchant of record. You enter your card and billing details on its own page; we do not receive them, and the provider's own privacy information applies to them. From us, the provider receives the chosen product, identifiers of your organisation and of the purchase and, if it already knows you, its own customer reference. If you change your plan under Settings → Plan and confirm the change in the checkout, we ask the provider to move your subscription to the new product: a more expensive plan applies at once and the provider charges the difference for the rest of the paid period; a cheaper plan applies from the end of the paid period, and we keep the scheduled change until then. If you cancel your plan under Settings → Plan, we ask the provider to end the renewal at the end of the paid period and, if you keep your plan after all, to continue it. For these requests, the provider receives only its reference of your subscription, the new product and whether the difference is charged now. The provider is established in the European Union and, according to its own information, uses safeguards such as standard contractual clauses (Art. 46(2)(c) GDPR) when it involves service providers outside the European Union.
(6) The legal basis is Art. 6(1)(b) GDPR. We delete a purchase that was not paid after 30 days and keep a paid purchase for as long as commercial and tax law require (Art. 6(1)(c) GDPR). As evidence of the steps taken for a purchase (the confirmation of your account, a payment that has to be checked, changes of plan and scheduled or withdrawn downgrades and cancellations), we keep a record for five years (Art. 6(1)(f) GDPR; our legitimate interest lies in being able to prove these steps).
(7) The Student plan is offered only to students. If you choose it, the checkout asks you, after you have signed in to the Workspace, for your university, for your first and last name as shown on your document and either for an email address of your university or for your student number. The email address must belong to a domain of the chosen university and can be used for only one running check. We then send a link valid for 7 days to that address or, with a student number, to the email address of your account; on the page that it opens, you upload one semester ticket, student ID or enrolment certificate (PDF, PNG or JPG, at most 10 MB). We read the text of the document on our own servers and do not store the text; we keep only whether it shows your name and your university and the date until which it is valid. If you used an email address of a university from our list and the document shows your name, your university and a date at most twelve months ahead, the check approves you at once; in every other case, a person of our team decides, usually within two working days. A check is never rejected automatically. If a check of another organisation at the same university uses the same student number, our team is shown a note. The student check counts requests from each IP address in the same way as the checkout (paragraph 4).
(8) When you start the check, the name you entered replaces the name of your Workspace account. With a university email address, that address becomes the main email address of your account, and your previous address remains a second address for signing in; sign-in codes go to both. Only the people of our team who decide on student checks can view your document, and each view is recorded. From one month before the valid date, we remind you weekly by email with a new link to upload a new document. If no new document has been approved by the valid date, the Student plan ends, your organisation moves to the Free plan, the university address is removed from your account and we inform you at both addresses. We delete the document 30 days after the decision and when the plan ends, and the whole check 30 days after it was rejected, ended or left without a document. As evidence, we keep a record of each step without your name, addresses, number or the content of the document for five years (paragraph 6). The legal basis is Art. 6(1)(b) GDPR and, for the note on the same student number, Art. 6(1)(f) GDPR; our legitimate interest lies in preventing misuse of the Student price. We use the data of the check for nothing else and do not pass it on; our payment service provider receives only the subscription, as for every plan.
(9) Once your student check has been approved, you can request a Student team under Settings → Team in the Workspace and name up to two fellow students with their first and last name and email address; you confirm that they agreed to this. We send each of them an email with your name and an invitation link valid for 7 days; on the page it opens, they agree again and do their own student check as described in paragraphs 7 and 8; for them, the address you gave takes the place of the email address of the account, and the check does not change any Workspace account. You see for each person only the name, the email address and the state of the check, never their document or what was read from it. Once everyone is verified, a person of our team decides on the team and informs you by email, with the reason if the team is not approved. Only then can the team plan be bought, and only the verified addresses can be invited to your organisation. If the valid date of a person passes without a new approved document, that person is removed from the team, their access to your organisation is blocked and they are informed by email; if your own Student plan ends (paragraph 8), the team ends and every verified person is blocked and informed. We delete the team with its people 30 days after it ended, and a person 30 days after they were removed from the team or their invitation expired unused; the records of each step are kept as in paragraph 8. The legal basis is Art. 6(1)(b) GDPR; you name the people with their agreement, and each of them agrees again before the check. We use the data of the team for nothing else and do not pass it on.

4. The SYNAC FLOW connect service

(1) The connect service allows you to connect an account with Google, Meta, X, LinkedIn, Atlassian, Canva, TikTok, Discord or Notion to SYNAC FLOW through an app registered for SYNAC FLOW. Our Google, Meta, LinkedIn, Atlassian, TikTok, Discord and Notion apps are used only for the SYNAC FLOW Workspace.
(2) To complete the sign-in, the connect service processes the data required for the sign-in, the authorisation code returned by the provider and the tokens it issues (for Discord also the webhook of the selected channel), also when a connection is renewed. It forwards the tokens in encrypted form to the SYNAC FLOW instance that started the sign-in and does not store them. It does not access your emails, videos, posts or files. Your IP address is processed temporarily to prevent misuse and is not stored.
(3) Some providers inform SYNAC FLOW about events of a connected account: TikTok when you remove SYNAC FLOW's access and when the status of a post changes, and Notion when a page or database you shared changes (section 5 (2)). The connect service checks that such a notification comes from the provider and keeps it, encrypted, until the SYNAC FLOW instance to which the connection belongs has retrieved and confirmed it, at the latest for 7 days; a notification is discarded on arrival if no connection is set up to receive it. It does not receive the content of posts, pages or databases. To assign a notification, it keeps only a keyed hash of the identifier of your account at the provider, until the connection is deleted, connected again or its access ends, or the SYNAC FLOW instance has not retrieved notifications for 30 days; to recognise a notification sent twice, it keeps a hash of the notification, or for Notion the identifier Notion gives it, for 7 days. The IP address of the provider's call is not stored.
(4) The legal basis is Art. 6(1)(b) GDPR, as you request the connection, and Art. 6(1)(f) GDPR; our legitimate interest lies in preventing misuse.

5. Connected accounts

(1) When you connect an account, SYNAC FLOW stores the access granted by the provider, or the access key you enter, in encrypted form until the connection is deleted, and uses it only to carry out the workflow steps that you or your organisation set up, or for chats in AI Chat (section 8.3); section 8.3 (3) describes how the access for a Claude plan is kept.
(2) Depending on the provider, SYNAC FLOW processes the following data:
  • Google (Gmail, YouTube): see section 7.
  • Meta (Facebook Pages, Instagram): the Facebook Pages you manage and your tasks on them, so that you can select a Page; publishing text, links, photos, videos and reels to the selected Page on behalf of the Page; for Instagram, the professional account linked to that Page and publishing photos and reels to it. Pages of a business portfolio are listed only if you also allow SYNAC FLOW to manage your business portfolios; SYNAC FLOW uses this permission solely for that list. SYNAC FLOW stores the ID and name of the selected Page or account and, instead of your Facebook ID, a pseudonymised identifier that is used only to process removal and deletion requests from Meta.
  • X: reading your profile and posts, and publishing posts.
  • LinkedIn: your member ID and name, and sharing posts on your behalf. The address of your profile picture and your language, which LinkedIn transmits during sign-in, are not stored.
  • Atlassian (Jira): reading and writing Jira issues and comments on the Jira site you select, and reading your Jira profile when you test the connection. SYNAC FLOW stores the site's ID, name and address, but not your name, email address or account ID.
  • Git servers (for example Forgejo, Gitea or GitHub): with the access key you enter, reading the repositories you allow, including their branches, the files that describe the software packages and container images they use, their pull requests and the results of the checks of these pull requests, and creating branches, commits, pull requests and comments in them. SYNAC FLOW stores the address of the server and the names and addresses of these repositories, but no other data of your account, such as your name or email address.
  • Canva: reading your profile and plan features, reading, creating, filling and resizing designs, reading brand templates, and reading and uploading media. Exported files are copied into your organisation's media library and kept until its removal date; Canva's download addresses are not stored. When you choose a design, your browser loads its preview picture directly from Canva.
  • LinkedIn Pages: the company pages on which you are an administrator or content administrator, and publishing posts, pictures and videos as such a page. Posts of a company page are public.
  • TikTok: the identifier that TikTok assigns to your account for SYNAC FLOW only, and your display name; publishing a video or photo with its caption on your account, or sending a video to your TikTok inbox to finish it in the TikTok app, in each case only after you have reviewed the post in the run and chosen its settings (audience, comments, Duet and Stitch, disclosure of commercial and AI-generated content); then reading the status of the post. When you open the review, SYNAC FLOW reads your account's name and current posting options from TikTok without storing them. SYNAC FLOW stores the identifier and the display name and, with the run record, the chosen audience, the publish ID, the status and the IDs of the published post. TikTok also informs SYNAC FLOW when you remove SYNAC FLOW's access (section 9 (2)) and when the status of a post changes, each with the identifier of your account and, as far as TikTok provides them, the IDs and the type of the post and the reason. SYNAC FLOW keeps the status of a failed, published, delivered or publicly visible post with the run record, as when it reads the status itself. If a switched-on workflow of your organisation starts on the status of a post your organisation published, it starts, and its run record keeps the status, the IDs and the type of the post, the reason and the name of the connection (section 6).
  • Discord: creating a webhook in the one channel of a Discord server that you select on Discord's page, and publishing the messages of your workflow steps in that channel through this webhook: text, an embed, files from your organisation's media library, a sender name and picture and, in a forum channel, a thread name. SYNAC FLOW does not read any messages, members or roles and does not ask Discord who you are. SYNAC FLOW stores the webhook, the name you give the connection and the IDs of the server and the channel and, with the run record, the ID and the address of each published message.
  • Notion: the pages and databases of your Notion workspace that you share with SYNAC FLOW on Notion's page, together with their content: adding and updating rows, creating pages, adding content and files from your organisation's media library to pages, and finding rows and reading pages for the later steps of the same run. This content is not stored in the run record; if the run waits, it is kept until the run ends. To let you select a person, SYNAC FLOW lists the names of the people of the workspace, without their email addresses. SYNAC FLOW stores the name and the ID of the workspace and, with the run record, the addresses of the pages it created or changed. It does not store your name or email address, which Notion transmits during sign-in. Notion informs SYNAC FLOW when a page or database you shared changes, for example when it is created, edited, moved or deleted. SYNAC FLOW keeps such a notification only while a workflow of your organisation that starts on such changes is switched on, and otherwise discards it on arrival. Of a kept notification, SYNAC FLOW stores only the kind and time of the change and the IDs of the workspace, of the changed page or database and of its parent, first in the connect service (section 4 (3)) and then with the run record of the workflow it starts (section 6); the notification's own identifier serves only to recognise repeats (sections 4 (3) and 6 (2)). The notification does not contain the content of the page, and SYNAC FLOW does not keep who made the change. Notion may process this data outside the European Union (section 11).
(3) If a workflow step transmits data to another service, it transmits the content entered by the author of the step to the address entered by the author. A “Packages” step also queries public registries of software packages and container images and the European Vulnerability Database of the European Union Agency for Cybersecurity (ENISA); it transmits to them only the names and versions of the packages and container images that it reads from the repository, and the CVE numbers of known vulnerabilities. SYNAC FLOW does not sell this data, does not use it for advertising and does not use it to train AI models.
(4) The legal basis is Art. 6(1)(b) GDPR.

6. The SYNAC FLOW Workspace

(1) In the SYNAC FLOW Workspace we process the data required to provide it:
  • account data: name, email address and sign-in data; passwords only as a hash;
  • data of your organisation: members, roles, workflows, files and connections;
  • run records: which steps ran, their status and their errors; for a run that another system starts through a webhook or HTTP trigger address of your organisation, also the method, query parameters, content type, user agent and content of that call and the time it arrived; for a run that an event of a connected account starts, the type and time of that event and the IDs it names; and, while a run waits for a decision, the post or email that a person is to review before it is sent;
  • a security log of sign-ins and important changes.
The legal basis is Art. 6(1)(b) GDPR and, for the security log and the protection against guessed addresses (paragraph 2), Art. 6(1)(f) GDPR; our legitimate interest lies in the security of the service.
(2) Run records are deleted automatically 30 days after the run started, or after the run ends if it is still waiting at that time. What is held for review before sending is deleted when the run ends; without a decision, the run ends after 30 days, and what nobody approves is not sent. Photos and videos for posts are kept for 30 days on every plan except the Free plan and, on the Free plan, only until they have been posted, at the latest for 24 hours; a file for TikTok, which TikTok retrieves itself after the run, is kept on the Free plan until these 24 hours have passed. They are sent only to the platform you post to. To recognise repeated calls, a record of each call to a webhook or HTTP trigger address, with a hash of the call's identifier and of its content but not the content itself, is deleted after 24 hours; a record of each event that starts a run, with a hash of the event's identifier and of its kept details but not the content itself, is deleted after 7 days. To prevent the guessing of addresses, a keyed hash of the IP address of a call to an unknown address is kept for 10 minutes; the IP address itself is not stored. All other data is kept until it is deleted; you can request deletion at any time (section 9).
(4) When your plan offers rewards, we process the following data under Settings → Rewards:
  • invitation codes: the code we give you, your name, email address and the identifiers of your account and organisation, how long the code is valid and whether it is blocked; when another company enters your code, the name of that company or of its buyer, the date of its first paid purchase, whether it counts and, if not, why. You see only how many friends joined, not who;
  • when you enter a code: the code, the identifiers of your account and organisation and the result;
  • RACI credits: each credit with its reason, start, end and use; to count RACI time, the number of tokens of each RACI question or workflow step and its time, but not the question, the answer or the content of the workflow;
  • creator videos: your creator mark, the platform and address of the public video you submit, the state of its review, the reason if it is not accepted and the months paid. We open only the public page of the video and do not use an account or interface of the platform.
The legal basis is Art. 6(1)(b) GDPR, as the rewards are part of the service you use, and, for checks against misuse such as a code of your own company, Art. 6(1)(f) GDPR; our legitimate interest lies in fair rewards and in RACI being available to all customers. Credits are not paid out in money.
(5) Each record of an invitation code, an invitation, a credit, its use or a creator video is deleted 12 months after it ended (code expired, invitation decided, credit ended or used, video rejected or ended), and your creator mark once it is older than 12 months and none of your videos is kept. The token counts for RACI time are deleted after 90 days.
(6) The Workspace uses only technically necessary cookies, to keep you signed in, to protect sign-ins and forms against forged requests and to remember your display settings. These cookies do not require consent (§ 25(2) No. 2 TDDDG).

7. Google user data

This section describes how SYNAC FLOW processes data from Google accounts that are connected in the SYNAC FLOW Workspace through our Google app.

7.1 Data we access

(1) Our Google app requests only the following permissions: openid, userinfo.email, gmail.send and youtube.upload. It does not request permission to read, modify or delete emails, or to read YouTube data.
(2) SYNAC FLOW receives:
  • the email address of your Google account, to label the connection, for example "Gmail (name@example.com)", and to identify your other connections to the same account when you disconnect one;
  • the authorisation to send emails from your account. Recipients, subject and text are set by a workflow step of your organisation. Gmail returns an identifier of the sent message, which SYNAC FLOW keeps only while the run lasts (7.5);
  • the authorisation to upload videos to your YouTube channel, with the title, description, visibility and made-for-kids setting specified in the step, and, if the step names one, to give the new video a cover picture from your organisation's media library. YouTube returns the identifier of the new video; the run record keeps the video's link;
  • the access and refresh tokens issued by Google and the list of granted permissions.
(3) The content of emails and videos is provided by you or your organisation. SYNAC FLOW does not read it from Google.

7.2 Purposes of use

(1) We use Google user data only for functions visible in SYNAC FLOW: to connect your account, to send the emails and upload the videos described by your organisation's workflow steps when the workflow runs, to display the result of a run, to renew access while the connection exists, and to revoke access at Google when you disconnect.
(2) A workflow runs when a person starts it, or when a trigger that a person of your organisation set up starts it: a schedule, a webhook or HTTP trigger address, or an event of a connected account.
(3) We do not use Google user data for advertising, do not sell it and do not use it to assess creditworthiness or for lending purposes.

7.3 Data protection

(1) We protect Google user data with technical and organisational measures appropriate to the risk (Art. 32 GDPR), in particular:
  • encryption of all connections (HTTPS/TLS), including calls to Google's APIs; the connect service transmits tokens to the Workspace in encrypted form;
  • encryption of stored access and refresh tokens (AES-256-GCM) with keys specific to each organisation, which are kept separately from the database; browsers never receive the tokens, and a running step receives only a short-lived access token;
  • access control: a connection belongs to one organisation and can be used only by members whose role permits building and running workflows; every request is checked against the person's organisation and permissions;
  • internal systems that are not accessible from the internet, and administrative access only for authorised persons with strong authentication;
  • logs and run records without tokens and without the text, subject or addresses of emails. Only a run that waits at a Human Approval or Delay step, at a Git step with the action “Wait for checks”, at a step set to “Review before sending” or at a “Create or edit media” step for a picture, a video or an edit keeps more until it ends (7.5);
  • encrypted backups.
(2) SYNAC.IO personnel do not read Google user data. We access specific data only with your consent, where necessary for security, for example to investigate misuse, or where required by law.

7.4 Sharing and disclosure

(1) Google user data is disclosed only to:
  • Google, to carry out what you requested: sign-in, sending, uploading, renewing and revoking access;
  • the recipients you choose: the addressees of an email, and on YouTube the audience given by the video's visibility (private, unlisted or public);
  • members of your organisation who are permitted to build and run workflows;
  • our technical service providers for hosting in the European Union, as processors (Art. 28 GDPR);
  • other services, only if a workflow step of your organisation transmits data to them, for example another email, an HTTP request or a post on another platform; such a step transmits what its author entered, to the address its author entered;
  • authorities, where required by law.
(2) Google user data is not disclosed to AI providers. In the Workspace, a workflow step that would pass data from a Google account to an AI step is refused before any data is sent (section 8).
(3) We do not sell Google user data and do not transfer it to advertisers, data brokers or information resellers.

7.5 Retention and deletion

(1) Tokens, granted permissions and the email address of the account are stored as long as the connection exists and are deleted immediately when you delete the connection.
(2) Run records, including the links of uploaded videos, are deleted automatically 30 days after the run started; a run that is still waiting at that time is deleted after it ends. You can delete a run earlier in the run history.
(3) Message identifiers from Gmail are kept only while the run lasts. A run that waits at a Human Approval or Delay step (at most 30 days at a time), at a Git step with the action “Wait for checks” (at most 24 hours), at a step set to “Review before sending” (at most 30 days) or at a “Create or edit media” step until Google has created a picture or video (at most two hours, including any wait until a place for it is free) or an edit is finished (at most one hour) keeps what its earlier steps returned until it ends, for example the account's email address, the identifier of a sent message or a text written by an AI step. A step that sends an email through Gmail or uploads a video to YouTube and is set to “Review before sending” also keeps what it is to send until the run ends: for an email its recipients, subject and text, for a video its title, description, visibility, made-for-kids setting and file name, each with the account's email address. Only the person who is to decide can see it, signed in as a member of your organisation who may open the workflow; the email to that person names the workflow and the step and contains a link, but nothing of what is to be sent.
(4) Backups are encrypted and kept only for a limited period; data deleted in the live system remains in a backup until that backup is deleted. After a restore, we delete again what was deleted after the backup was created; a restored Google connection whose access was revoked at Google cannot be used again.

7.6 Limited Use

(1) SYNAC FLOW's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
(2) We do not use data received from Google APIs, including Google Workspace APIs, to develop, improve or train generalised or non-personalised AI or machine learning models, including our own models. This applies to raw, aggregated, anonymised and derived data, regardless of any consent.

7.7 YouTube API Services

(1) SYNAC FLOW uses YouTube API Services. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google's processing of data is described in the Google Privacy Policy.
(2) In addition to deleting the connection in SYNAC FLOW (section 9), you can revoke SYNAC FLOW's access to your data at any time in Google's security settings: security.google.com/settings/security/permissions. Questions and complaints about our privacy practices can be sent to privacy@synac.io.

8. Artificial intelligence

SYNAC FLOW offers separate AI functions: the assistant RACI, AI steps in workflows, AI Chat, pictures and videos with Google, and captions from speech. They process different data.

8.1 RACI assistant

(1) RACI helps you build, check and run workflows. When RACI's AI functionality is enabled, requests are processed using the model service configured for that deployment. RACI never switches to another model or to an external AI provider if that model service is unavailable.
(2) RACI receives your question and the conversation, matching pages of its guide, and the information its tools read with your permissions: your workflows, the status and errors of runs, and the names of your connections. The name of a connection may contain the email address of a connected Google account, and a run record may contain the link of an uploaded video. RACI never receives tokens or the content of emails.
(3) In the Workspace, RACI is operated by SYNAC.IO. When RACI's AI functionality is enabled, its model is self-hosted: an open-weight model run by SYNAC.IO, not by an external AI provider. What RACI receives, including the email address of a connected Google account, is processed only by RACI's service and that model service and is never sent to the company that published the model, for training or for any other purpose. Before we enable it in the Workspace again, we will state here where its model service runs. In an installation, the operating organisation decides which model service is used.
(4) You decide whether your chats are saved as files in the Workspace's file storage, in a folder on your computer, or not at all. Saved chats are kept until you delete them.
(5) RACI's AI functionality is currently not enabled in the Workspace because no model service is running for it. RACI shows only matching pages from its guide, and the Web Agent step, which requires RACI's model, does not run.

8.2 AI steps in workflows

(1) An AI step sends the instructions written in the step, together with values from earlier steps, to the AI provider selected in the step: Anthropic (Claude), OpenAI, Google (Gemini API) or Mistral AI. It uses your organisation's own API key; the provider processes the request under its agreement with your organisation. Whether a provider may retain requests or use them to improve its models depends on your organisation's account and plan with that provider; some free plans allow this. SYNAC FLOW does not send tokens or keys of other connections.
(2) Data from Google accounts is never sent to these providers. In the Workspace, an AI step or Web Agent step that would receive data from a Google account, for example the account's email address, the identifier of a sent email or the link of an uploaded video, is refused before any data is sent. AI steps that use only content written by you or your organisation remain available.

8.3 AI Chat and personal AI plans

(1) AI Chat sends only what a person types, with that AI's earlier answers in the same chat, to the AI chosen by that person, and it has no access to workflows, runs, connections or files; data that SYNAC FLOW receives from connected accounts, including Google accounts, therefore never reaches it.
(2) In the Workspace, AI Chat works with an API key of Anthropic (Claude), OpenAI, Google (Gemini API), Mistral AI, DeepSeek, Moonshot AI (Kimi), Alibaba Cloud (Qwen), xAI (Grok) or Perplexity, or with a person's own Claude plan, to which the person signs in on Anthropic's own page. The provider processes the messages under its agreement with the holder of the key or plan, also outside the European Union (section 11). Whether it may retain messages or use them to improve its models depends on that account and plan; some free plans allow this.
(3) API keys are stored in encrypted form and are never displayed. An AI plan is personal: only the person who added it can see and use it. For a Claude plan, the access granted by Anthropic is kept on our servers by Anthropic's own program, without encryption by SYNAC FLOW, and is used only for that person's chats; when the plan is removed or the person's account is deleted, SYNAC FLOW first signs out and then deletes the access. Chats are saved only as set out in section 8.1 (4), and only the person who saved them can open them in SYNAC FLOW.
(4) AI steps that use a personal AI plan (Claude or ChatGPT through their own programs) are not available in the Workspace, and AI Chat offers no ChatGPT plan there. SYNAC FLOW offers no Gemini plan; Gemini works only with a Gemini API key.

8.4 No training of AI models

(1) We do not use Google user data, whether raw, aggregated, anonymised or derived, nor run records, chats or other data of our customers, to develop, improve or train AI or machine learning models, neither general-purpose models nor our own.

8.5 Pictures and videos with Google

(1) In a media step of a workflow and its editing window, an organisation can create pictures with Google's Nano Banana Pro and short videos with Google's Veo. It uses its own Google accounts: a Gemini API key for pictures and its own Google Cloud project for videos. Google processes the requests under its agreement with the organisation; the requests go directly to Google and not through a service of SYNAC.IO.
(2) A request is sent only when a person starts it in the editing window or when a workflow step set up by the organisation runs. It contains the description written for it (the prompt), which in a workflow can include text from earlier steps of the same run, the pictures chosen for it or created by earlier steps of the same run, and the selected settings. In the Workspace, a step that would send data from a connected Google account, for example from Gmail or YouTube, is refused before anything is sent.
(3) For pictures, Google decides where its Gemini API processes the request; this can be outside the European Union. Veo processes requests only in the United States of America. Before a connection for Veo can be saved, the person confirms that requests are processed there. The transfer takes place at the organisation's request (section 11 (2)).
(4) SYNAC FLOW asks Google not to keep requests for pictures; for videos, Google keeps the result until SYNAC FLOW has retrieved it. The finished picture or video is stored in the organisation's media library with the name of the model and a note that it was created with artificial intelligence, and is deleted under the retention periods of the media library (section 6). SYNAC FLOW does not store the prompt.
(5) The legal basis is Art. 6(1)(b) GDPR. Whether Google may use requests to improve its products depends on the organisation's agreement with Google; under Google's terms for paid use, this does not happen.

8.6 Captions from speech

(1) In the editing window of a media step, a person can have captions made from the speech in the video they are editing. Only when the person starts this, SYNAC FLOW cuts the sound of the project's clips, without music added in the editor, into pieces of at most 30 seconds and converts the speech into text with Voxtral Mini, an open-weight speech model published by Mistral AI. The model receives only these pieces and the language the person chooses, which also marks the language of the captions in the project. In the Workspace, SYNAC.IO runs this model itself on its servers in the European Union; in an installation, it runs only on the operating organisation's own server, if that organisation has set it up. The sound is not sent to Mistral AI or to any other external provider.
(2) The model only converts spoken words into text; it does not recognise who is speaking. The pieces of sound are kept only temporarily: for the editing job until it ends, and the model keeps the last piece and its text in its working memory until the next request replaces them. The model writes neither to disk, and neither the sound nor the recognised words are logged. The recognised text is added to the editing project as caption lines, which the person can check and change before the video is made; when the person asks RACI to in the editing window, RACI can read and change them like any other edit (8.1). The caption lines are kept in the project, also in the earlier versions kept for undoing changes, and are deleted with the project when its workflow is deleted. When a workflow run makes the video, the copy of the edits kept for that run is deleted 30 days after the edit has ended, or earlier with the project.
(3) The person chooses whether the captions appear in the picture of the video or are added as a subtitle file. For a subtitle file, the caption lines, whether typed by the person or made from speech, are stored with the finished video in the organisation's media library and are deleted with it under the retention periods of the media library (section 6). They are sent only to Facebook Pages or LinkedIn, to LinkedIn only if they are in English, as a subtitle file with their language together with the video the person posts there. SYNAC FLOW makes this file only for the upload; it is kept neither in the run record nor in what is held for review before sending. YouTube and Instagram do not receive the caption lines; the person can download the subtitle file in the editing window instead.
(4) The legal basis is Art. 6(1)(b) GDPR. Neither the sound nor the text is used to train or improve the model (8.4).

9. Disconnecting accounts and deleting data

(1) You can delete a connection in SYNAC FLOW under Workflows → Credentials. The stored access is deleted immediately. For a Google connection, SYNAC FLOW first asks Google to revoke the access; this also ends SYNAC FLOW's other connections to the same Google account. For a TikTok connection, “Delete” removes the connection only in SYNAC FLOW; “End TikTok access” also asks TikTok to revoke the access, which ends all of SYNAC FLOW's connections to the same TikTok account. For a Discord connection, SYNAC FLOW deletes the webhook in the Discord channel and asks Discord to end SYNAC FLOW's access to the Discord account. For a Notion connection, SYNAC FLOW first asks Notion to revoke the access.
(2) You can also revoke SYNAC FLOW's access directly with the provider: for Google at myaccount.google.com/permissions, for Facebook and Instagram in your Facebook settings under Business integrations or Apps and websites. Meta then informs SYNAC FLOW, which stops using all your Facebook and Instagram connections in every organisation. For TikTok, remove SYNAC FLOW in the TikTok app under Settings and privacy → Security & permissions → Apps and services permissions; TikTok then informs SYNAC FLOW, which stops using the connections to that TikTok account made before the removal in every organisation, at the latest when they are next renewed. For Discord, delete the SYNAC FLOW webhook in the settings of the channel or the server under Integrations → Webhooks; SYNAC FLOW can then no longer publish in that channel. For Notion, remove SYNAC FLOW in Notion under Settings → Connections; SYNAC FLOW can then no longer access the workspace.
(3) If you ask Facebook to delete your data (Settings & privacy → Settings → Apps and websites, removed apps, Send request), SYNAC FLOW deletes the affected connections together with their stored access, and Facebook shows you a confirmation code with a link to the status of the deletion.
(4) Run records and photos and videos uploaded for posts are deleted automatically (sections 6 and 7.5); you can delete them earlier. To delete your account or other data in the Workspace, contact privacy@synac.io. For data in an installation, contact its administrator. The connect service deletes notifications from providers once they are retrieved and confirmed, at the latest after 7 days, and the hash of your account identifier as described in section 4 (3); it stores no other data about you.

10. The Marketplace

(1) When you buy a workflow on the Marketplace, we process your email address, the language of the page, the workflow, its version and price, the time at which you agreed that the download is available right away, the status of the purchase and the references that our payment service provider gives the payment and the order. We use them to complete the purchase, to send you the email with the download link and the confirmation of your agreement, to provide the download and to let you rate the workflow. The link contains a random code, which we keep only in protected form. To tell you in this email whether you can sign in or create an account, we ask the SYNAC FLOW Workspace whether an account exists for your email address; the answer is not stored. The legal basis is Art. 6(1)(b) GDPR.
(2) Before you enter your email address, a picture check protects the purchase against automated misuse. We keep the state of the check for at most ten minutes. To limit the number of attempts, we use your IP address and a hash of your email address for at most one hour; we do not store your IP address with the purchase. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in protecting the Marketplace and its buyers against misuse.
(3) Our payment service provider, which sells the workflow in its own name, receives the product of the workflow, your email address, so that you do not have to enter it again, the language and identifiers of the purchase. You enter your payment details on its own page; we do not receive them. Section 3 (5) applies accordingly.
(4) We delete a purchase that was not paid after 30 days and keep a paid purchase for as long as commercial and tax law require (Art. 6(1)(c) GDPR).
(5) If you rate a workflow with the link from your purchase email, we store your rating, your text, the name you enter and the link to your purchase, and publish the rating, the text and the name on the page of the workflow; your email address is not published. If you comment with your SYNAC FLOW account, we store the comment, the name shown and references of your account and organisation, and publish the comment with the name. If you report a review or a comment, we store your reason and a reference of your account with the report until we have checked it. The legal basis is Art. 6(1)(b) GDPR for publishing your review or comment and Art. 6(1)(f) GDPR for checking reports and removing content; our legitimate interest lies in a Marketplace without unlawful content. We keep reviews and comments, and removed ones with the reason for their removal, for as long as we keep the workflow (paragraph 7).
(6) If you offer a workflow as an author, we process your author name, the email address you enter for the payout, your account and organisation, the workflow and its texts, the price, our review decision with its reason and the number of sales. We publish the workflow with your author name and name you as its author in the email to buyers. Our payment service provider receives the title, the summary and the price of the workflow, your email address and your percentage, so that it can invite you and pay out your share; for its sign-up and payouts, its own privacy information applies. When someone rates or comments on your workflow, we inform you by email at this address. The legal basis is Art. 6(1)(b) GDPR.
(7) We keep a workflow and its data for as long as buyers can download it with their links, and the records of its sales for as long as commercial and tax law require (Art. 6(1)(c) GDPR).

11. Recipients and transfers to third countries

(1) We use technical service providers for hosting and for sending emails. They process personal data only on our behalf and in accordance with our instructions (Art. 28 GDPR). Our servers are located in the European Union.
(2) If you connect an account with a provider outside the European Union or select such a provider in a workflow step or in AI Chat, data is transmitted to that provider at your request in order to carry out the connection, the step or the chat. Where an adequacy decision of the European Commission exists, the transfer is based on it (Art. 45 GDPR); otherwise it is necessary to provide the service you requested (Art. 49(1)(b) GDPR). The provider processes the data under its own responsibility.
(3) For the purchase of a plan or a workflow, our payment service provider receives the data described in section 3 (5) and section 10 (3); for the payout to authors, the data described in section 10 (6).
(4) We do not sell personal data.

12. Data security

(1) We take technical and organisational measures appropriate to the risk to protect personal data (Art. 32 GDPR), including encrypted transmission (HTTPS/TLS), encrypted storage of the access to connected accounts (with the exception described in section 8.3 (3)), role-based access control and encrypted backups. Section 7.3 describes the measures for Google user data.
(2) Backups are kept only for a limited period; data deleted in the live system remains in a backup until that backup is deleted.
(3) Please report security vulnerabilities to security@synac.io.

13. Your rights

(1) You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR). Where processing is based on Art. 6(1)(f) GDPR, you may object to it on grounds relating to your particular situation (Art. 21 GDPR). To exercise your rights, contact privacy@synac.io; we respond within one month.
(2) You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is:
Der Hessische Beauftragte für Datenschutz und Informationsfreiheit (HBDI)
Postfach 3163, 65021 Wiesbaden
Germany
datenschutz.hessen.de
(3) The website and the connect service are not directed at children under 16.

14. Changes to this policy

(1) We update this privacy policy when SYNAC FLOW or the legal situation changes. The date at the top indicates the current version.