Terms of Service

Last updated: 2026-10-25

These terms govern your use of Makasi (makasi.dev), the AI web app builder operated by OmniLab, a business registered in Quebec, Canada. You accept them expressly when you create your account or, for an account created another way, at its first sign-in; each purchase is made under the version in force on the day of the purchase. You can save or print this page at any time.

1. Who provides the service

Makasi is provided by OmniLab — Québec enterprise number (NEQ) 2282318825 — 7157, chemin des Forts, Lévis (Quebec) G6Y 0R7, Canada. Email: [email protected]. Full details are on makasi.dev/legal.

2. The service

Makasi lets you describe a web application and have AI agents plan, build, verify and host it as a real React + Supabase project — with its code history (git), a database, file storage, hosted previews and optional custom domains.

You must provide accurate account information and be at least the age of majority in your jurisdiction, or use the service under the supervision of someone who is.

3. Plans, credits and payments

Makasi offers a free plan and paid subscriptions (Pro and Business, each with several credit tiers), paid monthly or in advance for a longer period, by card through Stripe or by mobile money. What each plan includes is set out on the pricing page. Prices shown exclude taxes; applicable taxes (such as GST/QST) are calculated from your billing address or country and shown before you pay.

The billable unit is the credit. A credit is worth the same on every plan. There is no quota expressed as a count — no number of messages, minutes of dictation, searches or fixes per day: the only measure is what your usage actually costs. What you spend is not estimated up front: it is computed afterwards, from the work the AI models actually did on your request, and can then be viewed in the workspace and in your usage history. The number of credits included in each plan is on the pricing page; the price of a credit pack is shown in the app before you buy it.

Chatting with Makasi is free. Every month, every account — free or paid — receives free credits, shown in your balance, and a monthly allowance that covers, without touching your credits, your messages and their attachments, dictation, the assistant's web searches and the emails your applications send. Within that allowance, dictation, web search and emails each have a capped share, and a share is always kept for the conversation: building never draws on it.

Automatic hand-over. By accepting these terms, you agree once and for all that your resources take over from one another without any further request from us: when a share of the allowance runs out, the service concerned does not stop and carries on using your credits; when one source of credits runs out, the next one takes over, in the order set out in the next section. A message lets you know once a month, the first time the conversation goes past its allowance, and the cost of each message and each build can always be viewed in the workspace and in your usage history.

Changes you make yourself, without going through the AI (text, colours, theme…), are free; a change you ask the AI to make uses credits, just like a message. Going live and restoring a version never cost credits.

Hosting your applications is included in your plan — app, database and server. We never issue a surprise computing bill: if you exceed your plan's fair-use limits, your application is slowed down or temporarily capped and we offer you an upgrade, nothing more.

Subscriptions renew automatically until cancelled. You may cancel at any time; cancellation takes effect at the end of the paid period. If a renewal payment repeatedly fails, your account is downgraded to the free plan; your projects and data are preserved and your application stays online within that plan's limits.

Domain names. When you buy or renew a domain name, we register it for you with our provider. If that registration fails after your payment, for whatever reason, your order stays pending activation and you receive an email confirming that we received it: we retry automatically. If the domain still could not be activated by the end of the waiting period, you are refunded in full.

Prices may change; existing subscribers are notified at least 30 days before a change affects them.

4. Your credits: validity, caps and refunds

Validity. Free credits, the monthly allowance and, for subscribers, the plan's credits are valid for one month and renewed each month: the full amount is set again and any unused remainder does not carry over. Credits bought in a pack and credits offered (bonus, referral, a gesture from our team) never expire. A credit taken back at renewal is not restored, exchanged or refunded.

Order of use. Your credits are spent in this order: free credits, plan credits, offered credits, then purchased credits — and, within each of these, the oldest first. For chat, dictation, web search and your applications' emails, the monthly allowance comes first. When nothing is left, your own keys take over if you have provided them (see “Your own keys”), except for dictation; otherwise, the action is refused.

Credits are not money. They are not transferable, not convertible into cash (subject to the Termination section), and have no value outside the service.

Value of a credit. A credit represents a monetary value, not a number of messages or the use of a specific AI model: the cost of an operation reflects its actual cost at the time it is carried out. The models offered may change over time; your balance remains usable on the models available.

Spending during a mission. Before each task, we check your available credit balance; if it is empty, the task does not start. The work stops between two calls as soon as that balance runs out — work already saved is kept. You can also stop a mission at any time.

Overdraft. The cost of a call to an AI model is only known once the response comes back. The last call — a message or a build — may therefore slightly exceed what you had left: this overdraft is limited to a single call. It is deducted automatically from your next credits, whatever their source (renewal, purchase or bonus), and its cost can be viewed in the workspace and in your usage history. It is never shown as a negative balance — your balance then reads 0 — and is never claimed from you as a payment, including if you close your account.

Safety cap. On top of these checks, a technical safety cap limits each account's AI calls. If it is reached, the request is not sent to the AI provider and we let you know. It protects against a mistake on our side and is not a limit of your plan: it never results in any charge to you.

Your own keys (BYOK). On paid plans, you can provide your own API keys from AI providers and turn them on for a project. Your plan always comes first: your keys only take over when nothing is left for the usage concerned (building or chat). Those calls are then at your expense, billed by your provider under its own terms, and do not use your credits. Your plan's limits — storage, compute resources, access to the code editor — still apply.

Dictation. Dictation always goes through our own accounts with providers: your keys cannot be used for it. Before each recording, we check that you have enough left to pay for its maximum length; it is then charged for its actual length. When nothing is left, dictation is unavailable until the next renewal or your next credit purchase.

Web search. Each web search by the assistant costs a fixed price, known in advance. It only runs if what you have left covers it and never goes into overdraft; a search that fails on the provider's side is not charged to you. If the assistant cannot search, it tells you.

Shared projects. On a project you invite other people to, you, as the project owner, pay for everything done on it, whichever member acts; each spend is recorded with the person who triggered it. A monthly spending cap can be set for a member: once it is reached, that member can no longer trigger spending on that project until it resets, and the owner can carry on the work. When you are invited to someone else's project, your own credits are not used.

When a mission fails. The credits spent on the work already done remain due, and fixing it is charged like the work it requires. If a build stops because of an incident on our side, the step in progress is never charged to you. If a task could not be built, it is not charged to you, within the retries your plan provides for the same project; beyond that, further attempts are charged as usual until the next successful build. Finished work remains yours. Our team can take over under the conditions in the next section.

Refunds. Credits already spent are not refundable, except after an incident on our side or for a task that could not be built (see “When a mission fails”). A subscription payment is refundable within 7 days, as long as you have not spent more than 15% of the plan's credits for the period and that period has not been replaced by a plan change or a renewal; the subscription then ends and your account returns to the free plan, while your purchased or offered credits remain yours. A credit pack is refundable as long as it has not been drawn on (deducting an overdraft counts as drawing on it); the refund then removes the corresponding credits. You are entitled to one such refund, subscription and pack combined, per twelve-month period. Request it in the app, from your payment history, or by writing to [email protected]; it is made in full, to the means of payment you used. These terms are in addition to any statutory withdrawal rights you have under your local law — including the right of withdrawal described in the next section — and do not limit them.

5. Right of withdrawal (consumers in the European Union or the European Economic Area)

If you are a consumer residing in the European Union or the European Economic Area, you may withdraw from a paid subscription or a credit pack purchase within 14 days of the contract being concluded, without giving any reason.

Immediate start. At checkout, you ask us to start providing the service immediately, during the withdrawal period. If you then withdraw, you owe an amount proportional to what was provided until you informed us of your withdrawal, compared with the full coverage of the contract; credits already spent are part of what was provided. You lose your right of withdrawal once the service has been fully performed.

How to withdraw. Use the "Withdraw from contract" button, in the Billing part of your account, or email [email protected] with a clear statement of your decision before the 14 days run out. You may use the following model form, but you do not have to: "To OmniLab, 7157, chemin des Forts, Lévis (Quebec) G6Y 0R7, Canada, [email protected] — I hereby give notice that I withdraw from my contract for the following service: … — Ordered on: … — Name and account email: … — Date: …".

Refund. We reimburse the amounts received, less the proportional amount above, without undue delay and at the latest within 14 days of receiving your withdrawal, using the same means of payment you used, at no cost to you.

6. Referral programme

Your referral link earns bonus credits, once, for you and for the person you invite. The person you invite receives theirs when they complete their first build. You receive yours once they have paid for their first subscription and the 7-day refund window on that payment has passed without a refund. A sign-up alone earns nothing, and buying a credit pack does not count as a subscription.

To keep the programme fair, some referrals are not rewarded on the referrer's side: accounts created from the same network or device as yours (including several accounts belonging to the same person), and referrals beyond the monthly cap on rewarded referrals, shown in the app. The person you invited keeps their bonus whenever they genuinely used the service.

Abusing the programme — self-referral, fake or automated accounts, or any scheme designed to farm bonus credits — may lead to the removal of the credits obtained and, in serious cases, to the suspension of the accounts involved. Bonus amounts and caps can change at any time; a change never removes credits already granted.

7. Your code is yours

You own the applications Makasi builds for you: the generated source code, your git history, your database schema and your content. On any paid plan, you can export your project at any time, with no exit fee: you download a self-contained archive, ready to run, with your code and, if you wish, your data. On the free plan, if you need your data, write to our support team.

You grant OmniLab a limited, non-exclusive licence to host, run, copy and display your projects strictly to operate the service (builds, previews, hosting, backups).

The Makasi platform itself — site, agents, templates and infrastructure — remains the property of OmniLab.

Code size. The code of all your applications (the sum of their git histories) has a maximum size per account. Beyond it, no new build starts, and no credits are used, until the code is reduced with the help of our support team. You keep access to your code and, on a paid plan, can always export it.

Demo content. Makasi app templates contain demo images and text intended solely to illustrate the template; they may come from third-party stock image libraries. Before publishing your app or using it commercially, you must replace them with your own content or with content you hold the rights to. Makasi does not warrant that this demo content may be used beyond that illustration.

8. Hands-on help from our team

When a mission fails, you can ask our team to take it over. You then authorise Makasi's technical team to access that project's code and logs for as long as diagnosis and relaunch require, at our expense and without spending your credits.

This is a service we offer: its scope, its availability by plan and its turnaround may change, and it is neither a guarantee of outcome nor a commitment to a deadline. The plans that include it are listed on the pricing page.

Outside of that case, our team only accesses your projects to operate the platform (security, backups, incidents) or where the law requires it.

9. Acceptable use

You agree not to use Makasi to build or host anything illegal, harmful or abusive — including malware, phishing pages, scams, content infringing intellectual property or privacy, spam infrastructure or cryptocurrency mining — nor to attack, overload, probe or circumvent platform limits, including quotas, rate limits and anti-bot protections.

Technical caps protect the service: messages per minute, message length, number, format and size of attachments (images and documents), as shown in the interface, length of a dictation recording, and compute resources per project. These are abuse protections, never billing lines: hitting one slows down or temporarily suspends the action, it never triggers an additional charge.

Multiple accounts. We do not automatically block sign-ups coming from the same IP address, because many people share one. However, creating several accounts to accumulate free credits is abuse: it may lead to the removal of the credits obtained this way and to the suspension of the accounts involved.

Reporting abuse. Anyone — with or without an account — can report an application hosted on Makasi at makasi.dev/abuse. Every report is reviewed by a person. We aim to handle reports within two business days, and sooner for phishing, malware or fraud; this is a target, not a guaranteed turnaround.

Taking action. Depending on the case, we may ask you to fix the problem, unpublish the application, or suspend it or your account while we investigate — immediately if the risk to third parties requires it. We tell you why, unless the law or an ongoing investigation prevents it, and you can contest the decision by replying to our message.

App names and addresses. You choose your application's name and address under your own responsibility. We may refuse, change or remove a name or address that could be confused with Makasi or with a third party, misuses a trademark or impersonates a bank or a payment service, is reserved for technical use, or is offensive or unlawful, and suspend the application concerned while the situation is resolved. Except in an emergency or where the law requires otherwise, we let you know first and invite you to choose another one.

10. Copyright notices (Canada)

If you believe an application hosted on Makasi infringes your copyright, send a notice of claimed infringement to [email protected] or through makasi.dev/abuse, with the information required by section 41.25 of Canada's Copyright Act. As a host, we forward a compliant notice to the owner of the application as soon as feasible, tell you that it was forwarded (or why it could not be), and keep the records the Act requires — six months, or one year if you notify us that you have commenced proceedings.

Forwarding a notice does not mean we have assessed the claim. We may separately act under the acceptable use section.

11. Your responsibilities

You are responsible for the data you and your applications store, for keeping your credentials secure, and for ensuring that apps you expose to real users comply with the laws that apply to them, including their own privacy obligations.

Generated code is produced by AI under your direction. We run automated quality, security and isolation checks on every build — designed to leave no trace in your application (no file, no account, no data) — but you remain responsible for reviewing and validating generated code and configurations before relying on them in production, especially for applications handling payments, personal data or other sensitive operations.

If you bring your own API keys (BYOK), you are responsible for those keys and for the corresponding provider's terms and charges.

Most of the content Makasi produces is generated by artificial intelligence: code, text, images, plans and agent replies. It may contain errors or inaccuracies. It is your responsibility to check it, if needed with the help of qualified professionals (for example on legal, tax, security or accessibility matters), before using it in production or making it available to your users.

On the free plan, the Makasi badge shown on your applications must remain visible; hiding it is prohibited.

12. Availability

We work hard to keep Makasi available and your data safe — isolated infrastructure, daily backups — but the service is provided without an uptime guarantee. Maintenance windows and incidents are communicated by email and in the app.

Hosting included in your plan is subject to fair use: we may throttle or temporarily cap an application that exceeds its plan's limits, but we never bill for the overage.

13. Termination

Cancelling your subscription deletes nothing: it ends at the end of the paid period, your account then moves to the free plan, and your projects and data are kept. You can keep using them, within that plan's limits. Since export is reserved for paid plans, export anything you want to keep before the paid period ends.

You may also delete your account at any time. Your access is then cut off right away, and your account is deleted within 72 hours, together with your projects, their code, your databases and your files. So export (paid plan) or ask us for (free plan) anything you want to keep BEFORE you ask for deletion.

We may suspend or terminate an account for serious or repeated breaches of these terms.

If you move to a lower plan, your application stays online within the new plan's limits — nothing is deleted.

Credits left unspent when you cancel are neither refunded nor transferred, subject to any rights your local law gives you. If you are a consumer residing in Quebec, your purchased credit balance is never forfeited, and a balance of $5 or less is refunded on request — write to [email protected].

14. Limitation of liability

To the maximum extent permitted by law, Makasi is provided "as is" and OmniLab's total liability for any claim related to the service is limited to the amounts you paid us in the 12 months preceding the claim. We are not liable for indirect damages such as lost profits, or for the behaviour of applications you build and operate.

Nothing in these terms limits liability that cannot be limited under applicable law, including mandatory consumer protection rules.

15. Governing law

These terms are governed by the laws of the Province of Quebec and the federal laws of Canada applicable therein. Any dispute will be submitted to the courts of the judicial district of Montreal, Quebec, subject to any mandatory consumer protections of your place of residence.

16. Changes to these terms

We may update these terms; material changes are announced at least 30 days in advance on the site or by email. Continuing to use Makasi after a change takes effect means you accept the new terms.

17. Contact

OmniLab — [email protected]

© 2026 OmniLab — Makasi.TermsPrivacyLegal noticemakasi.dev