Kay-X Terms & Conditions
The agreement between Kay-X and the businesses that build on it.
Last updated:
These Terms govern your use of the Kay-X platform: the voice, language and translation APIs, the dashboard, and anything else we provide.
They are an agreement with a business, not with a consumer. If you are a caller whose voice was processed by a service built on Kay-X, the Privacy Policy is the document that concerns you.
1.The agreement, and who it is with
These Terms are a contract between [LEGAL_ENTITY_NAME], a company registered in [JURISDICTION_OF_INCORPORATION] under number [COMPANY_REGISTRATION_NUMBER] with its registered office at [REGISTERED_ADDRESS] ("Kay-X", "we", "us"), and the business or individual that creates an account or uses the Platform ("you", "Customer").
By creating an account, generating an API key or sending a request to the Platform, you accept these Terms. If you are accepting on behalf of an organisation, you confirm you are authorised to bind it. If you do not accept, do not use the Platform.
Definitions
| Term | Meaning |
|---|---|
| Platform | The Kay-X APIs, models, dashboard, documentation and related services. |
| End User | A person whose speech, text or other input is submitted to the Platform by you or through your application. |
| Customer Data | Data you submit to the Platform, including audio, text, configuration and intent definitions. |
| Voice Data | Audio recordings of End Users submitted to the Platform, and transcripts and extracted values derived from them. |
| Derived Data | Transcripts, detected intents, extracted values, confirmations, corrections, quality signals and other outputs generated by the Platform from Customer Data. |
| Output | What the Platform returns to you in response to a request. |
| Credits | The prepaid unit of account for Platform usage. One credit is one United States cent ($0.01). |
| Privacy Policy | The Kay-X Privacy Policy, as updated from time to time, which forms part of these Terms. |
2.Your account and your API keys
- 1You must give accurate registration details and keep them current. We collect an email address and a password, and optionally a business name.
- 2You are responsible for everything that happens under your account and your API keys, whether or not you authorised it.
- 3API keys are secrets. Keep them server-side. Do not embed them in a mobile app, a browser bundle, or anything else you ship to end users. We store only a salted hash of a key and cannot recover or re-display it.
- 4Tell us promptly at [SUPPORT_CONTACT_EMAIL] if a key is exposed or your account is compromised. You may revoke a key at any time from the dashboard.
- 5An account holder must be at least [MINIMUM_AGE].
- 6Do not share an account across separate legal entities. Each entity needs its own.
3.Credits, pricing and payment
- 1The Platform is prepaid. You buy Credits and usage draws them down. One Credit equals one United States cent ($0.01).
- 2Current rates are published in the dashboard and at our public pricing endpoint. Different operations cost different amounts — speech recognition is charged by audio duration, speech synthesis and translation by character count, and intent detection at a flat rate per call.
- 3We charge before we spend. Credits are reserved when a request begins. If an operation fails on our side, the Credits are refunded automatically. You are not charged for our failures.
- 4Some operations are free and are intended to stay that way: confirming or correcting a turn, the deterministic text normalizer, browsing the response template gallery, and previewing a response without audio. Confirmations and corrections are free because they are the most valuable training signal we receive and we do not want to discourage them.
- 5Replaying a request with an identifier we have already processed returns the stored result. It is not re-processed and not re-charged.
- 6Credits are non-refundable and have no cash value, except where a refund is required by law or where we have charged you in error. They are not transferable between accounts.
- 7We may change prices. Price increases take effect no less than [NOTICE_PERIOD_TERMS_CHANGE] after we notify you, and do not affect Credits you have already bought.
- 8Payment is taken by our payment provider. Card details are entered directly with that provider and never reach Kay-X.
- 9You are responsible for any taxes on your purchase other than taxes on our income.
- 10If your balance reaches zero, chargeable requests will be refused until you top up. We will not stop serving you without warning where we can avoid it, but we do not extend credit.
4.Acceptable use
You must not use the Platform to:
- 1Break the law, or help anyone else to.
- 2Identify, authenticate or verify a person by their voice. The Platform is for understanding what was said, not for recognising who said it. Do not use it, or its outputs, to build or operate voice biometric identification.
- 3Record anyone covertly, or in circumstances where you have not given the notice and obtained the basis required by section 5.
- 4Submit data you have no right to submit.
- 5Submit special-category data — health, biometric, financial or similar — unless you have a valid basis for doing so and have told us.
- 6Impersonate a person or organisation, or generate speech intended to deceive a listener about who is speaking.
- 7Generate or distribute material that is unlawful, harassing, defamatory, or that incites violence.
- 8Build a service whose purpose is surveillance of individuals, or social scoring.
- 9Reverse engineer the Platform, or attempt to extract, reconstruct or distil our models or their weights.
- 10Use Output to train a competing speech or language model.
- 11Circumvent rate limits, quotas or billing, or probe our security without permission.
- 12Resell raw Platform access as a substitute for a Kay-X account, unless we have agreed in writing.
We may suspend an account immediately where we reasonably believe it is being used in breach of this section and the risk of waiting is material. We will tell you why, and restore access if the matter is resolved.
5.Your obligations regarding End Users
This is the most important clause in this agreement
We have no relationship with the person whose voice we process. We cannot tell them what is happening and we cannot obtain their consent. You can, and you must. Note that section 22(1) of the Constitution of Sierra Leone, 1991 prohibits interference with a person's telephone conversations except with his own consent — so in our primary market, consent is not merely good practice.
You represent, warrant and undertake, on a continuing basis, that:
- 1You have a lawful basis for collecting each End User's voice and other input and for submitting it to the Platform, and you can evidence that basis.
- 2Before recording an End User, you have told them that they are being recorded; that the recording, the transcript and the values extracted from it will be retained and used by Kay-X to train and improve Krio language and speech models; and that trained human reviewers may listen to the recording and see the values extracted from it.
- 3Where consent is the applicable basis, you have obtained it, and you keep whatever record of it your own obligations require.
- 4You have given End Users a means of refusing, and you handle a refusal lawfully.
- 5You comply with all laws and regulations applicable to you, including any that govern your sector. Kay-X is general-purpose language infrastructure and does not carry any sector authorisation on your behalf. If you operate in health, financial services, payments, telecommunications or government, meeting those rules is your responsibility alone.
- 6You will pass on to us promptly any request or complaint from an End User that concerns data you submitted, and help us identify the relevant session.
- 7You will not submit the voice of a child without a valid basis.
We publish a short Krio consent script in the Privacy Policy that you may use or adapt to meet obligation 2. We provide it as a practical aid. It is not legal advice and it does not transfer any of these obligations to us.
6.Data used to train and improve our models
This clause is the commercial and technical heart of the arrangement, so we state it plainly rather than burying it.
The grant
You grant Kay-X a worldwide, non-exclusive, royalty-free, sublicensable licence to host, store, process, reproduce, adapt and create derivative works from Customer Data, Voice Data and Derived Data for the purposes of (a) providing the Platform to you, and (b) developing, training, fine-tuning, evaluating and improving our language, speech and intent models and the services built on them.
Why this is the deal
Krio has essentially no language technology and no corpus to license. Our models improve because real Krio speech passes through them and because their mistakes get corrected. The improvement is what you are buying, and it compounds across all customers: traffic from one integration improves the models every other integration depends on. We think that is a good deal for a customer in this market, and we would rather describe it accurately than hide it in a definition.
The limits on that grant
The licence above is subject to the following, which are binding obligations on us:
- 1Purpose limitation. We use the data only to operate the Platform and to develop, train, evaluate and improve models and services. For no other purpose.
- 2No sale. We will not sell, rent or licence personal data to any third party for that third party's own purposes.
- 3No advertising. We will not use the data for advertising, and we will not build advertising profiles.
- 4No profiling of End Users. We will not build profiles of, score, or make automated decisions with legal or similarly significant effect about individual End Users.
- 5No voice biometrics. We will not build voiceprints or perform speaker identification or verification.
- 6De-identification and aggregation. We will remove or replace direct identifiers, separate data from the originating account, and work in aggregate before using data for training.
- 7No re-identification. We will not attempt to re-identify individuals from de-identified data, nor permit others to.
- 8Confidentiality. Everyone with access to Voice Data is bound by confidentiality obligations and access is limited by role.
- 9No competitive use. We will not use your Customer Data to build a product that competes with yours.
- 10Externally released corpora. We will not include Voice Data originating from your traffic in any externally released language corpus unless you have confirmed that the relevant End Users consented to that use.
Opting out
We are building a setting that will exclude your traffic from model training while leaving the Platform fully functional. It is not built yet, and we will not describe it as though it were. Until it is available — target [OPT_OUT_SHIP_DATE] — you may request exclusion by writing to [PRIVACY_CONTACT_EMAIL], and we will give effect to it operationally.
Survival, and the limits of deletion
The licence in this clause is perpetual and irrevocable in respect of data already incorporated into a trained model, and survives termination of this agreement. This is not a land grab; it is a statement of what is technically true. A model that has been trained on data cannot be untrained. On termination or on a valid erasure request we will delete the underlying records, stop using them in future training, and exclude them from future corpora — but we cannot withdraw their influence from a model that already exists, and we will not promise that we can.
For all other purposes the licence ends when the relevant data is deleted in accordance with the Privacy Policy.
7.Intellectual property
- 1We own the Platform, our models, our training data, and everything we have built. Nothing here transfers any of it to you. You get a limited, revocable, non-exclusive, non-transferable right to use the Platform under these Terms.
- 2You own your Customer Data. Nothing here transfers it to us beyond the licence in section 6.
- 3As between you and us, you own the Output generated from your requests, and may use it for your own purposes — subject to section 4, and subject to our right to use it under section 6.
- 4Output is generated by statistical models. It may be wrong. Identical requests may produce different Output, and similar Output may be generated for other customers. We make no claim that Output is unique to you.
- 5If you send us feedback or suggestions, we may use them freely and without obligation to you.
- 6Our names, logos and marks are ours. Do not use them without permission, except to state factually that you use Kay-X.
8.Service availability and changes
- 1The Platform is provided without a service level commitment. We have not yet published an availability target and you should not design a safety-critical system on the assumption of one.
- 2Some requests hold a connection open while speech recognition and model inference run. There is currently no asynchronous or callback mode. Design your integration to tolerate latency and timeouts.
- 3Rate limits and quotas apply per key. Rate limiting is currently enforced per running instance rather than globally, so effective limits may differ from the configured value.
- 4There is currently no sandbox or test mode. Requests made while developing consume Credits and are treated as production traffic under section 6.
- 5We may change, improve or replace the models behind the Platform at any time. We aim to keep the shape of API responses stable when we do, but model behaviour will change as models improve — that is the point of section 6.
- 6We may add, change or discontinue features. If we discontinue something material we will give you [NOTICE_PERIOD_TERMS_CHANGE] notice where we reasonably can.
- 7We may perform maintenance, and will try to do it at low-traffic times.
9.Confidentiality
Each party may receive non-public information from the other. Each will protect the other's confidential information with at least reasonable care, use it only for the purposes of this agreement, and disclose it only to people who need it and are bound to protect it. This does not apply to information that is public through no fault of the recipient, was already known, is independently developed, or must be disclosed by law — in which case the recipient will give notice where it lawfully can.
10.Warranties and disclaimers
We warrant that we will provide the Platform with reasonable skill and care, and that we have the right to enter into this agreement.
Otherwise, and to the fullest extent permitted by law, the Platform is provided "as is" and we disclaim all other warranties, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, non-infringement, accuracy, or uninterrupted or error-free operation.
In particular: speech recognition, intent detection and translation are probabilistic. They will sometimes be wrong. A transcript may misrepresent what was said. An extracted amount or phone number may be incorrect. A translation may be inaccurate or lose meaning. The Platform reports its own confidence and asks the caller for clarification when it is uncertain, but that mechanism reduces error, it does not eliminate it.
You must validate before you act
You are responsible for validating Output before acting on it, particularly where acting has consequences — moving money, dispensing medicine, dispatching goods, or anything else that is hard to reverse. Do not treat an extracted value as verified simply because the Platform returned it with high confidence.
11.Limitation of liability
Neither party excludes liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be excluded.
Subject to that, and to the fullest extent permitted by law: neither party is liable for indirect, incidental, special, consequential or punitive loss, or for loss of profit, revenue, goodwill, business opportunity or data, however arising.
Subject to that, each party's total aggregate liability arising out of or in connection with this agreement is limited to [LIABILITY_CAP].
These limits do not apply to your obligation to pay amounts due, to your obligations under section 5, or to either party's indemnity obligations.
12.Indemnity
You will indemnify and hold us harmless against claims, losses and reasonable costs arising from: (a) your breach of section 4 or section 5; (b) any claim by an End User or a regulator that you collected or submitted data without a lawful basis or without proper notice; (c) your Customer Data infringing a third party's rights; or (d) your use of Output.
We will notify you of any claim, let you control the defence of it, and give you reasonable cooperation at your expense.
13.Term, suspension and termination
- 1This agreement starts when you create an account and continues until terminated.
- 2You may terminate at any time by closing your account. Unused Credits are not refunded.
- 3We may terminate for convenience on [NOTICE_PERIOD_TERMS_CHANGE] notice. If we do, we will refund Credits you have bought and not used.
- 4Either party may terminate immediately for material breach that is not remedied within 30 days of notice, or on the other's insolvency.
- 5We may suspend immediately under section 4, for non-payment, or where continuing would expose us or an End User to material risk or legal liability.
- 6On termination your access ends. We will delete or return your Customer Data in accordance with the Privacy Policy and [RETENTION_AFTER_TERMINATION], subject always to section 6 and to any records we must keep by law.
- 7Sections 6, 7, 9, 10, 11, 12 and 14 survive termination.
14.General
- 1Changes. We may amend these Terms. For material changes we will give at least [NOTICE_PERIOD_TERMS_CHANGE] notice by email or in the dashboard. Continuing to use the Platform after that is acceptance. If you do not accept, terminate and we will refund unused Credits.
- 2Governing law. These Terms are governed by the laws of [GOVERNING_LAW].
- 3Disputes. The parties submit to [DISPUTE_FORUM]. Both will try in good faith to resolve a dispute by discussion first.
- 4Assignment. You may not assign without our written consent. We may assign to an affiliate or in connection with a merger or sale of the business.
- 5Entire agreement. These Terms and the Privacy Policy are the whole agreement and replace anything said before.
- 6Severability. If a provision is unenforceable, the rest stands.
- 7No waiver. Not enforcing something once does not waive it.
- 8No partnership. Nothing here creates a partnership, agency or employment relationship.
- 9Force majeure. Neither party is liable for a failure caused by something genuinely beyond its reasonable control, which in our operating environment expressly includes sustained power or connectivity failure.
- 10Notices. To you, at your account email. To us, at [SUPPORT_CONTACT_EMAIL] and [REGISTERED_ADDRESS].
15.Contact
| Purpose | Contact |
|---|---|
| Commercial and support | [SUPPORT_CONTACT_EMAIL] |
| Privacy and data requests | [PRIVACY_CONTACT_EMAIL] |
| Legal notices | [LEGAL_ENTITY_NAME], [REGISTERED_ADDRESS] |
Appendix A — Questions for Counsel
Open legal questions identified while drafting these Terms and the accompanying Privacy Policy. The two documents share a question list because the issues cut across both.
- 1Sierra Leone has no data protection statute in force. The Data Protection and Right to Access Information Bill was approved by Cabinet on 21 April 2026 and is to be tabled in Parliament. Should these documents be drafted to the Bill as it stands, to GDPR-equivalent principles, or to the minimum the law currently requires? What is the transition plan when the Act commences?
- 2Is voice audio 'sensitive' or 'biometric' personal data? Kay-X does not perform speaker identification and builds no voiceprint, but the recording is inherently identifying. Note that the sibling product KACCP already states publicly that 'Voice recordings are biometric data'. Is there a risk in the two Geneline-X products taking different positions?
- 3Cross-border transfer. Recordings and transcripts leave Sierra Leone for United States infrastructure (Google Cloud Storage, OpenAI, Stripe, Vercel) and for a decentralised GPU network of indeterminate geography. With no statutory transfer mechanism in Sierra Leone law today, what should we commit to contractually? Does the ECOWAS Supplementary Act on Personal Data Protection, which Sierra Leone has signed, bind us in the absence of domestic implementing legislation?
- 4Kay-X acts as a processor for the business customer's transaction purpose and as a controller for model improvement, on the same data. Is that dual role defensible? Does it require a separate lawful basis, a data processing agreement, or a restructuring of the arrangement?
- 5Is it sufficient to place the obligation to obtain end-user consent on the business customer, or do we need evidence of that consent, a contractual flow-down, or a technical attestation in the API?
- 6Does the training-data licence survive termination? Our position is that a model already trained cannot be untrained, so the licence in respect of already-ingested data must be perpetual and irrevocable. Is that enforceable, and is it acceptable to state it plainly?
- 7Every [RETENTION_*] placeholder needs a defensible number. There is currently no automated deletion anywhere in the system. What minimum should we commit to, and what is the exposure until it is built?
- 8Paid human reviewers listen to end-user recordings and read the values extracted from them, which in some deployments will include financial or health information. What contractual, technical and training controls are required, and does this need separate disclosure or consent?
- 9Audio captured from production traffic is stored alongside, and is technically capable of being exported with, a corpus that consented contributors licensed under CC0 into the public domain. Provenance is tracked and the default export excludes production audio, but nothing enforces that. What controls must exist before any release, and what should the policy promise?
- 10End users are callers in Sierra Leone, many on feature phones, many with limited literacy, most of whom will never see an English web page. Is a Krio spoken consent script played by the business customer an adequate consent mechanism? What should it say to be legally sufficient rather than merely informative?
- 11We cannot verify the age of a caller. Is a contractual prohibition on directing the service at children adequate?
- 12Is the limitation of liability enforceable in [GOVERNING_LAW], and is [LIABILITY_CAP] appropriate?
- 13Is a unilateral right to amend the Terms enforceable, and what notice period is required?
- 14Do we need to register with any authority, appoint a data protection officer, or appoint a representative in any jurisdiction where our business customers operate?
- 15Section 22(1) of the Constitution of Sierra Leone, 1991 prohibits interference with a person's correspondence and telephone conversations 'except with his own consent'. Does recording and processing a caller's voice through a Kay-X-powered service engage that provision? If it does, (a) is it horizontally enforceable between private parties or only against the State, (b) does it create a private right of action, and (c) does it mean that end-user consent is not merely good practice but a constitutional precondition — which would make the business customer's failure to obtain it a materially greater risk than a contractual breach? This is the most consequential question on this list.
- 16If consent under section 22(1) is the operative basis, what form must it take to be valid for a caller on a feature phone? Is a recorded spoken 'yes' in response to a Krio script sufficient, and what record of it must the business customer keep?