Terms and Conditions

These terms are between Olee AI and the business that opens an account, referred to here as you. By creating an account, subscribing to a service or using Oleon Workspace, you accept them. If you are accepting on behalf of a company, you are confirming that you are allowed to bind it.

If your business has signed a proposal, an order form or a service agreement with us, that document governs where it says something different. These terms fill the gaps in it. They do not override it, and nothing you click here changes what was signed.

Oleon Workspace

The platform, the mobile app, the APIs and anything we provide alongside them.

Service

Any one of the products we sell inside Oleon Workspace, such as Connect, Scout or Chat. Each is subscribed to separately, per project, and a business can take as few or as many as it wants. Which products exist changes as we build; the ones available to you are the ones your project can subscribe to.

Project

A workspace with its own channels, conversations and subscription.

Controller seat

A person working the inbox. A plan includes a number of them, and seats beyond that are charged.

Active user

An end user your business exchanged messages with during a billing month, which is the unit some plans are counted in. One active user is counted as 50 messages: 25 inbound and 25 outbound. Other plans are counted in messages instead, and your plan says which of the two yours is. An active user is never a seat: a seat is somebody on your side and an active user is somebody on theirs, and no invoice confuses them.

End user

Someone your business exchanges messages with. They are your contact, not ours.

Your data

Everything you and your end users put into the product: messages, attachments, contacts, flows, training material and records.

• Give us accurate details and keep them current, particularly the billing address and the email we send invoices to.
• You are responsible for what the people in your organisation do with their access, and for removing someone who leaves.
• Keep credentials to yourself. Turn on two-factor authentication for anyone who can read conversations, and tell us promptly if you think an account has been taken.
• A seat is a person, not a shared login. Sharing one account between a shift is a breach of these terms and it also makes your own audit logs worthless.

Prices are in Sri Lankan rupees and charged per project. The figures themselves are not set out here: they change, and a contract carrying a number that is out of date is worse than one that names where the current number lives. What you pay is whatever your signed proposal or order form says, and otherwise the rates published on the pricing page on the day you subscribe. Your invoice is the record of it.

The subscription

Each service is subscribed to separately, per project, and billed monthly in advance at the rate that applied when you took it.

The one-time fee

Where a service carries a one-time development or implementation fee, it is charged once, at the start, and the pricing page says so before you subscribe. No service carries one today.

The included allowance

Every subscription includes a monthly allowance of the things it meters, such as AI replies, users or messages. It resets on your billing date and does not carry over.

Usage beyond it

Nothing stops when the allowance runs out. Usage past it is charged at the published per-unit rate, on the month you used it in, and it appears on that month's invoice.

Seats

Some services include a number of controller seats. Seats beyond what your plan includes are charged monthly, and a seat added part-way through a month is charged for the part you used.

Changes to your data

One dynamic-data change up to a set size is free every two weeks. Anything longer, or more often, is quoted before the work starts.

What the published price does not cover

The price of a service covers Oleon Workspace and the allowance that comes with it. Beyond that it does not cover what other companies charge for carrying or generating your messages: Meta's fees for WhatsApp, and what the external AI model providers charge. Those sit outside the published figure and are billed on top of it where they apply.

What Meta bills you

Meta charges you directly for WhatsApp messages, and it invoices you rather than us. Templates have always been charged. From 1 October 2026 Meta also charges for service messages, which are the ordinary replies you send inside the 24-hour window, once a business phone number passes the monthly allowance Meta gives it. Replying to someone who reached you from a click-to-WhatsApp advert stays free for longer. Those rules, those allowances and those rates are Meta's, Meta publishes them and Meta changes them, and we neither add to them nor control them.

Keeping WhatsApp working

Because Meta bills you rather than us, you need a payment method on file with Meta. Without one, WhatsApp stops delivering your messages once the free allowance for that number is used, and there is nothing we can do from our side to keep them going.

What the model providers charge

Generating a reply costs money at the model provider, and those rates are theirs to set, not ours. Where your allowance does not already cover it, that usage appears on the invoice for the month you used it in. If a provider raises its rates, that reaches our prices, and it reaches them under the notice below.

Fees exclude taxes, which are added where the law requires. Anything built for you after signing, such as an extra feature or an integration, is quoted separately before the work starts.

We can change what a package costs. Where we do, account holders get at least one month's notice by email before it affects an invoice, and the change never applies to a period you have already been charged for. Nothing is repriced quietly and nothing is repriced backwards.

The exchange rate is the thing most likely to move a price. What it costs us to run this is largely in US dollars while you are invoiced in rupees, so if the rate moves significantly in either direction we will reset package prices to match it, upwards or downwards. Olee AI decides when a movement is significant enough to act on, and that decision is ours alone. It reaches you the same way every other price change does: one month's notice, and never applied to a period already charged.

• Payment is by card through our payment provider, or by bank transfer against a receipt we verify.
• A card subscription runs on a recurring mandate: you authorise us to charge that card each month until you cancel. Cancel it in the product and the mandate stops with it.
• Subscribe part-way through a billing month and the first invoice is queued to the end of it, so you are not charged twice for the same weeks.
• If an invoice goes unpaid we will tell you. If it stays unpaid for 14 days we may suspend the project, and your data stays where it is during a suspension.

Fees already charged are not refundable. What that means in practice, and the cases where we do return money, is set out in the refund policy.

Every service can be started on a free trial with a code. A trial runs for a set number of days from the day you start it, seven at the time of writing, it takes no card, and the screen where you enter the code tells you the length and the team size before you begin.

• One trial per account, and one per project. A code belongs to a particular product and only works on a project running that product.
• A trial comes with an allowance to spend and a limit on how many people can be in the project. Both are set by the code you redeemed.
• When the trial ends, the allowance ends with it. Whatever is left of it expires and the agent stops answering.
• Your project, your conversations and your history stay exactly where they are. A trial ending removes nothing.
• Nothing is charged when a trial ends. There is no card on file and no automatic conversion to a paid plan. To carry on, you choose one.
• Your browser is asked for a fingerprint when a trial starts. It is used only to stop one device taking the same trial repeatedly, and the privacy policy says what becomes of it.

We can refuse a trial, or end one early, where it is being used to avoid paying rather than to evaluate the product. Opening accounts or projects to take the same trial again is the case we mean.

A subscription is monthly and renews by itself until you cancel it. Cancel from the project's billing screen at any time: the cancellation takes effect on your next billing date, and until then the service runs normally and you keep what you paid for.

You can also stop a single service and keep the others. Nothing you have already sent, drawn or recorded is affected by a change of plan.

We can end this agreement if you breach it seriously and do not put it right within 14 days of being asked, if payment stays outstanding, or if a channel provider requires us to. Your data stays available for 30 days after the agreement ends so you can ask us for an export of it, and it is deleted on the schedule the privacy policy and the data processing agreement set out.

However it ends, your data stays available to export for 30 days afterwards. After that we delete it, other than anything we are required to keep, such as the billing records behind invoices already raised. Ask us in writing inside those 30 days and we will hold it longer, or delete it sooner.

The rules that matter, and most of them are the channel providers' rules before they are ours.

• Message people who agreed to hear from you. Unsolicited bulk messaging is against WhatsApp's own policies and it is against these terms.
• Honour an opt-out promptly. Someone who asks a business to stop should not have to ask twice.
• Follow the terms of every channel you connect, including the WhatsApp Business Messaging Policy and Meta's platform terms. A breach of theirs is a breach of ours, because it is our infrastructure that carries it.
• Nothing illegal, and nothing that harasses, defrauds or deceives the person receiving it.
• Do not resell the product, rent access to it, or open it to a business that is not yours without our written agreement.
• Do not attempt to breach it, scrape it or reverse engineer it, and do not load it past the allowances on your plan in a way that degrades it for anybody else. Where that happens we will tell you what the limit is before we act on it.
• Say that an automated agent is answering where the law or the channel requires you to.

We may suspend a project immediately where continuing would put our infrastructure, another customer or a channel connection at risk. We will tell you why, and we will lift it as soon as the cause is dealt with.

Oleon Workspace connects to channels other companies run: WhatsApp, Instagram, Messenger, Telegram, SMS and the web. Those are somebody else's networks and this is worth being plain about.

• You need your own accounts and assets with them, and their terms apply to you directly.
• They can change their rates, their policies and their APIs, and they can suspend a business's access. We do not control any of that.
• Where a channel is down or has changed something, we will work to restore the connection, but we cannot promise a service that depends on a network we do not run.

You own your data. We do not claim any right to it beyond what is needed to run the product for you: to store it, transmit it, back it up, display it to your team, and process it on your instruction. That permission lasts as long as you use the product and no longer.

You can ask us for an export of your conversations at any time while the project is open, and your history belongs to your business rather than to the plan you were on. We do not sell your data. Anything the agent generates for you is your data on the same terms as the rest of it.

For your end users' personal data you are the one who decides and we act on your instruction. You are responsible for having a lawful basis to message them and for telling them what you do with what they send you.

What we owe you in return is the data processing agreement, which forms part of these terms and is a page of its own: who else we use and how you object to a new one, where the data is processed, how quickly we tell you when something goes wrong, what help you get when one of your customers asks a question, and what happens to all of it when you leave.

Two commitments about your data that are easier to state than to notice the absence of, so they are stated here as terms rather than left to the privacy policy alone.

It is never used to train a model

We do not use your conversations, your contacts or the material you upload to train our own models, and our arrangements with the model provider do not permit them to be used to train anyone else's. Content is sent to a provider to answer the message in front of it and for no other purpose.

It is encrypted in transit and at rest

Everything travels over TLS, between you and us and between us and every service we hand it to. Sensitive fields, including conversation history and stored credentials, are encrypted where they sit, with the keys held separately from the data they open.

Access is decided by role

What a person can see is what their role in your organisation allows, checked on our servers on every request rather than hidden in the interface. Administrative actions are logged, and those logs are visible to you rather than only to us.

A promise not to do something, made in a document we can change, is worth asking about. So: the commitment above is judged by the version in force when the data was handled. Weakening it is a change that materially affects your rights, which means a month's notice and your right to cancel before it lands, and it never reaches back over data we have already processed under the old wording.

No system is beyond reach and a term claiming otherwise would be telling you something false. If a breach affects your data we will tell you, and we will tell you what we know rather than the least we can get away with. The privacy policy sets out the whole of it: what is collected, who it is handed to and how long it is kept.

Scout generates replies from the material you train it on and from the conversation in front of it. It is a useful guess and not an authority, and it can be confidently wrong.

• You decide whether the agent answers, what it is trained on and when it hands over to a person.
• A reply the agent sends is your business speaking, and you are responsible for it as you would be for a member of staff.
• Do not rely on it for legal, medical, financial or safety advice, and do not train it to give any.
• Review what it is doing, particularly after you change its training material.

We work to keep the product running and we publish its state at status.olee.ai. Maintenance happens, and where it will be disruptive we will give notice.

There is no guaranteed uptime figure in these terms. If your business needs one it belongs in a signed service agreement with a number in it, and we would rather agree one than imply one here. Support is provided during business hours in Sri Lanka.

Oleon Workspace, its software, its design and its name are ours and stay ours. You get the right to use it while you are a customer, and nothing more is transferred.

What the agent writes for you is yours. We claim nothing in the replies it drafts, the summaries it produces or the data it collects on your behalf, and they fall under your data rather than under our software. We cannot promise those outputs are unique: the same question from another business may produce a similar answer, and nothing here stops that.

If you send us feedback we may act on it and build what it suggests, without owing you anything for it. Channel names and marks belong to their owners.

The product is provided as it is. To the extent the law allows, we do not give implied warranties, and we do not promise that it will be uninterrupted or free of faults.

Neither of us is liable to the other for indirect or consequential loss, or for lost profits, revenue, goodwill or anticipated savings, however it arises.

Our total liability to you, taking everything together rather than counting each claim separately, is limited to the fees you paid us in the 12 months before the claim. Fees you paid somebody else are not fees you paid us: what Meta or a model provider bills you never reaches us and does not raise this limit. Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not permit to be limited.

That limit is on what we owe you. It does not cap what you owe us, which is the fees themselves and the cover described next.

You will cover us against claims brought by a third party because of your data or your use of the product in breach of these terms, including a claim by someone you messaged. For that to be worth anything to either of us it needs a procedure, so: we will tell you promptly when such a claim arrives, you may take over defending it with counsel we both find acceptable, we will co-operate at your cost, and neither of us will settle in a way that admits fault on the other's part or binds the other to do something without that party agreeing first. Telling you late only reduces what you owe to the extent the delay actually cost you. None of this extends to a claim caused by our own breach of these terms or our own negligence.

Each of us will keep the other's confidential information to itself, use it only for this agreement, and protect it as carefully as its own. This does not apply to anything already public, anything independently developed, or anything a law or a valid order requires to be disclosed.

We may update these terms. The date at the top says when they last changed, and where a change materially affects your rights we will email account holders at least one month before it takes effect. Carrying on after that is acceptance. If you would rather not accept, cancel before the change lands and the old terms apply until your next billing date.

The clauses nobody reads until they matter, which is exactly when it is too late to add them.

If one part fails

If a court decides some part of these terms cannot stand, that part is treated as narrowed to whatever would stand, or removed if it cannot be. The rest carries on. One clause failing does not take the agreement down with it.

What outlives the agreement

Ending this does not end everything in it. Confidentiality, what belongs to whom, the limits on liability, the cover you give us, anything you already owe, and this section survive for as long as they need to.

Letting something go once

If either of us does not enforce something straight away, that is not us giving it up. A right is only waived if the party holding it says so in writing, and waiving it once does not waive it next time.

Handing the agreement on

You may not transfer this agreement without our written agreement, which we will not withhold unreasonably. We may transfer it to a company in the same group, or to whoever acquires the business, and we will tell you when we do. It binds whoever properly takes it on.

Telling each other things

Formal notice from us goes by email to the account holders, and is treated as received the day it is sent unless it bounces. Notice to us goes to the address at the foot of this page. Keeping a working email on the account is your side of that, because a notice you never read still counts as given.

What is actually agreed

These terms, your signed proposal or order form where you have one, the refund policy and the privacy policy are the whole agreement. Nothing said in a demo, a sales email or a call adds to them. That protects you as much as us: it means what you are held to is what you can read.

Things outside anyone's hands

Neither of us is in breach for failing to do something because of an event we could not reasonably control, such as a war, a natural disaster, a national outage or a channel provider withdrawing access. We will tell you what is happening and work to restore the service. This never excuses paying for what you have already had.

We are not partners

This is a supplier and a customer and nothing more. Neither of us can speak for the other, bind the other or hold itself out as the other's agent.

Nobody else can enforce this

This agreement is between the two of us. No one outside it gains a right to enforce any part of it.

These terms are governed by the laws of Sri Lanka, and the courts of Colombo have exclusive jurisdiction over any dispute arising from them.

Before either of us goes to court, we should talk. Write to the address at the foot of this page and we will put a person on it.