Testers, the recording notice and Flag this

Torqix can watch how it is used so the people who build it can see what is slow, broken or confusing. People who help test it — your own staff, or someone at another shop — are called testers. Nobody is a tester until an owner or manager ticks them, and nothing is recorded about a tester until they have read the notice and agreed. The recording is made with PostHog, a third-party analytics service; nobody who is not a tester is ever recorded, and neither is the customer portal.

Make someone a tester

Open /team. Under Testers, tick Tester beside the person and press Save. Their row then says whether they have read the notice yet, whether recording is on, or until when it is paused. Untick and save to stop them being a tester; the record of what they agreed to is kept, and ticking them again later asks them to read the notice again.

Being a tester is per location: a person who works at two of your shops is ticked at each one separately. Owners and managers can tick testers. When the shop's account is read-only because billing has lapsed, the tick is refused like every other change on the Team page.

What a tester sees first

The next time a tester opens Torqix they see one plain screen: what is recorded, what never is, where it is kept and how to pause it. It has two buttons. I understand stores when they agreed and which version of the notice they read. Not now closes the screen for the rest of that browser session and records nothing — recording stays off until they come back and press I understand. The same notice is always at /tester-notice, which works without JavaScript.

Recorded

Which screen and when; which button or control was pressed; rage-clicks, dead clicks and going back and forth; and a replay of the screen that shows Torqix's own labels — menus, buttons, tabs, column headings — with everything else blanked out.

Never recorded

Customer names, phones, emails, VINs, plates and addresses; anything typed into a box; prices, totals, payments and card details; photos, signatures and documents; search words and web-address details; and the customer portal.

Where it is kept

With PostHog, a third-party analytics service in the United States, which gets a random code instead of the tester's name. Screen replays are kept for 30 days and usage events for up to 12 months.

When the words of the notice change, every tester is asked to read the new version and press I understand again, and recording is off for them until they do.

The Recording dot, and pausing

A tester sees a small dot in the top bar: Recording while recording is on, Paused while it is paused, and Not recording before they have agreed to the notice. Pressing it opens /tester-notice, where Pause for 15 min and Pause for 1 h stop recording for that long — for example while on the phone with a customer — and Resume turns it back on early. A pause ends by itself when its time is up.

Flag this

Anyone signed in can press Shift and ? on any screen (not while typing in a box) to open Flag this; testers also have a Flag this button in the top bar. It asks What were you trying to do?, What did you expect to happen?, What happened instead? and How bad is it? — blocked, annoying or cosmetic. Only the first is required. The same questions are on /report-a-problem, which works without JavaScript.

Along with your answers the report carries the page's route pattern (/customers/[id], never the customer's id), the last ten browser errors this sign-in saw with personal details stripped, your browser family and the Torqix build — and, while you are being recorded, a link to that moment in your replay. It never carries anything you had typed into the page underneath, a screenshot, or the page's contents. Customer names, emails, phone numbers, VINs and plates are stripped from what you type as well, but do not type them.

A notice for your own staff

Some states ask an employer to tell staff in writing before their computer use is monitored, to get an acknowledgment, and to post the notice — New York, Connecticut and Delaware among them. On the Team page, Notice to your staff has ready-made text to copy, give to each tester and post where staff can see it. It is labeled a template, not legal advice, because it is one.

What PostHog sees, and who is recorded

PostHog runs only in the browser of a tester who has pressed I understand on the current notice and has not paused — the Torqix team records itself the same way, by being ticked as testers. Everyone else's browser never downloads it. Pausing, or being unticked, stops it on the next screen.

Every word on the screen is blanked out in the browser before anything is sent, except Torqix's own labels on menus, buttons, tabs, column headings and section titles. Everything typed into a box becomes stars, and photos, signatures and documents become grey boxes. Web addresses are cut down to the screen's pattern, with no search words. PostHog gets a random code for the tester and for the shop — never a name, email, phone number or shop name.