Mobobi Ltd Abena AI SDK Privacy Policy
Last Updated: January 19, 2026

Abena AI SDK Privacy Policy

Abena AI SDK provides on-device speech-to-text (ASR), text-to-speech (TTS), and speech-to-intent for enterprise applications. We built the SDK with privacy-by-design: speech processing happens locally on the user’s device.

Developer & Data Controller: Mobobi Ltd Primary principle: No personal data is collected by default

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.

Privacy-first by default: Abena AI SDK is designed to work with on-device processing. By default, the SDK does not transmit speech content (audio or transcripts) to Mobobi or to any third party.
Back to top

Quick Summary

On-device processing Speech recognition, TTS, and intent detection run locally on the device.
No speech content uploaded No audio recordings or transcripts are sent to Mobobi by default.
Minimal optional data Only an anonymous device ID and API key may be used for license/activation management (optional).
  • 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.
Back to top

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
Not mandatory: Both the anonymous device ID and API key mechanisms can be disabled based on client preference or contractual agreement. The SDK can be delivered in a configuration where no data at all leaves the device.
Back to top

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
Mobobi cannot access user conversations. Speech content stays on the device unless the client application itself chooses to handle or store it. Abena AI SDK does not upload speech content by default.
Back to top

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.
Back to top

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.
Defensible destruction: Upon contract termination, expiry of retention period, or written instruction from the client, Mobobi will securely delete any retained SDK-related technical records (if any exist) in line with our internal data destruction procedures and contractual obligations.
Back to top

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.
Tip for technical verification: When auditing, check for outbound requests during SDK initialization. If activation counting is disabled, expected outbound calls should be none.
Back to top

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.
Back to top

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 top

Contact 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:

Note This policy describes the Abena AI SDK. Host applications that integrate the SDK may collect additional data under their own policies.

Related: See our Data Destruction & Retention Procedure for details on defensible destruction on contract termination, retention expiry, or written instruction from an enterprise client.
Back to top