Know what you share.

Sign-in and storage

Members sign in with their Understand Tech account, the same account as on the Understand Tech platform; the Lab verifies the account and keeps its own session. Lab records are stored in the Lab’s own database, operated by Understand Tech.

Unsubmitted forum topics, replies and field reports are saved in this browser tab’s session storage so you can return after signing in. They are sent to the Lab only when you submit. Use Discard draft to remove an unpublished draft; closing the tab normally ends this storage session.

The browser remembers your comparison shortlist. Temporary sign-in intent and tagged campaign source are stored for the browser session. When you create a profile, a valid campaign source may be saved with it so the team can count registrations by source.

The Lab measures browser navigation with unlinked page events containing the page path, tagged campaign, referring hostname, coarse device/browser category and approximate request country when available. Full URLs, query strings, form contents, names, emails, raw IP addresses and precise location are not stored in analytics. Country is unknown when hosting metadata is unavailable, including local development. To measure whether the Lab is useful, your private profile records the day of a save, resumed plan or follow action, and the date of your first save. Up to 120 activity days are retained with your profile, included in your export and removed when you delete that profile. Editors see aggregate activation and return metrics. My Lab provides a personal inbox and a seven-day brief from published news for followed or saved machines and replies to conversations you joined. Read status and muted conversations are stored with your profile, included in exports and removed when the profile is deleted. The inbox covers the past 90 days and up to 200 recent replies; it does not expose pending or removed contributions. The Lab does not currently send email notifications or digests, and following does not subscribe you to email. Embedded external content and links may connect to the named third-party provider when used; those services have their own data practices. The launch film is served by the Lab itself.

Optional visitor analytics

You can allow or decline optional analytics using Analytics preferences at the bottom of the site. Allowing it creates a random browser ID valid for up to 90 days and a session ID that expires after 30 minutes without a browser event. This connects visits, sign-in attempts and selected actions to help us understand conversion and return use. Browser privacy signals disable this optional identification. There is no session recording or third-party analytics service.

Disabling optional analytics removes events linked to that browser ID and prevents further browser identification. Clearing browser cookies can prevent the Lab from recognizing an earlier browser ID. Basic unlinked page measurement continues.

Successful account actions and API reliability are measured on the server separately from optional browser analytics. Signed-in operational events use a pseudonymous account key. Account-linked event details are included in your account export, and the server removes them when your Lab profile is deleted. Admin reports contain aggregates and require a verified, explicitly allowlisted UT account.

Reports cover up to 90 days at a time. Admins can permanently delete older analytics events using the back-office cleanup control; automatic scheduled cleanup is not configured. Visitor figures are browser estimates, not exact counts of people. Ad blockers, privacy choices and bots affect coverage.

Exporting and removing information

My Lab → Account provides an export of your Lab records. Clearing your workspace removes your profile, followed machines and saved configurations; it does not delete your previously published contributions or evaluation history.

Use the removal controls on your own contributions where available. For other removal or access requests, write to support@understand.tech. The team verifies account ownership before acting.

Hardware evaluation data

Submit a description using synthetic or public examples. Do not upload confidential workloads through a request form. The exact machine, access method, isolation, retention and cleanup arrangements must be agreed before a session.

An evaluation request does not reserve hardware or authorize a purchase. Remote access is not proof that the full stack operates offline.