Cookie & Browser Storage Policy
1. The Short Version
REDDLAW currently sets no analytics, advertising or marketing cookies. Its authentication cookies are strictly necessary to provide secure account access. We do not run an analytics platform, an error-monitoring or session-replay tool, an advertising pixel or a tag manager on this origin.
2. Cookies We Set
Two cookies. Both are strictly necessary: they are what keeps you signed in and keeps your session attached to the right account. Neither is used to profile you, and neither follows you to another website.
| Name | Purpose | Lifetime | Attributes |
|---|---|---|---|
rli_client_session | Keeps you signed in to the client portal and identifies which organization your session is acting under. | 14 days | HttpOnly, SameSite=Lax, Secure in production, first-party |
rli_admin_session | Keeps REDDLAW’s own operations staff signed in to the internal administration area. It is never set for customers. | 12 hours | HttpOnly, SameSite=Lax, Secure in production, first-party |
HttpOnly means a script running in the page cannot read the cookie. SameSite=Lax limits when it is sent on requests that originate from another site. Both are signed, so a modified cookie is rejected rather than trusted.
3. Browser Storage
Separately from cookies, the Platform uses your browser’s local and session storage for a small number of things you have asked it to do. This data stays on your device and is not transmitted to us as part of ordinary page requests.
- A booking you have started. Details you have entered into a booking form are held in your browser so that moving between steps, or reloading the page, does not lose your work. This exists to provide a function you initiated.
- A once-per-visit notice flag. A single marker recording that an in-page notice has already been shown, so it is not repeated at every step of the same visit.
- The demo. The read-only demo mirrors the booking screens, so anything you type into a demo form is held in your browser’s session storage for the same reason. It is cleared when you close the tab and never reaches a real account.
You can clear this data at any time through your browser’s site-data controls. Clearing it discards an in-progress booking.
4. Third Parties
Payments. Card payment is completed on our payment processor’s own hosted checkout page. That processor may set cookies on its origin under its policy, which is what lets its checkout work and detect fraud. REDDLAW’s origin does not set those cookies and cannot read them.
Everything else. We do not load third-party analytics, error-monitoring, session-recording, advertising or social scripts on this origin. Search-engine site-verification meta tags, where present, set no cookies.
Operating the service still requires records that are not cookies — authentication, security logging and rate limiting. Those are described in our Privacy Policy.
5. Your Choices
Because we set no analytics, advertising or marketing cookies, there is currently nothing non-essential for you to opt out of, and we do not present a consent banner for cookies that do not exist.
You can block or delete cookies through your browser’s settings. Blocking the two cookies above will prevent you from signing in or staying signed in.
If we ever introduce a cookie or storage mechanism that is not strictly necessary, we will update this policy and put an appropriate consent mechanism in place before it is used.
6. Changes
We may update this policy. The effective date at the top reflects the current version.
7. Contact
Privacy Officer
REDDLAW Logistics Inc.
Hamilton, Ontario, Canada
Email: ops@reddlawlogistics.com