1. Who we are and what this policy covers
afka is a product of Afka, Inc., a Delaware corporation at 2810 N Church St STE 89857, Wilmington, DE 19802, United States. afka gives a company AI colleagues that receive work in a chat channel, plan it, act in its connected tools within the autonomy that company sets, and report back. Every action an agent takes is written to an append-only audit record.
It covers the website at afka.ai, the application at app.afka.ai, the voice surface at talk.afka.ai, the agents in a customer’s connected channels, the meeting assistant, the website chat a Customer places on its own website, the support inbox that receives the support email a Customer forwards to afka, the interview by link a Customer sends to candidates, and the public application programming interface (together, the Services).
Two roles run through it. For content flowing through a customer’s workspace, the customer is the controller and afka the processor, acting on that customer’s documented instructions under the Data Processing Agreement: if your data is there because you work at that company or dealt with it, your request goes to them and afka assists. For account administration, billing, security telemetry, product analytics and afka’s own website, afka is the controller.
Definitions used in this policy
- Customer: the organisation holding an afka workspace under the afka Terms of Service.
- Customer Data: content submitted to, generated in or retrieved by the Services on a Customer’s instructions: channel messages in conversations an agent is part of, meeting transcripts, voice text, tasks, runs, artefacts, approvals, workspace knowledge, and connected-account data.
- Connected Channel: a surface a Customer binds to its workspace: Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord, ClickUp, the web application, email, the voice surface and the public application programming interface.
- Customer-Enabled Integration: a third-party platform or account a Customer connects, or to which it directs an agent.
- Sub-processor: a third party afka engages to process Customer Data on afka’s behalf.
- Autonomy: the per-agent setting deciding how much an agent may do before asking a named human.
2. The information afka collects
- Account and workspace information: user identifier, name, email address, workspace and organisation identifiers, role and capabilities, identity provider identifiers where single sign-on is used, and session and device metadata. For the voice surface installed on a phone, the push address the phone’s browser gives afka for that installation, its public encryption key and an encrypted secret, so afka can send notifications to it.
- Connection references: the platform, the account, the scopes granted, the member who connected it and its status. For a connector reached through the connector platform the OAuth grant is held there and afka holds only a reference to it, in the platform secret vault.
- Workspace content: tasks and their prompts, plans, runs, artefacts, approvals and their context, agent outputs, workspace knowledge and its embeddings.
- Channel messages: an agent reads the conversations it has been added to and direct messages addressed to it, not the whole of a workspace. It reads every channel and chat it has been added to, in every chat app, with no per-channel setting, and stops reading a channel when it is removed from it. Within those, afka receives message content and metadata: sender and recipient identifiers, display names and timestamps.
- Meeting and voice data: where the afka meeting assistant is invited to a call it joins as a named, visible participant and announces itself. afka transcribes; it does not record video and keeps no recording library. Stored: the transcript, the associated speech recognition samples, participant identifiers and display names, meeting title, times and outcomes. For the voice surface, speech converted to text, with session metadata.
- Voice audio: afka stores the text of what was said on Talk and in an interview by link, not the audio: no afka voice surface turns call recording on. The platform has a store for call recordings, used only for a call recorded with the participant’s opt-in. A recording there is kept for thirty (30) days unless the workspace sets another period, and a purge removes the record of an expired recording. The voice provider that carries the call is a sub-processor listed in Section 4; for an interview by link it is told to keep no transcript, recording or logs.
- Website chat and support inbox: where a Customer places the afka chat on its own website, afka receives what a visitor types, the page the chat was opened on, browser and network metadata, and, when the visitor gives them, a name, an email address and an order number. Where a Customer forwards its support address to afka, afka receives the emails sent to it, with sender, recipients, subject, body and attachments, and sends the replies from the Customer’s verified domain. afka handles this data as the Customer’s processor. The chat tells the visitor it is an AI assistant and links to the Customer’s own privacy notice, which governs that visitor’s data. Where the Customer turns on Remember returning visitors and the visitor has agreed, the chat also remembers the first name the visitor gives and the topic of the last conversation, so it can greet the visitor on a later visit (Section 5.E).
- Interview by link: where a Customer invites a candidate to an interview by link, afka receives the candidate’s spoken answers converted to text, the candidate’s agreement given on the interview page, and session metadata. afka handles this data as the Customer’s processor, and every hiring decision is the Customer’s.
- Service, usage and billing data: audit entries, application and infrastructure logs, error and security telemetry including content security policy reports, credit consumption in an append-only ledger, and billing and transaction metadata. Card details are handled by afka’s payment provider, never stored by afka.
- Analytics and communications: usage events, website measurement and visitor-identification data after consent (Section 5), and support and sales correspondence.
Data afka asks you not to send. The Services are not designed, certified or intended for protected health information, payment card data, non-public financial information, special categories of personal data under Article 9 of the GDPR, criminal conviction data, personal data of children under sixteen (16), or export-controlled data. Submitting it is prohibited by the DPA.
3. How afka uses information
- To provide the Services: receive work in a Connected Channel, plan it, carry it out in connected tools within the configured autonomy, seek approval where required, and report back.
- To run the AI processing behind the output: content is sent to the AI providers described in Section 4 for inference, and model-written code runs in an isolated sandbox. Outputs are probabilistic and the Customer remains responsible for reviewing them.
- To secure, support and bill: authentication, tenant isolation, abuse and fraud prevention, bot detection, rate limiting, metering, payment and service notices.
- To improve the Services and create aggregated or de-identified data from metadata about how the Services are used: counts, timings, outcomes and labels from a fixed list, never the content of what users say, write, upload or record. A figure that combines customers covers at least ten workspaces, and no single workspace makes up more than a quarter of it. afka keeps de-identified data in de-identified form, publicly commits not to attempt to re-identify it, and contractually requires the same of anyone it shares such data with. Data obtained through Google APIs never enters a figure that combines customers, and data from Slack, Microsoft, Zoom and Discord is used only as their platform terms allow. afka does not use Customer Data to train general-purpose AI models, and requires the same of its providers.
- To market afka’s own products to business contacts, subject to Sections 5 and 8, and to comply with law and defend claims.
afka does not sell personal data for monetary consideration, does not use Customer Data for advertising or cross-context behavioural profiling, and never sells any information about a named customer. Depending on your jurisdiction, some website analytics described in Section 5 may count as a sale, a sharing or targeted advertising; the consent control there is how to stop it.
4. Sub-processors and how afka shares information
A. Current sub-processors
Each is engaged under a written contract imposing obligations in substance no less protective than those afka owes its Customers, and afka remains liable for its performance. afka gives at least thirty (30) days notice before a new one processes Customer Data, and a Customer may object under Section 7.3 of the DPA.
Current sub-processors:
| Sub-processor | Purpose | Data it may process |
|---|---|---|
| Supabase | Managed Postgres database, authentication including SAML single sign-on, realtime, server-side function execution, object storage and the secret vault. | Workspace and account records, user identifiers and authentication events, tasks, runs, approvals, artifacts, the audit record, meeting transcripts, the credit ledger, and the connection references held in the vault. |
| Render | Application hosting for the web application, the public application programming interface, the background worker, the static sites and the voice ingress. | Request metadata and application logs, and Customer Data in transit through the application while a request is served. |
| Cloudflare | The managed challenge used to distinguish humans from automated traffic, and custom hostname termination for Customer-facing pages. | Network metadata, the address a request comes from, and the result of the challenge. No workspace content. |
| Upstash | Managed key value store used as a hot cache and for per-tenant rate limits. | Short-lived cached values keyed to a workspace, and rate limit counters. |
| Temporal Cloud | Durable orchestration of long-running agent work. | Workflow state, and the inputs and results passed between the steps of a run. |
| E2B | Isolated microVM execution of model-written code. | The code an agent writes and the data that run is given to work on, for the life of the run. The guest is destroyed when the run ends. |
| TypeSafe | Closed-label decisions: choosing one label from a fixed set for a member’s message, such as the kind of request it is or the agent it belongs to. | The text of a member’s message for each decision, with afka’s question and the list of labels to choose from. No credentials, files or other workspace content. |
| Pipedream | The connector platform through which a Customer connects third-party accounts and through which connected-account actions are carried out. | The authorisation grant for a connector it manages, and the data passing to and from the connected account within the scopes the Customer granted. |
| Recall.ai | The meeting assistant that joins a scheduled call as a named participant and returns the transcript. | Meeting audio during the call, the resulting transcript, participant names and call metadata. There is no video recording. |
| Retell AI | The live voice agent that conducts a spoken conversation on the voice surface. | Call audio, the transcribed turns of the conversation, and call metadata. |
| Cartesia | Text to speech for the voice surface. | The text an agent speaks, and the audio generated from it. |
| Soniox | Real-time speech to text for the meeting agent. | Meeting audio during the call, and the text recognised from it. |
| Amazon Web Services (Amazon Transcribe) | Optional speech to text for the meeting agent, for a workspace set to use it, reached through Recall.ai. | Meeting audio during the call, and the text recognised from it. |
| Postmark | Transactional email sent by the Services, and inbound mail reception for the email channel. | Sender and recipient addresses, subject and body of the messages sent and received, and delivery results. |
| Resend | Internal notification and follow-up email sent by the Services, and inbound mail reception for the email-to-knowledge address. | Recipient addresses, and the content of the messages sent; for received mail, the sender, subject, body and attachments. |
| Device push services (Apple Push Notification service for iPhone and iPad, Google Firebase Cloud Messaging for Android, and the Mozilla push service where used) | Carrying notifications to the installed voice app. | The device’s push address, and an encrypted message the push service cannot read: a short summary of what needs attention, or a fixed phrase with at most a reference. The details open in the app. |
| Loops | Lifecycle email. | The name and business email address of an account contact, and lifecycle events. |
| PostHog | Product analytics for the application, on United States infrastructure, served through a first-party proxy at e.afka.ai. | Usage events, page views, and user and workspace identifiers. No message, transcript, email or task content is sent to it. |
| Stripe | Payment processing and subscription billing. | Billing contact details, and transaction and subscription metadata. Card details are handled by Stripe and are not stored by afka. |
Each processes only what its function requires, under contract, and each is bound by confidentiality and data protection terms.
The table above is the current list. It forms part of the Data Processing Agreement and is the list Section 7 of the DPA refers to. A Customer is given notice of an addition or a replacement in advance of that sub-processor processing Customer Data, and may object to it, by the mechanism Section 7 of the DPA sets out. To have a copy sent to you, or to subscribe a further address for change notices, write to privacy@afka.ai.
Changes to this list. October 13, 2026: TypeSafe and Amazon Web Services (Amazon Transcribe) were added. Notice of the addition is given under Section 7.3 of the DPA, and the right to object runs from the date of that notice.
The providers measuring the marketing website are named in Section 5: they process visitor data, not workspace content.
B. AI providers
afka uses a small number of AI model providers under contract:
- Anthropic: the primary language models, in use whenever an agent runs.
- Moonshot: a live fallback tier for the language models, reached when the primary provider is unavailable or degraded.
- Soniox: real-time speech to text for the meeting agent, reached while afka is in a call.
- OpenAI: speech to text only, reached when a voice or meeting feature is invoked.
- Voyage AI: embeddings, used to index the workspace knowledge base and to run a retrieval step over it.
- Tavily: the web research step, reached when a task requires research on the public web.
afka names a provider here only where that provider is in use.
- Current list: the providers named above are the providers in use, and they also appear in the sub-processor table in Section 4.A on this page. That list is maintained under Section 7.3 of the DPA, and a change to it is notified in advance.
- Data residency: inference runs on United States infrastructure. afka does not offer European Union data residency and does not claim it.
- Provider retention: providers may retain data temporarily under their own policies for security and abuse monitoring. Each request is processed in isolation, invisible to another Customer.
- No training: Customer Data is not used to train general-purpose AI models, by afka or its providers. This reflects the contracts in effect with each; if afka learns of a change materially reducing that protection it gives notice through the sub-processor change process, which carries thirty (30) days notice, an objection right and a route to terminate.
C. Customer-Enabled Integrations are not afka sub-processors
The provider of a platform a Customer connects is not a sub-processor of afka solely because the Customer connected it, unless it appears on the sub-processor list described in Section 4.A. Data is transmitted there at the Customer’s instruction and within the scopes granted, and what that provider does with it is governed by the Customer’s own agreement with it. The Customer is responsible for the scopes it grants, the notices and consents required, and compliance with that platform’s terms. Where a provider appears in both roles, its status as an afka sub-processor covers only afka’s use of it.
D. Tools afka uses to run its own business
afka also uses ordinary business tools of its own. They hold afka’s own records, including the contact details of people who enquire, and they are not processors of Customer Data. They are Attio, afka’s customer relationship system; Dub, for creator and affiliate links; Notion, for internal task tracking; GitHub, for source control; and Instantly, for afka’s own outbound sales.
E. Other disclosures
afka may disclose personal data where required by law or lawful request, or where necessary to protect rights, property or safety, or to defend legal claims; where permitted, afka informs the Customer first. On a merger, acquisition or sale of assets, data may transfer to the successor under this policy or one no less protective.
5. Cookies, analytics and the afka website
A. Strictly necessary cookies. The application sets cookies and browser storage needed to sign you in, keep your session, remember your workspace and protect against automated abuse. These load without consent because the Services cannot function without them.
B. The marketing website: two providers. In the United States, in Canada outside Quebec and in Australia, our analytics load when you arrive, and you can opt out at any time with Opt out in the cookie banner; opting out stops them and clears their cookies. Everywhere else, neither loads until you consent in the cookie banner.
- Google Analytics 4 measures visits, pages viewed, referral source and campaign performance, showing which pages and campaigns work.
- RB2B performs reverse-IP visitor identification. Stated plainly: it takes a visitor’s network address and attempts to identify the company that visitor works for, so afka’s sales team can see which companies have visited. afka names it because a visitor should know it is running before consenting.
If you decline, neither script loads at all. You can change or withdraw your choice at any time through the cookie control on the website. afka loads no advertising or social-media tracking pixels.
C. Product analytics inside the application. The application uses PostHog, on United States infrastructure, behind a first-party proxy at e.afka.ai so requests go to an afka domain rather than a third-party one. It records usage events, page views and user and workspace identifiers, showing which parts of the product are used and where they fail. It is not used for advertising, and message, transcript and task content is never sent to it.
D. Your controls. Browser controls can block or delete cookies, though blocking strictly necessary ones stops the application working. Every marketing email carries an unsubscribe link; unsubscribing leaves service and security notices in place.
E. The afka chat on a Customer’s website. The chat script keeps a conversation identifier in the visitor’s browser storage so a conversation continues across pages. It sets no cookie unless the website that shows it has the visitor’s agreement to remember a returning visitor. With that agreement, and only where the Customer has turned on Remember returning visitors, it keeps one random token made by afka in a first-party cookie and in the browser’s storage, and afka keeps against that token the first name the visitor gave, the topic of the last conversation and, only when the visitor asks to continue on another device, the visitor’s email address. These are kept for the period the Customer sets, from thirty (30) days to two (2) years after the visitor’s last visit (one hundred and eighty (180) days unless the Customer changes it), and are then deleted. A visitor can remove the token with the chat’s “Not you?” option or by clearing the browser, and the Customer can delete everything remembered about a visitor by that visitor’s email address. It reads no property of the browser to recognise it, loads no analytics or advertising script, and is not used to follow a visitor across sites. The Customer is responsible for describing it in its own privacy and cookie notice.
F. The afka chat on afka.ai. afka uses the same chat on its own website, where afka is the controller and the basis is your consent. If you accept optional cookies in the banner, the chat may remember the first name you give and the topic of your last conversation, so it can greet you when you come back, using one random token in a first-party cookie and in your browser’s storage. If you ask to continue on another device, afka also keeps your email address to send you the link. afka keeps these for one hundred and eighty (180) days after your last visit and then deletes them. If you decline, or later withdraw your choice, the chat remembers nothing and the token is removed. You can also choose “Not you?” in the chat, or write to privacy@afka.ai, to have everything the chat remembers about you deleted.
G. Pages viewed this visit, for a Live demo. On a website that shows afka’s Live demo or its chat, the afka script keeps the paths of the pages you view on that website in your browser’s session storage, for this visit only: the address without anything after a question mark or a hash, at most twenty, never the content of a page. They stay in your browser, on that website’s own domain, and are cleared when you close the tab. They are sent to afka only when you yourself start a Live demo, and then only so the demo agent can ask better questions (for example, noticing you looked at Pricing). If you start the Live demo from the offer inside the website chat, the chat tells you first that what was written in that chat during this visit goes with it, the last ten lines at most, so the demo agent does not ask you again; a Live demo started any other way takes no chat. What is sent is kept with the record of that demo, is not used for advertising or to follow you across websites. Nothing is sent before you press the button.
6. Where data is stored and how it is protected
A. Location
afka stores and routinely processes personal data in the United States: application hosting, the background worker, the voice ingress, caching, rate limiting and product analytics run in United States regions.
The primary managed database is located in the United States, in the East US (North Virginia) region.
afka does not offer European Union data residency.
B. The controls that carry the most weight
Tenant isolation is enforced in the database, by row level security on every tenant table with FORCE on the core tables, and the model never holds a credential: a backend gateway injects it at execution time. The security page covers these, the approval floors and the transport controls. Three points bear directly on personal data.
- Model-written code runs in an isolated microVM, one guest per task, destroyed after the run and never reused across workspaces, with short-lived scoped tokens rather than long-lived secrets, and CPU, memory, wall-clock and credit caps. Network egress from the sandbox is denied by default.
- The audit record cannot be edited or deleted. Every action an agent takes is written to it, not only the actions that required an approval, and append-only is enforced by a database trigger that rejects any update or delete of a row: application code cannot rewrite history and neither can afka. A row carries the actor, action, target, timestamp, credit cost, run identifier, the authorising approval where one was required, and whether a human or an agent initiated it. It carries no meeting speech, message or email bodies, document contents or task prompts, and Customers can export it in CSV and NDJSON.
- Secrets and tokens. Application programming interface keys, directory bearer tokens and mobile link tokens are stored as a SHA-256 hash, shown once and never retrievable. Connection references are held in the platform secret vault; for a connector managed by the connector platform the OAuth grant is held there and afka holds only a reference.
C. Encryption at rest
Encryption at rest is a property of the underlying managed database, storage and hosting providers, provided by them rather than implemented by afka.
D. Access by afka personnel
Access to production platforms is granted on the principle of least privilege, authenticated at each provider, and revoked when no longer required. There is no routine access to Customer content: afka staff do not read Customer messages in the ordinary course, and support access is limited to what the matter requires. Everyone authorised to process Customer Data is under a written confidentiality obligation surviving their engagement.
7. How long data is kept
A. Automatic deletion windows
Speech captured from meetings is deleted on a rolling thirty (30) day window by a scheduled job that runs daily: meeting transcripts and the associated speech recognition samples are deleted; the stored request text of a task that came from a meeting and the spoken instruction held in the context of a meeting approval are emptied; and the request text that a correction kept is emptied, in each case while the record itself is kept. Content security policy reports are deleted at thirty (30) days. The IP address, city, region and time zone of a sign-in, and the last known IP address, city and region of a device, are cleared after ninety (90) days; the country is kept.
Push delivery records hold the push service, the HTTP status, the size and the time of each attempt, and never the message. They are deleted a whole calendar month at a time, so each is kept for at least thirty-one (31) days and for at most about sixty-two (62) days. A notification record is deleted ninety (90) days after it is created. A push subscription is marked revoked when the push service reports it gone or when the person has no workspace left, and is deleted with the person’s account.
What the chat remembers about a returning visitor (Sections 5.E and 5.F) is deleted automatically when its period ends, counted from the visitor’s last visit. A pending approval that is not decided in time is marked expired, and an abandoned voice session is closed after thirty (30) minutes; neither record is deleted by those jobs. Website chat conversations, visitor contact details, support emails, interview transcripts and the words of a request made to afka are Customer Data: no scheduled job deletes them, so they are kept for the term and deleted on the Customer’s request or after termination, as set out below. Other scheduled jobs remove short-lived technical records that hold no customer content, such as rate limit counters and de-duplication keys for incoming webhooks and emails.
B. Deletion during the term
A Customer can delete data through the Services: a task and its content; a single call and its transcript, which the Services refuse until the meeting assistant has been removed from that call; and a connected account, by disconnecting it. On disconnection of a connector managed by the connector platform, afka revokes the connection there by an application programming interface call and records it in the audit record; because the OAuth grant is held by that platform, no afka-side token record exists to delete. Any further written deletion request is actioned within sixty (60) days, subject to Section 7.E.
C. After termination
On termination or expiry, on deletion of the account, or otherwise after the end of the Services, a Customer has thirty (30) days to export or request the return of its data, with self-service export of the audit record in CSV and NDJSON and assistance for anything further. If it does not, that is a deemed instruction to delete the data including existing copies, and afka does so within sixty (60) days after that thirty (30) day period ends. After the export window the data may not be recoverable. On written request within sixty (60) days of completion, afka confirms the deletion and identifies anything retained.
D. Backups
afka operates no backup infrastructure of its own. Backup and point-in-time restoration are functions of the managed database and hosting platforms, and backup media are overwritten in the ordinary course of those providers’ rotation. afka publishes no backup retention period and does not represent that deletion from active systems is at once reflected in backups.
E. Legal hold
afka may retain personal data where required by law, or under a reasonable legal hold for actual or anticipated litigation, investigation or dispute, retaining only what is required and only so long as required. Billing and tax records are kept for the periods the law requires.
F. What is not deleted: the audit record
The audit record described in Section 6 is not deleted and cannot be deleted: append-only is enforced by a database trigger, so it survives deletion of the underlying working data. The audit record contains no speech or message content. A row may still contain identifiers that are personal data, such as the name of the person who acted; where a Customer needs those erased to answer a data subject, afka will discuss in good faith what can be done consistently with the record’s integrity, whose retention it considers necessary to defend legal claims and to secure processing.
8. Your rights and choices
Depending on where you live, you may have the right to access the personal data held about you, to have it corrected or deleted, to receive a portable copy, to object to or restrict processing, to withdraw a consent, and not to be discriminated against for exercising these rights.
Which door to knock on depends on the roles in Section 1. If your data is in a Customer’s workspace, that Customer is the controller: write to them. If afka is the controller (your account, your billing records, your visit to the website), write to privacy@afka.ai.
- Response times: afka responds within forty-five (45) days, extendable once by a further forty-five (45) days where the request is complex, with notice of the extension and its reason. Identity may need to be verified first.
- Appeals: if afka declines a request you may appeal, by replying to the decision or writing to privacy@afka.ai with the words Privacy Appeal in the subject line. Where your state allows, you may also complain to its attorney general.
- Authorised agents: where the law allows, an agent may submit a request on your behalf with proof of authority.
- Withdrawing consent and disconnecting: a Customer can disconnect any connected account from the application, revoking the connection at the connector platform; a member can remove an agent from a channel; the meeting assistant can be cancelled or removed; and analytics consent can be withdrawn through the cookie control in Section 5.
- Complaints: in the EEA, the United Kingdom and Switzerland you may complain to your local supervisory authority; afka asks that you raise it first.
9. International transfers
Where personal data is transferred to afka out of the European Economic Area, the United Kingdom or Switzerland, the transfer is made under the European Commission Standard Contractual Clauses, and under the United Kingdom International Data Transfer Addendum where the UK GDPR applies, each as incorporated by Section 8 of the DPA. The measures relied on are in Annex II of that document.
EU representative under Article 27 of the GDPR. Afka, Inc. has designated Dmitry Melnik, established in Poland, as its representative in the Union for the purposes of Article 27 of the GDPR. Data subjects and supervisory authorities in the European Economic Area may contact the representative at privacy@afka.ai, and afka asks that correspondence be marked for the attention of the EU representative.
10. Google user data and Limited Use
afka’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
afka’s own Google application requests only the three scopes in the table below. It requests no sensitive and no restricted scope.
| Scope | What it permits | Why afka requests it |
|---|---|---|
| openid | Confirming that the person signing in is the holder of a Google account. | To sign a person in with Google, and to identify the Google Workspace that installs the afka Google Chat app. |
| userinfo.email | Reading the email address of that Google account. | To create the afka account and sign the person in. |
| userinfo.profile | Reading the name and profile picture of that Google account. | To create the afka account and sign the person in. |
Sign in with Google
When a person chooses Sign in with Google, afka receives the name, email address and profile picture of that Google account. afka uses them only to create the account and sign the person in. They are kept with the account record in afka’s database (Supabase, Section 4) for as long as the account exists, and are deleted with it as Section 7 describes. afka never sells them, never uses them for advertising and never uses them to train artificial intelligence or machine learning models.
The afka Google Chat app
When a Google Workspace installs the afka Chat app, afka asks the installing person for openid, userinfo.email and userinfo.profile once, to identify the Workspace the app is installed in. The access token from that step is revoked at Google immediately, and afka keeps no standing Google grant from it. The app then receives and answers the messages addressed to it through the Google Chat API, using a Google service account with the chat.bot scope. That scope belongs to the app itself: no user is asked to approve it on a consent screen.
Gmail and Google Calendar
Gmail and Google Calendar are connected through Pipedream Connect (Section 4), not through afka’s Google application. The user consents to Pipedream’s application. afka receives only what each action returns, within the scopes granted, and never the credentials.
Limited Use commitments
These commitments apply to all Google user data afka receives.
- afka uses data from these scopes only to provide and improve user-facing features prominent in the afka interface: sending mail, reading and scheduling calendar events, and operating an agent in a Google Chat space at the user’s instruction.
- afka does not transfer it to others except as necessary to provide or improve those features, to comply with law, or in a merger, acquisition or sale of assets with the notice and consent the law requires. Sub-processor transfers fall under Section 4.
- afka does not use that data for serving advertisements and does not sell it.
- afka does not use that data to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models, whether afka’s own or a model provider’s.
- No person at afka reads it. afka does not allow humans to read data obtained through these scopes, with four exceptions: the affirmative agreement of the relevant user for specifically identified data; necessity for security purposes, such as investigating abuse; a requirement of law; or data that has been aggregated and de-identified.
- A user may revoke access at any time by disconnecting the account in the afka application, or at myaccount.google.com/permissions. Disconnecting revokes the grant at the connector platform and records it in the audit record.
11. Platform and marketplace compliance
Each block states what afka receives on that platform, what it commits to, and how to revoke access. Across all of them an agent reads only the conversations it was added to and direct messages addressed to it, never a whole workspace; platform data is used only to operate that Customer’s agents, write the audit record and support the Customer; and it is never sold or used for advertising.
A. Slack
What afka receives. Workspace and team identifiers, user identifiers and display names, and message content and metadata in channels the app was added to and direct messages with it.
Commitments. afka does not use data obtained from the Slack application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models. afka requests the narrowest scopes its features need.
Revoking access. A workspace owner or administrator can remove the app in the Slack administration settings, revoking the grant; removing it from one channel stops the agent reading it.
B. Microsoft Teams
What afka receives. Tenant, team and channel identifiers, user identifiers and display names, and message content and metadata in conversations the app is part of. Where the meeting assistant is invited to a call, the transcript and participant identifiers.
Commitments. afka does not use data obtained from the Microsoft application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models. Access is limited to the permissions the administrator consents to.
Revoking access. A tenant administrator can remove the app from Teams, or revoke its consent in the Microsoft Entra administration console.
C. Google Chat
What afka receives. Space identifiers, user identifiers and display names, and messages addressed to the application in spaces it was added to, with metadata. The scope is chat.bot, described in Section 10.
Commitments. The Limited Use commitments in Section 10 apply in full here: afka does not use data obtained from the Google application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models, and does not allow humans to read it save for the four exceptions listed there.
Revoking access. Remove the application from the space, disconnect the Google account in afka, or revoke at myaccount.google.com/permissions.
D. Zoom
What afka receives. In Zoom Team Chat: account and channel identifiers, user identifiers and display names, and message content and metadata in conversations the agent is part of. Where the meeting assistant is invited to a call: the transcript, participant identifiers and display names, and meeting metadata. It joins as a named, visible participant and announces itself; afka transcribes and does not record video.
Commitments. afka does not use data obtained from the Zoom application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models. Transcripts and speech recognition samples are deleted on the rolling thirty (30) day window in Section 7.
Revoking access. An account owner or administrator can uninstall afka from the Zoom App Marketplace management page. A Customer can cancel the assistant before it joins, or remove it mid-call.
E. Discord
What afka receives. Guild and channel identifiers, user identifiers and display names, and message content and metadata in channels the application was added to and direct messages with it.
Commitments. afka does not use data obtained from the Discord application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models.
Revoking access. A server administrator can remove the application from the server at any time.
F. ClickUp
What afka receives. Workspace, space, list and task identifiers, member identifiers and display names, and the tasks and comments an agent is asked to work with.
An important disclosure. Delivery into ClickUp uses the credentials of the member who linked the account, read from the secret vault for each delivery. Comments and updates the agent makes therefore appear under that member’s own name, not a separate application identity. A Customer should tell that member first.
Commitments. afka does not use data obtained from the ClickUp application programming interfaces to develop, improve or train generalised or general-purpose artificial intelligence or machine learning models.
Revoking access. Disconnect the ClickUp account in the afka application, revoking the connection at the connector platform, or revoke afka in the ClickUp integrations settings.
12. Children
The Services are business software, sold to organisations for use by their personnel. They are not directed to children under sixteen (16) and afka does not knowingly collect a child’s personal data. Submitting the personal data of a child under sixteen (16) is prohibited by the DPA. If afka learns it holds such data it deletes it; write to privacy@afka.ai if you believe this has happened.
13. Changes to this policy
afka reviews this policy at least annually and updates it when the product or the law changes; the current version is the one at afka.ai/legal/privacy. Where a change materially reduces the protection afforded to personal data, afka gives notice by email to the account administrator of record and by posting to afka.ai/legal before it takes effect. Sub-processor changes follow Section 7.3 of the DPA.
November 5, 2026: the device push services (Apple Push Notification service, Google Firebase Cloud Messaging and the Mozilla push service) were added as sub-processors. They carry only an encrypted message they cannot read. Push is off for a workspace until afka turns it on.
November 6, 2026: Section 7 now states the deletion jobs that run, and the Children section states that the Services are not directed to children under sixteen (16).
November 11, 2026: Section 5.G now describes the pages viewed during a visit, and the chat that is passed to a Live demo when you start it from the chat.
November 12, 2026: Section 5.G now states plainly that nothing is sent before you press the button.
November 16, 2026: Telnyx was removed from the sub-processor list. afka has no phone line and gives agents no phone numbers.
14. How to contact afka
Data protection matters go to privacy@afka.ai: questions about this policy, requests to exercise the rights in Section 8, requests under the GDPR and the United States state privacy laws, correspondence for the EU representative named in Section 9, privacy appeals and questions about a personal data breach.
Everything else goes to support@afka.ai: support, billing, sales and general questions and contract notices. Where formal service by post is required, write to Afka, Inc., 2810 N Church St STE 89857, Wilmington, DE 19802, United States.
See also the Terms of Service, the Data Processing Agreement and the security page.