Privacy Policy

Effective: 2026-10-03 · Last updated: 2026-10-03

1. Who we are

BeeGentic is a workflow automation service. It is a product of CleverCreator AI, Inc. ("CleverCreator", "we", "us", "our"), which operates from the United Kingdom. For the personal data described here, CleverCreator decides how and why it is used (we are the "controller"), except where section 4 says we act for you.

This policy covers the BeeGentic app, the BeeGentic docs site (docs.beegentic.ai) and the connections you make from BeeGentic to other services. Your CleverCreator account, plan and payments are covered by the CleverCreator Privacy Policy.

Contact us about privacy through the CleverCreator contact form or at support@beegentic.ai.

2. The short version

• We use your data to run the workflows you build. Nothing else.
• We do not sell your data and we do not use it for advertising.
• We do not train AI models on your data, and we don't let anyone else do so.
• Data from Google, Facebook, Instagram, Threads and other connected services is used only to perform the actions your workflows ask for.
• You can disconnect any account and delete your BeeGentic account at any time. See User Data Deletion.

3. What we collect

Account data. Your name, email address and profile picture. If you sign in with email and password, we store a hash of your password, never the password itself. If you sign in with your CleverCreator account, CleverCreator sends us your account ID, name, email address and profile picture.

Session and security data. When you sign in we record a session with your IP address and browser type. We use it to keep you signed in, protect your account and investigate abuse.

Workflows and workspace content. The workflows you build, the blocks and settings in them, files you upload, knowledge bases, tables, variables, schedules and comments.

Run logs. Each time a workflow runs, we record when it ran, whether each step succeeded, how long it took and the inputs and outputs of each step. These logs can include content from your connected accounts, for example an email subject, a spreadsheet row or the text of a post, because that is what the step handled. Logs let you see and debug your runs.

Connected accounts. When you connect an account (for example Google, Slack, Notion, LinkedIn, Facebook, Instagram, Threads, X, Bluesky, Mastodon, Buffer, ChatterMate or TutorMigo), we store the access token, refresh token and permissions that service gives us, plus the account's ID, name or email so you can tell your connections apart.

API keys and secrets you add. For example, your own AI provider keys (OpenAI, Anthropic, Google and others), ChatterMate or TutorMigo keys, or other values you save as secrets.

Support messages. What you send us when you ask for help.

What we don't collect. We don't use analytics, advertising or tracking cookies, and we don't run third-party tracking scripts in the app or on the docs site. Product telemetry is switched off.

4. How we use your data

Purpose	Data used	Legal basis (UK/EU GDPR)
Provide BeeGentic: sign-in, building and running your workflows, schedules and triggers	Account, workflows, connected accounts, secrets, files	Performance of our contract with you
Show you run history and help you fix failed runs	Run logs	Performance of contract
Keep the service secure, prevent abuse and fraud	Session and security data, logs	Legitimate interests (keeping the service and our users safe)
Answer support requests	Support messages, the data needed to investigate	Performance of contract; legitimate interests
Send service emails (for example security or account notices)	Email address	Performance of contract; legitimate interests
Meet legal obligations	Whatever the law requires	Legal obligation

When your workflows process personal data about other people (for example your customers' emails or form responses), you decide what is processed and why. For that data we act on your instructions as your processor, and you are responsible for having a lawful basis and giving any notices required.

People at CleverCreator only look at your workflow content, logs or connected-account data when you ask us to (for example in a support request), when it is needed for security or to investigate abuse, or when the law requires it.

5. Connected accounts and OAuth access

• You choose which accounts to connect and which permissions to grant. Each service shows you the permissions on its own consent screen.
• We only call a connected service when one of your workflows, triggers or settings screens needs it. For example, a Gmail trigger checks your inbox for new messages, and a Facebook Page block publishes the post you configured.
• You can disconnect an account in BeeGentic at any time (Integrations, open the connection, Disconnect), or revoke access in the other service's settings. Disconnecting deletes the stored tokens for that connection.
• The other service's own terms and privacy policy apply to data you keep there.

6. Google user data

BeeGentic'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. The use of information received from Google Workspace APIs will also adhere to the Google Workspace API User Data and Developer Policy.

What this means in practice:

• What we access. Depending on the Google blocks and triggers you use and the permissions you grant: Gmail (read, label, modify and send messages), Google Sheets, Drive, Docs, Calendar, Forms, Tasks, Contacts, YouTube (including uploading videos you choose) and the other Google services listed on the consent screen.
• How we use it. Only to provide the features you set up in BeeGentic: running your workflows and triggers, showing you the results in your run logs, and letting you pick files, calendars or channels in the editor.
• We don't sell Google user data, use it for advertising (including retargeting or interest-based ads), use it to decide on credit or lending, or transfer it to anyone except as needed to run your workflows, for security, to comply with the law, or as part of a merger or acquisition with your prior consent.
• We don't use Google user data to create, train or improve any AI or machine-learning model, ours or anyone else's.
• People don't read it unless you ask us to (for example in a support request), it's needed for security or abuse investigations, or the law requires it.
• Your workflow decides where data goes. If you build a workflow that sends Google data to another service (for example, an AI step or Slack), that transfer happens because you configured it.

You can remove BeeGentic's access at any time at myaccount.google.com/permissions.

7. Facebook, Instagram and Threads (Meta) data

When you connect a Facebook Page, an Instagram professional account or a Threads profile, Meta gives BeeGentic access to that account with the permissions you approve.

• What we access. For Facebook: the list of Pages you manage and the business portfolios they belong to, permission to publish posts on those Pages, and the engagement data Meta returns for them. For Instagram: your professional account's profile, publishing, comments, messages and insights. For Threads: your profile, publishing, replies, insights and deleting your own posts. We only use the parts your workflows actually call.
• How we use it. To publish the content you configure, to read what is needed for that (for example which Pages you can post to and whether a post succeeded), and to perform the reads and replies your workflows ask for (for example fetching comments or insights). Results appear in your run logs.
• We don't sell Meta Platform Data, use it for advertising or profiling, share it with data brokers, or use it to train AI models.
• Deletion. Removing BeeGentic in your Facebook, Instagram or Threads settings tells us automatically, and we delete the stored access for that account straight away. See User Data Deletion.

8. AI features

• Your own AI keys. AI steps (such as the Agent block) use the AI provider and key you choose, or your ChatterMate key. The prompt and the data your step sends go to that provider under your own agreement with them.
• Built-in AI helpers. The Generate buttons in the editor and knowledge-base search use an OpenAI account run by CleverCreator. When you use them, the text you typed (and, for knowledge bases, the content of the documents you upload) is sent to OpenAI to produce a suggestion or a search index. OpenAI states that it does not use API data to train its models by default.
• No training. We do not use your workflows, logs, files or connected-account data to train AI models.
• AI output can be wrong. Check it before you rely on it or publish it.

9. Who we share data with

• Service providers (subprocessors) that host and run BeeGentic for us, under contracts that limit their use of the data. The current list is on the Subprocessors page.
• Services you connect or send data to. When your workflow calls Google, Meta, Slack, an AI provider or any other service, we send that service the data your workflow sends. You choose these; they are not our subprocessors.
• CleverCreator services. If you sign in with your CleverCreator account or connect ChatterMate or TutorMigo (other CleverCreator products), the data needed for that feature is exchanged with those services.
• Legal and safety. When the law requires it, or to protect the rights, property or safety of our users, the public or CleverCreator.
• Business transfers. If CleverCreator is involved in a merger, acquisition or sale of assets, data may transfer as part of it. We'll tell you before your data becomes subject to a different privacy policy.

We do not sell or rent personal data, and we do not "share" it for cross-context behavioral advertising as US state laws define those terms.

10. Where your data is stored

BeeGentic runs on servers in the United States (a Hostinger data center in Boston). Uploaded files are stored in Microsoft Azure in the United States (East US). If you are in the UK or EU, your data is transferred to the US. Where required, we rely on appropriate safeguards for these transfers, such as the UK International Data Transfer Addendum or the EU Standard Contractual Clauses.

11. Security

• All traffic to BeeGentic uses HTTPS (TLS).
• API keys and other secrets you save are encrypted in our database with AES-256-GCM.
• OAuth tokens for connected accounts are stored in our database, which is not reachable from the internet.
• Server access is limited to key-based SSH for a small number of administrators, behind a firewall.

No system is completely secure. If you think your account or data has been put at risk, contact us right away.

12. How long we keep data

Data	How long
Account data	Until you delete your account
Workflows, files, knowledge bases, tables	Until you delete them or your account
Run logs	As long as the workspace they belong to exists. Deleting a workspace or your account deletes its logs
Connected-account tokens	Until you disconnect the account, revoke access at the provider, or delete your BeeGentic account
Secrets and API keys you saved	Until you delete them or your account
Sign-in session records (IP address, browser)	Until you delete your account
Server logs (errors and requests, kept for troubleshooting and security)	No longer than needed for those purposes, normally up to 90 days
Support messages	As long as needed to resolve the request, then up to 2 years for reference

When you delete your account (Settings → General → Delete account), we delete your account, the workspaces only you own, their workflows, logs, files and connections. Workspaces you share with other members are transferred to another member instead of being deleted. Copies in backups are overwritten on a rolling basis.

13. Your rights

Depending on where you live (including under the UK GDPR, the EU GDPR and US state privacy laws such as California's), you can ask us to:

• tell you what personal data we hold about you and give you a copy;
• correct it;
• delete it;
• give it to you in a portable format;
• restrict or object to how we use it;
• withdraw consent where we rely on consent.

Many of these you can do yourself in the app: edit your profile, disconnect accounts, delete workflows, or delete your account. For anything else, contact us through the contact form. We may need to confirm your identity first. We won't treat you differently for using your rights. If you authorize someone to act for you, we may ask for proof.

If you're in the UK you can complain to the Information Commissioner's Office (ico.org.uk); in the EU, to your local data protection authority. We'd appreciate the chance to sort it out first.

14. Cookies and local storage

• The app uses only the cookies needed to sign you in and keep you signed in, and to keep sign-in and connection requests secure. No analytics or advertising cookies.
• The docs site uses no cookies. It saves your guide progress in your browser's local storage; that never leaves your device.
• Services you are sent to (for example a Google or Meta sign-in page) set their own cookies under their own policies.

15. Children

BeeGentic is for adults and businesses. It is not meant for anyone under 18, and we don't knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.

16. Changes to this policy

We'll update this page when our practices change and change the "Last updated" date above. If a change materially affects how we use your data, we'll tell you in the app or by email before it takes effect.

17. Contact

CleverCreator contact form · support@beegentic.ai