Privacy policy

Operator and contact

LoadCatcher is operated by Tengiz Kalandadze, an individual entrepreneur registered in Georgia. Contact support@loadcatcher.online for support, privacy requests or questions about this notice. Effective date: 9 November 2026.

What we collect

Google sign-in provides an account identifier, verified email and profile information. We store your name, email, account role and workspace membership. Separately connecting Gmail stores encrypted authorization tokens for sending your requested messages. We store templates and signatures, sending preferences, mailbox addresses, invitations, paired-browser credentials and subscription records.

DAT and message information

For user-selected actions, the extension processes the recipient contact and pickup/destination city and state from the DAT listing. Sending history stores the recipient, route, subject, timestamps, status and errors. The current history table does not store a separate rendered message body; saved template bodies are stored. Copying a phone number uses your clipboard. Opening Google Maps shares route locations with Google.

Purpose and providers

We process this information to authenticate users, provide workspaces, render templates, send requested messages, manage access and subscriptions, and investigate failures. Google handles authentication and Gmail delivery. Render hosts the application and database in Oregon, United States. Cloudflare supplies domain and DNS services. Data may therefore be processed outside your country. Production payments are not yet enabled. If Paddle is enabled as our reseller, it will process checkout and billing data under its own applicable notices; this policy will be updated before launch. We do not receive your full card number.

Google account data

We request Gmail send permission, not inbox-reading permission. Google receives the recipient and message when you request a send. We do not sell Google user data or use it for advertising or training generalized AI models. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Your controls

Disconnect Gmail and revoke paired browsers from Gmail & extension. You can also revoke access in your Google Account connected-app settings. Team sending is disabled unless a mailbox owner enables sharing. A paired browser can send using its permitted selections, so keep pairing codes private.

Retention and deletion

We retain account information, templates and message history while operating your account unless deletion is requested or retention is required to resolve billing, security or legal obligations. The current application does not automatically expire send history or offer self-service account deletion. Email support@loadcatcher.online to request access, correction or deletion; we will verify the request and explain any information we must retain. Disconnecting Gmail removes the stored mailbox record but does not erase sent Gmail messages, templates or past activity.

Security and rights

Google tokens are encrypted at rest; session and device credentials are stored as hashes. Other database fields are not all encrypted by the application, and no service guarantees absolute security. Depending on applicable law, you may have rights to access, correct, delete or restrict processing, or complain to a relevant authority. Contact us to exercise them. We will publish material changes to this policy on this page.