Test Mode

Every new project starts in test mode. It records exactly as a live project does — the same snippet, the same replay, the same Argus — but what it records is treated as a rehearsal, and it says so wherever the project appears.

What test mode costs you

• Recordings are deleted after 3 days, whatever retention your plan allows.
• At most 50 sessions a day. The count starts over at midnight UTC. A session that would be the fifty-first is refused with 402 test_mode_cap_reached; sessions already in progress keep recording to the end.

Everything else is the same. Sessions still count towards your plan's monthly allowance while they exist, translation and Argus work normally, and nothing is watermarked or cut short.

Going live

Open the project's Settings → Mode in the dashboard, or the Settings tab in the app, and turn test mode off. From that moment new recordings are kept for as long as your plan allows.

When to stay in test mode

• A staging or preview environment, where you want replay while developing and never want the recordings afterwards.
• The first days on a new site, while you check masking and the allow-list are right before keeping anything.
• A demo or a spike, where fifty sessions a day is plenty and you would rather the data cleaned itself up.

Test mode or a session cap?

They answer different questions. A session cap limits how much one project records in a month and keeps everything it does record. Test mode limits a day and throws the result away. Use a cap on a live project; use test mode while the project is not real yet.