Step 1
Your code
Type or paste it when the game starts, then Continue. Used already, or doesn't work? Ask whoever sent it for a new one.
For testers
You're playtesting a game.
A studio sent you a build and a code. Here's what happens when you play, what's recorded, and how to get your recording deleted.
Windows 10 (22H2) and 11 · free · no account. Get the Launcher below, or, if your studio sends a zip and a code, use those.
Step 2
The NDA, then consent
If the studio asked, you read their NDA first. Then you choose what's recorded. Decline records nothing, and you can still play.
Step 3
Play
REC sits in a corner the whole time anything records. Pause it with F9, flag a moment with F6, finish from F10.
WHAT'S RECORDED
Only what you agreed to.
The consent screen lists each stream. Picture and game sound start on; your mic and webcam start off and only record if you turn them on yourself.
Game pictureWhat's on your screen in the game
On
Game soundThe game's own audio
On
Your microphoneThink out loud, if the studio asks you to
Off until you turn it on
Your webcamOnly if the studio offers it
Off until you turn it on
What you do in the gameMenus, where you went, the game's errors and frame rate
Once you accept
An events-only build never records picture or sound at all, only what you do in the game. The consent screen says so.
THE REC LIGHT
If it records, you'll see REC.
A small REC sits in a corner for as long as anything records, and turns into an amber PAUSED square when you pause. A faint PLAYTEST BUILD mark tells this build apart from the real game.
REC12:04
PAUSEDF9 to resume
Can't see REC while something records?
Stop playing and tell the studio. A build for outside testers must never hide it.
Your keys while you play.
These are the defaults. A studio can change them, so check its instructions. Every screen works with a gamepad too.
A short note box. Type what happened, leave a voice note, or just press through.
What kind, how bad, and when it happened. Your PC and build info go along.
Picture and sound stop; the game keeps going. What you do is still recorded.
Finish, or stop and delete my recording if you change your mind.
Goes back from any playtest screen.
Uploading
Your recording uploads in the background while you play, straight to the studio's storage: Mulno Cloud, or the studio's own bucket. Close the game whenever you like: it picks up the next time you launch it, within 3 days. Each part is deleted from your PC once it's safely uploaded.
Windows warnings
The game, its uploader and the Launcher aren't code-signed yet. If you see “Windows protected your PC”, select More info, then Run anyway. An antivirus prompt about a program reaching the internet is the uploader; allow it if you trust the studio.
YOUR RECORDING
Want it deleted? Ask the studio.
The studio that sent you the build decides what happens to your recording. Where it lives depends on the studio: on Mulno Cloud (storage Mulno provides, the default for a new project) or in the studio's own bucket. Its privacy notice says which. On our deletion page, a Mulno Cloud session is hidden at once and deleted for good within 30 days; for a bucket the studio owns, we hide what we indexed and tell the studio.
Deletion requests, in detail-
1
Copy your session ID
The end screen shows it, with a Copy button. Copy it before you close the game.
Session 7Fq2Kx9PzR -
2
Send it to the studio
Their contact is on the same end screen, if they gave one. The ID is how they find your recording. No contact? Enter the ID on our deletion page. If the studio uses Mulno Cloud, your session is hidden at once and deleted for good 30 days later; if it uses its own bucket, we hide what we indexed and tell the studio for you.
-
3
It gets deleted
On Mulno Cloud, it is hidden at once and, unless the studio restores it, deleted for good within about 31 days of you asking on our deletion page (the clean-up runs once a day). The studio can restore it in that time, and should do so only if the request wasn't yours or the law lets it keep the recording. If you ask again after a restore, the studio is told again. In a studio's own bucket, the studio deletes it. Used stop and delete my recording mid-session? It cleared your PC; ask the studio for the parts already uploaded.
Questions testers ask.
Anything about the game itself, or your recording, goes to the studio that sent it.
Do I need a Mulno account?
No. Type the code or open the link the studio sent. Testers never sign up, and never pay.
Can I play without being recorded?
Yes. Decline on the consent screen records nothing, and you can still play. If a studio's build is set to keep recording what you do in the game after a decline, that is only menus, where you went and errors, never your picture, sound or camera, and the consent screen says so.
Does Mulno see my recording?
It depends on where the studio keeps it, and its privacy notice says which. On Mulno Cloud, the default for a new project, your recording is stored on Mulno's servers for the studio, whose team watch it there. It is kept for the studio's plan period (14 days on Free, a year on Indie, no fixed limit on Team) and then deleted. In the studio's own bucket, it goes straight there and doesn't pass through Mulno; Mulno can read it only if the studio lends us a read key for that project.
What does Mulno itself get?
A short technical report on how well recording worked on your PC: your graphics card maker, dropped frames and similar numbers. No picture, no sound and no name, unless the studio turned it off.
I'm under the studio's minimum age.
Answer the age question honestly. Then only what you do in the game is recorded, never your picture or sound.
The code says it was already used.
A code is yours alone and works once. Ask whoever sent it to you for a new one.
Got a link from a studio?
Open it. The Mulno Launcher takes it from there: the NDA, the download, updates and uploads. If your studio sends a zip and a code instead, unzip it and type the code.