Introduction
Welcome to the privacy policy for the Abena AI SDK. Abena AI SDK is a software development kit by Mobobi Ltd that provides on-device speech processing features (speech-to-text, text-to-speech, and speech-to-intent) for enterprise applications.
This policy explains in clear language what data (if any) Abena AI SDK collects, how it is used, and how enterprise clients can configure or audit the SDK’s data behavior.
Quick Summary
- No personal data collected by default: The SDK does not collect names, phone numbers, contacts, messages, call logs, or location.
- No third-party advertising or trackers: The SDK contains no ads and does not include third-party analytics trackers.
- Enterprise control: Clients can disable optional activation/telemetry by configuration or contract.
Data We Collect (Optional and Minimal)
By default, Abena AI SDK does not collect any data from end users. The core functionality runs on-device. The only information the SDK may collect (and only if explicitly enabled) is shown below.
| Data | What it is | Why it is used | Optional |
|---|---|---|---|
| Anonymous Device ID | A randomly generated identifier used solely to count unique SDK activations. | Activation counting, license enforcement, and abuse prevention (non-personal, non-content). | Yes |
| API Key | A client-provided key that authenticates SDK usage. | License validation and ensuring the SDK instance is authorized to run. | Yes |
Data We Do Not Collect
The Abena AI SDK is designed to avoid collecting personal data. Specifically, the SDK does not collect or access:
- Names, email addresses, phone numbers, or other personal identifiers
- Contacts, call history, SMS, messages, photos, or files
- Audio recordings, live audio streams, or speech-to-text transcripts (sent to Mobobi)
- Location data (GPS), biometric data, or any sensitive personal data
- Behavioral tracking data for advertising or profiling
- Social media logins, friends lists, or profile data
On-Device Processing & Privacy by Design
Abena AI SDK runs speech-to-text (ASR), text-to-speech (TTS), and intent recognition locally on the device. The SDK does not require an internet connection for core speech features.
- User audio and transcripts remain on-device: Audio is processed locally; Mobobi does not receive speech content by default.
- Reduced data exposure: Fewer network calls means less risk of data leakage.
- Enterprise-ready: Supports privacy and compliance requirements by minimizing transmitted data.
Legal Basis for Processing
Because the SDK generally does not process personal data, legal bases are typically not applicable to end-user content. However, if optional technical data is enabled (anonymous device ID and/or API key), Mobobi may rely on:
- Performance of a contract: To provide license validation or activation counting agreed with the client.
- Legitimate interests: To protect against abuse and ensure reliable delivery of SDK licensing and access control.
- Consent (if applicable): If a client application introduces additional data collection outside the SDK’s default behavior, the client is responsible for ensuring appropriate end-user notices and consent where required by law.
Retention & Deletion
If the SDK is configured with no external data collection, Mobobi retains no end-user data. If optional technical data is enabled, Mobobi retains it only as long as necessary for licensing and activation purposes.
- Anonymous device IDs (if enabled): Retained for the duration of the client agreement or as needed for license/activation accounting.
- API keys: Maintained to allow authorized operation; can be revoked/disabled on contract termination.
Enterprise Controls & Auditing
Enterprise clients can configure and verify the SDK’s privacy posture. We can provide documentation on data flows and support network-traffic verification.
- Disable optional data: The SDK can be configured so no device ID or activation data is transmitted.
- Audit-friendly: Clients can monitor outbound traffic to validate that speech content is not transmitted.
- Contractual alignment: Specific data handling requirements can be reflected in the enterprise agreement.
Data Security
Mobobi applies standard security controls appropriate to the limited nature of SDK technical data. Where network communication is used (e.g. optional license checks), transmissions should occur over encrypted channels (TLS/HTTPS).
- Secure transmission: Encryption in transit for any optional network calls.
- Secure storage: Access controls and reasonable security measures for any stored technical records.
- Minimal data footprint: On-device design reduces the privacy impact surface.
Changes to This Policy
We may update this policy from time to time to reflect product improvements or changes in legal requirements. The “Last Updated” date at the top will always reflect the latest revision.
Back to topContact Us
Mobobi Ltd is the developer and provider of Abena AI SDK. If you have questions about this privacy policy or enterprise compliance requirements, contact us:
- Email: info@mobobi.com
- Company: Mobobi Ltd