Privacy
Last updated: 31 August 2026.
When you use the signed-in Tessera application, we record a generated app-session identifier, the allowlisted workspace area in use, cumulative estimated active seconds, timestamps, and the signed-in user and workspace ownership needed to count distinct organisation memberships and keep a session within the correct workspace. A person active in two organisations counts once in each.
An app session is a browser activity period, not a Clerk login or authentication record. Estimated active time is sampled and capped while Tessera is visible, focused, and has had recent interaction. It is not exact task time, working hours, productivity, or attendance.
Product-usage signals do not contain names, email addresses, page URLs, record IDs, customer content, form values, search text, keystrokes, keys pressed, pointer or mouse movement, click details, scroll position, session replay, IP addresses or user agents. Interaction details are not sent or stored.
Restricted Tessera owners use organisation-level trends, allowlisted work-area totals, and aggregate user cohorts to understand product adoption and improve design or support. It does not return an individual user activity table. The first release has no export and must not be used for productivity, attendance, employment or disciplinary decisions.
Detailed app-session and workspace-area data is deleted 90 days after the session's last recorded activity. Cleanup continues if new activity capture stops. History begins when Product Insights is deployed and is not reconstructed from Clerk, Audit, logs, marketing analytics or Sentry.
Email hello@tesseraconnect.co.uk to ask how product-usage data is handled, request correction or deletion where applicable, or raise a privacy objection. You do not need to provide customer-record content or describe the work you were doing.
Where enabled, Tessera sends privacy-filtered technical error events to Sentry so restricted engineering staff can detect, investigate and resolve reliability faults. An event may include the exception type, filtered message and stack trace, a redacted route, request method and status, service, environment, release, and limited browser, operating-system or runtime details. This is separate from Product Insights and is not used to measure attendance, productivity or working time.
Tessera is configured not to send user identity, request or response bodies, form or page content, cookies, headers, query strings, local variables, console logs, interaction breadcrumbs, session replay or profiling data. Recognised email addresses, record identifiers and tokens are redacted before transmission. Sentry receives ordinary connection data when an event is sent; Tessera requires Sentry's IP-storage prevention and server-side data-scrubbing controls to remain enabled. Monitoring events are retained for the period configured for the Sentry account and are available only to authorised operational staff. Email hello@tesseraconnect.co.uk with a monitoring or privacy question.
When you contact us, Tessera Connect collects the name, email address, company name, approximate user count, modules of interest and message you submit.
We use this information to respond to your enquiry, discuss workflow or setup needs and keep a record of the conversation.
We keep enquiry information only for as long as needed to manage the enquiry, follow up with you and maintain basic business records.
You can ask Tessera Connect to update or delete enquiry information by emailing hello@tesseraconnect.co.uk.
Where enabled, Google Analytics is limited to allowlisted public marketing pages. It is disabled on sign-in, signed-in workspace, Help Centre and Owner Console routes, and page-view locations omit query strings and referrers. This is separate from signed-in Product Insights; see Cookie Information for more detail.