Trust

How we govern AI

Ordibl talks to your customers on your behalf, so you should be able to see what it does. This page describes the controls in the product. It is not a certification, and it is not legal advice.

Governance

How decisions are governed

  • Rules before every action. Before the AI replies, books, spends or touches data, Ordibl checks the action against platform safety rules, regional rules and your own policies.
  • Strictest rule wins. When layers disagree, the stricter outcome is the one that stands.
  • Fail closed. If the check cannot run, the answer is no.
  • People approve sensitive actions. You choose which actions need a person. The person who asks cannot approve their own request.
  • Roles and access. Owners, admins and staff each see only what their role allows.
  • Spending limits. A hard cap on AI spending, with cost reserved before a call to a model.

Privacy

Your data

  • Separated per organization. Each customer's data is isolated at the database level.
  • Data region. An organization can be assigned a data region. Routing of model calls follows that assignment in the product. This website does not promise a hosting country.
  • Retention and legal hold. The product has controls for how long records are kept, and records under a legal hold stay until the hold is released.
  • Data rights. Export, correction and deletion requests are part of the product.

The marketing chat at ordibl.ai is a scripted preview in your browser. It is not sent to Ordibl.

Transparency

AI transparency

  • AI disclosure. Customers are told they are talking to an AI and can ask for a person.
  • Explanations. For a governed decision, admins can see the outcome, the rule that applied and a plain-language reason.
  • Eight languages. English, Spanish, French, Arabic, Yoruba, Hausa, Igbo and Pidgin are in the catalog. Customer-facing lines are served when reviewed. Greetings on the home page are samples. We do not claim finished voice quality for every language.
  • Recording. This site does not record calls. Call recording is not something we advertise as switched on.

Accountability

Audit and accountability

  • An append-only history. Decisions and actions are recorded in a history the app cannot edit or delete.
  • Who, what, when and why. A record can carry the actor, the rule and the reason.
  • Handover on record. When your team takes over a conversation, that handover can be recorded too.

Regulation

Laws we design with in mind

This is a description of how we build, not a claim of compliance or certification. Your own obligations depend on your business. Please take your own legal advice.

  • Canada: PIPEDA and provincial privacy laws.
  • United States: state privacy laws and telemarketing rules such as the TCPA, as rules the policy gate is meant to be able to enforce. That is not a statement that a given campaign is lawful.
  • Europe: GDPR, where a pilot's data region calls for it.

Subprocessors

Subprocessors

We do not publish a full subprocessor list on this marketing site, and we do not claim a signed data-processing agreement or a Business Associate Agreement here. Before a pilot, ask us which providers that pilot would use. The public website itself loads no third-party scripts and sets no analytics cookies.

Contact

Report a concern

If you think something has gone wrong with a conversation or with your data, contact us and choose Security or Support. Please do not include passwords or full payment card numbers.

Book a demo / join the pilot