The Yara Promise

Why this manifesto exists

Voice AI vendors have published commitments before. Most quietly softened them once scaling pressure, a hostile press cycle, or a regulatory finding made the original wording inconvenient. The original promise gets buried in updated terms of service. The new posture is communicated through silence, not retraction.

We are writing this down before Yara is big enough that this kind of retreat is easy. The category Yara is building — the Fully Autonomous Call Center — touches people at their most vulnerable moments: a denied claim, a delayed reimbursement, a frightening medical bill, an account they cannot access. A vendor that handles those moments without an enforceable promise is not selling autonomy. It is selling abdication.

The Yara Promise is three pledges. To consumers — the people whose voices we process. To customers — the enterprises that buy Yara. To regulators — the bodies whose evidentiary standards keep the whole system honest. Each pledge is specific enough to be checked against. Each one is published so that if Yara ever walks it back, there is a public record to hold us to.

This manifesto is pinned to the homepage and the footer. It does not move. It does not change between sales calls. It is updated only by addition, never by quiet edit. The change log is in the git history of this very file.

The promise to consumers

To the person on the other end of the line who did not ask to be served by an AI.

Your audio stays in the jurisdiction it was spoken in. A call in the UAE never crosses the UAE border in any form — not raw audio, not transcript, not embedding. The model weights are deployed locally; the data residency is binding by architecture, not by promise. The same holds for every regulated market Yara serves.

Your dialect is recognized, not translated. We do not flatten Khaleeji Arabic to MSA. We do not collapse Maghrebi French into Parisian French. The acoustic and language models Yara deploys are trained on the dialect we will hear, not on the convenient majority dialect of the open dataset.

Your PII is encrypted in transit, hashed at rest, and never leaves your jurisdiction. Name, account number, government ID, biometric voiceprint — none of these cross borders, none of these reach a third-party model provider, none of these are retained beyond the regulator's schedule.

You will always know you are speaking with an AI. Yara identifies itself at the start of every call. We do not simulate a human name. We do not adopt a human-presenting accent designed to deceive. The trade-off between trust and fluency is settled on the side of trust.

You always have a path to a human. Saying the words 'I want a person', or any of their natural equivalents in the languages Yara speaks, gets you a person. We will not gate that with friction, captchas, or 'are you sure' loops.

Outbound respects do-not-call. If you say 'do not call me again', you will not be called again. The opt-out is registered on the call, not delegated to a website.

The promise to customers

To the enterprises that write Yara a check.

Containment rate is reported transparently, monthly, segmented by intent. You will see it. Your CFO will see it. The board will see it. There is no version of this dashboard that exists only inside Yara.

If we miss the containment rate we committed at signature, we keep working at our cost until we hit it. No change orders. No escalating engagement fees. The commitment is the commitment.

We do not bill for capacity we did not deliver. Concurrency that the system handled — billed. Concurrency that the system dropped, queued, or escalated to your human team because we missed our spec — not billed. The invoice reconciles to delivery, every month.

No lock-in by architecture. Model weights, prompts, voice configurations, audit logs, and integration mappings are exportable on demand. If you choose to leave, you leave with everything you would need to migrate. We will charge for the engineering hours of the export. We will not weaponize switching cost.

Deployment timelines are honest. Standard deployment is 60 to 90 days. Regulated deployments add 30 to 60 days for regulator review and cadence alignment. If your scope is harder than that, we tell you in the first call, not after the SOW is signed.

We tell you what we cannot do, before the contract. If your use case requires a capability Yara has not shipped, we will say so. We will not promise a roadmap to win the deal and then negotiate when the deadline arrives. The contract is built on what works today, not what we hope works in six months.

The promise to regulators

To the bodies whose evidentiary standards keep enterprises operating.

The audit log is complete by architecture. Every call, every model output, every routing decision, every escalation is logged immutably from the first ring. The log is not produced when you ask for it. The log exists continuously, and your query is what reaches into it.

Regulatory tagging is applied in real time. When a call enters a regulated topic — claims advice, account fraud, vulnerable customer detection — the tag is attached at the moment of detection, not retrofitted in post-processing. The tagging vocabulary is published, per jurisdiction, and updated when regulators update theirs.

A specific call from a specific date is a query. Not a forensic project, not a scramble through cold storage, not 'we will get back to you in 30 days'. Production audit log queries return in seconds. The data is online by design.

Vulnerability detection patterns are documented, not proprietary. If you ask how Yara recognizes a minor, a customer in distress, or a customer being defrauded, the answer is a published document — not 'trade secret'. Regulators cannot supervise what they cannot read.

Compliance posture is documented per jurisdiction, updated quarterly. UAE Insurance Authority, UAE Central Bank, EU AI Act, GDPR, HIPAA, MAS, FCA — each posture is a separate document, with mapped controls, gaps disclosed, and remediation timelines.

We will accept independent audit. Not vendor-selected audit. A regulator-approved auditor reviewing the production system on the regulator's schedule, not Yara's. That is the only audit that means anything.

What we will not do

Equally important — the things Yara refuses, even when asked.

We will not impersonate a human. Not at the start of the call, not in the middle, not at the customer's request. A voice agent that pretends to be human in a regulated industry is a liability the entire industry will eventually pay for. Yara will not contribute to that liability.

We will not deploy without simulator coverage. Every agent design is run against thousands of synthetic conversations, including adversarial ones, before it touches production traffic. If a customer wants a faster timeline by skipping simulation, the answer is no.

We will not run an agent in production with audit gaps. If the audit log breaks for any reason — storage incident, integration failure, schema drift — that agent is paused until the log is intact. A contact center without auditability is not Yara's product.

We will not take a regulated deployment without local presence. If a jurisdiction's regulator needs to be able to reach Yara, Yara has staff in that jurisdiction. Not a sales agent. Not a partner. Yara employees, accountable to local law.

We will not sell 'voice AI tools' as Yara. The company sells the Fully Autonomous Call Center as a solution. We do not slice it into APIs to chase developer-tier revenue. Customers who want components should buy from vendors built for that, not from us pretending to be one.

We will not quote AHT or FCR as our headline metric. Average Handle Time and First-Call Resolution are augmentation metrics. The headline number we publish is containment rate. Anything else is dilution.

How we will hold ourselves to this

Commitments without accountability are slogans. The mechanisms.

Annual public report. Every year, Yara publishes containment rates by deployment, escalation accuracy, regulator findings (with consent), customer NPS, and the deviations from this manifesto if there were any. The report is signed by the founders.

Independent audit. A compliance audit commissioned by Yara from an auditor we did not choose alone — selected from a regulator-approved list. The findings are summarized in the annual public report. We do not get to pick the auditor that produces the friendliest result.

Containment SLA in every contract. The containment commitment is contractually enforceable, refundable in service credits or cash at the customer's choice. The default in voice AI today is to bury performance language in marketing copy and exclude it from the legal document. Yara puts it in the legal document.

Direct founder access for every enterprise customer. There is a Slack channel, an email address, and a phone number. They are not gated by an account manager. If the contact center is down at 2 a.m., the founders pick up.

Customer NPS by audit cadence — published. We will not publish a top-line NPS that averages happy pilots with struggling deployments. The cohort-level numbers are published, by quarter, by industry, by region.

What we ask in return

This contract works only if it is mutual. What we ask of the people on the other end of it.

From consumers: tell us when we sound wrong. The dialect we missed, the moment we should have escalated, the phrase that felt off — the easiest way to make the next call better is to tell us about the one that failed. The feedback channel is on every call summary.

From customers: realistic SLAs that match operating reality. We can hit aggressive numbers; we cannot hit numbers that ignore your call mix and your data quality. The pre-migration audit is honest because it has to be. We need the same honesty back when you set the spec.

From regulators: tell us what you need before we ship. The cost of building it right the first time is a fraction of the cost of retrofitting it after a finding. We will sit through the briefings. We will read the consultation papers. We will respond. We need the engagement to start before the first complaint, not after.

From the industry: do not race to the bottom. Voice AI in regulated industries is a fragile category. One bad actor can set the entire vertical back five years. The bar Yara is publishing here is the floor, not the ceiling. We expect competitors to match it. We will applaud when they do.

On the record

This page is published. Versioned. Signed. It is not a slide that changes between sales calls. It is not marketing copy that softens when the legal review comes back. It is the document a customer prints out, hands to their procurement team, and asks: will Yara still believe this in two years?

The answer is yes. And if it is not, the public commit history of this manifesto will show what changed and when. We will not edit silently. We will not delete sections that became inconvenient. The only legitimate change to this document is addition — a new pledge that strengthens an existing one, a new commitment we did not think to make at the seed round.

We are writing this on the record because the alternative — leaving the promises in keynote slides and pitch decks where nobody can hold us to them — is what every other vendor in this space has chosen. Yara is choosing differently. This page is the difference.