Forms currently create a local text brief.
No automatic email or CRM submission.
Operator and hosting details still need confirmation.
1. What this notice covers
This Privacy Policy describes the current 4PL website code: informational pages, a shipment planner, downloadable shipment briefs, a checklist and a demonstration tracking tool. It does not describe a live booking platform, customer portal or operational transport system.
The website operator’s registered identity, registered address and privacy contact have not yet been provided. This is therefore a draft for review, not a completed statement for a live data-collection service.
2. Information entered in the forms
The shipment forms allow you to enter a name, company, email address, origin, destination, transport preference, approximate cargo weight, ready date and cargo or handling notes. The homepage planner passes the selected mode, origin and destination to the shipment form within the page.
In this version, the website code does not transmit those entries to 4PL, email them, send them to a CRM, upload them to a server or save them in a customer database. The fields are used to prepare a brief in the page.
Browser autofill, session restoration or synchronisation features may operate according to your browser settings. The website does not control copies retained by your browser.
3. Downloading and sharing a brief
When you create a brief, the page prepares a text file and displays a download link. The website does not automatically send the file to anyone. If you download it, the resulting file is stored wherever your device or browser saves downloads.
You control later sharing and deletion of that downloaded file. Editing a form invalidates its previously displayed download link. Closing the page ends the page’s active form session, but does not delete files already downloaded or copies managed by your browser.
4. Tracking-demo inputs
The shipment reference is checked locally in the page. Only 4PL-DEMO-001 displays sample shipment information. The website does not contact a carrier or transport-management system with the entered reference.
Use the sample reference when exploring the demo. Do not enter a confidential shipment reference into an unconnected demonstration tool.
5. Hosting and technical records
Visiting a deployed website involves requests to its hosting infrastructure. The host or associated delivery and security services may process technical information such as an IP address, requested URL, request time, browser details and security events.
The final hosting provider, enabled logging features, purposes, access controls, retention periods and any relevant international transfers must be confirmed for the actual deployment. The local form-generation code does not add form contents to a request URL or send them to a logging endpoint.
6. Cookies, analytics and browser storage
The current site code does not set cookies, use localStorage or sessionStorage, embed advertising pixels, or include analytics or marketing trackers. Fonts and illustrations are included with the website rather than loaded from an external asset host.
This statement concerns the code supplied with this version. Features added by the eventual hosting configuration, third-party embeds or future integrations must be assessed separately. Non-essential tracking should not be enabled without the information and choices required by the applicable law.
7. Sharing and external websites
The current website does not sell form entries, add visitors to marketing lists or automatically share entered details with logistics providers. You choose any recipients after downloading a shipment brief.
If you follow a link to another organisation, that website receives the request and applies its own privacy practices. Review its notice before entering information there. Hosting providers may separately process the technical data described above.
8. Retention and security
The website has no server-side store of shipment-form entries in this version. Page data is used for the active interaction. Device downloads and browser-managed copies remain under the control of their respective owners and settings.
A production retention schedule for hosting records, submitted enquiries and any later operational processing has not been established in this draft. It must reflect actual purposes, legal requirements and the systems in use. Do not send highly sensitive documents through these planning fields.
No website can promise absolute security. A future submission service will need suitable transport security, server-side validation, access control and safeguards appropriate to the information collected.
9. Privacy choices and requests
You can edit or clear the form fields and choose not to download a brief. You can remove downloaded copies through your device’s file controls. Browser autofill and stored-history options are managed in your browser.
Depending on applicable law and any actual processing, privacy rights may include access, correction, deletion, restriction, portability, objection and complaint to a relevant authority. Where processing relies on consent, a suitable withdrawal route must be provided. These rights are not identical in every country or context.
No verified privacy-request contact is published in this preview. The operator must add an accessible contact channel and any required supervisory-authority information before public launch. The shipment form is not a privacy-request submission channel because it does not send a message.
10. Changes and future services
This draft was last updated on 15 November 2026. It must be reviewed when hosting is configured or features change.
Before adding live enquiry submission, CRM or email routing, carrier tracking, analytics or customer accounts, publish the relevant operator details, processing purposes, applicable lawful basis, recipients, retention information and transfer safeguards. Explain the changes at the point where visitors provide information.