CruiziBeta

A little help, along the way.

Sending, travelling and looking after a parcel.

Sending a parcel

Search by route, delivery deadline and parcel size. Sending a request does not confirm a delivery. When the traveller accepts, review and complete your booking.

Choose Cruizi Envelope, Cruizi S or Cruizi M. The size and weight limits appear in search; your packed parcel must fit the chosen category.

Travelling with a parcel

Publish a journey you are already making. Review incoming requests before accepting. Arrange collection before departure and delivery after arrival, using the meeting points and times on the trip.

Collection and delivery

Check the parcel and the other person at the agreed meeting point. Use the collection code only when handing over the parcel. The receiver uses the delivery code at the final handover. Never share a handover code in an issue report.

Cancellations or something going wrong

Open your delivery to see its current status and available actions. Cancellation depends on the delivery stage; a collected parcel must not be treated as an ordinary cancellation.

If someone misses the meeting or a delivery has a problem, report the issue and select the related trip or request. A support report does not itself cancel a booking or issue a refund.

Report an issue

Balance and earnings

Production payments and traveler payouts are not available yet. No simulated credits are issued in production.

Data protection & privacy

Our privacy notice explains who processes your personal data, why it is used, who receives it, how long it is kept and how to exercise your rights. It is hosted by our external data-protection provider.

Open privacy notice ↗

Cookies & storage

Storage information version 1.0 · Reviewed 30 October 2026

Cruizi currently uses essential browser storage and no analytics or advertising trackers. Essential storage supports services you request, including signing in and keeping your delivery workflow available when you move between pages.

Sign-in and security
Our separate sign-in service uses authentication cookies. Their expiry is controlled by the sign-in service and may differ from this app’s tab lifetime. This app stores temporary sign-in transaction state under oidc.* in session storage. Access and refresh tokens are kept in memory, not persistent browser storage. Signing out clears the app’s authenticated state.
Search and booking continuity
Session storage keeps search criteria ( cruizi.search-criteria ), selected traveller options ( cruizi.traveler-selection ), and pending trip/request and command-retry records. Some records contain account identifiers, selected locations or submitted form data. These support the workflow you requested and prevent duplicate submissions. They normally last for this tab’s session, or until the relevant workflow removes them. Browser session restoration can preserve a tab’s data; clearing site data removes it.
Your privacy choice
Local storage entry cruizi.cookie-choice records your choice, policy version and date for 180 days. This is a product retention period, not a legal deadline. After expiry the app asks again; the stored entry is not automatically deleted at that time. It contains no account identifier and is not sent to our server. This choice is not acceptance of the terms and conditions.
Browser notifications
Notifications require your explicit action and browser permission. The local storage entry cruizi.browser-push.binding.v1 links the browser installation and device record to your account identifier. When enabled, Firebase uses IndexedDB and a service worker for push delivery. Push registration data is sent to Firebase and Cruizi’s notification API. The local binding has no fixed expiry; disabling notifications or signing out attempts to remove the binding and revoke delivery. Browser permission and some SDK data may remain until cleared in browser settings. Cookie settings do not revoke notification permission.
Location search and maps
When you search for a place, Cruizi’s API sends the search text and session identifier to Google Places and retrieves the selected place details. This does not load Google’s map SDK in your browser. The selected location and its coordinates support journey matching and distance estimates. The app does not request your device location automatically.

You can review your choice here or through the footer at any time. Clearing site data removes the saved choice. Settings apply to this browser, not every device. Optional services must remain off until you choose to allow them.

Read the company privacy notice for information about personal data and your rights.