Data & privacy notice

Start with less data.
Move records with care.

This page describes the current public-site and pre-engagement workflow. Engagement-specific handling requirements must be confirmed in writing before customer freight records are accepted.

Current public notice · September 23, 2026

01

Public qualification form

The free-audit qualification form runs in your browser. It does not upload files, post form data to a server, or save entries to browser storage. Nothing is transmitted by the site when you complete the fields.

After the form is complete, the site can prepare a non-sensitive email summary. You decide whether to open, review, and send that email from your own account. The summary may include your name, work email, company, role, freight-volume ranges, modes, carrier context, available-history range, approximate invoice count, available record categories, prior-audit status, and a short general reason for the review.

Do not include freight documents in the qualification request.

Do not email invoices, contracts, credentials, payment-card information, bank details, unrestricted mailbox access, or other confidential records.

02

Records and formats

Structured invoice exports such as CSV are the preferred starting format because the current audit workflow includes structured invoice and rule adapters. Spreadsheet, PDF, carrier-portal, payment, and shipment exports require review before acceptance. Support is not implied merely because a format appears in the qualification form.

Before any files move, RETALLY should confirm the population, date range, carrier and mode scope, allowed record categories, transfer route, access method, and responsible contacts.

03

Data used for an accepted audit or recovery engagement

Depending on the agreed scope, records may include invoice exports, rate agreements or tariff authority, shipment and delivery evidence, payment or credit evidence, approved claim correspondence, and settlement or reversal evidence. Only records needed for the agreed business purpose should be provided.

Customer records should be used to qualify, analyze, review, document, administer, and reconcile the agreed freight-recovery work. They should not be used to train a general-purpose model or for an unrelated purpose unless separately disclosed and authorized.

04

Security and authority boundary

The public GitHub Pages site is intentionally unable to accept freight files. A secure intake route is an operational requirement, not a capability claimed by this page. Its provider, access controls, encryption, authorized users, and evidence should be confirmed for the engagement.

Payment does not authorize record access. A free audit request does not authorize carrier contact, dispute submission, settlement acceptance, money movement, credential use, or another outside action. Those actions require the authority specified by the engagement and the applicable workflow.

05

Retention, correction, and deletion

No universal retention period is promised by this public page. The appropriate retention and deletion schedule depends on the engagement, active claims, settlement and reversal evidence, contractual obligations, recordkeeping needs, backup behavior, and applicable law. The schedule should be documented before customer files are accepted.

Audit outputs should keep potential, validated, approved, disputed, recovered, fee-eligible, and reversed amounts distinct. Corrections and later reversals should produce an updated record rather than silently rewriting historical evidence.

06

Questions and requests

Contact RETALLY to ask what qualification information was received, correct a request, withdraw before file intake, or discuss engagement-specific access, retention, export, or deletion requirements.

Email a privacy question

This notice is operational information, not legal advice and not a substitute for an engagement-specific privacy or data-processing agreement where one is required.