Privacy Policy
Last updated: August 27, 2026 · Effective: September 9, 2026
This policy explains what "IRSA" MCHJ, a limited liability company organised under the laws of the Republic of Uzbekistan, TIN 313132120, does with personal information in Carrier Safety Check (the "Service"). It covers two groups:
- our customers and users — people who hold or use business accounts; and
- drivers and other individuals whose details appear in carrier documents
our customers upload. If that is you, section 9 is written for you.
The Service is designed for businesses engaged in United States freight brokerage and motor-carrier operations. Users may access it from other countries.
1. Information we collect
Account information. Your work email address, authentication information, interface language and business account information. Passwords and session credentials are handled by our authentication provider; we do not store plain-text passwords.
Verification requests. Carrier MC/DOT number, carrier name and, where you provide them, a driver name, commercial driver's license number, vehicle VIN, license plate, load reference, phone number, address and notes.
Uploaded documents. We store the source files you upload for the limited retention period described below. We may extract structured fields such as: carrier names and identifiers, addresses, phone numbers, insurance information, vehicle details and, where a commercial driver's license is provided, the driver's full name, license number, issuing state, expiration date and endorsement codes.
We do not intentionally extract dates of birth, photographs, signatures, physical characteristics or biometric identifiers into structured fields, and we do not use those fields in carrier risk analysis. The original document image or PDF may nevertheless contain those items as part of the source document until that source file is deleted. We do not perform facial recognition on uploaded documents and do not intentionally create biometric templates or biometric identifiers from document photographs.
Verification and audit records. We record information needed to reproduce what the Service showed at the time of a check, which may include carrier identifiers, source timestamps, source statuses, findings, risk score, PASS/REVIEW/BLOCK status, policy/ruleset version, system events and billing or usage information. Audit-event payloads do not contain document contents, driver names, CDL numbers, original filenames, or other direct document-derived personal information; they reference internal account, request and object identifiers instead.
Subscription and billing information. Plan, subscription status and billing metadata required to administer the account. Payments are handled by our merchant-of-record/payment provider. We do not receive or store payment card numbers.
Security and technical information. We may process IP address, request metadata, authentication events, device/browser information and operational logs as needed to secure and operate the Service.
We do not build advertising profiles and we do not buy personal information from consumer data brokers for this Service.
2. Why we use information
We use information to:
- provide the carrier-verification checks you request;
- read and compare uploaded documents with available records;
- calculate and preserve the results shown to you;
- operate monitoring, alerts and audit history where enabled;
- administer accounts, subscriptions and billing;
- secure the Service, prevent abuse and diagnose faults;
- respond to correction, privacy and support requests; and
- comply with law and protect legal rights.
The Service is designed for commercial motor-carrier verification. It is not designed for consumer credit, insurance, housing or employment screening, and customers are prohibited by the Terms from using it for those purposes.
We do not sell personal information or share it for cross-context behavioural advertising.
3. Automated analysis and product outputs
The Service uses automated rules and models to extract document fields, compare information and calculate carrier-level findings.
The proprietary risk score is not an official FMCSA safety rating. The PASS/REVIEW/BLOCK status is a configured product status based on the information and rules available at the time of the check; it is not a legal opinion or a guarantee of safety or trustworthiness.
A BLOCK status may only be produced by configured hard-block findings supported by authoritative evidence. Fuzzy or heuristic signals cannot block on their own; they produce REVIEW and/or affect the proprietary risk score.
4. Who else receives information
We use service providers and public/government data sources. Each receives the information needed for its function.
| Provider / source | What it receives | Why |
|---|---|---|
| Supabase | account, request, report and audit data | database and authentication |
| Cloudflare | uploaded files, application traffic and configured caches | hosting, delivery and object storage |
| Google Gemini API | uploaded image/PDF | document extraction and classification |
| FMCSA / US DOT | carrier MC/DOT number or carrier name | authority/safety records |
| NHTSA vPIC / US DOT | vehicle VIN | VIN decoding |
| trade.gov / US Commerce | carrier legal name | denied-party/sanctions screening |
| AbstractAPI | phone number | phone enrichment/validation |
| Geoapify, if enabled | minimum carrier business address needed for the lookup | geocoding/map display |
| Lemon Squeezy | billing/customer details required for payment | merchant of record |
A document you upload — including a commercial driver's license — may be sent to Google Gemini API for extraction. Production document processing is configured to operate only with an approved paid Gemini API Cloud Project, so that the Paid Services data terms apply, and is refused unless that configuration is explicitly confirmed. Google may still retain or cache content for limited safety, abuse-prevention or legal/regulatory purposes under its terms, and such processing may occur in countries where Google or its agents maintain facilities.
We do not use the public nominatim.openstreetmap.org endpoint for production carrier-address processing. Geoapify is our approved geocoding provider. While geocoding is disabled, no carrier address is transmitted to any geocoding provider.
We may also disclose information where required by law; to investigate abuse or security incidents; to protect rights, safety or property; or in connection with a merger, acquisition, financing or sale of the business, subject to applicable law.
Inside your own organisation. A subscription can hold seats for several people. If your account is a seat on someone else's subscription — normally your employer's — then the account that pays for it can see the verification work done in yours: the requests you create, the documents you upload, the reports produced and the record of the actions you took in the Service. This is one-directional. You cannot see the work of the account that holds your seat, or of anyone else sitting in one.
The records made in a seat belong to the account that pays for it. If your seat is removed, that account decides whether to keep the verification work done in it or delete it, and can do either. This is why the seat cannot be closed from inside: what is in it is not only yours to end.
5. Cookies and similar technologies
We currently use:
| Cookie / storage | Purpose | Typical lifetime |
|---|---|---|
| authentication session | keeps you signed in and secures the account | until expiry/sign-out, as configured |
| locale | remembers your interface language | up to one year |
We do not currently use advertising or cross-site behavioural tracking cookies. We also do not currently use analytics cookies that require a separate tracking profile of your behaviour.
We do not display a cookie-consent banner for the current configuration. If we add non-essential analytics, advertising or similar tracking technologies, we will reassess notice and consent requirements before deploying them.
6. How long we keep information
Our default retention schedule is:
| Data | Default retention |
|---|---|
| Original uploaded documents, including CDL images/PDFs | up to 90 days from upload, or earlier deletion |
| Full commercial driver's license numbers | up to 90 days, then reduced to the last four digits (for example ******4567) wherever they are stored |
| Verification requests, their reports and their document records | 3 years from the date of the check |
| Account data | while the account is active |
| Audit records of actions taken in the Service | 3 years |
| Billing, tax, fraud-prevention and legal records | for the period reasonably required by applicable law, accounting obligations, dispute handling or enforcement |
| Routine security/operational logs | normally up to 90 days |
| Security-incident/investigation records | up to 2 years, or longer where reasonably necessary for an active claim, investigation or legal obligation |
A verification report keeps the driver's name where a check compared names, because a finding that cannot say which spellings differed cannot be checked or challenged. It does not keep the full license number: after 90 days only the last four digits remain, which is enough to identify which license was meant. Section 9 explains what this means for a driver whose license was uploaded.
You can delete a verification request through the Service at any time; associated source documents are deleted from our active object storage without waiting for the ordinary raw-document retention period.
Closing an account is scheduled rather than immediate. When you ask to close an account, it stops being able to run new checks straight away, but nothing is deleted for 30 days. During that period you can cancel the closure and the account continues as before. You stay able to sign in and read what is in the account throughout, which is also how the closure is cancelled.
At the end of the 30 days the account is deleted, together with its requests, reports and source documents. Stored files that cannot be removed immediately are removed by a daily process, normally within 24 hours of that deletion. We may retain limited records where reasonably necessary for billing, security, legal obligations or dispute handling.
The delay exists because closing an account can destroy records other people depend on — where an account holds seats, it also holds the verification work of everyone using them. It is a window for undoing a mistake, not a way of keeping data you have asked us to erase: if you would rather it went sooner, contact us at the address in section 13.
Deletion from active systems does not necessarily remove data immediately from disaster-recovery backups, where maintained. Backup data is isolated from ordinary product use and is removed as those backups are overwritten in the normal backup cycle. If a backup is restored, applicable deletion requests and retention rules are re-applied.
7. How we protect information
We use technical and organisational safeguards appropriate to the Service, including encryption in transit, access controls, tenant isolation, secret/token protection, logging and restricted production access.
API tokens are stored only as non-reversible hashes. We cannot recover a token, only verify one; a token is shown once, when it is created.
No system is perfectly secure. If we learn of a security incident involving personal information, we will investigate and provide notices required by applicable law and our contractual obligations.
8. Your choices and rights as a customer/user
You can access and correct account/request information available in the application, delete requests and their source documents where supported, export reports, and close your account.
Depending on applicable law, you may also have rights to request access, correction, deletion or other action concerning personal information. Contact privacy@irsa.digital. We may verify your identity and authority before acting.
We do not sell personal information or share it for cross-context behavioural advertising, so we do not currently offer a sale/sharing opt-out for those activities.
9. If your details are in a document someone else uploaded
A freight broker or other business customer may upload paperwork containing your personal information while verifying a motor carrier. In that context, we process the document primarily on the customer's instructions.
What is kept about you: the uploaded image of your license is deleted 90 days after upload. Your full license number is also reduced at 90 days to its last four digits. Your name can remain for up to three years inside the report the broker ran, but only where a check actually referred to it — for example a record that the name on the license did not match the name on another document.
If you believe information in a report is inaccurate, or you want to ask whether we hold information about you, contact the business that performed the check if you know who it is. You may also write to privacy@irsa.digital. We may need to verify your identity and may refer the request to the relevant customer, coordinate with them, or act directly where applicable law requires us to do so.
A correction to a historical report may be recorded as an amendment rather than silently rewriting the original report, so the parties can see what information was available at the time and what changed later.
10. Children
The Service is for business use and is not directed to children. We do not knowingly offer the Service to anyone under 18.
11. International access and processing
The Service is designed for US freight operations, but customers and their staff may access it from other countries. Some providers may process data in multiple countries under their service terms.
We do not claim that all data is stored or processed exclusively in the United States unless and until the applicable infrastructure and contracts guarantee that result.
12. Changes
We may update this policy. We will change the "Last updated" date and provide notice of material changes as required by law or our contracts.
13. Contact
"IRSA" MCHJ TIN: 313132120 1376 Mustaqillik Street, Do'stlik MFY, Sherobod District, Surxondaryo Region, Republic of Uzbekistan privacy@irsa.digital
The English version of this policy is the authoritative one. Translations are provided for convenience; if they differ, the English text governs.