Claude Connector Privacy Notice

Last updated: October 1, 2026

This notice explains what data moves, and what we keep, when you connect your bruknow workspace to Claude through the bruknow connector. bruknow is operated by Framesoft Solutions Ltda. (NIT 900266799-2), a company registered in Bogotá, Colombia. This notice supplements our general Privacy Policy and applies only to the connector.

1. Who does what

Claude is a product of Anthropic. When you connect bruknow in Claude and approve the request, you authorize Claude to read and, if you allow it, change your bruknow workspace on your behalf. bruknow answers the requests Claude makes for you; it does not see your conversation with Claude.

What Claude receives from bruknow is handled by Anthropic under your own agreement with Anthropic and its privacy policy. Anthropic is not a subprocessor of bruknow for that data: you are the one sending it there, by asking Claude a question that needs it.

For the messages and details of your own customers, you remain the data controller and bruknow the data processor, as described in Section 5 of our Privacy Policy. Asking Claude about a customer conversation sends that conversation to Claude. Make sure your own privacy notice and the laws that apply to you allow it.

2. What bruknow receives from Claude

• The name of the tool Claude is calling and the values it passes: for example the flow to read, the text of a step to change, a message for a test conversation, or the text of a support ticket.
• The technical details of connecting: the name of the application, the address it returns you to after signing in, and the network address the request came from.

bruknow does not receive, request or read your conversation with Claude, Claude's memory, or files you gave Claude.

3. What bruknow sends to Claude

Only the answer to the tool Claude called. Depending on what you ask, that can include:

• Your flows: their steps, texts, settings and review results.
• Your AI assistants: their instructions, rules, playbook and saved versions.
• Your CRM records when you ask about them: contacts with their name, email, phone number, company, notes, tags and custom fields, and deals with their value, stage, comments and activity. A team member only receives the records they are allowed to see in bruknow.
• Your plan, subscription status and usage figures.
• Your connected channels and their status, and your WhatsApp templates.
• Your own support tickets and our team's replies.
• Customer conversations you ask about or search for: the contact's phone number or identifier, the messages exchanged, the values captured in the conversation and the steps it went through; and the recipients and error messages of messages that could not be delivered. A team member only receives the conversations they are allowed to see in bruknow.
• The responses to your web forms when you ask for them: what each person answered, including the name, email and phone number they typed, the names of the files they attached, and the page and campaign they came from. The visitor's IP address and browser are not sent.
• Your campaigns when you ask about them: their names, templates, schedules and delivery figures, and, when you prepare one, how many contacts it would reach with the names and numbers of the first few. A team member who cannot see every contact receives the figures only.
• Your calendar when you ask about it: the titles, times, meeting links and attendees of your events, the name, email and phone number of guests who booked with you, and the times your connected calendar marks as busy. A team member only receives their own calendar.
• Your reports when you ask for them: your support agents' names with their chat counts, response times and ratings; the customers whose chats need attention; the results of your satisfaction surveys with the written answers, without the name of who answered; and the ratings and comments left in your web chat.

Passwords, API keys and access tokens stored in your flows and channels are never sent. Notes our support staff write for internal use on a ticket are never sent.

4. What bruknow keeps

• The connection: which of your accounts connected which application to which workspace, when, and when it was last used.
• Access tokens: kept only in hashed form, so they cannot be read back from our database.
• What you asked to be changed: edits to flows and assistants, published versions, deal comments and stage changes, test conversations and support tickets become part of your workspace like anything created in bruknow itself.
• A record of each change: who made it, through which application, on which flow and what kind of change it was. It appears in your activity log.
• Diagnostics on tickets: when a ticket is opened through the connector, bruknow attaches a summary of your account's status, visible only to our support staff, so they do not have to ask you for it.
• Usage counters: how many AI tokens your workspace's tests used each day, to apply the daily allowance.
• Technical logs: the time of a request, the tool called and whether it failed, as for any other request to the Service.

Apart from the items above, bruknow does not keep the content of the requests Claude makes or of the answers it receives.

5. What we use it for

• To carry out what you asked Claude to do in your workspace.
• To keep the connector secure and prevent abuse, including limits on how often it can be used.
• To answer your support requests.

We do not sell this data, do not use it for advertising or profiling, and do not use it to train artificial intelligence models.

When you ask for a test in which your AI steps answer, the test conversation is processed by the same artificial intelligence providers that generate your bot's replies, as described in our Privacy Policy.

6. How it is protected

• All exchanges use HTTPS.
• Claude signs in with OAuth 2: you approve the connection in bruknow, with your own account, and bruknow never sees your Claude password nor Claude your bruknow password.
• An access token lasts one hour. Every request is checked again against your current role in the workspace, so removing a person from a workspace ends their connector access at once.
• Each workspace's data is isolated from every other workspace's.

7. How long we keep it

• A connection that is not used for 90 days expires.
• When you disconnect an application, its tokens and the connection record are deleted immediately.
• Flows, tickets, test conversations and activity records created through the connector are kept as long as the rest of your account's data, as described in our Privacy Policy.

8. Your choices

• On the approval screen you choose whether the application may only view your workspace or also make changes.
• You can disconnect an application at any time under Connected apps in bruknow, or by removing the connector in Claude.
• The owner of a workspace decides what each member may do; the connector follows those permissions.

You may request access to, correction of, a copy of, or deletion of your data. We respond within the period required by applicable law.

9. Changes to this notice

We may update this notice from time to time. The "Last updated" date above reflects the latest version.