Last updated: October 7, 2026
Clerk processes account and authentication information. TraceRemove stores the conversations, messages, agents, runtime records, and billing state needed to provide the features you use. If you request paid access, we also collect your name, work email, organisation, requested plan, activation timeline, intended workspace use, and any pilot success criteria you provide.
When you interact with product, pricing, billing, or workspace calls to action, TraceRemove automatically records a bounded event name, page path, placement, plan, source, result, timestamp, and available UTM campaign fields. Session storage is used to retain campaign attribution and suppress duplicate view events during the browser session.
This information is used to authenticate access, save your work, run the mode and model you select, enforce available account entitlements, operate the service, and evaluate and answer direct paid-access requests. We do not accept agency, reseller, partner, or white-label requests.
Your prompts are processed by the model and runtime selected for the request. Configured routes can include TraceRemove's owned runtime or hosted OpenAI, Anthropic, Google, and approved OpenRouter models. Search mode may send the query to OpenAI's web-search tool and return links to public sources. Hosted requests are made through server-side routes; the selected provider's terms and privacy practices apply to its processing.
Conversation data is stored in Supabase. Direct paid-access requests and the conversion events described above are collected through Netlify Forms; access requests are routed to the TraceRemove corporate support inbox so they can be answered. Application endpoints require Clerk authentication and scope conversation reads, changes, and deletion to the signed-in user. Provider credentials remain in server-side configuration and are not returned to the browser.
TR Companion can use the goals, preferences and facts you explicitly save and enable. That profile and connector enable flags are stored in private Clerk account metadata and read only by authenticated server endpoints for your account. Enabled personal context is included in your Companion requests to the selected AI model. You can edit, disable or delete the saved profile at /assistant; this does not delete previous conversation messages.
Google and GitHub connections require provider permission through Clerk and a separate per-connector enable control. This version reads only on an explicit request: Gmail message headers and snippets, Drive file metadata and links, upcoming primary-calendar events, or public GitHub repository metadata. It does not send mail, change events, modify files or repositories, or run background monitoring. OAuth tokens are managed by Clerk and retrieved server-side; they are not returned to the browser or included in model prompts.
Connector results are shown for your review. Choosing to use results in Companion stages a draft in this tab's account-keyed session storage and removes it after the workspace consumes it. You must send the draft yourself; its selected contents are then processed by the AI provider and can be retained in conversation history like other messages. Disable stops new Expert reads without unlinking your sign-in account or revoking provider permission. You can revoke grants through your authentication account settings or the provider.
TraceRemove does not sell connector data, use it for advertising, or train its own models on it. Google API data is used to provide the user-requested connector and assistant functions; TraceRemove's use and transfer of that data must adhere to the Google API Services User Data Policy, including its Limited Use requirements. The selected AI provider's processing terms remain applicable to any contents you choose to send.
When paid billing is used, checkout and subscription management are handled by Stripe. TraceRemove stores the customer, subscription, plan, status, quantity, renewal, and usage records used by its billing and entitlement code.
The workspace provides controls to delete individual saved conversations. To request account or additional data deletion, contact support@traceremove.expert. TraceRemove will process applicable requests subject to identity verification and records it must retain for legal, security, billing, or fraud-prevention purposes. Additional account controls may be available through the configured authentication and billing services.