Privacy policy

Updated September 23, 2026

This notice describes information handled by the TitleThread application and its production website.

Sign-in and Google account information

Clerk provides authentication. When you choose Google sign-in, Google shares the identity information approved on its consent screen with Clerk, such as your account identifier, email address, name and profile image. TitleThread uses your Clerk user identifier and verified email to identify your account, match invitations and enforce access. Clerk account controls may display your profile information.

Google sign-in is used for identity, not to read your Gmail, Google Drive documents or contacts. Your Google password is entered with Google, not stored by TitleThread. Signing in does not automatically grant access to another person’s workspace.

Project information and its use

TitleThread stores information users submit, including project and client details, source PDFs, extracted text, parties, tracts, ownership information, notes and review decisions. Records may include personal information contained in source documents. The application uses these records to provide document review, title research, maps, reports and collaboration.

Account, membership, invitation and change-history records support access control and traceability. Hosting and authentication services also process technical request and security information, such as IP addresses, browser information and request times, to operate the service and investigate problems.

Access and service providers

Workspace members and invited collaborators can access content according to their assigned permissions. Application Global Admins can administer accounts and access workspaces. Authorized service operators can access stored data to maintain and recover the application.

DigitalOcean hosts the production application, database and document storage. Application backups are encrypted before storage in DigitalOcean Spaces. Clerk processes authentication and invitations; Google processes Google sign-in. These services receive the information needed for those functions.

If AI processing is configured and requested, the configured model provider receives relevant document text, page images or project context for extraction, grouping or land-scope analysis. Model responses and processing details can be retained with the project. Ask your administrator which provider is enabled before submitting content for AI processing; provider handling depends on that service and its account settings.

Displaying the OpenStreetMap street basemap sends tile requests, including the area viewed and the website origin, to OpenStreetMap. Its servers also receive normal connection information such as your IP address.

Storage, history and choices

Cookies maintain sign-in and selected workspace context. Browser storage remembers interface preferences. You can clear browser storage or sign out; doing so does not delete server records.

Project records and review history are retained until an authorized removal is performed. Archiving hides records from active views and is not permanent deletion. Backups can retain earlier versions after a change or removal. Removing a sign-in account does not automatically erase shared project history.

Contact the administrator to request access, correction, export or deletion, or to ask about retention and active providers. Requests need to account for your identity, shared records and preserved history. You can also manage connected access in your Google account and your sign-in profile through Clerk.

For privacy, account or data requests, contact your TitleThread administrator.

Provider notices and updates

Read the provider notices for their services: Clerk, Google, DigitalOcean and OpenStreetMap Foundation.

This page will be updated when the described handling changes. Its date identifies the current notice.