Privacy Policy
Last updated: November 12, 2026
Introduction
This Privacy Policy explains how ClusterCode LLC (“AptiveAI”, “we”, “us” or “our”) collects, uses, shares and protects personal data when you use our website at aptiveai.io and its forms, AptiveAI Agents (the Console), and AptiveAI Connect (together, the “Services”).
We play two different roles, and the difference matters:
- For data about the people who use the Services (accounts, billing, and the messages you send us through our website), we decide how the data is used. Data protection law calls this being a controller.
- For data inside your own systems (the mailbox, business software or website that an agent or connector reads because you told it to), we act on your instructions and on your behalf. Data protection law calls this being a processor. You decide what is connected and what an agent is asked to do.
This policy is published in English and in Spanish. If the two versions differ, the English version governs. If you have questions, write to privacy@aptiveai.io.
Information We Collect
On our website. When you use the contact form, we collect your name, email address, company, the reason you are writing and your message. When you complete the online AI Assessment, we collect your company name, email address, phone number and role, and your answers about your business and the systems it uses. We also process technical data about each request, such as your browser, your device and the pages you request. Our telemetry masks your IP address (see “Security”). To stop automated abuse, the forms briefly count requests per IP address in memory. That count is not stored.
Your account. We collect your name, email address, profile photo if you add one, and sign-in details. AptiveAI operates sign-in itself: we keep your password only as a one-way hash, and we record the browsers you are signed in on (browser type, IP address and when each was last used) so you can see and end those sessions, and so we can ask for a code by email on a computer we have not seen. We also record the enterprise, organization and workspace you belong to, your role in each, and your language and notification preferences.
Billing. Stripe processes payments and holds your card details. We see only the card brand, its last four digits and its expiry date, together with your invoices, your subscription status, and the ledger of AI credit and computer time your enterprise has used.
AptiveAI Agents. When you use agents, we store:
- each agent’s configuration: its instructions, the knowledge files you give it and the text we extract from them, its skills and its automations;
- each task: your messages, the agent’s replies, the steps it took, the files you upload and the files it produces;
- the agent’s computer: the pages its browser visits while it works, and a persistent browser profile that holds the cookies, signed-in sessions and saved passwords of the sites you sign it in to;
- the sign-ins you store for an agent, encrypted (see “Security”);
- the approvals an agent asks for, and your answers;
- training sessions, when you train an agent: a record of the steps taken, with screenshots and page snapshots left out;
- usage: the AI credit and computer time each task consumed.
AptiveAI Connect and connectors. We store the credentials of the connectors you set up, encrypted. While a task runs, we process the data a connector reads from your systems. A mailbox connector is read-only: it never sends, deletes, moves or flags a message. A connector to another application’s API can also write to it, and an agent asks a person for approval before it makes such a write. When you use AptiveAI Connect, your own ChatGPT or Claude account sends requests to connectors we host, which pass them to your systems and return the answer. We process the content of those requests only to answer them.
Communications. We keep the emails we send you (task results, invitations, and billing and account notices) and a log of what was sent to whom.
AptiveAI Messaging. When an owner of your enterprise turns it on, your agents can email and text people who do not use the Services, such as drivers or customers, on your behalf and on your instructions. Their email is sent through Amazon SES from your business’s address at notify.aptiveai.io; their texts are sent through AWS End User Messaging from +1 844-571-9591, and start once the mobile carriers approve that number. For this we store, for each message, the recipient’s phone number or email address, where the agent found it, the message as sent, whether a person approved it or an automation sent it, its delivery status and its charge. We also keep your enterprise’s opt-out list: the numbers and addresses that replied STOP, used the unsubscribe link, bounced or complained, or that an owner added, so that no agent of your enterprise messages them again (a STOP to AptiveAI’s number is also kept as a list for the whole number, so no business texts that person). You decide who is messaged and what is said, and you must have each recipient’s agreement to receive the messages; for this data we act as your processor (see “Introduction”). AptiveAI Messaging is not for health information: do not use it to send protected health information or other health details. A recipient stops texts by replying STOP to AptiveAI’s number, which stops texts from every business that uses AptiveAI Messaging. A recipient stops email with the unsubscribe link in every message. Recipients’ phone numbers, email addresses and their agreement to receive messages are never sold and never shared with third parties or affiliates for marketing or promotional purposes. If an agent texted or emailed you through AptiveAI Messaging, reply STOP to stop its texts, and write to privacy@aptiveai.io to ask for your data to be deleted. Text notices from AptiveAI. If you opt in to AptiveAI’s own text notices under Settings > Notifications, we store your US mobile number, that you agreed and when, the wording you agreed to, where you agreed (the settings page) and the address the request came from, and, if you later turn texts off or reply STOP, when that happened; we keep that record after you opt out. Opting in is optional. We use your number only to text you the notices you choose, from +1 844-571-9591, and to honour your opt-out. Reply STOP to opt out or HELP for help, or write to dev@aptiveai.io. We do not sell your number or your agreement, and do not share them with any third party or affiliate for marketing or promotional purposes. We send no marketing by text, and the notices carry no health information.
Whatever you use, we never sell your data, never use it for advertising, and never use it to train, fine-tune or improve any AI model, ours or anyone else’s. How the AI model providers that run your tasks treat it is explained under “AI Models and Training”.
How We Use Your Information
We use the information we collect to:
- run the tasks you start or automate, and operate the connectors you set up;
- measure usage, apply AI credit and bill your enterprise;
- send you in-app and email notices, such as task results, approvals waiting for you, invitations, and account and billing notices like a trial ending or credit running low;
- reply to your contact and assessment requests and, where you asked about our services, propose them to you;
- provide support;
- keep the Services secure: detect and prevent fraud and abuse, enforce account suspensions, and keep audit records of account changes;
- improve the Services, using aggregate usage information only;
- comply with our legal obligations.
Who Can See Your Data
Inside your enterprise. What other people in your enterprise can see depends on their role and on what is shared with them. A task, agent, automation or skill belongs to the person who created it, and other people see it only when it is shared with them or with everyone in a workspace. The owners of a workspace can open any task or agent in that workspace. Owners and admins manage who belongs to your enterprise.
AptiveAI staff. Authorised AptiveAI staff can open a task or an agent when it is needed to provide support, investigate abuse or a security issue, or meet a legal obligation. Staff do not browse your task lists. A task they open is read-only to them, and they can watch an agent’s computer but cannot control it.
Sub-processors and Third-Party Services
We use these service providers to run the Services:
- Stripe: payment processing and invoicing.
- Microsoft Azure: hosting, databases, file storage, telemetry and logs, and the email AptiveAI sends you (such as task results, invitations, and account and billing notices) through Azure Communication Services, in the United States.
- Amazon Web Services: the email your agents send with AptiveAI Messaging, through Amazon SES, and, once the carriers approve AptiveAI’s number, the texts AptiveAI sends to its own users who opted in and the texts your agents send with AptiveAI Messaging, through AWS End User Messaging, in the United States.
- OpenRouter: routes each AI request to the model an agent is configured to use. The operator of that model then processes the request.
- Anthropic: runs Claude models directly, as a fallback when OpenRouter cannot serve a request.
- Google Fonts: the fonts in our emails, which your email program fetches from Google when it displays a message.
Each of these providers has its own privacy policy that governs its use of your data. If we add or replace a provider, we will update this list.
AI Models and Training
AptiveAI holds the accounts with the AI model providers and pays them. You do not supply a model key of your own. While a task runs, its content (your instructions, the pages and documents the agent reads, the results of its tools and the conversation so far) is sent to the provider that runs the agent’s model, through OpenRouter or, as a fallback, directly to Anthropic.
We do not use your content to train, fine-tune or improve any model, and we will not start doing so without your explicit opt-in consent. On every request, we ask OpenRouter to route only to model endpoints that do not collect prompts. If no such endpoint serves the model an agent is configured with, or the requested settings are otherwise unavailable, the request is sent without that restriction to a provider that can serve it, and that provider’s own terms then govern how it treats the request.
AI output can be wrong. Our Terms of Service explain your responsibilities when you rely on it.
Google User Data
When you connect Gmail, Google Calendar or Google Drive as a connector, you sign in with Google and choose to give AptiveAI Agents access. We ask only for the access each connector’s tools need: to read, label, draft and send email (Gmail); to read your calendars and create, change and delete events (Google Calendar); and to read your files (Google Drive, read-only). We also receive your Google account’s email address, so you can see which account a connector uses.
We use this data only to provide the features you ask for: an agent reads, searches, drafts or acts in your Google account when a task you started or scheduled tells it to, and its results appear in that task. To do that work, the data the agent reads is sent to the AI model provider that runs the agent’s model, as described in “AI Models and Training”. We do not use Google user data to train, fine-tune or improve any AI model, we do not use it for advertising, and we do not sell it.
We do not let people read your Google user data except: people in your enterprise who can see a task, as described in “Who Can See Your Data”; people you share the connector with, whose agents can then use it as you allowed; AptiveAI staff, only when you ask us to look at a specific task, or when it is needed to investigate abuse or a security issue or to comply with the law.
Google sign-in tokens are encrypted before they are stored. Content an agent reads is kept in the task’s history for the periods in “Data Retention and Deletion”. Deleting a Google connector deletes the tokens we store for it, and you can also remove AptiveAI Agents’ access at any time from your Google Account’s security settings.
AptiveAI’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.
Data Retention and Deletion
We keep the following data for the periods below, and then delete it automatically:
- Tasks: each tool call, what it returned and the system lines for 30 days after the task’s last activity, except the few lines that record the task’s state (a stored sign-in it filled; the end of a recording or training session), which are kept with the task; the task itself, with its conversation (your messages and your answers, the agent’s replies, and the questions and approval requests it put to you), for 1 year after the task’s last activity. When the agent asks you to approve an action, the request, your answer and the record that you approved it are part of the conversation, and so is the detail of what it proposes when that is a new agent or a change to an agent, its skills, knowledge or training, or to an automation; the detail of any other action, such as a write to another application or a secret it types, is a tool call. The files in a task’s Documents are kept for the periods for files below, not for the task’s. A task that is still working or waiting on someone is kept until it is not.
- Files you upload to a task: 2 days, or 8 hours for a file over 10 MB.
- Files an agent produces: 10 days.
- Files a connector returns: 1 hour in our storage, and removed from the agent’s computer after 5 minutes.
- Files an agent writes while it works on a task (kept only so they come back if the task moves to a new computer, never shown as documents): 8 hours after the task’s last activity, and deleted at once when the task is deleted. They are not kept for a computer you connected yourself.
- Deleted files: recoverable in our storage for 14 more days, and then removed.
- Database backups: 7 days.
- Telemetry, server logs and operational logs: 90 days.
We keep the following for as long as your account exists, or until you remove it:
- your account, enterprise and workspace data, and your agents, automations, skills and knowledge files;
- stored sign-ins and connector credentials;
- each agent’s browser profile, with the sign-ins and cookies of the sites it visited;
- the log of emails we sent, and audit records of account changes;
- the record of the messages your agents sent through AptiveAI Messaging (each message’s recipient, status and charge; the text of a message follows its task and is deleted with it, on the task periods above), and your enterprise’s opt-out list;
- the messages you sent through our website’s contact and assessment forms.
If you cancel your subscription (or ask us to cancel it), your enterprise is permanently deleted the day after the subscription ends — for a cancellation you make yourself, the day after the paid period ends — with all its data: its workspaces, agents, tasks, automations, connectors, skills, knowledge files, stored sign-ins and files. If you reactivate before the period ends, nothing is deleted. The people in it keep only their own sign-in, with access to nothing. What outlives the deletion: the audit record of account changes and of staff access, which records the deletion itself; a record of each AI model call your agents made (the model, its size in tokens and its cost, never its content); the deleted files, recoverable in our storage for 14 more days and then removed; database backups, for up to 7 days; your customer record and invoices at Stripe, which Stripe keeps; and the browser profiles your agents used, which are stored on our computers apart from the enterprise and deleted when you ask us at privacy@aptiveai.io. A subscription that ends because it was not paid is not deleted this way: the enterprise is cancelled and its data kept until you ask us to delete it, or we delete it.
The product does not offer a self-serve export today. Cancelling your subscription deletes your enterprise and its data the day after the paid period ends, as described above; for any other deletion, or to ask for a copy of your data, email privacy@aptiveai.io or support@aptiveai.io. You can delete your own tasks at any time, and the owners and admins of an enterprise can remove its members. A task you delete leaves the product at once; we keep it, recoverable on request, for 30 days after its deletion, and its conversation for 1 year after its deletion, on the same terms as above. Removing a member from an enterprise does not delete the tasks they ran: those belong to the enterprise’s workspaces and are kept for the periods above. When we delete an enterprise, its tasks are deleted with it.
Some records outlast a deletion request: database backups until they expire after 7 days, and deleted files for their 14-day recovery window. Where we suspend or terminate an account for fraud, abuse or a breach of our Terms of Service, we keep the record of that action and the evidence for it for as long as we need them to resolve disputes, stop the same person returning and meet our legal obligations, even if you ask us to delete your account.
Your Privacy Rights
Subject to applicable law, you have the right to access the personal data we hold about you, to correct it, to delete it, to receive it in a portable format, to restrict or object to its processing, and to withdraw any consent you gave. You may also complain to your local data protection authority.
California residents. The California Consumer Privacy Act, as amended by the CPRA, gives you the right to know what personal information we collect, use and disclose; to delete it, subject to legal exceptions; to correct it; to opt out of its sale or sharing; and not to be discriminated against for exercising these rights. We do not sell your personal information, and we do not share it for cross-context behavioural advertising. You may use an authorised agent to make a request on your behalf.
To exercise any of these rights, email privacy@aptiveai.io. We will respond within the time the law requires: generally one month under the GDPR, and 45 days under the CCPA.
If your request concerns data that we hold on behalf of a customer (for example, data in a customer’s workspace or in the systems it connected), we will pass the request to that customer and help them answer it.
Legal Basis for Processing (EEA, UK and Switzerland)
If you are in the European Economic Area, the United Kingdom or Switzerland, we process your personal data on these legal bases:
- Performance of a contract: to provide the Services you signed up for, including your account, billing and support.
- Legitimate interests: to secure, maintain and improve the Services, to prevent abuse, and to answer business enquiries, balanced against your rights.
- Consent: where it is required, for example for optional cookies. You may withdraw your consent at any time.
- Legal obligation: to comply with applicable laws, including tax and accounting requirements.
International Data Transfers
ClusterCode LLC is based in the United States, and the Services are hosted on Microsoft Azure in the United States. If you use the Services from outside the United States, your personal data is transferred to and processed in the United States. The AI model providers that run your tasks may process requests in other countries.
We comply with the data protection laws that apply to us. Where the law requires a safeguard for transfers from the EEA, the UK or Switzerland, we rely on appropriate mechanisms such as the European Commission’s Standard Contractual Clauses. We do not yet publish a standard data processing agreement. Business customers who need one can contact us.
Security
Each agent works on its own isolated computer. Data is encrypted in transit and at rest, and stored sign-ins and connector credentials are also encrypted by our application with AES-256-GCM before they are stored. An agent asks for your approval before an action that cannot be undone. Where we can recognise the values of stored and flagged secrets, we hide them from task history, although very short values stay visible. We do not record your agent’s screen: the live view is relayed to you and is not stored. Access to our production systems is limited to the people who need it.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security. We hold no security certification today. If we become aware of a personal-data breach that affects you, we will notify you without undue delay and, where the law requires it, notify the relevant authority. You can read more on our Security page, and report a vulnerability to security@aptiveai.io.
Children’s Privacy
The Services are for businesses and for people who are at least 18 years old. They are not directed to children, and we do not knowingly collect personal information from anyone under 18. If we learn that we have, we will delete it promptly. If you believe a minor has given us personal information, contact privacy@aptiveai.io.
Sensitive and Regulated Data
You decide what your agents and connectors can reach, and you are responsible for having the right to process the personal data in those systems. AptiveAI does not offer a HIPAA Business Associate Agreement today, so do not use the Services to process protected health information without a written agreement with us. We can mark a workspace as holding regulated data, which turns off agent training for that workspace.
Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will post the updated policy here with a new “Last updated” date and, where appropriate, notify you by email or with a notice in the product. We encourage you to review this page periodically.
Contact
If you have questions about this Privacy Policy or about your data, contact ClusterCode LLC at privacy@aptiveai.io.