Privacy

Who we are

Kipwise Inc. (“Kipwise”, “we”) is a Delaware corporation at 3 Germay Dr, 4 STE, Wilmington, DE 19804-1127, United States. This policy covers kipwise.com and kipwise.eu, the Kipwise knowledge base, Kipwise Agent in Slack and Microsoft Teams, and the support desk, request desk and Tasks that come with them (together, the “Services”). It explains what we collect, why, where it is stored, who sees it and how to control it.

Questions go to support@kipwise.com. Our Data Protection Officer is at dpo@kipwise.com.

The short version

• Your workspace lives in one region, the United States or the EU, and stays there. Details are under Where your data is stored.
• Kipwise Agent reads Slack and Microsoft Teams messages live to answer. For an ordinary request it does not keep the message text. It keeps short facts (workspace memory) that a Kipwise admin can switch off and delete.
• Kipwise Agent works as the person who asked, with that person’s own access. It writes to another system only after that person presses Approve on a card.
• We do not train or fine-tune AI models on customer data. We do not sell personal data or use it for advertising.
• For the content your team puts into Kipwise, you are the controller and we are your processor. A data processing agreement is available on request.

Our role: controller and processor

Kipwise as controller. For visitors to our websites, for the people who create an account or sign in, for billing contacts, for people who write to us, and for security and fraud prevention, Kipwise decides why and how personal data is used.

Kipwise as processor. For content and data that a customer (the company or team that installed or signed up for Kipwise) puts into the Services, such as wiki pages, Slack and Teams messages the agent reads, support conversations, requests and Tasks cards, the customer is the controller and Kipwise processes it on the customer’s instructions. If you are an employee or a customer of one of our customers, that customer is the one to ask about your data. If you ask us, we pass your request to them.

What we collect

Category	What it includes	Where it comes from
Website and device data	IP address, browser type, language, referring site, pages visited, date and time, and the cookies described below.	Your browser, when you visit kipwise.com or kipwise.eu.
Account and workspace data	Name, email address, profile picture, time zone, Slack, Microsoft or Google user and workspace IDs, workspace name, role (for example admin, member or guest) and settings.	You, your Slack or Microsoft workspace when you sign in or install, and your admin.
Billing data	Company name, billing contact, plan, seats, invoices, credit balance and top-ups. Card details go straight to Stripe and we never see the full card number.	You, and Stripe.
Knowledge base content	Pages, comments, files, folders, tags, reviews and the activity on them. Public pages are visible to anyone with the link.	Your team.
Kipwise Agent data	Requests and replies in Slack or Teams, read live. Workspace memory (short facts, see below). Scheduled tasks and automations. Approval records. A log of each action (which action, who asked, when, whether it worked). Usage records for credits. Files you ask it to handle, kept briefly. Connections to tools such as Gmail or Notion, stored as encrypted tokens.	Your team, and the tools you connect.
Support desk data	The customers your team talks to: name, email address, messages, attachments, ticket history, and visitor details such as page, language, time zone and referrer.	Your customers and your team.
Requests and Tasks	Internal requests, tickets, boards and cards, with their comments and attachments.	Your team.
Messages to us	What you send to support, in chat or by email.	You.

We do not need special categories of personal data (such as health or political opinions) to run the Services. Customers decide what they put into their own content, and should not put such data into the Services unless they have the right to.

Slack and Microsoft Teams data

What the agent reads. When someone mentions Kipwise Agent, replies in a thread with it, or sends it a direct message, it reads the thread it is in, and the channels, files and records that the asking person can reach, to answer. It reads them live from Slack or Teams and sends the relevant text to an AI model to write the reply (see AI processing).

What we store. For an ordinary request, the text of the message and of the reply are not stored in our database. They stay in your Slack workspace, under your own retention settings. What we do store: the thread and channel IDs and the person who asked, which tools ran and whether they worked, how many tokens the request used and what it cost, and the approval cards described below. Scheduled tasks and automations store the instruction that someone asked the agent to run later. In Microsoft Teams, we also keep a transcript of the conversation for 90 days.

Workspace memory. Memory is on by default in each workspace. While it is on, the agent looks at messages that the app can read in channels where it is present, including messages that were not addressed to it, and keeps short facts from them, such as a decision, a preference or a date, with the source channel and a link to the original message. The message text is held encrypted only until the facts are extracted, and then cleared. Messages written by guests are not used. Memory starts with messages posted after installation and does not read back through old history. A fact from a private channel or a direct message is shown only to people who can still read the source. A Kipwise admin can turn memory off, and can delete all saved facts. Anyone can ask the agent to forget a fact. Facts are deleted after 365 days, or after 90 days on Slack Free and Lite workspaces and in Teams.

Approvals. The agent reads without asking. Before it creates, changes, sends or deletes something in another system, it shows a card with the exact action, and the person who asked must press Approve. The card expires after 30 minutes. The agent runs the action with that person’s own credentials, so it cannot do more than they can.

Per-user permissions and tokens. When you connect a tool to Kipwise Agent, you sign in at that tool and grant access yourself. The agent then uses your access, not a shared one, and respects the permissions you have there. Access tokens and approval records are encrypted at the application level with AES-256-GCM. You can disconnect a tool at any time by asking the agent, or by revoking Kipwise in that tool’s settings.

Guests and shared channels. People from other companies in a shared channel, and Slack guests, reach only what their own connection allows. An admin can restrict them further. The agent warns before a personal account is used where someone outside the company can see the answer.

AI processing and model training

To answer a request, the agent sends the relevant text (the request, the thread, and what the tools returned) as a prompt to a large language model (Anthropic’s Claude) hosted on Amazon Web Services Bedrock. For a US workspace this runs in the United States. For an EU workspace it runs in the EU. Under AWS’s Bedrock terms, prompts and outputs are not used to train the underlying models, and are not shared with the model providers.

Kipwise does not train or fine-tune any model on customer data, and does not allow anyone else to. Two functions send data outside the workspace’s region: web search for an EU workspace is run by Bedrock in the United States and receives only the search query, and the AI answers feature of the knowledge base is processed in the United States (see Sub-processors). If you ask the agent to generate an image, the description you give is sent to OpenAI. Using Kipwise Agent from ChatGPT is described below.

AI can be wrong. Kipwise Agent shows the source it used where it can, so you can check it, and it asks before it changes anything. See our Terms of Service for how we treat AI output.

Support desk, requests and Tasks

When a customer of yours writes to your support desk by chat or email, we store the conversation, attachments and visitor details for you, in your workspace’s region. We keep conversation and ticket content for 24 months after the last message, and then delete it with its attachments. Raw inbound email is deleted 14 days after it is processed, and an export file is deleted after 7 days. A Kipwise admin of your workspace can export or permanently delete everything held about one contact. That erases the content, tickets, attachments and visitor details, and leaves only a record with no message text that says an erasure happened. Auto-answers use the same AI processing as the agent and are drawn from your public help center. Requests and Tasks cards are stored for you in the same way as knowledge base content.

How we use personal data, and our legal bases

Why we use it	Legal basis (GDPR and UK GDPR)
To provide the Services you ask for, run your account and process your content.	Performance of a contract. For customer content, we act on the customer’s instructions as processor.
To take payment, send invoices, keep accounting records and meet tax rules.	Contract, and legal obligation.
To keep the Services secure, prevent fraud and abuse, fix errors and measure capacity.	Legitimate interests in running a safe and reliable service.
To understand how our websites and product are used and improve them.	Legitimate interests. Consent where the law of your country requires it for cookies.
To send service messages, and product news and offers to people who signed up.	Contract for service messages. Legitimate interests or consent for news, and you can opt out at any time.
To answer your questions and requests.	Legitimate interests, and contract.
To comply with law and defend legal claims.	Legal obligation, and legitimate interests.

Where your data is stored

Kipwise runs two separate regions on Amazon Web Services: US (us-east-1, N. Virginia) and EU (eu-west-2, London, United Kingdom). A workspace is in exactly one region. Its accounts, knowledge base content, Agent data, support desk, requests and Tasks, with their databases and file storage, live in that region and are not copied to the other. The EU region has its own services, databases and keys. Kipwise Agent installs from kipwise.eu are placed in the EU region.

The following do not stay in the region. If Kipwise staff outside the EU need access to EU data for support or operations, that access is a transfer, covered under International transfers below. Cloudflare delivers and protects our sites and the addresses Slack and Microsoft call, worldwide. Stripe, email providers and the other providers on our Sub-processors page run in their own locations, and that page marks where AI answers and web search are processed in the United States.

Sub-processors and services you connect

We use the service providers listed on our Sub-processors page to run the Services. They process customer data only to provide their service to us, under written terms. We update that page when the list changes, and customers can ask dpo@kipwise.com to be told by email.

When you connect Gmail, Notion, GitHub, Google Drive, Confluence, a CRM or any other tool, Kipwise reads from it and writes to it at your request, with your own permissions. That tool is a third party you directed us to use. It is not our sub-processor, and its own privacy policy applies to what it holds. Slack and Microsoft are the platforms Kipwise Agent runs in, and their terms apply to your use of them.

Who else sees personal data

We share personal data with our sub-processors as above, with the people and workspace admins your team gives access to, with a buyer if Kipwise or its assets are sold, and with authorities when the law requires it or when we believe in good faith that disclosure is needed to protect people, the Services or our rights. We do not sell personal data, and we do not share it with third parties for their advertising. Kipwise staff do not read your content unless you ask, or it is needed to investigate abuse or a failure you reported, or the law requires it.

International transfers

Kipwise Inc. is in the United States. When personal data from the European Economic Area, the United Kingdom or Switzerland is sent to a country without an adequacy decision for it, including to Kipwise Inc. in the United States and to sub-processors there, we rely on the European Commission’s Standard Contractual Clauses and, for the UK, the UK addendum, together with supplementary measures: encryption in transit, encryption of tokens, access controls and the regional design above.

Retention and deletion

We keep personal data while your account is active and as long as needed to provide the Services, resolve disputes and meet legal duties. Specific periods:

Data	How long
Agent workspace memory (facts)	365 days; 90 days on Slack Free and Lite workspaces and in Teams. Earlier if forgotten or deleted by an admin.
Queued message text waiting for memory extraction	Until the facts are extracted, then cleared. Cleared after three failed attempts.
Approval records	Pending cards expire in 30 minutes. Records are deleted 7 days after they were created.
Microsoft Teams transcript	90 days.
Files staged for upload by the agent	Deleted once fetched. A storage rule removes anything left after 1 day.
Action log (which action ran, who asked, whether it worked, usage)	Until the workspace asks us to delete it.
Support desk conversation and ticket content	24 months after the last message. Erased at once on a contact deletion.
Server logs	30 days.
Database backups (Agent, support desk, requests and Tasks)	7 days. A record we delete can stay in a backup until the backup expires.
Knowledge base content	While the workspace is active. Deleted pages can be restored from trash.
Billing records	As long as tax and accounting law require.

When you uninstall or leave. When Kipwise Agent is removed from a Slack workspace, we deactivate the installation, delete that workspace’s memory and queued messages, and delete the accounts that were connected to channels. A workspace admin can ask us to delete the rest, such as settings, per-person tool connections, scheduled tasks and logs, and anyone can ask us to delete their personal data. A Kipwise admin can delete workspace content from the knowledge base. We complete deletion requests within 30 days, and records can remain in backups for up to 7 days after that. To ask, email support@kipwise.com or dpo@kipwise.com, or see Delete your data.

Cookies and analytics

On kipwise.com we set first-party cookies: _kl (your language), _r (the page that sent you to us, used to understand where visitors come from), _t (set by the app to show that you are signed in), kw_consent (your cookie choice, kept for 12 months) and kw_geo (the country Cloudflare reports for your connection, kept until you close the browser). Your theme choice is kept in your browser’s local storage. We use Google Analytics 4 to measure how the site is used, and Google Ads tags to measure whether our ads lead to sign-ups. These set Google cookies and send Google your IP address, device details and the pages you visit. A reviews widget from Elfsight loads on some pages. If you open the chat on the site, it runs on our own support desk. Inside the app we use error reporting and usage analytics from the providers on our Sub-processors page.

Cookie banner. If you visit from the EU/EEA, the United Kingdom or Switzerland, or Cloudflare cannot tell where you are, the site shows a banner with equal Accept and Reject buttons. Until you accept, Google Analytics and Google Ads run in Google Consent Mode with analytics and ad storage denied: they set no cookies, and Google receives only cookieless pings (page address, browser details, IP address). The _r cookie and the Elfsight widget also wait for your acceptance. Elsewhere there is no banner and these run by default. You can change your choice at any time with “Cookie settings” in the footer.

You can also block or delete cookies in your browser settings, and opt out of Google Analytics with Google’s browser add-on or at myadcenter.google.com. The site still works without them.

Your rights

Depending on where you live, including under the GDPR, the UK GDPR, and the laws of California and other US states, you can ask us to:

• tell you whether we process your personal data, and give you a copy;
• correct it, or delete it;
• limit or object to our use of it, including where we rely on legitimate interests;
• give it to you, or to another company, in a portable format;
• withdraw consent you gave, at any time, without affecting the earlier use;
• not be subject to a decision based only on automated processing that has legal or similarly significant effect on you. We make no such decisions.

You can often do this yourself in your account settings. Otherwise email dpo@kipwise.com. We may ask you to prove who you are, and we reply within one month. If your data sits in a workspace that someone else runs, we send your request to that workspace’s admin, who is the controller. We do not discriminate against anyone who uses these rights. You also have the right to complain to your data protection authority. In the EU, that is the authority in your country of residence, work or where you think the law was broken. In the UK, it is the Information Commissioner’s Office.

Security

Our servers run in AWS data centers that hold SOC 1, SOC 2, ISO 27001 and ISO 9001 certifications. Data is encrypted in transit with TLS. Access tokens and approval records are encrypted at the application level. Staff access is limited to those who need it. Services are monitored, and databases are backed up. We build the agent so that it acts with the asker’s own access, asks before it writes, and applies checks against prompt injection from text it reads. No system is completely secure. If we learn of a breach of personal data we hold, we tell the affected customers without undue delay, and the authorities where the law requires.

Children

The Services are for businesses and are not directed to children. We do not knowingly collect personal data from anyone under 13, or the higher age set by local law. If you think a child has given us data, write to us and we will delete it.

Links to third-party sites

Our sites and the Services link to other sites. This policy does not cover them, and we are not responsible for how they handle information. Read their policies.

Communications

If you signed up, we may email you about new features and ask for feedback. Every such email has a way to stop receiving it. We will still send messages about your account, billing and security.

Data from other platforms

The next three sections apply when you connect Google products, use Kipwise Agent from ChatGPT, or connect a Facebook, Instagram or Threads account. They add to everything above.

Google user data

This section applies to the Kipwise Agent, our AI assistant for Slack, when you connect one or more Google products to it. Each Google product is connected separately, by you, through Google's consent screen. The agent only acts when you ask it to in Slack.

What we access and why.

Gmail (gmail.modify): to search your mail, read messages, drafts and attachments you ask about, create, edit and delete drafts, reply to messages, archive, trash or restore messages, mark them read or unread, star them, and apply or remove your existing labels. Emails are only sent after you confirm the send in Slack, either immediately or at a time you schedule.
Google Calendar (calendar.events): to list events on your primary calendar and to create, update or delete events when you ask. Invitation updates are sent to attendees when an event has attendees.
Google Drive (drive.readonly): to search, list and read files and folders you ask about. The agent cannot change, share or delete Drive files.
Google Analytics (analytics.readonly): to list your properties and run reports. The agent cannot change anything in Google Analytics.
Google Search Console (webmasters.readonly): to list your sites and read search performance and sitemap data. The agent cannot change anything in Search Console.
Google Ads (adwords): to read accounts, campaigns, keywords, search terms and performance data. The only changes the agent can make are pausing or enabling a campaign and changing a campaign's daily budget when you ask.

How we use it. We use Google user data only to carry out the request you make in Slack or in ChatGPT and to show you the result there. We do not use it for advertising, we do not sell it, and we do not use it to build user profiles or for any purpose unrelated to the feature you are using.

AI processing. To answer your request, the relevant Google data (for example the text of an email or a file) is sent as part of the prompt to a large language model (Anthropic’s Claude) hosted on Amazon Web Services Bedrock in your workspace’s region (the United States, or the EU for an EU workspace). AWS acts as our sub-processor. Under AWS's Bedrock terms, prompts and outputs are not used to train the underlying models. Kipwise does not use Google Workspace data or any other Google user data to develop, improve or train generalized or non-personalized AI or machine learning models. When you use Kipwise Agent from ChatGPT, Kipwise Agent does not run its own language model on your request; ChatGPT (OpenAI) writes the answer from the results described below.

How we store it. Your Google OAuth access and refresh tokens are stored in our database on AWS in your workspace’s region (the United States, or the EU for an EU workspace), encrypted at the application level with AES-256-GCM. The agent does not keep a separate copy of your mailbox, calendar or files. To operate and troubleshoot the service, we keep a log of each action the agent takes, which records the action, its inputs, whether it succeeded, and the IDs of the items involved. For Google actions the log does not keep the result (such as email text, file text or calendar details), and it does not keep inputs copied from your Google data (an email body or subject, or an event description). For emails you schedule, we keep the draft reference, recipients, subject and delivery status. The agent's replies are posted in your Slack workspace, where they are subject to your Slack retention settings.

How we share it. We do not share or transfer Google user data to third parties except: AWS, which hosts our service and database and runs the AI model; E2B, a code sandbox provider, only when you ask the agent to run an analysis that requires code and that data is part of the analysis; GitHub, where our engineers receive a private error report when an action fails, containing your request, the action's inputs and the error, but never the data the action returned from Google, and with email bodies, subjects and event descriptions copied from your Google data removed from the inputs; Slack, where results are delivered to you; OpenAI, when you use Kipwise Agent from ChatGPT, where the result of your request is delivered to you in ChatGPT; and where required by law. These providers process data only on our behalf to provide the service.

Human access. Kipwise staff do not read your Google user data except with your explicit permission, when necessary for security purposes such as investigating abuse, to comply with applicable law, or to investigate and fix a failure in an action you requested, as described above.

Retention and deletion. OAuth tokens are kept while your Google connection is active. You can disconnect at any time by asking the agent in Slack, for example "disconnect my Gmail": it revokes the access at Google and deletes the stored token immediately. You can also revoke the Kipwise Agent's access at myaccount.google.com/permissions. After you revoke access there, Google rejects our token and we delete the stored token the next time the agent tries to use it. Action logs and scheduled-email records are currently kept until you ask us to delete them. To delete your stored tokens, action logs and any other Google user data we hold, contact us and we will delete it.

Limited Use. Kipwise'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.

Kipwise Agent in ChatGPT

This section applies when you connect Kipwise Agent to ChatGPT. Kipwise Agent only acts when you ask it to in ChatGPT.

What we receive. When you sign in with Slack we receive your Slack user ID, your workspace's ID and name, and your name and email address, to confirm that you are a member of a Slack workspace that uses Kipwise Agent. When you ask, we read from the Xero organisation you connected the invoices, customer names and email addresses, amounts, currencies, dates and statuses needed to answer you; from the Gmail account you connected, the sender, recipients, date, subject and a short excerpt of emails you exchanged with that customer's email address; and we create the Gmail drafts you ask for.

How we use and share it. We use this data only to answer the request you make in ChatGPT. The answer is returned to ChatGPT, which is operated by OpenAI; OpenAI's terms and your ChatGPT settings apply to what ChatGPT does with it. We do not use it for advertising, we do not sell it, and we do not use it to train AI models.

What we keep. For your ChatGPT connection we keep your Slack user and workspace IDs, your name, email and workspace name, and hashed (unreadable) ChatGPT access tokens, until the connection ends; a connection ends when you disconnect it in ChatGPT, when Kipwise Agent is removed from your Slack workspace, or 90 days after you signed in, whichever comes first. We do not keep a copy of your invoices or emails. Each action is recorded in the same action log described above, without the data it returned. To avoid saving the same reminder twice, we keep the recipient and subject of each reminder draft for 2 days.

Your controls. Disconnect Kipwise Agent in ChatGPT at any time. To remove Kipwise Agent's access to Xero or Gmail, ask Kipwise Agent in Slack (for example "disconnect my Gmail"), or revoke it in Xero or at myaccount.google.com/permissions.

Facebook, Instagram and Threads data

This section applies to the Kipwise Agent, our AI assistant for Slack and Microsoft Teams, when a Facebook Page, an Instagram professional account or a Threads profile is connected to a channel. Facebook, Instagram and Threads are run by Meta. A member of the workspace connects each account separately, through the consent screen of Facebook, Instagram or Threads.

What we access and why. The agent reads an account when a person in the channel asks it to. If a member turns on alerts for the channel, the agent also receives each new comment, message, reply or mention that Meta sends us, and posts an alert in the channel. The agent writes to an account only after the person who asked presses Approve on a card in the chat. The card shows the account and the exact content. It expires after 30 minutes. A scheduled automation cannot write through an account.

Facebook Page (pages_show_list, pages_read_engagement, pages_read_user_content, pages_manage_posts, pages_manage_engagement, public_profile, business_management):

• At connection: the agent reads the list of Pages you manage, so you can pick one. It checks that your role on the Page allows posting and receives the Page's access token. It reads your Facebook name, which appears in a message in the channel saying who connected the Page. Facebook's login also asks you to pick the business that owns the Page. We do not read or change ad accounts, business assets or business settings.
• When asked: the agent reads the Page's published and scheduled posts, with their text, links, photos or video and their comment, reaction and share counts. It reads the comments other people left on those posts: the text, the author's name, the time and the number of replies.
• After approval: the agent publishes a post, photo, video, Reel or Story, and can schedule a post. It changes the text of a post it published, deletes a post, photo, video or Reel, and comments or replies as the Page.

Instagram (instagram_business_basic, instagram_business_content_publish, instagram_business_manage_comments, instagram_business_manage_messages, instagram_business_manage_insights):

• At connection: the agent reads the account's username, id and account type, to check that it is a business or creator account.
• When asked: the agent reads the account's latest posts and live Stories (caption, link, like count and comment count), the comments on a post, its direct message conversations, and its insights for the last 1 to 30 days. Insights are reach, views, interactions, likes, comments, saves, shares and, from 100 followers, audience country, age and gender.
• After approval: the agent publishes a photo, a carousel, a Reel or a Story. It comments on a post, replies to a comment, hides or shows a comment, deletes a comment under the account's own posts, and turns comments off or on for one post. It sends a private reply to a commenter. It replies to a direct message from a person who wrote first, inside Instagram's 24-hour window.

Threads (threads_basic, threads_content_publish, threads_delete, threads_manage_insights, threads_manage_mentions, threads_manage_replies, threads_read_replies):

• At connection: the agent reads the profile's id, username and name.
• When asked: the agent reads the profile's posts (text, type and link), the replies under a post, the profile's own replies, the public posts that mention the profile, and its insights. Insights are followers, views, likes, replies, reposts, quotes, link clicks and, from 100 followers, audience country, age and gender.
• After approval: the agent publishes a post (text, image or video, carousel, poll, link preview or quote), a reply or a repost. It hides or shows a reply under the profile's posts. It deletes one of the profile's own posts or replies. A deletion is permanent.

How we use it. We use this data to carry out the requests people make in the channel, to show the results there, and to post the alerts a channel has turned on. We do not sell it. We do not use it for advertising. We do not use it to build profiles of people. We do not use it to train AI models.

AI processing. To answer a request, the relevant data from the account (for example the text of a comment or a direct message) is sent as part of the prompt to a large language model (Anthropic’s Claude) hosted on Amazon Web Services Bedrock in your workspace’s region (the United States, or the EU for an EU workspace). AWS acts as our sub-processor. Under AWS's Bedrock terms, prompts and outputs are not used to train the underlying models.

How we store it. We store this data on AWS in your workspace’s region (the United States, or the EU for an EU workspace). Access tokens are encrypted at the application level with AES-256-GCM, and so are approval records. What we keep, and for how long, is listed under Retention and deletion below and on the Delete your data page.

How we share it. We do not share or transfer this data to third parties, except where the law requires it and except the providers below. They receive it only to provide the service.

• Amazon Web Services hosts our service and database, stores staged files and logs, and runs the AI model.
• Anthropic provides the Claude AI models that write the agent’s replies, which we use through Amazon Web Services Bedrock.
• Typesafe (typesafe.ai, United States) runs the checks that decide how the agent handles a request, for example whether you asked it to stop and which of its specialists should answer. It receives the latest message someone sent the agent, and never the text of comments or messages from your connected accounts or of their alerts.
• E2B, a code sandbox provider, receives text from your account only when you ask the agent to run an analysis that needs code and that text is part of it.
• GitHub receives a private error report for our engineers when an action fails. It contains ids such as team, user, channel and thread, the name of the action and its error message. It never contains your request, the action's inputs or the data the action returned.
• Slack and Microsoft Teams carry your messages and the agent's answers.

Shared channels. A connection belongs to the channel, not to one person. Everyone from the workspace that owns the channel can ask the agent to read the account and, after an approval card, to post or reply as it. For Instagram, this includes reading the account's direct messages. Any member of the workspace can connect or disconnect an account. Guests cannot. Before connecting, the person sees a private card that warns them of this, and the channel gets a message saying who connected which account. People from other companies in a shared channel can only read what the account has published, plus its comments or replies that are not hidden. They cannot write through the account.

Retention and deletion. We keep this data for the periods below.

• Access tokens and connection details: until the connection ends. A connection ends when someone disconnects the account, when the agent is uninstalled from the Slack workspace or removed from the Teams team or channel, or when Meta ends the access and the agent next tries to use it.
• Approval records: deleted 7 days after they were created.
• Alert notices: the text is removed once the notice has been handled.
• Files you attach for Instagram or Threads: deleted once they have been fetched. A storage rule expires anything left after 1 day.
• Microsoft Teams transcript (including the agent's own replies and cards): 90 days.
• Server logs: 30 days. Database backups: 7 days.
• Action log: it records which action ran, who asked and whether it worked. It keeps only the length of any text, not the text. We keep it until you ask us to delete it.

Disconnecting and revoking. Any member of the workspace can disconnect an account by asking the agent in Slack or Microsoft Teams. A card first says that everyone in the channel will lose the connection. When it is approved, we delete the stored connection and its access token. This does not remove Kipwise Agent from the account at Facebook, Instagram or Threads, because the same account may be connected in another channel. To revoke the access, remove "Kipwise Agent" in your Facebook, Instagram or Threads settings. Meta then notifies Kipwise, and we delete the stored connection.

Deletion requests. To have the data we hold about a connection deleted, see Delete your data. We complete deletion requests within 30 days. You can also email support@kipwise.com or dpo@kipwise.com.

Changes to this policy

We may update this policy. We will post the new version here with a new date, and if a change matters, tell customers by email or in the product before it takes effect. Using the Services after that means you accept the change.

EU representative (GDPR Article 27)

Our representative in the European Union and European Economic Area under Article 27 of the GDPR is FatCouple OÜ, Telliskivi 60a/5, B-building, 10412 Tallinn, Estonia. Contact: dpo@kipwise.com. This representative covers the EU/EEA only.

Contact us

Kipwise Inc., 3 Germay Dr, 4 STE, Wilmington, DE 19804-1127, United States. Email support@kipwise.com. Data Protection Officer: dpo@kipwise.com.