Privacy

What we hold, where it is held, and who else sees it.

IntelDocks shows a company its own yards, terminals, aircraft stands and deals. We hold what that takes and very little else. There is no advertising here and nothing is sold on.

Last updated 21 October 2026.

Who we are

IntelDocks is a product of IntelWork4ce. Write to hello@intelwork4ce.com with any question about this page, including a request to see, correct, export or delete what we hold. Our legal notice is at intelwork4ce.com/terms.

We play two roles, and the difference matters.

• For the people who sign in, we are the controller. We decide what we keep about your account and why, and this page tells you.
• For the operational data your company connects, your company is the controller and we process it on its behalf. Containers, shipments, gate visits, flights, documents, deals and the rest belong to your company. We handle them only to run IntelDocks for it, under the contract we sign with it, which sets out the processing terms. If you want to know what your company does with that data, ask your company.

What we hold about the people who sign in

• Your account. Clerk creates your account and holds your email address and your name, and the picture Google or LinkedIn returns if you sign in with one of them. Our database keeps the identifier Clerk gives your account and the identifier of your organisation, so that the database can decide what you are allowed to see. We keep them until your account is deleted.
• Your organisation and your role. Which organisation you belong to and the role your administrator gave you. The role decides which screens and which tools you can use.
• Your decisions. When you approve or reject a change an agent proposed, we record your account identifier, the decision, the time and the note you wrote. Nothing is written to your company's systems without such a decision, so the record has to say who made it.
• How the AI agents are used. For each call to the AI model we record the organisation, the role, the tools the agent called, the tokens in and out and the cost. When an agent calls one of your company's own systems, we record the tool, a scrambled fingerprint of what was sent (never the content itself), the size of the answer, how long it took and whether it worked.

What your company connects

Your company decides which of its systems IntelDocks reads: a terminal operating system, a warehouse system, flight and freight systems, documents. What comes in is about cargo, equipment, places and deals. It can contain personal data in passing, such as a driver's name on a gate record or a contact on a bill of lading. We use it only to show it to your company, to compute the figures it asks for and to run the checks its kits contain.

The login credentials your company gives us for its systems are kept in a secret store. They are never shown on a screen, written to a log or sent to the AI model.

The AI model

The agents in IntelDocks run on Google's Gemini models through Google Cloud's Vertex AI, on Google's European Union endpoint, so your company's data stays inside the EU when the model reads it. Google states that it does not use this data to train or improve its models without permission. Google may keep prompts to detect abuse under its cloud terms, and it may hold a request in memory for up to 24 hours to answer repeated requests faster.

If you connect your own frontier model, Claude or ChatGPT, to IntelDocks, what you send to it is governed by your agreement with that provider, not by this page.

An agent never changes anything in your company's systems on its own. It proposes, and a named person in your company approves or rejects.

What we do not do

• We do not sell personal data, share it for advertising or build profiles.
• We do not show one company's data to another. The only exception is a single container that two companies both work with, such as a trader and a port. Its number, location and status cross from one to the other only when both companies have agreed, and every such read is logged.
• We do not take card payments. Customers pay our invoices by bank transfer.

Where it is held

• The application runs on Google Cloud Run in Europe.
• The database is PostgreSQL on Google Cloud SQL, in Belgium (Google Cloud region europe-west1).
• Scene files and kit files are stored on Cloudflare R2, and Cloudflare serves the site at the edge.
• Map tiles are read, for now, from the Protomaps public map archive and from MapLibre's demonstration tiles. They move to Cloudflare R2, and this line changes, when we host the map ourselves.
• The AI model runs on Vertex AI's European Union endpoint.

Who else sees it

• Clerk handles sign-in and holds your email address and name.
• Google Cloud hosts the application and the database, and runs the AI model.
• Cloudflare serves the site and stores the scene and map files.
• Protomaps (build.protomaps.com) serves the base map archive, and MapLibre (demotiles.maplibre.org) serves the low-zoom world tiles, so loading the map sends your browser's request, including its IP address, to them until the map is hosted on Cloudflare R2.
• Esri serves the satellite imagery under the map, so loading that layer sends your browser's request, including its IP address, to Esri.

Nobody else. We have no affiliate or data partnerships.

How long we keep it

Your account details stay until your account is deleted. Your company's operational data stays for the length of its contract and is returned or deleted when the contract ends, as the contract sets out. Invoices are kept as long as French tax law requires.

Your rights

If you are in the EU or the UK you can ask to see, correct, export, restrict or delete your personal data, and you can object to how we use it. Write to hello@intelwork4ce.com and we will answer within a month. If your request is about data your company connected, we will pass it to your company, because it decides. You can also complain to your national data protection authority; in France that is the CNIL.

Changes

When this page changes materially we will change the date at the top and tell the administrators of every customer organisation. Version 1.0.0 of 21 October 2026 did not name Protomaps and MapLibre; 1.1.0 of 22 October 2026 adds them. 1.2.0 of 22 October 2026 moves the database from Supabase to Google Cloud SQL, before any customer data was held.

Version 1.2.0, 2026-10-22. Basis: Regulation (EU) 2016/679 (GDPR), Articles 13, 14 and 28.