Terms of Service

These terms are the agreement between the customer and Somnolent Team Limited (บริษัท ซอมโนเลนท์ ทีม จำกัด), registration no. 0105566229327, 374/19 Soi Lat Phrao 71, Khlong Chao Khun Sing, Wang Thonglang, Bangkok 10310, Thailand, trading as Mulno ("we", "us"). They cover the use of Mulno: Mulno Studio, the web app, the Mulno Launcher, the Unity package, the uploader, the command line and remote MCP, and Mulno Cloud storage.

The customer is the organisation a workspace's owner acts for or, when an owner signs up for themselves, that person. In these terms the customer is "you". The customer pays for Mulno, is bound by the DPA and covers us under section 15. Section 3 says how we identify it.

If you were invited into someone else's workspace, you are a member, not the customer. Section 19 is the part that applies to you.

By creating a workspace, buying a plan, or using Mulno for a workspace you own or administer, you agree to these terms for the customer. If you don't agree, don't use Mulno.

1. How these terms fit with our other documents

Paying. Paddle is our merchant of record: the seller in law of every paid plan. That is Paddle.com Market Limited, or the Paddle company its buyer terms name for where you buy (Paddle.com Inc. in the US, Paddle.com (Canada) Ltd in Canada). Paddle's buyer terms govern the purchase (the payment, tax, invoices, and its own refund rules). These terms govern the use of Mulno. Section 5 says more.
Personal data. Our privacy notice covers what we hold about the people who sign in. The DPA covers the recordings and other personal data we process for you, and is part of these terms (section 7). If these terms and the DPA disagree about personal data, the DPA wins.
The rest. What we store, retention, subprocessors, security, the AI statement and the refund policy describe the service and explain these terms. Where one makes us a promise, we keep it, and we change such a promise only as section 17 allows. The Plans and quotas guide in our documentation says what each plan includes, and the Pricing page gives an overview.
Your testers are not covered by these terms. Section 8 says who covers them.
If documents conflict, this order applies: (1) the standard contractual clauses, where the DPA brings them in; (2) the DPA or, for an Enterprise customer, its countersigned DPA, which replaces the DPA; (3) an Enterprise agreement or order; (4) these terms; (5) the Plans and quotas guide and the Pricing page, for a plan's numbers; (6) the other pages above. A plan's price is the one in section 4; the Pricing page only shows the most it can be.

2. Mulno is in beta

We are straight about where Mulno stands today.

The web app is new. app.mulno.com is where workspaces, billing and review in the browser live. During the beta we let new studios in from a waitlist (below). We may add, change or remove features during the beta.
Some things are marked "Soon" or "Coming" on the Pricing page or in a feature list. We promise nothing that is marked that way, and never the numbers in the Plans and quotas guide. Don't buy a plan for a feature that isn't there yet.
Our installers are not code-signed yet. Windows will show a SmartScreen warning, and some antivirus products flag a new recorder. Our guides explain what to do. You accept that cost, and you decide whether to install.
Things will break. We fix what we find, but a beta can lose a recording, show a wrong number, or stop for a while. Keep your own copy of anything you can't afford to lose. A Private bucket (section 6) is your own copy by design.
For now, new Mulno accounts are offered only to studios in Thailand, from our waitlist. Studios in Thailand join the waitlist on our website, and we choose whom to let in and when; joining doesn't promise an account. We e-mail the person we let in, and their account is made when they sign in. Someone invited into an existing workspace doesn't need the waitlist. Elsewhere our website says Mulno is coming soon, and you can write to us through its contact form or at developer@mulno.com. An account that already exists keeps working from any country.
Mulno accounts are not offered to people in the EEA or the UK until we name representatives there. If you are in one of them, don't create an account, and don't use someone else's. For the same reason, campaigns can't target testers in Europe or Worldwide for now: the product refuses those audiences. Section 8 says what that still asks of you.

3. Accounts and workspaces

Signing in. You sign in with a link we e-mail you, so you need an e-mail address you control. Keep it accurate. Whoever can read that mailbox can sign in as you, so you are responsible for what happens under your account.
Who is the customer. The customer is the organisation the workspace's owner acts for or, if the owner is an individual who doesn't act for one, the owner. We identify it by the legal name given when the workspace is created or by an owner or admin on its Billing page or, without one, by the workspace's name and its owner's e-mail address in Mulno. The person who creates a workspace or buys a plan for an organisation confirms they may bind it. We record which version of these terms was accepted, by which account, how and when (signing in, accepting an invitation, signing in through an AI client, creating a workspace, starting a checkout). On the workspace we also keep the legal name it had when its terms were last accepted. Only the customer pays, is bound by the DPA and covers us under section 15.
Who may open an account. You must be at least 18 and of legal age to make a contract where you live. During the beta, you must also have been let in from our waitlist, or invited into a workspace (section 2).
Workspaces and roles. A workspace is where a studio's projects, builds, campaigns and recordings live. Its owner and admins act for the customer: they decide who joins and what role each person has (owner, admin, member), and what they do in the workspace binds the customer. Members are invited people and agree only to section 19. When someone leaves your organisation, remove them. Their access to the workspace ends on their next request, though their sign-in itself stays valid until they sign out or it expires.
One Free workspace per account. To own a second workspace you pay for the first or you are invited into another. There is also a limit on how many workspaces one account can create and how fast. Being a member of other workspaces is never capped. Don't open extra accounts to get around a limit.
Testers are not members and never count as seats. They play a build with a code or a link and do not need an account.
Closing. An owner closes a workspace, and anyone erases their own account, in a workspace's settings (section 12).

4. Plans and limits

What each plan includes is in the Plans and quotas guide in our documentation, and the Pricing page gives an overview: seats, active campaigns, remote sessions a month, Mulno Cloud storage, how long sessions are kept on Mulno Cloud, and what the watermark and overlay are. We don't repeat the numbers here, because they change in one place. The numbers in the guide on the day you buy or renew are the ones that apply to that period, unless we agree other numbers in writing. Each plan also has technical caps, such as how many projects a workspace holds and how many builds a project keeps; the guide lists them, and the product names the cap when you reach it.
What a paid plan costs is the price we agree with the workspace owner or an admin in writing (an e-mail is enough) before the first payment. It is at or below the most the Pricing page shows for that plan, and checkout shows it. During the beta the Pricing page shows only that most, because we set the price with each studio. An agreed price stays the same through every renewal until we change it under Changes below (30 days' notice, from the start of a paid period), and never changes during a period you have already paid for.
The limits are real. The service enforces them. A push or an upload that would go over your storage is refused with a message that names your plan. Builds and sessions kept on Mulno Cloud count towards storage. A Private bucket is not counted.
"Unmetered" and "fair use". Where a plan says unmetered or fair use, we expect ordinary use for playtests. If you use far more than a team of your size reasonably would, or it harms other customers, we will write to you first and then may limit it.
Changes. We may change a plan's numbers or prices. A change takes effect at the start of a paid period that begins at least 30 days after we tell the workspace owner by e-mail, never in the middle of one you have already paid for. If you don't want the new terms of the plan, cancel before it takes effect.
Free. Free is a free plan with no card. We may change or end it. If we end it we give at least 30 days' notice, so you can export (section 12).
Enterprise is sold by separate agreement. Where that agreement and these terms differ, the agreement wins.

5. Paying, renewals and refunds

Paddle is the seller. When you buy a paid plan you buy it from Paddle, which takes payment, collects and files sales tax, VAT and GST where they apply, sends the invoice and handles chargebacks. Paddle shows the tax before you pay. We never see your card number. We pass Paddle the e-mail address of the admin who starts the checkout.
Prices are the ones we agreed with the workspace owner or an admin and that checkout shows, in the currency Paddle shows. If the price at checkout is not the one we agreed, don't pay: write to us and we will put it right.
Renewal. A paid plan renews on its own, monthly or yearly as you chose, until you cancel.
Cancelling. An owner or admin cancels on the workspace's Billing page. You choose at the end of the period you have paid for (the default: you keep the plan until then, nothing more is charged, and the page shows the day it ends) or right away (the plan stops now and the workspace goes to Free). Cancelling refunds nothing by itself: inside the refund window, use Cancel and refund instead (below). Paddle's e-mails also link its customer portal, where you can update your payment method, download invoices and cancel. Changing seats or switching plans on a running subscription isn't offered on the Billing page or in Paddle's portal yet: write to us and we do it for you.
A payment that fails. Paddle tries again. While it does, the workspace keeps its plan. If the subscription ends, the workspace returns to Free's limits (section 12).
Refunds are in the refund policy: in short, 14 days from the first payment and from each yearly renewal. Inside that window an owner or admin can press Cancel and refund on the Billing page: we ask Paddle at once for a full refund of that payment, with no reason asked, and the plan ends when Paddle approves it. Nothing in these terms limits a right to a refund or to withdraw that the law of your country gives you and that you can't give up.
A full refund or a chargeback ends the plan. When Paddle approves a full refund of a payment, however it was asked for (in Mulno, at paddle.net, through Paddle's support or through us), we cancel the subscription at once and the workspace goes to Free's limits (section 12 says what that means for your content). A partial refund leaves the plan running.
A chargeback (your bank or card issuer taking back all or part of a payment) does the same as soon as Paddle tells us of it, unless Paddle has already marked it rejected or reversed. If it is reversed later, the plan doesn't come back by itself: write to us and we put it right, or buy the plan again. A warning that a chargeback may come changes nothing.
If you dispute a charge with your bank, please write to us first. We can usually fix it faster, and a chargeback ends the subscription, as above.

6. Your content, and what we do with it

Your content is everything you put into Mulno or record with it: builds, recordings (video, audio, events, positions, notes, transcripts), project, branch, build and campaign names, the Catalog, and what we derive from them to run the service (an index, frames, cached transcripts).

It is yours. You own it, and so do the people who have rights in it. We claim no rights over it. We never use it to train a model, for advertising, or for any purpose of our own. The one thing we use for our own purposes is the small technical report on how recording went (no picture, sound or words), to build statistics that don't point to a person or a studio. The what we store page says exactly what that is.
What you let us do. You give us permission to store, copy, process, transmit and show your content to the members you choose, only as needed to run Mulno for you and as you instruct through the product. That permission ends when your content is deleted (section 12).
A Private bucket stays yours. In Private mode, recordings go from the tester's PC straight to your own bucket (Cloudflare R2; Amazon S3 isn't offered in the beta), and our servers don't receive them. The bucket, its cost, its key and its settings are yours. You are responsible for keeping them as the guided setup asks. The setup shows you the risk of an R2 key and asks you to accept it before the first upload. If you lend us a read key (one switch per project, off by default), our servers read that project's sessions to index them, show them in the browser and answer AI questions, as the statement you accept says. The files stay in your bucket, and turning the key off ends this.
Mulno Cloud. Where you choose Mulno Cloud (a new project's default), we store the content in our own Cloudflare R2, in the region your workspace uses. Members get short-lived signed reads. Nothing is public. Who at Mulno can look at it is described in the security page. Every read our servers make under a lent key is recorded in your workspace's audit log; reads of Mulno Cloud storage are not logged one by one.
What we can see in any mode: ids, states, byte counts, the names people type, and the text of an NDA you set for the Launcher to show before download. Don't type anything secret into a name; use a code name for work under NDA.
Hosted AI is not part of Mulno yet. When it is, it ships under the commitments in the AI statement, including no training on your content.
Feedback. If you tell us how to improve Mulno, we may use the idea freely. We don't use your content that way.

7. Personal data

You are the controller of the personal data in the recordings and other session data (your testers', and anyone else's in them). We are your processor for what Mulno Cloud, a lent key and our broker's records hold. The DPA is part of these terms for that data, from the first time you use Mulno: you don't need to sign anything. Its opening note says how it names you from the workspace's details. A countersigned copy, with terms you negotiate, is for Enterprise customers; ask at privacy@mulno.com.
We are the controller of the data we hold about people who sign in, under our privacy notice, and of the cross-studio capture-health statistics.
Our subprocessors are on the subprocessors page. We tell you 30 days before adding or replacing one that processes personal data for you.
If a breach affects your data, we tell you within 48 hours (see the DPA).

8. Your testers, and what you must do for them

Testers are your data subjects and not our customers. They don't sign these terms, they have no account with us, and we have no contract with them. They are covered by your consent screen, your privacy notice and your tester terms. Because we hold some records about them for you, they can also read what we store and the deletion page. Because you decide who is recorded and why, you must:

Get consent and tell testers the truth. Use the consent screen the Unity package provides. Show what is recorded and who sees it. Don't hide the recording indicator in a build with testers outside your own supervised team. Let testers say no, and don't treat a refusal as a reason to push them.
Publish your own privacy notice under your own name and address, before your first outside tester. You can also save it on a campaign: the Launcher shows it before the build downloads and we record which version it showed, not that testers agreed. It stays yours; saving it doesn't replace publishing it. We give you a template in the web app, and templates for a tester privacy notice and consent text on request (developer@mulno.com). They are not legal advice. Have your own lawyer read the version you publish for your game and your countries.
Set a minimum age that fits where your testers live (20 for people in Thailand; at least 16 in the EU unless you collect parental consent; never below 13). Turn on "parental consent collected by studio" only if you really did collect it. A tester under your minimum age without it gets no picture or sound.
Use your own NDA. The NDA a tester accepts is yours. We store the acceptance and show the text before the tester records (in the game, and in the Launcher once it is available); we are not a party to it and we don't draft it or enforce it.
Use the recordings only for what you told testers. Don't use someone's face, voice or words in public (a trailer, a post, an advert) without their separate yes. Don't use Mulno to build face or voice templates or to detect people's emotions.
Answer your testers. Handle their requests to delete or see their data. A tester can also ask on our deletion page; the request then shows on the session in your campaign. If the project keeps sessions on Mulno Cloud, we hide the session at once, e-mail your owners and delete it for good 30 days after the request unless you restore it (do that only if you are sure the request was not the tester's own, or the law lets you keep the recording; a tester's own request is an erasure request you must honour otherwise). If the tester asks again after you restored it, we don't hide it again: we e-mail your owners once and list the request again with Delete now and Keep. Deleting a session from its campaign deletes our records of it and, if the project keeps sessions on Mulno Cloud, its recording, notes and index at once, with no undo. You can also delete a Mulno Cloud session from its review in the web app (section 12). Anything else we hold of a session, ask us for through the product, not by e-mail (we act within 10 business days under the DPA). Don't e-mail us testers' session IDs or other details of theirs: our mailbox isn't used for your personal data (DPA section 7).
Look after your reviewers' AI and transcription. A speech-to-text provider or an AI assistant that your reviewers connect runs under your own account with that provider, not ours. You are responsible for it.
Don't aim campaigns at testers in Europe or the UK for now. We have no EU or UK representative yet (our privacy notice says so). The product refuses a campaign whose audience is Europe or Worldwide (a campaign made before it did keeps the audience it had). But an audience is only what you say you want, and a campaign may have none: we don't check where a tester is. So don't invite testers you know to be in the EEA or the UK, whatever the audience says. Keeping this rule is still your duty.
Follow the law that applies to you and your testers, including rules on recording people, children and cross-border transfers.

9. Acceptable use

Don't use Mulno to, and don't let anyone you invite:

break the law, or record or keep anyone's data without a lawful basis;
record people secretly, or in a way that works against their consent;
store, share or send material that is illegal, that infringes someone's copyright or other rights (section 20), or that sexually exploits children;
attack, overload or probe the service, or look for weaknesses without our written permission (if you find one by accident, write to security@mulno.com and we will work with you);
get around a limit, a plan check or a lock: for example by making extra accounts or Free workspaces, patching the software, or sharing one sign-in between people;
use Mulno Cloud as general file hosting, or to distribute anything other than builds for playtests and the recordings of them;
put malware in a build you send us to store, or use Mulno to deliver it;
use the software to make a competing playtest product (section 10); or
resell Mulno, or give someone access to it who isn't a member of your workspace or a tester.

If you break this section, we may act under section 13.

10. The software

What you get. While you follow these terms, you may install and use Mulno's software (Studio, the Launcher, the uploader, mulno, the capture core and the Unity package) for your own playtests, with the games and the testers you run. This includes copying the Unity package's runtime, the capture core and the uploader into builds of your games, and giving those builds to your testers to run for your playtests. Don't leave them in a build you release to the public unless we agree in writing. The right is non-exclusive and can't be transferred. Builds your testers already hold when these terms end may stay with them, but they can no longer record to Mulno's service.
Source-available components. Some components, such as the Unity package and the capture core, are published with their source. Where a component ships with its own licence file, that licence is the one that applies to it, and it wins over these terms for that component. Unless that licence allows it, you may not repackage the software into a competing playtest product.
What stays ours. Mulno's software, names and logos belong to us or our licensors. These terms give you no right to them beyond this section. Third-party parts (for example Unity, Cloudflare, and open-source libraries) have their own terms.
Updates. Studio and the Launcher check for updates. Some updates are needed for the service to keep working with them.
Sessions are plain files. A session is a folder in an open, documented format. You can read and keep it without us.

11. Availability and support

There is no service-level agreement (SLA). Mulno is provided "as available". The Status page on our website shows the results of our automatic checks of the main services, and the incidents we post. It is there to inform you: it isn't a promise that Mulno will be available, and it can be late or wrong. We may pause the service for maintenance, and Cloudflare and Paddle, which we rely on, may stop working.
Local recording works without our servers. A remote playtest needs them: if they are down, a tester may not be able to start or upload until they are back.
Support is by e-mail to developer@mulno.com on every plan, Free included. It is best effort: we answer as soon as we can, on working days in Thailand, and promise no response time. Enterprise customers get priority support if their agreement says so.
Mulno Cloud is not a backup. It is a place to review playtests, within your plan's limits and retention. Keep your own copy of anything that matters.

12. Retention, export and deletion

How long we keep sessions. On Mulno Cloud, how long depends on your plan; the retention page has each plan's number. When a session is older than that, it is hidden from everyone and deleted for good 30 days later. What a Private bucket keeps is up to you.
Deleting one session. An owner or admin deletes a Mulno Cloud session from its review in the web app. By default it is hidden from everyone at once and its recording, notes and index are deleted for good 30 days later; until then it can be restored. Or choose to delete it right away: then it is gone at once and can't be restored. A session a tester asked to have deleted on our deletion page is hidden at once and deleted for good 30 days after the request, unless you restore it first; restore it only if you are sure the request was not the tester's own, or the law lets you keep the recording (GDPR Art. 17(3)), because anyone who has seen a session ID can make a request. While it is hidden nobody can export it, and a plan change's hold doesn't delay its deletion. You can also delete it right away from its campaign. For a Private project, the recording is in your bucket: delete it there (with a lent key, we delete what we indexed from it when you ask through the product).
How deletion works. We may delete in two steps: marked deleted first, removed for good up to 30 days later. Copies can stay in Cloudflare's database backups for up to 30 more days (we can't turn that off), our request logs expire after 7 days, and the traffic log Thai law asks us to keep after 90 days. The retention page lists our own records and their times.
If your plan ends or drops. The lower plan's limits apply from then, and new uploads over them are refused. We won't delete anything only because your plan changed without first writing to the workspace's owners and giving 30 days to export it. When the new plan keeps sessions for less time, nothing is deleted for those 30 days: we e-mail the owners, the Billing page shows the date, and moving back up stops it. After that, the lower plan's retention applies. A build is never deleted because your plan changed.
Exporting. Your sessions are plain folders in an open format, and a Private bucket never left your hands. There is no export button in Studio yet. An admin can already download a Mulno Cloud project's sessions through Mulno's API (it signs short-lived links, and each export is in the audit log). Or ask us at developer@mulno.com from the owner's address, before a plan ends or before you close the workspace, and we make your files available to download for 30 days. Builds you pushed also stay on your own computer. An admin can export the workspace's audit log.
Closing a workspace. An owner closes it in the workspace's settings, by typing its name. It can't be closed while a subscription still bills: cancel first (a cancellation at the end of the period bills until that day). Closing is immediate and can't be undone: every member, invitation and AI connection is removed at once, its campaigns stop, and testers can no longer upload or download its builds. Export first: once it is closed, nobody can reach its content. From day 14 we delete what we hold for it (Mulno Cloud's recordings and builds, the search index, and its rows in our databases, our broker's included), finish within 30 days of the closing, and tell you in writing. What stays: the audit log's entries until their own year ends, with every member's address, account and sign-in details taken off them when we delete the workspace; a record that the workspace existed and was deleted (its id, plan and dates, no name), so its id is never used again; backups and logs until they expire; and records that the law requires us to keep (for example invoices, which Paddle keeps too). A Private bucket is yours and we don't touch it.
Erasing your account. You erase your own account in a workspace's settings, by typing your e-mail address. If you are the only owner of a workspace that is still open, hand it to someone or close it first. If you belong to no workspace any more (for example after closing your last one), write to privacy@mulno.com from that address instead. Erasing is immediate: your memberships, invitations, AI connections, sign-ins and account are deleted, and your address is taken off the audit log's entries. What stays is in the privacy notice: the record of which terms you accepted, the traffic log until it expires, and Paddle's own records.
Idle accounts. An account with no workspace that hasn't signed in for 24 months is deleted, once the job that does it exists. The privacy notice says when it does.

13. Suspending and ending

You can stop at any time. Cancel the plan (section 5), then close the workspace (section 12) if you want the data gone.
We may suspend or end your access if you break these terms, if the law or a court says we must, if we have to to protect the service, other customers or testers, or if your use creates a real risk. We tell you why and what you can do, and we give you a chance to put it right and to export your recordings, unless the law or a serious security risk means we can't. A suspension lasts only as long as it needs to.
We may end Mulno, or a plan, altogether by writing to you at least 30 days ahead. If we end a paid plan other than because you broke these terms, we have Paddle refund the unused part of what you prepaid.
When it ends, section 12 applies. Sections that by their nature should survive (6 to 8, 12, 14 to 16, 18 and 19) do.

14. What we don't promise

Mulno is provided "as is" and "as available". To the extent the law allows, we give no promise that it will be uninterrupted or error-free, that a recording will capture everything (a tester's PC, a driver or a game can stop it), that a transcript or an answer from an AI assistant is correct, or that it fits your particular purpose.
Nothing here is legal advice. Our templates and legal pages are drafts for you to take to your own lawyer. Meeting your own duties to your testers, publishers and regulators is up to you.

15. Limits on liability

One cap, for both of us. To the extent the law allows, each party's total liability to the other for everything arising out of or in connection with Mulno, these terms and the DPA, whatever the cause, is limited to the greater of what the customer paid for Mulno (through Paddle or under an order) in the 12 months before the event that gave rise to the claim, and US$100. It is one cap for these terms and the DPA together: the two are not added up. The US$100 is a floor for Free workspaces.
What sits outside the cap. The customer's duty to pay for Mulno, and the customer's duty under "Your side" below to cover us for a claim by one of its testers.
No indirect loss. We are not liable for lost profit, lost revenue, lost goodwill, or for loss that wasn't reasonably foreseeable, or for lost data you didn't keep a copy of.
What isn't limited. Nothing in these terms limits liability that the law doesn't allow to be limited: for fraud, intentional wrongdoing or gross negligence, for death, personal injury or harm to health, or our liability to a data subject or an authority under the law on personal data.
Your side. The customer is responsible for its content, its recordings and its testers' consent. It will cover us for a third party's claim, and what it reasonably costs us to defend it, to the extent the claim arises from (a) the customer's content infringing someone's rights or breaking the law, or (b) the customer breaking section 8 or 9, and not to the extent it arises from our breach of these terms or the DPA. We tell you promptly, let you handle the defence if you wish, and don't settle without your agreement. Only the customer gives this cover, never a member. A claim by one of the customer's own testers is outside the cap above; other claims under this paragraph count towards it.

16. Governing law and disputes

These terms, and any dispute about them, are governed by the laws of Thailand. The courts of Bangkok have exclusive jurisdiction. The standard contractual clauses in the DPA's annex keep their own governing law and forum. Paddle's buyer terms have their own, for the purchase.
Arbitration is offered only in an Enterprise agreement we negotiate. Otherwise the courts decide.
If you are a consumer (someone buying for personal use rather than for a business), nothing here removes the protection the mandatory law of your country gives you, including a right to go to your own country's courts where that law gives it. Mulno is meant for business use.
Before you start a claim, write to developer@mulno.com and give us 30 days to try to settle it.

17. Changes to these terms

If we change these terms we update the version and date at the top. A change that makes things worse for you takes effect at least 30 days after we e-mail the workspace owner, and never applies to anything that happened before it took effect. If you don't accept it, cancel and, if you are on a paid plan, we have Paddle refund the unused part of the period you paid for. If you keep using Mulno after the date, you accept the change.

18. The rest

The whole agreement. These terms, the pages they point to, and any order or Enterprise agreement are the whole agreement between us about Mulno. If part of them isn't enforceable, the rest still is.
Waiver. If we don't enforce something straight away, we haven't given it up.
Assignment. You may not transfer your rights to someone else without our consent. We may transfer ours to a successor of the business, and we tell you if we do.
Beyond our control. Neither of us is liable for a delay or failure caused by something outside its control, such as an outage at a provider we rely on, a power or network failure, or an act of authority.
Third parties. Nobody else has a right under these terms, except data subjects under the standard contractual clauses in the DPA. That includes your testers and Paddle. Paddle's rights come from its own terms.
Notices. We write to the e-mail address of the workspace's owner. You write to the addresses below. A notice by e-mail is given when it is sent, unless the sender gets a message that it wasn't delivered.
Language. These terms are in English. If we publish a translation, the English text wins.

19. If you were invited into a workspace

A member is someone a customer invites into its workspace. A member isn't the customer. The customer pays, is bound by the DPA and covers us under section 15. A member agrees only to this section, and to sections 14, 16 and 20 where they apply to a member.

Keep your sign-in safe. Sign in with the link we e-mail you, at an address only you can read. Don't share your sign-in. If someone else may have it, tell the workspace's owner and write to security@mulno.com.
Use Mulno for the workspace's playtests, and follow the law. Don't record people secretly, or in a way that works against their consent, or keep anyone's data without a lawful basis. Don't store, share or send material that is illegal, that infringes someone's copyright or other rights, or that sexually exploits children, or malware. Don't attack, overload or probe the service, or get around a limit or a lock. Don't resell Mulno, or give someone who isn't a member or a tester access to it.
Copyright. If material you put in a workspace is disabled after a copyright complaint and isn't put back, that is a strike against your account too. Three strikes in 12 months end your account, in every workspace (section 20).
Your access is the customer's to give and take. An owner or admin can remove you, and your access ends on your next request. We may suspend a sign-in that breaks this section. You can erase your own account at any time (section 12).
What you don't owe. You don't pay for Mulno through these terms, you aren't a party to the DPA, and you don't cover us for anyone's claim. What you write or review in a workspace belongs to the customer's workspace (section 6). Our privacy notice says what we hold about you.
If you also own a workspace, the whole of these terms applies to that workspace, as its customer.

20. Copyright complaints

Anyone who believes that something stored in Mulno infringes their copyright can tell us, and we handle it as this section says. It follows Thailand's Copyright Act (sections 43/1 to 43/8) and the US Digital Millennium Copyright Act (17 U.S.C. §512). In this section the sender is whoever sends us a notice, and "you" is still the customer. It binds members too (section 19).

Where to send a notice. To the Copyright Agent of Somnolent Team Limited, trading as Mulno (mulno.com): by e-mail to copyright@mulno.com (the fastest way), or by post to Copyright Agent, Somnolent Team Limited, 374/19 Soi Lat Phrao 71, Khlong Chao Khun Sing, Wang Thonglang, Bangkok 10310, Thailand. We read notices in English and Thai.
What a notice must contain. Nothing in Mulno is public, so a notice must say enough for us to find the material. It needs all six of these:

the sender's name (or their organisation's), postal address, phone number and e-mail address;
the copyrighted work said to be infringed (for several works, a representative list);
the material said to infringe it, and where it is in Mulno: the workspace, project, build or session, and how the sender came across it (for example, the code or link they were given);
a statement that the sender believes in good faith, having considered whether the law allows the use (for example as fair use), that the use isn't authorised by the copyright owner, its agent or the law;
a statement that the information in the notice is true and accurate and, under penalty of perjury, that the sender owns the copyright or may act for its owner;
the sender's signature, handwritten or electronic.

What we do with a notice. If something is missing, we write back and say what, and we act once the notice is complete. Then we promptly disable access to the material: no one in the workspace and no tester can open or download it, but we keep it, so it can be put back. We don't judge who is right. We e-mail the workspace's owners what we disabled and why, with a copy of the notice and how to answer it. If the material is in your own bucket (a Private project), we don't hold it and can't remove it: we stop Mulno from reaching it instead (for example, the Launcher's downloads of a build, or what a lent key let us index), and tell your owners and the sender so. We don't publish notices.
If you think we got it wrong: a counter-notice. If the material was disabled by mistake or because it was misidentified (for example, you have a licence for it), an owner or admin can send us a counter-notice, to the same agent. It needs all four of these:

your name (or the customer's), postal address, phone number and e-mail address;
what was disabled, and where it was in Mulno;
a statement that you believe in good faith that it was disabled by mistake or misidentification;
your signature, handwritten or electronic.

Putting it back. We promptly send the sender a copy of a complete counter-notice, with your contact details, so they can take the matter to court, and tell them when we will put the material back. When 30 days have passed since we received your counter-notice, we put the material back within the next 15 days, unless by then the sender has sent us proof that they have filed a lawsuit about it. If your plan no longer keeps the material by then, nothing comes back (section 12). We use this timing for every notice, including one made under US law.
Repeat infringers. Each time material is disabled under this section and isn't put back, or a court finds that it infringes, that is one strike. It counts against the workspace the material is in and, where our records show who put it there, against that person's account. A workspace or an account with three strikes in 12 months is a repeat infringer. We end it under section 13, after giving you a chance to export what wasn't disabled: the account can no longer sign in, and the workspace is closed as section 12 describes. We may end it at the first strike when a court has found the infringement, or when it is plainly deliberate (for example, someone else's whole game pushed as a build). Three strikes can't be put right, so they count as breaking section 9, and section 13's refund for a plan we end doesn't apply. A strike is struck off when its notice is withdrawn or a court finds no infringement. We may refuse a new account or workspace opened to get round this.
False notices. Don't send a notice or counter-notice that you know, or ought to know, is false. Whoever does may have to pay for the harm it causes: under Thailand's Copyright Act (section 43/8) and, in the US, including costs and lawyers' fees (17 U.S.C. §512(f)).
Other complaints. This section is for copyright. For anything else in Mulno you believe is illegal, write to developer@mulno.com. What we do with the personal data in a notice or a counter-notice is in our privacy notice.

21. Contact

developer@mulno.com: anything about these terms, your account, billing, closing a workspace or support.
privacy@mulno.com: personal data, the DPA and deletion requests.
security@mulno.com: a security concern.
copyright@mulno.com: a copyright notice or counter-notice (section 20).

What changed in version 10

Section 11: the Status page now shows live, automatic checks of our main services and the incidents we post (it showed a marked sample before). It is information, not a promise of availability; there is still no service-level agreement, and nothing else changes.

What changed in version 9

The opening and section 20: our company's English name is written as Thailand's company register has it, Somnolent Team Limited (it was Somnolent Team Co., Ltd.). It is the same company, บริษัท ซอมโนเลนท์ ทีม จำกัด, registration no. 0105566229327, and nothing else changes.

What changed in version 8

Sections 1, 4 and 5: the Pricing page now shows only the most a paid plan can cost (Indie up to $29 a month or $279 a year; Team up to $49 a seat a month, or $39 a seat a month billed yearly). During the beta we agree the actual price with the workspace owner or an admin in writing, at or below that most, and an agreed price carries through renewals until changed under section 4's 30-day rule. A plan's numbers are in the Plans and quotas guide, unless we agree other numbers in writing. Section 2 is unchanged in scope; it now says the "Soon" and "Coming" disclaimer never covers the guide's numbers. Nothing changes for an existing workspace: the most the page shows is the list price it showed before, and nobody pays a different price.

What changed in version 7

Sections 2 and 3: during the beta, a new account is opened only for someone we let in from our waitlist, or someone invited into a workspace; we no longer set workspaces up by e-mail. Nothing changes for an account or workspace that already exists, its plan or its price.

What changed in version 6

Section 8: you can save your privacy notice for testers on a campaign. The Launcher shows it before the build downloads, and we record which version it showed, not that testers agreed. Publishing your notice stays your duty.
The DPA (2026-10-07): section 1.4 names the Mulno Launcher; sections 1.3, 7(a), (c) and (d) and Annex 1 section 2 cover the notice, its template and the record of which version was shown.

What changed in version 5

Section 20 (new): copyright complaints. Where to send a notice and what it must contain, what we do with it, the counter-notice and putting material back (after 30 days, within the next 15), the repeat-infringer rule (three strikes in 12 months), and false notices.
Sections 9 and 19: material that infringes someone's copyright or other rights is named in what you and members mustn't store or share; members agree to section 20 too, so a strike counts against a member's own account.
Section 21: Contact (it was section 20) adds copyright@mulno.com.

What changed in version 4

Section 2: the web app at app.mulno.com is open; campaigns aimed at Europe or Worldwide are now refused by the product. What Mulno Cloud holds is on the what we store page and the Pricing page, not repeated here.
Section 3: the legal name can be given when a workspace is created, the Terms record lists where acceptance is recorded and keeps the workspace's legal name, and closing and erasing are in the product.
Sections 4 and 6: Mulno Cloud is a new project's default; sessions kept there count towards storage.
Section 5: cancelling defaults to the end of the period; Cancel and refund inside the refund window; a full refund, however it is asked for, ends the plan at once, and so does any chargeback Paddle hasn't rejected or reversed.
Section 8: the product refuses Europe and Worldwide audiences; not inviting testers in the EEA or the UK stays your duty; a tester's deletion request hides its Mulno Cloud session at once and deletes it after 30 days unless you restore it.
Section 12: deleting one Mulno Cloud session (30 days to undo, or right away); what happens to sessions past their plan's retention, the 30-day hold and notice when a plan drops, exporting through the API, closing a workspace and erasing an account in the product, and what stays afterwards (the audit log without members' details).
Sections 13 and 19: closing and erasing point to section 12.