← Terms and Conditions

R.E.L.A.Y. Privacy Policy

Pre-publication review draft. This copy contains unresolved owner and attorney decisions. It is available here for testing and review; it is not the final production privacy notice.

Privacy acknowledgment

Sign in to review and acknowledge this Privacy Policy as part of account setup.

Sign in

Readable Privacy Policy

  Part A — Draft Privacy Policy
  R.E.L.A.Y. Privacy Policy

  Effective date: [OWNER TO CONFIRM: effective date]

  Last updated: [OWNER TO CONFIRM: last-updated date and version identifier]








  1. Who we are and what this policy covers
  1.1 Who we are. R.E.L.A.Y. is operated by Operator Workbench LLC ("Operator
  Workbench", "we", "us"). This policy explains how we handle personal information.
  Personal information means information that identifies you or can reasonably be linked to
  you.

  1.2 What this policy covers. This policy applies when you:

          visit or use the R.E.L.A.Y. application at https://app.operator-relay.com;
          create an account, including before you buy a subscription;
          buy, use, cancel, or close a subscription or account; and
          contact us for support through [OWNER TO CONFIRM: support channels, for
          example email or an in-app form].

  1.3 Our company website. [OWNER TO CONFIRM: whether
  https://operatorworkbench.com is covered by this policy or has its own notice. Use one:
  "This policy also applies to our company website at https://operatorworkbench.com." or
  "Our company website has its own privacy notice at [URL]."]

  1.4 What this policy does not cover.

          Websites and services run by other companies. They have their own privacy notices.
          Information about our own employees, contractors, and job applicants. [OWNER TO
          CONFIRM, with attorney: whether a separate notice exists or is needed.]
          Information a business customer controls. Section 2 explains how that works.

  1.5 How to contact us about privacy.

          Operator Workbench LLC
          Mailing address: [OWNER TO CONFIRM: business mailing address]
          Privacy contact: [OWNER TO CONFIRM: dedicated privacy email or request form]

  [OWNER TO CONFIRM, with attorney: whether a Data Protection Officer or an EU or UK
  representative is legally required and has been appointed. Add their details here only if
  both are true. Otherwise delete this line.]


  2. Our role: when we decide, and when we act for a business
  2.1 When we decide how information is used. We decide how personal information is
  used for our own purposes of running R.E.L.A.Y. These are [OWNER TO CONFIRM: the list
  of own-purpose activities, for example creating and administering accounts, billing,







  answering support requests, keeping the service secure, and meeting our legal
  obligations]. For these activities, we are responsible for the information.

  2.2 When we act for a business customer. A business, such as a fleet or a dispatch
  company, may use R.E.L.A.Y. to keep information about its drivers, employees, customers,
  and other people. [OWNER TO CONFIRM, with attorney: which features and data fall into
  this role.] For that information, the business decides what is collected and how it is used.
  We handle it on the business's instructions to provide the service.

  2.3 What the business is responsible for. The business is responsible for telling its drivers
  and employees how it uses their information, for having a lawful reason to collect it, and
  for answering their privacy requests.

  2.4 If a business added your information. If you are a driver or employee and your
  information is in a business's R.E.L.A.Y. account, send questions and requests to that
  business first. If you contact us instead, we will [OWNER TO CONFIRM: the actual
  process, for example tell you which business to contact, pass your request to that
  business, or both]. We help the business respond.

  2.5 Individual accounts. [OWNER TO CONFIRM, with attorney: our role for information
  that an individual account holder, such as an owner-operator, enters about other people.]

  2.6 Separate agreements. Some laws require a written data processing agreement
  between us and a business customer. [OWNER TO CONFIRM, with attorney: whether one
  is offered and how a customer gets it.] This policy is not that agreement, and reading this
  policy does not replace it.


  3. Information we collect
  [OWNER TO CONFIRM: every category in this section against the actual product. Delete
  categories that are not collected and correct the examples.]

  3.1 Account and contact information. [OWNER TO CONFIRM: the exact registration and
  profile fields, for example name, email address, phone number, and username.]

  3.2 Business and fleet information. [OWNER TO CONFIRM: fields describing a business
  or fleet, for example company name, role, and team members.]

  3.3 Sign-in information. [OWNER TO CONFIRM: how sign-in works. State whether
  R.E.L.A.Y. receives the password you choose, how it is stored, whether an outside identity
  provider handles sign-in, and whether sign-in through another account is offered. Do not
  publish any statement about password storage until the developer verifies it.]








  3.4 Subscription and payment information. Payments are processed by [OWNER TO
  CONFIRM: payment provider]. Card details are entered [OWNER TO CONFIRM: where
  card details are entered and who receives them]. We receive [OWNER TO CONFIRM:
  what Operator Workbench actually receives and stores, for example billing name and
  address, plan, transaction identifiers, a payment token, card brand, last four digits, and
  expiry date].

  3.5 Support communications. When you contact us, we receive what you send, such as
  your message, contact details, and attachments. [OWNER TO CONFIRM: support
  channels and tools.]

  3.6 Usage, device, and log information. [OWNER TO CONFIRM: what is recorded
  automatically, for example IP address, browser and device type, dates and times, actions
  taken in the application, and error reports.]

  3.7 Cookies and similar technologies. Section 9 covers these.

  3.8 Content you add. You may add records, files, images, and messages to R.E.L.A.Y.
  [OWNER TO CONFIRM: the content types the product accepts.] This content can include
  personal information about you and about other people.

  3.9 Trucking information. [OWNER TO CONFIRM each item, and delete any that is not
  collected: driver identifiers; load and customer details; routes; location, and if so whether
  approximate or precise, whether from GPS, and whether collected in the background;
  receipts; financial records; and documents.]

  3.10 Sensitive information. [OWNER TO CONFIRM, with attorney: whether anything
  collected is treated as sensitive under applicable law, for example precise location,
  government identification numbers, or financial account details, and what extra steps
  apply.]

  3.11 Information about other people. Information in R.E.L.A.Y. may be about people who do
  not have an account, such as drivers, customers, or contacts named in records and
  messages. The account holder or business that adds it is responsible for having the right
  to do so.


  4. Where the information comes from
  4.1 From you. You give us information when you register, fill in forms, upload files, send
  messages, contact support, and go through checkout.








  4.2 Collected automatically. [OWNER TO CONFIRM: which automatic technologies are
  actually used, for example server logs, cookies, pixels, software development kits, or
  telemetry, and what each collects.]

  4.3 From other people and services.

          A business administrator may add you to an account or invite you. [OWNER TO
          CONFIRM: whether this exists and what the administrator enters.]
          Connected services. [OWNER TO CONFIRM: each integration, the permissions it
          requests, and the data it brings in.] If you connect another service, we collect only the
          information that connection is set up to provide, as shown when you connect it.

  4.4 Collection in the background. [OWNER TO CONFIRM: whether any information,
  including location, is collected while the application is not in active use, which permission
  controls it, and how to turn it off. If none, the developer must verify that before a
  statement saying so is published.]

  4.5 Required and optional information. Required fields are marked when we ask for them.
  [OWNER TO CONFIRM: which fields are required.] If you do not provide required
  information, you may not be able to create an account, buy a subscription, or use the
  feature that needs it. Optional information can be left blank.


  5. How we use information
  5.1 Purposes. We use personal information for the purposes below. [OWNER TO
  CONFIRM: each row. Delete purposes that do not apply.]


     Purpose                                            Information used

     Provide the features you ask for                   Account information, content you add,
                                                        trucking information

     Create and administer accounts                     Account, business, and sign-in information

     Bill for subscriptions                             Subscription and payment information

     Answer support requests                            Support communications, account
                                                        information, and content needed to resolve
                                                        the request

     Keep the service secure and prevent abuse          Sign-in information, usage and log
                                                        information








     Purpose                                            Information used

     Find and fix problems                              Usage and log information, error reports

     Understand how the product is used                 Usage information
     [OWNER TO CONFIRM: whether product
     analytics is done and with what tool]

     Meet legal obligations                             The information the obligation requires

     Send marketing [OWNER TO CONFIRM:                  Contact information
     whether any marketing is sent]

     Advertising [OWNER TO CONFIRM: see                 [OWNER TO CONFIRM]
     Section 8]


  5.2 Legal bases. [OWNER TO CONFIRM, with attorney: whether EU or UK data protection
  law applies. If it does, insert the legal-basis table from Part E, supplement E1. If it does not,
  delete this paragraph.]

  5.3 Consent. Where we rely on your consent, we ask for it separately and you can
  withdraw it at any time. Withdrawing consent does not affect what was done before.
  Agreeing to the Terms and Conditions, or acknowledging this policy, is not consent to
  optional uses of your information.

  5.4 New purposes. If we want to use personal information for a new purpose that is not
  compatible with those above, we will tell you first and, where the law requires it, ask for
  your consent.


  6. Who can see your information in R.E.L.A.Y.
  [OWNER TO CONFIRM: this whole section against the product's actual permissions.
  Delete what does not exist.]

  6.1 You. You can see the information in your own account.

  6.2 Fleet administrators. If you use R.E.L.A.Y. under a business's account, that business's
  administrators can [OWNER TO CONFIRM: what administrators can do, for example view,
  export, change, and delete] information in that account. This can include information
  about you and your activity in the account. [OWNER TO CONFIRM: exactly what a driver's
  administrator can and cannot see.] Do not assume that what you enter in a business's
  account is private from that business.








  6.3 Teammates. [OWNER TO CONFIRM: what invited teammates can see, and who
  controls it.]

  6.4 People you choose. Messages and content you send or share are visible to the
  recipients you choose. Recipients can keep copies, and we cannot take those copies back.
  [OWNER TO CONFIRM: messaging and sharing features.]

  6.5 The public. [OWNER TO CONFIRM: whether any content can be made public. If none,
  the developer must verify that before a statement saying so is published.]

  6.6 Our staff. Authorized Operator Workbench personnel can access account information
  [OWNER TO CONFIRM: when and how, for example only to resolve a support request you
  raise, to investigate a security or abuse report, or to maintain the service, and what
  controls and logging apply].

  6.7 Leaving a fleet. [OWNER TO CONFIRM: what happens when a user is removed from or
  leaves a business account: what the business keeps, what the user keeps, and what
  happens to the user's login.]

  6.8 How we use message content. We do not review all messages or content. [OWNER
  TO CONFIRM: whether message content or attachments are used for any of the following,
  and delete those that are not: spam or abuse detection, moderation after a report,
  support at your request, analytics, or AI features.]


  7. When we disclose information
  7.1 Service providers. We use other companies to help run R.E.L.A.Y. [OWNER TO
  CONFIRM: each category actually used, and delete the rest: hosting and storage; sign-in
  and authentication; payment processing; email or text message delivery; customer
  support tools; analytics; AI providers; contractors; and professional advisers such as
  accountants and lawyers.] They receive the information needed for their service.
  [OWNER TO CONFIRM: that written contracts limit each provider's use of the
  information, before saying so here.]

  7.2 Provider list. [OWNER TO CONFIRM: where the current list of providers is available,
  for example a web address or on request to the privacy contact, and how customers are
  told about new providers.]

  7.3 Your business or fleet. As described in Section 6.

  7.4 At your direction. We disclose information when you ask us to, for example when you
  share content or connect another service.








  7.5 Legal requirements. We disclose information when the law or a valid legal order
  requires it. We review each request, disclose only what is required, and [OWNER TO
  CONFIRM: whether affected users are notified where the law allows].

  7.6 Safety, fraud, and security. We may disclose information where it is needed to
  investigate fraud, protect the security of the service, or prevent harm. We limit this to the
  information that is needed.

  7.7 Business changes. If Operator Workbench is involved in a merger, sale, or similar
  transaction, personal information may be transferred as part of it. The recipient must
  continue to honor this policy, or tell you about any change and give you the choices the
  law requires.

  7.8 Advertising partners. See Section 8.


  8. Advertising, sale, and sharing of information
  [OWNER TO CONFIRM, with attorney: advertising in R.E.L.A.Y. has been discussed but
  not decided. This section cannot be written until the owners decide whether ads will
  appear, whether they are contextual or based on a user's behavior, which advertising tools
  are involved, and what information each one receives. After that, the attorney decides
  whether any practice is a "sale", "sharing", or "targeted advertising" under the laws that
  apply, including where no money changes hands. Insert the matching alternative from
  Part E, supplement E5. Do not publish a statement that information is never sold or shared
  until that review is complete.]


  9. Cookies, tracking, and device permissions
  9.1 What these are. Cookies are small files stored in your browser. Similar technologies
  include local storage, pixels, and software development kits.

  9.2 What we use. [OWNER TO CONFIRM: the actual cookie and tracking inventory, using
  the table in Part E, supplement E4. For each one give the provider, purpose, category,
  duration, and whether it is first-party or third-party.] Some of these are needed for sign-in
  and security. [OWNER TO CONFIRM: whether any are used for analytics or advertising.]

  9.3 Your choices. [OWNER TO CONFIRM, with attorney: whether a cookie consent
  interface is needed and what it offers.] You can also block or delete cookies in your
  browser settings. Blocking cookies needed for sign-in will stop the application from
  working. Browser settings do not stop every kind of tracking.








  9.4 Browser privacy signals. [OWNER TO CONFIRM, with attorney: how R.E.L.A.Y.
  actually responds to the Global Privacy Control signal and to older "Do Not Track" signals.
  These are different signals. Describe only handling that has been built and tested.]

  9.5 Device permissions. [OWNER TO CONFIRM: which device permissions R.E.L.A.Y.
  requests, and delete those not used: location, notifications, camera, microphone,
  contacts, and files or photos. For each, give what it is used for and the real settings path
  to turn it off.]


  10. AI, automated decisions, and de-identified information
  10.1 AI features. [OWNER TO CONFIRM: whether R.E.L.A.Y. has AI features or uses AI
  tools on personal information in its own operations. If yes, insert supplement E6 from Part
  E. If no, the developer must verify that before a statement saying so is published.]

  10.2 Automated decisions. [OWNER TO CONFIRM, with attorney: whether R.E.L.A.Y.
  makes decisions about people by automated means alone that have legal or similarly
  significant effects. If no, delete this paragraph or state it once verified.]

  10.3 Aggregated and de-identified information. [OWNER TO CONFIRM: whether
  aggregated or de-identified information is created and used. If yes, insert supplement E7
  from Part E. If no, delete this paragraph.]


  11. Security and incidents
  11.1 Safeguards. We use safeguards designed to protect personal information. [OWNER
  TO CONFIRM: the safeguards the developer has verified are in place, described in general
  terms, for example encryption of data in transit, encryption of stored data, limits on staff
  access, sign-in protections, monitoring, backups, staff training, and review of providers.
  List only what is verified. Do not name certifications, audits, or tests that have not been
  done.]

  11.2 No guarantee. Safeguards lower risk. They cannot remove it, and we cannot promise
  that information will never be accessed or lost.

  11.3 What you can do. Use a strong, unique password and tell us promptly at [OWNER TO
  CONFIRM: security or support contact] if you think your account has been accessed
  without permission.

  11.4 Incidents. If we learn of a security incident, we assess what happened and what
  information was affected. We notify affected individuals, customers, and regulators when
  and how the law and our contracts require. Where we hold information on a business







  customer's instructions, we notify that business as our agreement with it requires, so that
  it can meet its own duties.


  12. How long we keep information, and how to cancel, export, and delete
  12.1 How we decide. We keep personal information for the period needed for the purpose
  it was collected for, and then delete or de-identify it. The table shows the period or the
  rule for each category.


     Information                                        How long we keep it

     Account and contact information                    [OWNER TO CONFIRM: for example while
                                                        the account is open, plus a set period after
                                                        closure]

     Content you add, including trucking and            [OWNER TO CONFIRM]
     financial records

     Messages                                           [OWNER TO CONFIRM, including what
                                                        happens to copies held by recipients]

     Billing and transaction records                    [OWNER TO CONFIRM, with attorney: the
                                                        period tax and accounting rules require]

     Support communications                             [OWNER TO CONFIRM]

     Usage and security logs                            [OWNER TO CONFIRM]

     Backups                                            [OWNER TO CONFIRM: backup expiry
                                                        period]

     Records of privacy requests and consent            [OWNER TO CONFIRM, with attorney]
     choices


  12.2 Cancelling, closing, and deleting are different.

          Cancelling a subscription stops future billing. Your account and its information stay in
          place. [OWNER TO CONFIRM: what a cancelled account can still access, and for how
          long.]
          Closing an account ends your access. [OWNER TO CONFIRM: how to close an
          account, and what is deleted and when.]








          Requesting deletion asks us to delete personal information. You can do this whether
          or not you close your account, using [OWNER TO CONFIRM: deletion request
          procedure].

  12.3 Export. You can get a copy of your information through [OWNER TO CONFIRM:
  export method and formats]. After cancellation or closure, export stays available for
  [OWNER TO CONFIRM: post-cancellation access period].

  12.4 Backups. Deleted information can remain in backup copies until those backups
  expire, which takes up to [OWNER TO CONFIRM: backup expiry period]. We do not use
  backup copies of deleted information for any active purpose. [OWNER TO CONFIRM: that
  deletions are re-applied if a backup is restored.]

  12.5 When we keep information longer. We keep specific information beyond these
  periods only where:

          the law requires us to keep records, such as billing and tax records;
          we are under a legal duty to preserve it for a dispute or investigation;
          it is needed to detect or prevent fraud or to protect security; or
          it is needed to establish or defend a legal claim.

  In each case we keep only the information that reason requires, and only for as long as the
  reason lasts.

  12.6 Information held for a business. We keep and delete information in a business's
  account on that business's instructions and our agreement with it. If you are a driver or
  employee and want that information deleted, ask the business. When a business deletes
  information or closes its account, [OWNER TO CONFIRM: what is deleted, when, and
  what remains in backups until they expire].


  13. Where information is stored and sent
  13.1 Locations. R.E.L.A.Y. is hosted in [OWNER TO CONFIRM: hosting locations]. Our staff
  and providers may access information from [OWNER TO CONFIRM: support-access and
  provider locations].

  13.2 Transfers between countries. [OWNER TO CONFIRM, with attorney: whether
  personal information is transferred between countries in a way that the law regulates. If
  so, insert the transfer wording from Part E, supplement E1, naming only safeguards that
  are actually in place. If not, delete this paragraph.]








  13.3 Asking about safeguards. Where a transfer safeguard applies, you can ask the
  privacy contact for information about it. We may remove confidential commercial terms
  from any copy we provide.


  14. Your privacy choices and rights
  14.1 Choices open to everyone. [OWNER TO CONFIRM: the account controls that
  actually exist, for example view and edit profile information, export, close account, and
  marketing preferences, with the real settings path for each.]

  14.2 Rights under the law. Depending on where you live and which laws apply, you may
  have legal rights over your personal information. These can include rights to access it,
  correct it, delete it, receive a copy, limit or object to certain uses, withdraw consent, and
  opt out of certain advertising uses. These rights have conditions and exceptions, and they
  are not the same everywhere. [OWNER TO CONFIRM, with attorney: which laws apply,
  and whether Operator Workbench will voluntarily offer any of these to all users
  regardless of location. Insert the matching supplements from Part E.]

  14.3 How to make a request. Contact [OWNER TO CONFIRM: request email or form]. You
  do not need an account to make a request.

  14.4 Checking who you are. We may need to confirm your identity before acting on a
  request. We ask only for what is reasonably needed, and we use it only to verify the
  request.

  14.5 Someone acting for you. [OWNER TO CONFIRM, with attorney: authorized-agent
  procedure, where the law provides for one.]

  14.6 When we respond. We respond within the time the applicable law allows. [OWNER
  TO CONFIRM, with attorney: the response period to state, including any permitted
  extension.] If we cannot do what you ask, we tell you why. [OWNER TO CONFIRM, with
  attorney: appeal process, where the law requires one.]

  14.7 Information a business controls. If your request is about information in a business's
  account, we direct you to that business and help it respond, as described in Section 2.4.

  14.8 No penalty. We do not treat you worse for using your privacy rights.

  14.9 Complaints. Section 19 explains how to raise a concern.








  15. Additional information for California and other US states
  [OWNER TO CONFIRM, with attorney: whether California's privacy laws or another state's
  privacy law applies to R.E.L.A.Y., based on a documented assessment. If one applies, insert
  the matching supplement from Part E (E2 for California, E3 for other states). If none
  applies, delete this section. Do not publish a state supplement "just in case": it makes
  commitments that must then be kept.]


  16. Communications and your choices
  16.1 Service messages. We send messages needed to run your account, such as sign-in,
  security, billing, and service notices. These are not marketing. You cannot opt out of them
  while your account is open, because we need them to provide the service and meet our
  legal duties.

  16.2 Marketing email. [OWNER TO CONFIRM: whether marketing email is sent. If so:] We
  send marketing email only [OWNER TO CONFIRM, with attorney: the basis, for example to
  people who opted in through a separate, optional choice]. Every marketing email has an
  unsubscribe link, and you can also [OWNER TO CONFIRM: any account setting].
  Unsubscribing from marketing does not stop service messages.

  16.3 Tracking in email. [OWNER TO CONFIRM: whether emails record opens or clicks, and
  with what tool. Describe it here if so.]

  16.4 Text messages and push notifications. [OWNER TO CONFIRM, with attorney:
  whether marketing texts or push notifications are sent. If so, insert supplement E8 from
  Part E, with its separate consent and opt-out. If not, delete this paragraph.]


  17. Children
  17.1 Age. R.E.L.A.Y. is a business tool for people working in trucking. It is not directed to
  children. You must be at least [OWNER TO CONFIRM: minimum age, matching Section 1.5
  of the Terms and Conditions] to use it.

  17.2 If a child's information reaches us. We do not knowingly collect personal information
  from children under [OWNER TO CONFIRM, with attorney: age]. If you believe a child has
  given us personal information, contact [OWNER TO CONFIRM: privacy contact]. We will
  look into it and delete the information where the law requires. [OWNER TO CONFIRM:
  how eligibility is actually checked at registration, if at all.]








  18. Other companies' services, and changes to this policy
  18.1 Other companies' services. R.E.L.A.Y. may link to or connect with services run by
  other companies. Those companies handle information under their own privacy notices,
  which we encourage you to read. We remain responsible for the information we choose to
  disclose to them, as described in Sections 7 and 8.

  18.2 Changes to this policy. We may update this policy. The dates at the top show when
  the current version took effect and when it was last updated. [OWNER TO CONFIRM:
  whether earlier versions are available, and where.]

  18.3 How we tell you. For a material change, we give notice through [OWNER TO
  CONFIRM: notification method, consistent with Section 20.2 of the Terms and
  Conditions] at least [OWNER TO CONFIRM: notice period] before it takes effect.

  18.4 New uses need more than a notice. If a change would use personal information we
  already hold in a materially different way, we will ask for your consent or give you another
  choice where the law requires it. We do not treat your continued use of R.E.L.A.Y. as
  agreement to a new use that needs consent.


  19. Contact and complaints
  19.1 Contact us. For any privacy question, request, or concern:

          Privacy contact: [OWNER TO CONFIRM: dedicated privacy email or request form]
          Mail: Operator Workbench LLC, [OWNER TO CONFIRM: business mailing address]
          [OWNER TO CONFIRM, with attorney: Data Protection Officer or EU or UK
          representative details, only if required and appointed]

  19.2 Raising a concern. Tell us what happened and how to reach you. We will look into it
  and reply. [OWNER TO CONFIRM: target reply time, if the owners want to commit to one.]

  19.3 Regulators. You may also have the right to complain to a government privacy or
  consumer protection authority where you live. [OWNER TO CONFIRM, with attorney:
  which authorities to name, based on the laws that apply. Part E gives the wording.]

  End of proposed Privacy Policy.