Back to Tragent Last updated: 12 August 2026

Privacy Policy

This Privacy Policy explains what information Tragent collects, how we use it, where it is processed, how long it is retained, and your rights.

Tragent helps trade businesses respond to customer enquiries, manage jobs and follow up with customers. In providing these services, Tragent processes information about account users and their customers.

Who we are

Tragent is operated from the United Kingdom.

If you have questions about this Privacy Policy or wish to exercise your privacy rights, contact support@trytragent.com.

Information we collect

When you use the Tragent app, we may collect and process:

Customer names, contact details, messages, job information and attachments are third-party personal information that Tragent processes on behalf of the trade business using the service.

If you use Try It Live on our website, we may collect and process:

Try It Live does not create a Tragent app account or write this information to Tragent's application database. The submitted content is processed through Vercel, Anthropic and Resend to generate and deliver the demonstration. Resend stores the sent email content and associated delivery metadata for the retention period described below.

The public website is delivered through Vercel, which receives visitor IP addresses, user agents, requested URLs and related technical request information. Website fonts are served locally from the Tragent website and do not create a runtime request to Google Fonts.

Connected email accounts

Tragent allows you to connect Gmail or Microsoft Outlook through the relevant provider's authorisation process.

For Gmail, Tragent requests the identity scopes openid, email and profile, together with gmail.readonly and gmail.send.

For Microsoft Outlook, Tragent requests openid, email, profile, offline_access, Mail.Read, Mail.Send and User.Read.

These permissions allow Tragent to identify the connected mailbox, read relevant post-connection messages, detect customer enquiries, create job and conversation records, send replies and follow-ups, and keep the job timeline current. Tragent applies the recorded connection time before retrieving message bodies for processing or storage.

Tragent does not access a mailbox until the account user explicitly authorises access. Authentication credentials are stored in encrypted form and are presented only to the selected mailbox provider when required.

Disconnecting a mailbox removes Tragent's stored connection credentials and stops future inbox access, automatic replies and follow-ups. Disconnecting is not the same as deleting the Tragent account. Jobs, conversations, messages and stored attachments already copied into Tragent remain while the Tragent account is active.

When an account is deleted, Tragent removes its stored mailbox credentials and makes a bounded attempt to revoke provider access where supported. Local credentials are removed regardless of whether provider-side revocation succeeds. You may also revoke Tragent directly through your Google or Microsoft account settings.

How we use your information

We use information to:

Tragent does not sell personal information, use it for advertising or use it to track people across other companies' apps or websites.

AI processing

Tragent uses Anthropic to classify enquiries, extract job information and generate replies and follow-ups.

Depending on the requested feature and the information supplied, Tragent may send Anthropic the customer message or email subject and snippet, recent conversation text, customer and job details, business profile, availability and calendar-summary context. This may include names, phone numbers, postcodes or towns, job details, timing and urgency.

Tragent does not intentionally send stored attachment files, mailbox credentials, OAuth tokens or API keys to Anthropic.

Anthropic processes this information under its commercial terms and does not use commercial API inputs or outputs to train its models. Tragent's optional Anthropic feedback sharing is disabled and Tragent has not joined Anthropic's Development Partner Program.

Anthropic's standard API retention currently applies. API inputs and outputs are ordinarily deleted from Anthropic's backend within 30 days, subject to limited safety, security, usage-policy enforcement and legal exceptions. Zero Data Retention is not currently enabled for Tragent's Anthropic organisation.

Tragent uses limited Google-derived content with Anthropic only to provide the user-facing feature requested by the account user. Tragent does not use Google Workspace API user data to create, train or improve artificial-intelligence or machine-learning models.

Push notifications

If you enable push notifications, Tragent sends an Expo push token and notification payload through Expo Push Service and Apple Push Notification service.

A notification may contain a customer name or email address, up to 120 characters of an enquiry snippet or sent follow-up, a notification type and an opaque job identifier. Notification content may be visible on the device lock screen.

Tragent removes its stored push token when the account is deleted. Expo states that notification content remains in memory or queues until handoff and that push receipts are cleared after 24 hours. Expo does not publish a numeric provider-side deletion period for Expo push tokens. Because Tragent currently sets no notification expiry, Apple may retain one undelivered notification for the app and device for up to 30 days. An already queued notification cannot be recalled through Tragent account deletion.

Subscriptions

Tragent uses RevenueCat and Apple StoreKit to manage subscriptions. They may process an opaque Tragent app-user identifier, Apple transaction information, product and plan identifiers, entitlement status, trial status and renewal or expiry information.

Apple controls payment processing and Apple-account transaction records. Tragent does not collect payment-card details.

When a Tragent account is deleted, local subscription and RevenueCat event records are removed and Tragent queues deletion of the corresponding RevenueCat customer profile. The task retries until RevenueCat confirms deletion or reports that the profile is already absent. Later RevenueCat webhooks for that deleted Tragent account are ignored and cannot recreate local subscription or account state.

Deleting a Tragent or RevenueCat customer profile does not cancel or erase subscription and payment records controlled by Apple. You must manage or cancel an Apple subscription through your Apple account.

Sharing and service providers

Tragent uses the following service providers and external services:

These providers process information to provide and secure their services, subject to their contracts and applicable law. Some providers may separately process account, service-usage, security, fraud-prevention, support or legal-compliance information for their own lawful purposes.

Google and Microsoft are the mailbox providers selected by the account user. They receive authorised API requests and outbound messages and provide mailbox information under the user's relationship with that provider and the applicable API and account terms.

Tragent does not:

Crash and diagnostic data

Tragent uses Sentry for application error monitoring and diagnostics and is currently on Sentry's Developer plan. Diagnostic information may include crash or exception details, device and operating-system information, app version, performance traces and opaque account or job identifiers.

Tragent does not intentionally send customer email bodies, mailbox credentials, OAuth tokens or raw request objects to Sentry. Tragent disables default personal information, request data and console-log breadcrumbs and applies additional redaction and privacy controls.

Diagnostic event data follows Sentry's applicable plan and data-type retention period. At the end of that period, the event data becomes inaccessible through Sentry's active service. Sentry separately creates infrastructure backups and states that those backups are deleted 90 days after creation.

Data protection

We use technical and organisational measures designed to protect information, including encrypted network connections, encrypted credential storage, access controls, production-system protections, monitoring and logging.

Stored attachments are kept beneath Tragent's configured private storage root. Tragent uses mailbox-scoped access controls, opaque storage identifiers, validated paths and monitored background deletion retries designed to prevent one account from reading or deleting another account's files.

While we take reasonable steps to protect information, no method of electronic transmission or storage can be guaranteed to be completely secure.

Data retention and account deletion

We retain active-account information for as long as needed to provide Tragent, meet legal obligations, resolve disputes and protect the service.

Disconnecting a mailbox removes its stored connection credentials and prevents future access and sending. It does not remove jobs, conversations, messages or attachments already stored in the active Tragent account.

When you delete your Tragent account, account access ends immediately. Active account records, sessions, connected-mailbox credentials, jobs, customer information, messages, attachment records, push tokens and local subscription records are removed through the account-deletion process.

Tragent then begins monitored background deletion of the corresponding stored attachment files. If a temporary filesystem failure occurs, access remains revoked and secure retries continue until cleanup succeeds. Tragent does not promise that physical-file cleanup will finish within 24 hours.

Tragent retains deletion-processing metadata for 30 days. It contains only opaque identifiers, timestamps, attempt counts, controlled error codes and cleanup status. It does not contain email content, attachment names, mailbox addresses or reusable provider credentials.

Tragent also stores an independent deletion ledger in a private Cloudflare R2 bucket so that deletion can be reapplied following a controlled restore. The ledger contains opaque account and deletion identifiers and deletion-stage timestamps, but no mailbox addresses, message or attachment content or reusable provider credentials. The production lifecycle rule deletes these ledger objects after 90 days.

The R2 bucket uses Cloudflare's Western Europe location hint. This is a placement hint and is not a guarantee of EU-only storage or processing.

Railway may retain operational application and deployment logs for up to 30 days. Tragent does not currently maintain Railway volume backups of its production database or attachment storage.

If production backup functionality is enabled in future, deleted-account data may remain in a backup for the applicable backup-retention period. Before a restored system returns to service, Tragent's controlled restore process reapplies the independent deletion ledger so that accounts deleted after the backup was created are removed again.

Tragent queues deletion of the corresponding RevenueCat customer profile and retries until RevenueCat confirms deletion or reports that the profile is already absent. Apple-controlled subscription and payment records are not deleted through this process.

Other service-provider retention

International processing and transfers

Some service providers process information outside the United Kingdom or European Economic Area, including in the United States.

Where Tragent makes a restricted international transfer through a processor relationship, the applicable provider terms use safeguards such as the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum or other recognised transfer mechanisms where applicable.

Anthropic states that stored API data is held in the United States and that processing may occur in the United States, Europe, Asia and Australia. RevenueCat, Resend and Vercel also identify United States processing in their published terms.

Vercel's production function is currently configured for London, Cloudflare R2 uses a Western Europe location hint and Resend uses an Ireland sending region. These settings do not guarantee that all storage, logging, support, security or subprocessor activity remains in the United Kingdom or European Economic Area.

Service providers may use subprocessors. Their current published subprocessor registers provide the authoritative list of those organisations and processing locations.

Your rights

If you are located in the United Kingdom or European Economic Area, you may have the right to:

To exercise these rights, request account deletion information or ask for the status of a background attachment-cleanup retry, contact support@trytragent.com. A pending physical-file retry does not restore access to a deleted account.

Google API Services User Data Policy

Tragent's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Information received from Google APIs is used only to provide and maintain the user-facing Gmail features authorised by the account user.

Google API data is not:

Limited Google-derived content may be processed by Anthropic for user-facing inference, by Railway for Tragent's active application storage and processing, and by the other providers identified above where necessary to operate and secure the authorised feature. Those transfers are limited to providing or securing Tragent and do not permit model training on Google Workspace API user data.

Disconnecting Gmail removes Tragent's stored Google credentials and stops future mailbox access and sending but does not remove existing Tragent jobs, conversations or attachments. Deleting the Tragent account removes Google-derived information from active Tragent systems and starts monitored physical attachment cleanup under the retention and deletion process described above.