1. Data we collect on this website
| Category | Data | Purpose | Legal basis |
|---|---|---|---|
| Contact form | Name, email, phone (optional), preferred language (optional), your message | To answer your request | Your consent, given by ticking the box under the form |
| Technical | IP address, browser type, requested page, timestamp, in the hosting provider's server logs | Security, abuse prevention, keeping the site running | Legitimate interest |
| Preferences | Chosen language and colour theme, stored in cookies on your device | To show the site the way you chose | Necessary to provide the feature you asked for |
This website does not use analytics, advertising, tracking pixels or social-media plugins. We do not build profiles of visitors. See the Cookie Policy for every cookie the site sets.
2. Data we process on the platform
When your company signs up for Relay Assist, it creates an organization and invites its dispatchers and drivers. On the platform we process:
- Account data: email address, display name, role in the organization, hashed password or sign-in provider identifier.
- Operational data your organization enters: driver names and driver statuses, trucks and trailers, trips, saved search filters, notes, and the documents your organization chooses to upload.
- Telegram data: if you link Telegram, your Telegram user identifier and chat identifier, so the bot can deliver messages your organization configured, and the text of the alerts it sends you.
- Extension data: the extension works in your own signed-in Amazon Relay tab and never sends your Amazon Relay password or sign-in tokens to our servers. For your organization it sends: the carrier's trips, including stop locations and the truck's last reported position; the driver roster (names and phone numbers); trucks (plate, VIN, unit number, make, model, year); settlement statements and pay figures; truck posts; and presence signals (whether the extension and a Relay tab are active). While a dispatcher is signed in, it also reads the Amazon Relay load board in the background and sends the load rows (lane, stops, times, payout, equipment) to a load pool shared across Relay Assist customers. Other customers never see which carrier recorded a load; we keep that link only for our own audit. The extension's Chrome Web Store listing describes what it does in more detail, including what runs without a click.
- Connection routing: if Relay Assist sets your company up for it, the extension sends its requests to relay.amazon.com through our own gateway, which forwards them through an exit we rent from a datacenter proxy provider, so Amazon Relay sees that exit's address instead of yours. Our gateway sees your IP address and which Amazon Relay host is contacted and when; the provider sees which host and when, but not your IP address. Neither sees the content, which stays encrypted. Each user can turn this off on their computer in the extension's settings.
- Chrome Web Store Limited Use: the use of information the extension receives complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use it only to provide and improve the Relay Assist features described in this policy. We do not sell it, transfer it to data brokers, use it for advertising, or use it to decide creditworthiness or lending. People read it only with your organization's permission, for security and abuse investigations, or when the law requires it.
Your organization decides what operational data to enter and is responsible for informing its drivers. Driver compliance fields (for example work-authorization status) are stored as status values only, never as document numbers, and are visible only to roles your organization's administrator allows.
3. Automated processing and AI features
Some platform features send text or documents to an AI model to produce a result, and each is enabled per organization. The rate-confirmation reader extracts fields from a document you upload by sending it to Anthropic, PBC. The dispatcher assistant answers questions about your organization's own data; it receives your question, any files you attach, the data of your organization it looks up to answer (which can include driver details) and, when you ask from the extension, the visible text of the Amazon Relay page you are on. Its model requests go to OpenRouter, Inc., which routes them only to model endpoints that keep no copy of the data (zero data retention). Those endpoints are currently in the US or Asia. The assistant itself runs on Railway, with a separate workspace for each user that is deleted when it goes idle. We do not use your data to train AI models. No decision with legal effect on a person is made automatically.
4. Who receives the data
| Recipient | What | Why |
|---|---|---|
| Supabase, Inc. (database and authentication, hosted in Frankfurt, Germany) | Platform account and operational data | Storing and authenticating platform data |
| Railway Corp. (application hosting; EU and US regions) | Website and dashboard traffic and server logs; the assistant's requests and files while it answers; for companies with connection routing, your IP address, which user and company is connecting, and the Amazon Relay host and time of each request through our gateway | Running the website, the dashboard, the assistant and the gateway |
| Telegram FZ-LLC | Messages delivered through the Relay Assist bot, including contact-form submissions | Messaging you chose |
| OpenRouter, Inc., routing only to zero-data-retention model endpoints (currently in the US or Asia) | What the dispatcher assistant receives (see section 3), where your organization enabled it | Generating the assistant's answer |
| Anthropic, PBC | Rate-confirmation documents you upload to the reader, where your organization enabled it | Extracting the fields |
| PostHog, Inc. (EU cloud) | Product usage events and error reports from the dashboard, only after you press Allow in its analytics prompt (see the Cookie Policy): user and organization identifiers, role, pages visited, browser details and IP address; not email addresses, page text or session recordings | Understanding and fixing the product |
| Oxylabs (datacenter proxy provider) | Which Amazon Relay host is contacted and when (not your IP address), only for companies set up for connection routing | Routing the connection your company was set up for |
| Google LLC (YouTube) | Your IP address, only if you press play on an embedded video | Playing the video you requested |
We do not sell personal data and do not share it for advertising. We disclose data when the law requires it or to protect our rights, and we add any new recipient to this table before it receives data.
5. International transfers
Platform data is stored in the European Union. Our team and some providers operate from other countries, including the United States, and the dispatcher assistant's model requests may be processed outside the EU, currently in the US or Asia. Where data leaves the country it was collected in, we rely on the provider's standard contractual clauses or an equivalent safeguard.
6. How long we keep data
- Contact-form messages: until your request is resolved, and no longer than 12 months.
- Server logs: deleted automatically by our hosting provider, within 90 days.
- Preference cookies: 12 months, or until you clear them.
- Platform data: for as long as your organization's account is active. After an account or organization is deleted, the data is removed from live systems within 30 days. Database backups taken before that rotate out automatically within a further 30 days.
7. Your rights
Depending on where you live (including the EU, the UK, California and other US states, and Kazakhstan) you may have the right to access the personal data we hold about you, receive a copy in a machine-readable format, correct it, delete it, restrict or object to its processing, and withdraw consent at any time. You also have the right to complain to your data-protection authority.
To exercise a right, message us through the channels below. Platform users can also file a deletion request from Account settings, which their organization's administrator sees. We answer within 30 days. We will ask you to confirm your identity through the channel you registered with, and we never ask for passwords.
8. Security and breach notification
Data travels over HTTPS, passwords are hashed, database access is restricted per organization with row-level security, and administrative access is limited to named staff. If a breach affects your personal data, we will notify the competent authority and the affected people without undue delay, and no later than the deadline the applicable law sets, with a description of what happened and what we are doing about it.
9. Children
Relay Assist is a business tool for carrier companies. It is not directed to anyone under 18, and we do not knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.
10. Changes
When this policy changes materially we update the date at the top and notify platform users by email or in the dashboard before the change takes effect.
Who we are and how to contact us
Relay Assist is provided by Relay Assist.
- Telegram: @relay_assist_bot
- Email: support@relayassist.co