Data processing agreement
This agreement covers how Appsotech Limited processes personal data on your behalf when you, as a customer, use Appsocom Live. It's part of the Terms of service and applies automatically to every account. If you need a signed copy, write to legal@appsocom.dev.
Draft, not yet in force. This agreement is being reviewed by our lawyers and may change before launch. Last updated 19 November 2026.
Draft change pending lawyer review (19 November 2026): the parts about the in-app AI assistant (conversations, voice transcripts, the audit log and their retention in section 6, the processing in Annex 1) and the new subprocessor entries for Anthropic, Deepgram and Cartesia in Annex 3 are new and have not yet been reviewed by our lawyers.
1. Roles
- You are the controller of the personal data of your end users and the other people whose data goes through the Service ("customer personal data").
- We are your processor. We process customer personal data only to provide the Service.
- "Data protection law" means the Nigeria Data Protection Act 2023 and its regulations, and, where they apply, the EU and UK GDPR and any other law that applies to the processing.
2. Our commitments
We will:
- process customer personal data only on your documented instructions. The Terms of service, your configuration of the Service, and your API calls are your instructions. We'll tell you if we think an instruction breaks data protection law;
- make sure everyone who can access customer personal data is bound by confidentiality;
- apply the security measures in Annex 2;
- use subprocessors only as described in section 4;
- help you, as far as is reasonable and taking into account what we process, to respond to requests from data subjects, carry out impact assessments and consult regulators;
- tell you without undue delay, and within 48 hours of becoming aware, of a personal data breach affecting customer personal data, with the information we have, so you can meet your own duty to notify (72 hours under the Nigeria Data Protection Act and the GDPR);
- delete or return customer personal data when the agreement ends, as described in section 6;
- make available the information you reasonably need to show compliance with this agreement, as described in section 7.
3. Your commitments
You will:
- have a lawful basis, and give the notices and get the consents the law requires, for the processing you instruct, including recording, captions, transcripts, summaries, AI agents and avatars, the in-app AI assistant, live streaming and phone dial-in;
- tell your end users when they are talking to an AI assistant, and decide what your assistant's tools return and what you put in an assistant token's
context, because that is what the assistant's AI model sees; - only send us the personal data you need to;
- avoid putting sensitive personal data (such as health data) in metadata, room names, user IDs, webhook payloads, assistant instructions or assistant token
contextunless you need to, and turn on end-to-end encryption where it fits your use; - keep your API keys secure.
4. Subprocessors
You authorise us to use the subprocessors in Annex 3. We'll give you at least 30 days' notice by email before adding or replacing a subprocessor. If you object on reasonable data protection grounds, we'll try to find a solution. If we can't, you may end the affected part of the Service and get a refund of unused prepaid credit. We impose data protection terms on each subprocessor that are at least as protective as this agreement, and we remain responsible for them.
When you connect a third-party service yourself, such as a YouTube or Facebook stream target, or your own webhook endpoint, that service is not our subprocessor. You're sending the data there.
5. International transfers
Our subprocessors may process customer personal data outside Nigeria. For transfers out of Nigeria, we rely on the grounds in Part VIII of the Nigeria Data Protection Act, including adequate safeguards in our contracts. For personal data from the EEA, UK or Switzerland, the EU Standard Contractual Clauses (and the UK addendum) apply between you and us, and between us and our subprocessors, where needed.
6. Retention and deletion
- Live media (audio, video and screen shares) is relayed in real time and not stored, unless you turn on recording.
- Shared files are deleted when the room has been empty for 2 minutes.
- Recordings, transcripts and summaries are stored until you delete them through the API, or until 30 days after your account closes.
- AI assistant conversations (your end users' messages, the assistant's answers, the tool calls it made and what your tools returned, thumbs up or down and comments, and the text of what was said in assistant voice calls) are deleted automatically a set number of days after the conversation's last message: 90 days unless you set a shorter or longer period (1 to 730 days) for the project or for one conversation. You can delete a conversation at any time through the API. Assistant voice calls are not recorded as audio.
- The AI assistant's audit log (each change the assistant proposed, who confirmed or cancelled it, the tool's arguments and a shortened result, and hand-overs to your staff) is kept so you can show who approved what. It isn't deleted with a conversation and has no automatic expiry yet. We'll delete it on your written request, and it is deleted with your other data when your account closes.
- Usage records tied to your account are kept for billing as described in our Privacy policy.
- Backups are overwritten on their normal cycle, within 35 days.
7. Audits
On request, once a year, we'll answer a reasonable security questionnaire and give you summaries of our security measures and of our subprocessors' independent certifications (such as Cloudflare's SOC 2 and ISO 27001 reports). If the law or a regulator requires more, we'll agree on a reasonable audit at your cost, with 30 days' notice, during business hours and under confidentiality.
8. Liability and order of precedence
Liability under this agreement is subject to the limits in the Terms of service. If this agreement and the terms conflict about personal data, this agreement wins. If the Standard Contractual Clauses apply and conflict with this agreement, the clauses win.
Annex 1: Details of the processing
| Subject matter and duration | Providing the Service for as long as you have an account, and the deletion period after it |
| Nature and purpose | Relaying real-time audio, video and data between participants; optional recording, live streaming, captions, transcription, summaries, AI agents and avatars, phone dial-in and file sharing; an optional AI assistant inside your apps, which answers your end users by text or voice using an AI model, the tools you connect and your knowledge base; usage metering; webhooks |
| Data subjects | Your end users and anyone else who joins rooms in your apps, including people who dial in by phone, and the people who use the AI assistant in your apps |
| Categories of data | Participant IDs, display names and metadata you set; IP addresses and connection data; audio, video and screen content; chat messages, polls, questions and files; captions, transcripts and summaries; recordings; phone numbers of callers who dial in; AI assistant conversations, including the user ID, name, role and context you put in the assistant token, what your tools return, voice call transcripts, ratings and the audit log of proposed and confirmed changes |
| Sensitive data | Only what you or your end users choose to share in calls. Use end-to-end encryption and avoid recording where calls include health or other sensitive data, unless you need it |
Annex 2: Security measures
- Encryption in transit: TLS 1.2+ for the API, console and signalling; DTLS-SRTP for all media; optional end-to-end encryption, where media is encrypted on your end users' devices with a key we never see.
- Encryption at rest for stored data, provided by Cloudflare R2 and D1.
- Access control: short-lived, signed participant tokens with per-role permissions; API keys stored hashed and revocable from the console; per-project isolation.
- Production access limited to named Appsotech staff, with multi-factor authentication on infrastructure accounts.
- Rate limiting and bot checks (Cloudflare Turnstile) on sign-up and log-in.
- Logs kept for no more than 30 days unless needed for an investigation.
- Regular dependency updates, code review, and a security review before major releases.
- Incident response: on-call monitoring and the breach notice in section 2.
Annex 3: Subprocessors
| Subprocessor | What it does | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting and compute (Workers, Durable Objects), real-time media (Realtime SFU and TURN), storage (R2, D1), live streaming (Stream), AI models for captions, transcripts, summaries and agents (Workers AI), email delivery | Global network; company in the United States |
| Africa's Talking Limited | Phone dial-in: carries callers' audio and phone numbers between the phone network and the Service | Kenya and Nigeria |
| [VPS provider] | Runs the phone gateway that connects dial-in calls to rooms | [location] |
| Anthropic, PBC | Claude AI models: writes the AI assistant's answers (messages, instructions, context, tool results and knowledge passages are sent to it for each answer) and is the language model for AI agents and lessons | United States |
| Deepgram, Inc. | Speech to text (and some voices) for AI agents, AI lessons and AI assistant voice calls, used only when one of those is in use | United States [confirm] |
| Cartesia, Inc. | Text-to-speech voices for AI agents, AI lessons and AI assistant voice calls, used only when one of those is in use | United States [confirm] |
| OpenAI, Simli, Anam, D-ID | Optional speech, voice and avatar models for AI agents and avatars, used only when a room uses a feature that needs them | United States and [confirm] |
Paystack processes payments, but only for our own billing with you. It doesn't receive customer personal data, so it isn't listed here.