Trust Center
Data privacy information without the usual marketing theater
This page is a plain-language overview of how BuniAI handles customer data and where the platform's current operational boundaries are.
It is not a replacement for our legal documents. It is a clearer way to understand them before you go deeper.
Plain language
1.Our privacy principles
BuniAI is designed for teams building customer-facing chatbot, automation, and USSD experiences. That means privacy is not an optional marketing layer. It is part of how the product is expected to work.
- We try to collect only the information needed to run and support the platform.
- We aim to give users clear control over integrations, analytics consent, and data flows they configure.
- We describe our current setup honestly instead of promising dedicated environments or certification coverage that is not part of the product today.
Operational data
2.What BuniAI processes
To deliver the platform, BuniAI may process account details, workflow configuration, project content, user messages, support requests, usage telemetry, billing records, and credentials or tokens for the integrations you connect.
The exact data involved depends on the features you use. A simple marketing-site visit is different from running production chatbot or USSD workflows with connected third-party services.
Sensitive data handling
4.How credentials and secrets are handled
Many BuniAI workflows depend on API keys, OAuth tokens, webhooks, or other credentials for services you connect. We treat those values as sensitive.
- Credentials are stored in encrypted form.
- They are used only by authorized service processes that need them to execute configured integrations.
- When you revoke or remove an integration, the connected automation may stop working unless fresh credentials are supplied.
Cookie controls
5.How analytics consent works
BuniAI uses necessary cookies to operate the site and application. Those are distinct from optional analytics tooling used to understand product usage and improve UX.
Product analytics and replay tooling are loaded only after consent is granted through the cookie banner. If consent is declined, those scripts are not loaded.
Where possible, sensitive areas and fields are masked or blocked from replay capture.
AI-assisted features
6.How AI providers fit into the product
BuniAI supports AI-assisted features that may involve third-party AI providers when you use model-backed capabilities inside the product.
Inputs needed to fulfill the requested feature may be sent to those providers. The exact data involved depends on the prompt, workflow context, or feature you invoke.
If you need the legally binding description of that processing, refer to the Privacy Policy.
Delivery dependencies
7.Third-party services and subprocessors
BuniAI depends on third-party services to provide hosting, payments, analytics, authentication, communications, AI requests, and optional integrations. Those services may process data as part of delivering the platform.
The exact providers involved can change over time as the product evolves. That is why our legally binding policy focuses on categories of service providers and representative use rather than a fixed trust-center-style vendor catalog that may drift out of date.
Lifecycle
8.Retention, deletion, and privacy requests
We retain data for as long as needed to provide the service, maintain platform security, meet contractual and legal obligations, and resolve operational issues. Retention periods vary by data type.
If you need help with access, correction, deletion, or a similar request, contact us at admin@buni.ai. We may need to verify identity or authority before acting on the request.