Last updated August 12, 2026

Privacy Policy

This policy covers two separate things: the personal data we hold about you as a rignu subscriber, and the public federal carrier records, including business contact details, that we republish to subscribers.

1. Subscriber data we collect

When you create an account we store your email address, authentication identifiers, plan tier, saved filters, export history and notification preferences. If you sign in with Google we receive your email and basic profile identifiers from that provider. Payment details, if collected, are handled by our payment processor and are not stored by us.

2. How we use subscriber data

We use it to authenticate you, enforce plan limits, deliver the product, monitor export usage for abuse, and send service or digest emails you have opted into. We do not sell subscriber account data.

3. Carrier data: what we resell

rignu is a data product. We collect publicly available motor carrier registration records published by the Federal Motor Carrier Safety Administration and make them available to paying subscribers. Those records include business identifying and contact information such as legal name, DBA name, USDOT number, physical and mailing address, telephone number and, where the carrier filed one, an email address.

Many U.S. motor carriers are sole proprietors, so a record may contain what is effectively an individual's name, home address, personal phone or personal email, even though it was filed as business contact information. We publish it as it appears in the public federal file. We do not enrich it, append data from other sources, or attempt to identify individuals beyond the filed record.

Access to contact fields is tiered: public pages and Starter accounts see masked records without phone, email or street address. Growth and Enterprise subscribers can see and export the full record.

4. Carrier requests about their own record

If you are a carrier and want your record suppressed from rignu, contact us and we will remove it from our index. Because the underlying data remains public at the federal source, removal from rignu does not remove it from FMCSA or from other resellers. We cannot correct the federal record on your behalf.

5. Cookies and analytics

We use strictly necessary cookies for authentication, and optional functional, analytics and marketing cookies subject to the consent choices you make in our cookie banner. You can change those choices at any time.

6. Retention and security

Subscriber data is retained while your account is active and for a reasonable period afterwards for legal and accounting purposes. Carrier records are retained as an ongoing historical index. Data is stored with our hosting and database providers under access controls and row-level security.

7. Your rights

Depending on where you live you may have rights to access, correct, export or delete the personal data we hold about you as a subscriber, and to object to certain processing. Send requests through our contact page and we will respond within the period required by applicable law.

8. Google API Services usage disclosure

Compliance with Google's Limited Use Policy

rignu's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Data access and collection

When you click Connect Gmail in the rignu dashboard, we request access to restricted Gmail scopes. Specifically, we request permission to read, compose, and send emails on your behalf, and to modify messages so you can delete (move to Trash) a message from the rignu inbox at your request. We only request the minimum permissions necessary to implement our application's features.

How we use your Google data

We strictly limit the use of your Google user data to providing and improving user-facing features that are prominent in the rignu application's user interface. Your data is used exclusively to:

  • Send the commercial carrier outreach sequences that you have configured and authorized in your Outreach Queue.
  • Sync and display email replies directly within the rignu Inbox so you can manage communications without leaving the platform.
  • We do not use your data to train non-personalized artificial intelligence or machine learning models.

Data sharing and transfers

rignu does not sell your Google user data, nor do we transfer it to data brokers or use it for advertising purposes. Transfers of data are prohibited, except in the following limited circumstances:

  • To provide or improve appropriate user-facing features that are visible and prominent in the application's user interface, and only with your consent.
  • For security purposes, such as investigating abuse.
  • To comply with applicable laws.
  • As part of a merger, acquisition, or sale of assets, strictly after obtaining explicit prior consent from the user.

Human access restrictions

rignu prohibits its employees and human personnel from reading your email data. Exceptions to this rule are strictly limited to the following scenarios:

  • We first obtain your affirmative agreement to view specific messages, files, or other data (e.g., to resolve a technical support ticket you submitted).
  • It is necessary for security purposes, such as investigating a bug or abuse.
  • It is necessary to comply with applicable law.

Data security and storage

We implement industry-accepted encryption standards to protect your data. All Google user data and credentials, including OAuth access and refresh tokens, are transmitted securely over HTTPS and kept encrypted at rest on our systems.

Data retention and revocation

You maintain full control over your connected accounts. You may disconnect your Gmail account at any time through the rignu dashboard. Upon disconnection, or if you request account deletion, rignu will promptly revoke the OAuth tokens and securely delete your cached email data and authentication credentials from our active servers.

9. Changes

We will update this page when our practices change and revise the last updated date at the top.