If you are a tester
The game's end screen shows your session ID with a Copy button — this is how a studio (and, where it applies, Mulno) finds your recording without knowing your name.
- While you're still playing: the playtest menu's "Stop and delete my recording" stops recording and deletes everything recorded of you from that computer immediately. In a remote playtest, the game also tells the studio's campaign that you withdrew, so the studio sees your session marked as withdrawn — but any part already uploaded is not deleted by this step: the studio deletes it (step 2).
- After you've played, or for anything already uploaded: write to the studio running the playtest (its contact is on the consent screen and its privacy notice) with your session ID. The studio deletes what it holds, and Mulno's records too.
- Or ask on Mulno's deletion page: enter your session ID at www.mulno.com/delete. We mark your session so the studio that ran the playtest sees that you asked. The page answers the same whether or not the ID is one we know, so nobody can use it to find out about a session. Please don't send your session ID to us by e-mail: our mailbox isn't used for playtest records. If the studio keeps its recordings on Mulno Cloud (storage Mulno provides for it; its privacy notice says so), your request hides the session at once (nobody in the studio can open, search or export it unless an owner or admin restores it first), tells the studio's owners, and Mulno deletes the recording it holds, with its notes and what it indexed from it, for good 30 days after your request, together with Mulno's records of it. A change in the studio's plan doesn't delay that. Because a session ID isn't a secret, we can't tell your request from someone else's, so the studio can restore the session within those 30 days: it should do that only if the request wasn't yours (or the law lets it keep the recording). If it was yours, the studio shouldn't restore it. If the studio restores it and you ask again, we tell the studio again and don't hide the session a second time, so the studio then decides. If the recording is in the studio's own storage, Mulno hides and then deletes only what it indexed from it; the recording itself is the studio's to delete.
- Mulno's own records (the broker's rows: your session's state, byte counts, the age answer, and your NDA acceptance if there was one) are deleted automatically 90 days after the campaign closes, expires or is stopped, whether or not you ask — see retention. After a request on the deletion page for a Mulno Cloud session they are deleted when Mulno's copy of the recording is, 30 days after the request. The studio can delete them sooner, and they go within 30 days if the studio closes its workspace.
We don't know your name from the recording — the session ID is how any request is matched to the right one. A studio should answer within the time its own privacy notice promises (typically one month; 30 days in Thailand).
Mulno's traffic log, which Thai law asks us to keep for 90 days, holds your IP address but no session ID, so it can't be matched to your recording and isn't deleted early on a request.
If you are a studio
- Your own Private bucket: deleting a session's files is entirely in your hands — it's your storage.
- Mulno's records of a session (the broker's rows): open the campaign and delete the session there (in Mulno Studio, "Delete Mulno's records of this session"). It deletes them at once. A session a tester asked about on our deletion page is marked "Tester asked for deletion". If the project keeps sessions on Mulno Cloud, the same action deletes the recording, its notes and what we indexed from it, at once, with no undo.
- A tester's request on our deletion page (Mulno Cloud, or what we indexed under a lent key): Mulno hides the session at once, e-mails the workspace's owners, and deletes its copy for good 30 days after the request, unless an owner or admin restores it first. The request is listed in the web app's campaign screen with its date and a Restore button. Restore a session 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)), and then tell the tester: anyone who has seen a session ID can make a request. A tester's own request is an erasure request (the recording rests on your legitimate interests, so it is not a withdrawal of consent) that you must honour unless the law lets you keep the recording. While the request stands, nobody can export the session either: an owner or admin restores it first, which is audited. After 30 days it can't be restored (a plan change's hold doesn't delay that). You can also delete it right away, as above.
- A tester who asks again after you restored it: Mulno doesn't hide the session again (so a request can't keep a recording hidden by being repeated). It records the repeat in your audit log, e-mails each owner once (at most one such e-mail per session in 7 days: "asked again after you restored it; unless you know the first request wasn't the tester's, delete it now") and lists the request again in the campaign screen with Delete now and Keep. Delete now deletes the session at once, as above. Keep closes the request, leaves the session as it is and is audited; if the tester asks yet again, it is listed again.
- Mulno Cloud, any session: an owner or admin deletes it from its review in the web app. By default it is hidden from everyone at once and its files are deleted for good 30 days later, so it can be restored meanwhile; or tick right away and it is gone at once. Until it is deleted for good, an admin can download its files through our api (not a session a tester's request is hiding: restore it first).
- A Private project with a lent key: the recording is in your bucket; delete it there. What we indexed from it is deleted at once through our api, or for the whole project by turning the key off. Anything else we hold of a session, ask for through the product: under the DPA (§11.2) we act within 10 business days. Don't e-mail us session IDs or other details of your testers (DPA §7(j)).
- Closing the workspace entirely: an owner closes it in the workspace's settings, once no subscription bills. Access ends at once; from day 14 we delete what we hold for it, all within 30 days, and confirm it in writing (DPA §16). Before you close it, ask for a copy of our records, or for your Mulno Cloud recordings to be made available to download for 30 days: afterwards nobody can reach them. What we store lists what stays.
- Erasing your own account: each person does it in a workspace's settings (the privacy notice says what stays).
Last updated 2026-10-04: deleting one Mulno Cloud session (30 days to undo, or right away); a tester's request hides the session at once and deletes it for good after 30 days unless the studio restores it (PLAN D164), whatever the studio's plan changes meanwhile, and nobody can export it while it is hidden; a tester who asks again after a restore is told to the studio, not hidden again (PLAN D165); closing a workspace and erasing an account are in the product.