Privacy
Last updated: 11 November 2026.
When you use Tessera while signed in, we record a generated identifier for your visit, the approved workspace area you use, estimated active seconds and times. We also record the user and workspace references needed to count membership in each organisation and keep each visit within the correct workspace. A person active in two organisations counts once in each.
An app session is a period of activity in your browser, separate from your sign-in record. Estimated active time is checked at intervals and limited. It counts only while Tessera is visible, selected and recently used. It does not measure 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.
Authorised Tessera owners use trends for organisations, totals for approved work areas and groups of users to understand how Tessera is used and improve its design or support. There is no table of individual activity and no export. These figures 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.
When Help measurements are enabled, we collect optional Helpful or Not helpful ratings and optional reasons chosen from a list. We also count Help searches that contain text and searches with no result available to the reader. Daily records contain only the guide’s identifier and version for ratings, the Help area, where the guide was read and combined counts. They exclude search words or coded copies of them, customer content, user, workspace and session identities, record IDs, page addresses, IP addresses, browser identifiers and productivity measures.
A random receipt and a coded summary of the approved rating fields stop a retried rating from being counted twice. The receipt stays in browser memory while the guide is open. It does not create a cookie or a saved browser activity profile. Daily totals and receipts expire after 90 UTC calendar days, including today. Cleanup continues if collection stops, and reports leave out expired totals. Collection is off by default.
Active platform owners use combined summaries for 7, 30 or 90 days to improve instructions, examples and images. Percentages appear only with at least five responses or requests. Counts can include repeats and do not measure individual people, completed tasks, attendance or productivity. Help data is kept separate from Product Insights, identity, Audit and monitoring data, and cannot be exported. Ratings are optional and do not create a support request; use Still need help for support. Email hello@tesseraconnect.co.uk for privacy questions or requests without including customer content. Combined records cannot be looked up by person or workspace.
When enabled, Tessera sends technical error reports to Sentry, with private information filtered out. Authorised engineering staff use them to find and fix reliability problems. A report may include the error type, filtered message and code trace, a page or service address with private details removed, the request method and result, the service, environment, software release, and limited browser, operating-system or runtime details. This is separate from Product Insights and does not 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.
When enabled, Google Analytics runs only on approved public marketing pages. It is disabled on sign-in pages, inside workspaces, in Help Centre and in Owner Console. Page-view addresses leave out details after the ? and the address of the page you came from. This is separate from signed-in Product Insights; see Cookie Information for more detail.