This page explains what data may be collected when you browse this site or contact the Desk, why it is collected, how long it is kept, and what choices you have. It is written as an operational summary. If you need a formal legal policy for a specific jurisdiction or for regulated processing, you should obtain counsel and publish a jurisdiction-appropriate privacy policy. This note is intended to be clear, accurate, and not overstated.
Like most websites, we may process limited technical data to load pages, keep the site secure, and understand aggregate usage. If you submit a message through the Contact Desk, we will receive the information you choose to provide. We do not require you to provide sensitive personal information to use the reference pages, and you should avoid including sensitive data in free-text forms unless it is necessary for your request.
| Category | Examples | Purpose | Typical retention |
|---|---|---|---|
| Basic technical logs | IP address (often truncated by providers), browser type, device type, timestamp, requested URL, referrer. | Security monitoring, fraud/abuse prevention, basic troubleshooting, and aggregate performance. | Short-term unless needed for security investigation. |
| Analytics (aggregate) | Page views, session counts, traffic sources, approximate region, device breakdown. | Understand what content is useful, improve site structure, reduce broken navigation. | Varies by tool; keep only as long as needed for trend analysis. |
| Contact submissions | Name (optional), email, message content, attachments you include (optional). | Respond to requests, provide templates, and clarify packaging questions. | Kept long enough to respond and maintain a working record. You may request deletion. |
| Cookies / local storage | Session cookie, preference storage (e.g., language), analytics identifiers (if enabled). | Enable basic site functions and optional usage measurement. | Varies by cookie type; you control many via browser settings. |
If you contact the Desk, include operational details (commodity type, pallet height/weight, damage signature) rather than personal data. For example, “Unit load shifts during intermodal lane” is useful; personal identifiers are not. If you share photos, avoid including faces, vehicle plates, or documents unless required to communicate the packaging issue.
Cookies are small files stored by your browser. Some are functional (they help pages load correctly or remember preferences). Others are optional and used for analytics (understanding what content is read, where users drop off, and whether navigation works). You can block or clear cookies in your browser. If you disable certain cookies, some site features may not work as intended.
Used to support page rendering, basic security, and preferences. They generally do not exist to profile you for advertising.
Used to understand aggregated usage patterns. If enabled, they help us improve guide clarity, reduce broken pages, and prioritize updates.
We do not promise that browsing is anonymous. Networks and browsers have their own behavior. We aim to keep data collection minimal and purpose-limited.
Operating a website typically involves hosting providers, email delivery services, and (optionally) analytics tools. These providers may process limited data on our behalf to deliver the service (for example, delivering pages or routing messages). We do not publish sensitive operational details that would create security risk. We do not claim “perfect security.” Instead, we aim for reasonable safeguards appropriate to the nature of the site.
Hosting and delivery partners may see technical logs needed to deliver pages and maintain uptime. If analytics are used, they may process aggregate events.
Reasonable controls may include access restrictions, software updates, and monitoring for abuse. No online system can guarantee absolute prevention of misuse.
If we identify misuse or a security issue affecting contact submissions, we may take steps to limit access and preserve relevant logs for investigation.
We may update this note to reflect operational changes (new forms, new analytics, new hosting). If you rely on this page for compliance documentation, you should periodically re-check it and keep your own records of the version that applied at the time you interacted with the site.