Privacy Policy

1. Introduction

Welcome to Shipwize Services Ltd and Circles Logistics Ltd ("we," "us," "our," or collectively "the Companies").

This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you interact with our services — including the websites shipwize.com and circlesja.com, the customer portals at dashboard.shipwize.com and dashboard.circlesja.com, our mobile applications, the interfaces that connect them, and the back-office system our staff use to run the warehouse and the branches (collectively, the "Services").

It also outlines your rights under the Data Protection Act 2020 (Jamaica), the General Data Protection Regulation (GDPR – EU 2016/679), the UK Data Protection Act 2018, and the California Consumer Privacy Rights Act (CPRA 2023).

By using our Services, you acknowledge that you have read and understood this Privacy Policy.

2. Scope

This Privacy Policy applies to all digital and offline interactions between you and the Companies. Your information is handled by five connected parts of one platform:

• Our public websites — shipwize.com and circlesja.com, including the rate estimator, the branch locator, and the customs forms you can fill in and download.
• Our customer portals — the signed-in areas at dashboard.shipwize.com and dashboard.circlesja.com. This is where you create your account and sign in, and then see your packages and their tracking, your invoices and receipts, your store credit, rewards points and referral credit, your U.S. shipping address and Suite Number, and a rate estimator — and where you change your profile, your delivery address and directions, the people you authorize to collect for you, your email address, your password, and your notification preferences.
• Our mobile applications — which give you the same account from a phone, and where you can also choose pickup or home delivery, ask to collect from a different branch, manage the people you authorize to collect for you, turn on two-step sign-in, see and sign out the devices signed in to your account, download your invoices, receipts, and monthly statements, get directions to a branch, and close your account.
• Our application interface (API) — the service that sits between those apps and our database, handles sign-in, and sends account email.
• Our back-office system — the desktop application our warehouse, branch, and billing staff use to receive, manifest, scan, bill, and release your packages.

Where something in this Policy applies to only one of those parts, it says so. The short version: the public website is everything you can use without an account, and the customer portal is everything you see after you sign in. They are separate websites on separate addresses and they do not behave the same way — in particular, the portal loads no analytics of ours, and its hosting platform collects its own operational analytics; Section 7 explains why. The cookie question is asked once per browser, on whichever of the two you reach first, and the answer you give is shared by both — so the portal asks it only if you arrive there without having answered here, and it loads the advertising conversion pixel only after an acceptance given on either site.

It also covers customer-service communications, social-media interactions, and offline registrations at our counters that reference this Policy.

This Policy does not apply to third-party websites, services, or applications that we do not control.

3. Definitions

• Account – a unique profile you create to access our Services.
• Affiliate – an entity that controls, is controlled by, or is under common control with either Company.
• Application – the Shipwize or Circles mobile or desktop software you install or use.
• Companies / we / us / our – Shipwize Services Ltd and Circles Logistics Ltd, both headquartered in Kingston, Jamaica.
• Cookies – small text files stored on your device to remember preferences or session information.
• Device – any hardware that can access our Services (computer, smartphone, tablet, etc.).
• Personal Data – information relating to an identified or identifiable individual (as defined in Section 2 of the Jamaica Data Protection Act 2020).
• Service Provider – any third party that processes data on our behalf under a written contract.
• Suite Number – the personal identifier we issue you, which forms part of the U.S. shipping address you use when you buy online.
• Tracking Number – either the number given to a parcel by the store or carrier that shipped it, or the internal number we assign when the parcel reaches our warehouse.
• Usage Data – technical data automatically collected when you use the Services (e.g., IP address, browser type, session duration).

4. What We Collect

A. Personal Data You Provide

When you interact with our Services, we may collect:

• Name, email address, and up to two phone numbers
• Tax Registration Number (TRN), date of birth, and gender. The TRN and date of birth are needed for customs paperwork; your date of birth is also what makes you eligible for a birthday reward. Once your account exists, your name, gender, and date of birth are shown to you in the portal but cannot be edited there — ask us if one of them is wrong.
• The branch or pickup zone you choose to collect from, the company name and business type if you register as a business, and a referral code if someone gave you one
• Shipping, billing, or delivery addresses
• Account credentials — a password, and, if you choose to use one, a passkey registered to your device (we hold only the passkey's public part) — and whether you have turned on two-step sign-in
• Payment or transaction information
• Your authorization paperwork — the USPS authorization form (PS Form 1583) and the customs authorization form. When you create an account in the customer portal these are filled in from the details you have just entered, shown to you to check, signed with your name, and stored with your customer record once you confirm them and the account is created. You can download your own copies at the same time.
• The name and details of anyone you authorize to collect packages on your behalf: their full name and, if you give them, their phone number, the type and number of the identification they will show, and whether they may collect all of your packages or only one (see Section 4 E)
• Your delivery preference — pickup or home delivery — and, for delivery, the address (street, town, and parish) and any directions you give us, and any request you make to collect from a different branch (see Section 4 E)
• If you close your account, the reason you choose from our list and any comment you add (see Section 10 B)
• The mobile number you give us for WhatsApp package notifications, if you choose to receive them (see Section 6)
• Communications or support messages you send us, including live chat conversations on this website (see Section 7 A)

B. Automatically Collected Data

We automatically gather Usage Data such as:

• IP address, browser, and operating system
• Device identifiers and mobile network data when you use our applications
• Pages visited, duration, and actions taken
• Sign-in events, request logs, and diagnostic and performance logs, which we keep for security and troubleshooting
• For each device signed in to our mobile application: an identifier for the device, the device's name, its platform, the application version, when it signed in and when it was last used, and — if you allow notifications — its push-notification registration (see Section 4 F)
• A record each time a sign-in code is sent, entered, or resent, holding a masked form of your email address and never the code itself (see Section 4 F)

Neither our public websites nor the customer portal asks for or uses your device's location. If you type an address into one of the forms on this website, the text you type is sent to the OpenStreetMap Foundation's address-lookup service so that it can suggest matching addresses (see Section 8). The customer portal has no address lookup of that kind: an address you type there goes only to us.

In the customer portal, the pages you see are assembled by our own server, which contacts our application interface on your behalf — your browser never contacts it directly, and the sign-in credential it uses is never given to your browser. We record sign-in events, and a diagnostic entry when something fails. If an attempt to create an account fails, that entry includes the details you had entered, so that we can work out why; it never includes your password.

C. Information We Create About You

Running your account produces records about you that you did not directly give us:

• Your Suite Number and the internal tracking numbers assigned to your packages
• Package records — description, weight, declared value, tariff classification, status history, and the record of any staff edit
• Account balance, invoices, receipts, and payment history
• Your store-credit balance and the history of every adjustment to it
• Your rewards-point balance and the packages that earned each point
• Your referral code, and the record that a particular customer signed up using it — which necessarily links your account to theirs
• Your WhatsApp notification state and the trail of how it changed (see Section 6)
• Notes, incident records, and audit entries created by staff while handling your packages or your account
• When your delivery preference or pickup branch last changed and when our staff were told, which sets the date from which you can next change it
• If you close your account, the date you closed it and the fact that you closed it yourself

D. Third-Party Sources

We may receive limited data from logistics partners, carriers, customs brokers, payment processors, or referral partners, in accordance with their privacy policies. If someone adds you as an authorized collector on their account, we receive your details from them rather than from you.

E. Delivery, branch requests, and authorized collectors

When you switch to home delivery, change your delivery address, or switch back to pickup, and when you ask to collect from a different branch, we email the request to the administrators who assign customers to branches and to delivery. That email carries what they need to update your account — your name, Suite Number, and current branch, and, for delivery, the address and directions, the parish, and whether delivery there is free — and when the request was made. When a package is delivered, the staff member, driver, or courier delivering it receives your name, contact number, delivery address, and directions. Our diagnostic logs record that a request was handled, never the address itself.

The details of a person you authorize to collect for you are held with your customer record and used only to check that person's identity and authority when they collect a package. You, and anyone signed in to your account, see an identification number only as its last four characters; our branch staff see the full details at pickup so that they can check them. No log entry contains a collector's name, phone number, or identification number. Removing a collector takes their details off your record, and closing your account removes all of them. Because these details come from you rather than from the person named, you must have their agreement before you add them (our Terms and Conditions, Section 10 D). A person named as a collector can exercise the rights in Section 11 over their own details.

F. Signed-in devices and two-step sign-in

Our mobile application can show you the devices signed in to your account — each with its name, platform, application version, and when it signed in and was last used — and lets you sign any of them out. We keep that information to show it to you, to tell your devices apart, and to protect your account. The list shows no location. A device's sign-in record is deleted automatically when it expires, at most sixty days after the device was last used; signing a device out ends its access straight away and deletes its push-notification registration.

If you turn on two-step sign-in, a six-digit code is emailed to you when you sign in to our mobile application with your password on a device your account has not verified. We store the code only in a form that cannot be read back, it works once and for ten minutes, and it is deleted automatically about an hour after it expires. We keep an audit record of each code being sent, entered, or resent, holding your customer reference and a masked form of your email address, never the code. We email you whenever two-step sign-in is turned on or off.

5. How We Use Your Information

We use Personal Data only for lawful purposes, including:

• Provide, maintain, and improve our Services
• Manage your Account, your Suite Number, and your shipments
• Process payments, shipments, and deliveries
• Calculate freight, duty, GCT, and other charges, and apply store credit, rewards, referral credit, and promotional discounts
• Estimate what a shipment would cost, when you use the rate estimator on the website or in the customer portal
• Send you transactional email — your welcome email, package status updates, receipts and invoices, password resets, email-change confirmation codes, sign-in codes, notices that a security setting has changed, and confirmation that your account has been closed
• Send push notifications about your packages to devices on which you allow them
• Arrange home delivery or a change of pickup branch, tell our staff about the request, and apply the six-month rule on changes
• Check the identity and authority of a person collecting a package for you
• Secure your account — sending sign-in codes, showing and signing out your signed-in devices, and detecting and limiting misuse, including by limiting how often an action can be repeated
• Produce copies of your invoices, receipts, and monthly statements when you download them
• Close your account when you ask, and use the reasons customers give for leaving to understand why and improve the Services
• Send WhatsApp package notifications, if you have opted in and confirmed (see Section 6)
• Communicate with you about customer support and service issues
• Send promotional offers by email to selected active accounts. We treat these as service messages to customers of the business; we do not sell your details to anyone else, and if you would prefer not to receive them, tell us using the contact details in Section 15 and we will exclude your account
• Comply with tax, customs, and anti-fraud laws
• Analyze usage and improve functionality
• Keep audit records of financial and account changes, which we must be able to reconstruct
• Manage business transfers or restructuring
• Enforce terms and protect against fraud or misuse

We do not sell or rent your Personal Data.

6. WhatsApp Package Notifications

You can choose to receive package updates on WhatsApp. It is optional, it is off unless you turn it on, and it is in addition to — not a replacement for — the emails we already send.

A. How you opt in, and why one message arrives before you are opted in

Consent is double opt-in. Ticking the box does not switch notifications on by itself. It records your number and sends you exactly one WhatsApp message asking you to confirm. Package notifications begin only when you confirm inside WhatsApp, and not before. If you never answer that message, your consent stays pending and we send you nothing further.

In the customer portal the switch is in My Account → Notifications, alongside a plain-language description of the state your consent is currently in, the statuses that will message you, and how to stop. You can also opt in through our mobile application, at one of our counters if you ask a member of staff to do it for you, or from inside WhatsApp itself. Only a masked form of your number is ever shown back to you or to our staff.

B. What we share with Meta, and what it can see

WhatsApp is operated by Meta Platforms. Opting in means we share your mobile number with Meta so that it can carry our messages to you. The content of each message, and its delivery state — sent, delivered, read, or failed — passes through Meta, and Meta reports that state back to us. Your use of WhatsApp is also governed by Meta's own terms and privacy policy, which we do not control.

C. What is in the messages

A notification tells you the package status, the tracking numbers concerned, and your Suite Number.

We never send payment details, card data, or identity-document data over WhatsApp.

D. Which statuses notify, and how often

We message you when a package reaches one of four stages:

• Received In Miami
• Arrived In Jamaica
• Ready for Pickup
• Delivered to Client

That is roughly one message per package per stage. If several of your packages reach the same stage at about the same time, they are combined into a single message rather than sent one by one. Standard carrier or data charges may apply to you, depending on your mobile plan.

E. How to stop

You can withdraw consent the same four ways you gave it — on our website, in our mobile application, at a counter, or inside WhatsApp — including by simply replying STOP to any of our WhatsApp messages. We record the withdrawal and stop sending.

If the number you gave us turns out not to be reachable on WhatsApp — a landline, for example — or if Meta permanently rejects it, we mark it as unreachable and stop attempting to message it. That state is visible on your account so the number can be corrected.

F. The consent trail

We keep an append-only record of every change to your notification consent: what it changed to, when, through which route (website, application, counter, or WhatsApp), and who made the change. Entries are never edited or removed — a later change adds a new entry. This record is how we can show, if you or Meta ask, when and how you agreed. It is an internal audit record; it is not published, and it is not returned as a list in your account.

Inside our own systems, staff screens and log entries show only the last four digits of your number.

7. Cookies & Tracking Technologies

We use cookies and similar browser storage to operate our sites and keep you signed in. The public website and the customer portal are separate websites on separate addresses, and what they store is not the same, so they are described separately below. Your answer to the cookie banner is the one thing they share: it is kept in a single cookie covering every shipwize.com address, so you are asked once — on whichever of the two you reach first — and both of them honour the same answer.

• Strictly Necessary – signing you in and keeping you signed in on the customer portal and mobile applications, protecting sign-up, sign-in, and password reset against automated abuse, and, on this website, the live chat cookies: they are set by LiveChat (Text, Inc.) only when you start a chat, to run that chat, and nothing of LiveChat's is stored on your device before then.
• Preferences – remembering choices you make in the interface, including your answer to the cookie banner described below.
• Analytics – this website loads Google Analytics 4 only when we have configured an analytics account for it and you have accepted it on the cookie banner. When either is missing, no analytics script is requested at all. When it does load, it sets its own cookies and it records visits and which pages are used. Accepting on the banner is a single answer covering three things together: Google Analytics, the Google map embedded in the branch locator, and the advertising pixel described below.
• Advertising – we advertise on X (formerly Twitter), and we use X's conversion pixel to measure whether those adverts work. It is operated by X Corp., it loads only once you have accepted it on the cookie banner, and it is described in Section 7 A.
• Live chat – the chat window on this website, operated by Text, Inc. (LiveChat). Its cookies are listed under Strictly Necessary above, and it is not part of the cookie banner's choice: nothing from it loads until you start a chat, and what it then stores is what it needs to run the chat you started. It is described in Section 7 A.

We run no ad network's retargeting tags, we build no advertising profile of you, and we do not sell or share your data for advertising (Section 8). The one advertising technology we use is the X conversion pixel described above and in Section 7 A: it measures our own adverts, it is not loaded unless you accept it, and it is the only thing of its kind on either the public website or the customer portal.

A. On this website (shipwize.com)

The cookie banner. On your first visit this website asks you to accept or reject three things together: Google Analytics, the Google map embedded in the branch locator, and the X (formerly Twitter) advertising conversion pixel operated by X Corp. You are asked this once per browser, on whichever of this website and the customer portal you reach first, and the answer you give is shared across shipwize.com and the portal, so neither of them asks you a second time. None of them loads before you answer — with no answer on file, no analytics script is requested, no map is embedded, and no advertising script is requested. Reject and Accept sit side by side in the banner, the same size and equally easy to press, and nothing is pre-selected. Closing the banner without pressing either is not consent: nothing is turned on, nothing is recorded, and the banner returns on your next page view. The website works the same whichever you choose.

What we store, and for how long. Your answer is kept in a cookie named shipwize_cookie_consent, set on the shipwize.com domain so that every Shipwize address — this website and the customer portal at dashboard.shipwize.com — reads the same answer and you are only asked once. It holds only which button you pressed and the date and time you pressed it: no name, account, identifier, or anything else about you. It is marked Secure (it is sent only over an encrypted connection) and SameSite=Lax (it is not sent with requests started from another site), and it is deliberately not HttpOnly, because the page's own scripts have to read it to know what you allowed. It is never sent to us and never read by our servers. We also keep a matching copy in your browser's local storage on this website, under the name shipwize.cookie-consent, so that your answer still stands if the cookie is blocked or removed; if you answered before we moved to the shared cookie, that stored answer was carried across on your next visit, keeping its original date, rather than asking you a second time. We honour your answer for six months and then ask again. It is per browser and per device, so a different browser, a different device, or clearing your browsing data means you are asked again.

Changing your mind. Every page of this website carries a Cookie Preferences link in the Legal column of the footer. It reopens the banner, shows the answer currently on file, and lets you replace it. Choosing Reject after having accepted stops Google Analytics and the X pixel being loaded again, instructs the copies already running on the open page to stop sending, and deletes the cookies a website is permitted to delete from your browser: the Google Analytics ones, whose names begin with _ga, _gid, _gat or _gcl, and X's first-party click identifier _twclid. Cookies that X Corp. or Google set on their own domains — x.com, t.co, google.com and the like — are not ours to delete: no website can remove another site's cookies, so you have to clear those in your browser's settings, or through your settings on X. It does not recall information already sent to Google or to X Corp. before you withdrew; Section 11 sets out your rights over that. You can also change your answer from the customer portal, whose footer carries the same Cookie Preferences link; because the answer is shared, changing it there changes it here. A withdrawal made on the portal takes effect on this website the next time you open it, which is when the Google Analytics and X scripts are refused and their cookies are deleted.

The X advertising conversion pixel. We advertise on X (formerly Twitter), and the third thing the banner asks about is X's conversion pixel, operated by X Corp. Accepting loads a script from static.ads-twitter.com into the page. That script may set a first-party cookie on this website named _twclid, the click identifier X uses to connect a visit to an advert, and X may set further cookies on its own domains (x.com and t.co) as any request to those domains can. It records that a visitor reached this website and, on the customer portal at dashboard.shipwize.com, that an account was created; both are reported to X Corp. so that we can measure how our adverts on X perform. It is not used to build a profile of you for anyone else, and we send X no name, email address, telephone number, or account details. Until you accept, no request is made to X at all and no X script exists on the page — on this website or on the customer portal, which loads the pixel only after an acceptance given on either site. What X Corp. does with the information it receives is governed by its own privacy policy, at https://x.com/en/privacy.

The branch locator embeds a Google map, and Google may set its own cookies when that map loads — which is why it is covered by the same choice. Until you accept, the branch address and a link to Google Maps are shown in place of the map, alongside a Show map button that loads the map for that visit only and turns nothing else on. The address suggestions in the customs forms are not part of this choice: the text you type is sent to the OpenStreetMap Foundation's lookup service (Section 4), but that request carries no cookies and stores nothing on your device.

Your colour theme. Every page has a Match device / Light / Dark switch for the colours this website is shown in, in the header, the menu and the footer. If you choose Light or Dark, that choice is kept in your browser's local storage on this website under the name shipwize-theme, so that pages open in the theme you picked; choosing Match device deletes it, and pages then follow your device's own light or dark setting. It holds only the word light or dark, it is never sent to us or to anyone else, and it is not part of the cookie banner's choice, because it is a setting you asked for. Clearing your browsing data removes it.

Live chat. The chat button in the corner of the home page connects you to our support team through LiveChat, a service operated by Text, Inc. Nothing from LiveChat is loaded until you press that button: before then no LiveChat script is requested from livechatinc.com and nothing of LiveChat's is stored on your device. Once you have scrolled part-way down a page, a small "Need help? Chat with us" prompt may appear beside the button, at most once per visit; it is part of this website, loads nothing from LiveChat, and pressing it does exactly what pressing the chat button does. Pressing either one is you asking us to open a chat, so it is not part of the cookie banner's choice, and it works the same whether you accepted, rejected, or have not answered. Once it has loaded, LiveChat receives your IP address, information about your browser, the address of the page you are on, and whatever you write in the chat — including any name or email address you choose to give — so that our support team can read and answer it. To keep the conversation connected, LiveChat may use your browser's storage on this website and set cookies on its own domains — these are the strictly necessary live chat cookies listed above; cookies on LiveChat's domains are not ours to delete, so you have to clear those in your browser's settings. If LiveChat cannot load — some browser extensions block it — the button shows our other contact details instead. What Text, Inc. does with the information it receives is governed by its own privacy policy, at https://www.livechat.com/legal/privacy-policy/.

B. On the customer portal (dashboard.shipwize.com)

The customer portal asks the same cookie question only when no current answer is on file — that is, if you reach the portal before ever visiting this website. It writes the identical cookie described in Section 7 A, so whichever of the two asked you, neither asks again. It loads no analytics of ours, no profiling technology, and no embedded map. It does carry the same X conversion pixel described in Section 7 A, and loads it only after an acceptance, given on either site; it is there — not here — that the pixel records that an account was created when you sign up. Everything else it puts on your device is either necessary to run the portal and sign you in, or a preference you set yourself, or your answer to the cookie question. The portal carries a Cookie Preferences link in the Legal column of its footer, and this website carries the same link in its own footer; both change the one shared answer, so you can replace it from whichever site you happen to be on.

Platform measurement by our hosting provider. The portal is built and served on Lovable, and the platform runs its own measurement of the service — the kind a hosting provider uses to keep a site running, available, and secure. It is delivered as part of the site itself rather than by an outside company, so you will not see it listed as a third party in your browser, but it is still collection and we would rather say so than let the absence of a familiar name imply otherwise.

Through it, the platform may receive technical information about your visit, such as the pages you open in the portal, timing and performance data, your approximate location derived from your IP address, and your browser and device type. If a page in the portal fails, the error report sent to the platform includes the address of the page it happened on. We use this to keep the portal working, not to build a profile of you, not to advertise to you, and not to follow you across other websites, and we do not sell or share it for advertising.

This measurement comes with the platform the portal is built on, so we cannot switch it off for an individual visit. If you would like to know more about it, or you object to it, contact us using the details in Section 15 and we will tell you what we can and consider any request you make. Your rights in Section 11 apply to this information as they do to the rest.

Besides anything the X pixel sets once you have accepted it (Section 7 A), the portal stores these things of its own on your device:

• shipwize_session — the cookie that keeps you signed in. It is encrypted and signed, so its contents cannot be read or altered in your browser. It is marked HttpOnly (scripts on the page cannot reach it), Secure (it is sent only over an encrypted connection) and SameSite=Lax (it is not sent with requests started from another site). Inside it are the credential for your signed-in session and your customer reference, name, and email address. It lasts seven days; signing out clears it. The credential itself is used only by our own server and is never handed to your browser.
• shipwize-theme and shipwize_theme_account — two entries in your browser's local storage for the portal's Match device / Light / Dark switch, shown in the top bar, on the sign-in pages and under Appearance on My Account. shipwize-theme holds the word light or dark when you pick one (choosing Match device removes it), so pages open in your theme before anything else loads; shipwize_theme_account holds the last theme this browser received from or saved to your account, so that a change you make on another device takes effect here without undoing one made here. Neither is sent to anyone. When you are signed in, the theme you pick is also saved to your account, so it follows you to other browsers and devices; it is stored with your customer record and holds only that one setting. An entry left by an earlier version of the portal under the name shipwize_theme is read once and then removed.
• shipwize_fav_reward — a single entry in your browser's local storage recording which reward amount you starred on My Rewards, so the star is still there next time. It holds that number and nothing else, it is never sent to us or to anyone else, and un-starring removes it. Like anything in local storage it is per browser and per device.
• shipwize_cookie_consent — your answer to the cookie question, described in Section 7 A, whether you gave it here or on this website. It is set on the shipwize.com domain rather than by the portal alone, which is what allows one answer to cover both. It holds only which button you pressed and when, it is not sent to us, and inside the portal the only thing it governs is the X conversion pixel described in Section 7 A. The portal's Cookie Preferences link writes this same cookie, so accepting or withdrawing there is the same act as doing it here.

Signing in, signing up, and resetting a password additionally run Cloudflare Turnstile, a check that tells a person apart from an automated script. It runs in your browser, so Cloudflare receives your IP address and information about your browser and may use storage on your device to carry the check out. It is a security control, not a tracking one: it is what keeps those three pages from being attacked in bulk, it is not used for advertising, analytics, or profiling, and we cannot offer the pages without it — so it is not something we ask you to consent to. The sign-up form also carries a hidden field that a real person never sees or fills in; anything typed into it marks the attempt as automated.

The sign-up page shows a country flag beside each phone-number field, and those flag images are fetched by your browser from a public image host rather than from us (Section 8). That host therefore sees your IP address and your browser, as any site you load an image from does. Nothing about you or your account is sent with the request.

You can block or delete cookies at any time through your browser settings. Blocking the strictly necessary ones will stop you from staying signed in to the portal.

8. Sharing & Disclosure of Data

Your information may be shared in the following limited circumstances:

• Between the Companies: Shipwize and Circles run on one platform and one database, and administrators may work across both for unified logistics, billing, and support.
• Carriers, customs authorities, and brokers: the information needed to move, clear, and deliver your shipment, including the customs documentation you provide.
• Payment processors: to take and reconcile payment.
• Meta Platforms: your mobile number and message content, only if you have opted in to WhatsApp notifications (Section 6).
• Amazon Web Services: hosts our application interface in the United States and holds the credentials it uses.
• Lovable: the platform on which the customer portal at dashboard.shipwize.com is built and served, so it carries the traffic between your browser and the portal. It also collects its own operational analytics about the service, described in Section 7.
• MongoDB Atlas: the managed database service that stores customer, package, billing, rewards, and consent records.
• Cloudflare: its Turnstile check runs in your browser on the customer portal's sign-up, sign-in, and password-reset pages to confirm the attempt comes from a person and not an automated script, and it receives your IP address and browser information in order to do so (Section 7).
• Google: analytics for this website, and the embedded map on the branch locator — both only once you have accepted them on the cookie banner (Section 7).
• X Corp.: its conversion pixel receives that a visitor reached this website and that an account was created on the customer portal, so that we can measure the adverts we run on X — only once you have accepted it on the cookie banner (Section 7). We send it no name, email address, telephone number, or account details. Its privacy policy is at https://x.com/en/privacy.
• Text, Inc. (LiveChat): runs the live chat on this website. Once you press the chat button it receives what you write in the chat, any name or email address you give there, your IP address, your browser information, and the page you are on, so that our support team can answer you (Section 7 A). Nothing is sent to it unless you press that button. Its privacy policy is at https://www.livechat.com/legal/privacy-policy/.
• OpenStreetMap Foundation: receives the address text you type into a form on this website, in order to suggest matching addresses.
• The country-flag image host used by the portal's sign-up page (a public GitHub Pages site, purecatamphetamine.github.io): your browser fetches the small flag images shown beside the phone-number fields from it, so it sees your IP address and browser. We send it nothing about you or your account.
• Our email provider: delivers the transactional and promotional email described in Section 5, including the requests about delivery and pickup branches we send to our own staff (Section 4 E).
• Drivers and couriers: your name, contact number, delivery address, and directions, when a package is delivered to you (Section 4 E).
• Google (Firebase Cloud Messaging) and Apple (Apple Push Notification service): a push-notification token for each device on which you allow notifications, and the content of each push notification, so that it can be delivered to that device.
• Maps applications: when you ask our mobile application for directions to a branch, it hands the branch's address to the maps application on your device, such as Google Maps or Apple Maps. We send nothing about you or your account; what that application collects is governed by its provider's own privacy policy.
• Legal Requirements: if disclosure is required by a court order, regulator, or law-enforcement authority.
• Business Transfers: during mergers, acquisitions, or similar restructuring, subject to confidentiality.
• With Your Consent: when you explicitly authorize sharing.

Service providers act on our instructions under written data-processing agreements consistent with the Jamaica DPA and GDPR Article 28.

We will never sell your data to advertisers or data brokers.

9. International Data Transfers

We operate from Jamaica, but we are not hosted there. Our application interface and our database run on servers in the United States, and our forwarding warehouse is in Miami, so your Personal Data is transferred to and processed there as a matter of course. The providers named in Section 8 may process data in other countries under their own arrangements.

Whenever data is transferred internationally, we ensure adequate protection consistent with the Jamaica Data Protection Act 2020 and Standard Contractual Clauses (SCCs) or other recognised safeguards under GDPR Chapter V.

By using our Services, you consent to such lawful transfers.

10. Data Retention & Deletion

We keep your account and shipment records for as long as your account is open, and afterwards for as long as we need them for the purposes in this Policy or as the law requires — customs, tax, and accounting rules in particular oblige us to keep shipment and financial records after a shipment is finished.

Where those rules apply, we keep the record for as long as they require — for customs and tax records, that can be up to seven years after the transaction — and then dispose of it.

Some of our records are deliberately append-only: they are corrected by adding an entry, never by deleting one.

• Invoices, receipts, store-credit history, and rewards history
• Package status and edit history, and the staff audit trail behind account and financial changes
• The WhatsApp consent trail described in Section 6

These stay with the record they belong to for as long as that record is kept, because their whole purpose is to show what happened and when.

The authorization forms produced when you create your account, and any other customs or identity documents held against your customer record, are kept with that record while your verification remains in force.

Two things are kept only in your own browser and never reach us: the reward you starred in the customer portal, and your answer to this website's cookie banner. Clearing your browsing data removes them, and there is nothing for us to delete on request.

Application and access logs are kept so we can investigate faults and security incidents.

A few records are deleted automatically: a sign-in code about an hour after it expires, and a signed-in device's record when its sign-in expires (Section 4 F). Apart from those, we do not run an automatic timetable that deletes each category of record after a fixed period. Disposal at the end of a retention period is carried out by us, and records are otherwise removed when you ask us to erase them and the law allows it. We act on that request except where the law requires us to keep something — and where it does, we will tell you what we are keeping and why. You may make that request using the contact details in Section 15.

A. Closing your account

You can close your account yourself in our mobile application, or in the customer portal where it offers the option, or by contacting us. Closing takes effect at once. It ends sign-in to your account, signs out every device and browser, deletes the push-notification registrations of your devices, revokes your passkeys, turns off two-step sign-in, and removes your authorized collectors and their details. We email a confirmation to the address on your account.

Closing archives your account; it does not delete it. The archived customer record stays in our systems, marked as closed by you, and our staff can still see it. It keeps your identity and contact details, including your name, TRN, date of birth, phone numbers, and addresses, and it keeps your invoices, receipts, payment history, package and customs records, authorization forms, store-credit, rewards, and referral history, and the audit and consent trails in this section. We keep them because customs, tax, and accounting law requires us to be able to produce them, and because we may need them to establish or defend a legal claim. They are kept for as long as that requires — up to seven years, as described above — and then disposed of. A WhatsApp notification consent is not withdrawn by closing; withdraw it as described in Section 6 E.

If you want details erased that the law does not require us to keep — a second phone number or your delivery directions, for example — ask us using the contact details in Section 15, whether or not you have closed your account, and we will act on it as described in Section 11.

B. The reason you give for leaving

When you close your account in our application, we ask why: you choose a reason from a list and may add a comment of your own. The reason is kept with your archived customer record for as long as that record is kept. We use it, together with other customers' reasons, to understand why customers leave and to improve the Services — a legitimate interest of ours. We do not use it to market to you or to make any decision about you. Please do not put sensitive personal information in the comment.

11. Your Rights

Under the Jamaica Data Protection Act, GDPR, and CPRA, you may exercise the following rights:

• Access: Request a copy of your data.
• Rectification: Correct inaccurate or incomplete information.
• Erasure: Request deletion where no lawful basis exists to retain it.
• Restriction: Limit processing in certain cases.
• Data Portability: Receive your data in machine-readable format.
• Objection: Object to marketing or profiling.
• Withdraw Consent: Revoke previously given permissions, including WhatsApp notifications.

Where a record is one of the append-only financial, audit, or consent records described in Section 10, we can restrict it and, where lawful, delete it with the rest of your account — but we cannot rewrite an individual historical entry. The point of those records is that they cannot be altered after the fact.

Closing your account (Section 10 A) is not the same as asking us to erase your data. You can make an erasure request whether or not you have closed your account; we will erase what we are not required or entitled to keep, and tell you what we kept and why. A person you have named as an authorized collector can exercise these rights over their own details.

To exercise these rights, email privacy@shipwize.com or privacy@circlesja.com. We will respond within 30 days (Jamaica DPA) or one month (GDPR), whichever applies.

12. Security of Your Information

We implement technical and organizational measures including:

• Encrypted connections between your device, our applications, and our database
• Credentials and keys held in a managed secrets store rather than in application code or configuration files
• Passwords stored only as one-way hashes. The customer portal signs you in with your email address and password; passkeys are supported where the application you are using offers them
• A signed, encrypted session cookie your browser cannot read, and a credential that stays on our server: every request the portal makes for your data is made by our server on your behalf, never by your browser
• Automatic sign-out of the customer portal after thirty minutes without activity
• Security headers on every page of the customer portal: it refuses to be displayed inside another site's frame, instructs browsers to reach it only over an encrypted connection, and blocks pages from requesting camera, microphone, location, or payment-handler access
• Role-based access control, so staff reach only the screens and records their role requires
• Rate limiting and bot protection on sign-up, sign-in, and password reset
• Rate limiting of sign-in codes, password and security-setting changes, device sign-outs, delivery and authorized-collector changes, and account closure
• Optional two-step sign-in in our mobile application, with single-use sign-in codes that expire after ten minutes (Section 4 F)
• A list of your signed-in devices from which you can sign any of them out; changing your password signs out every device
• Passkeys, where supported, whose private key stays on your device: we keep only the public part
• Identification numbers of authorized collectors shown to you only as their last four characters, and never written to a log
• Audit and access logging of account, financial, and package changes
• Masking of phone numbers to their last four digits wherever they are shown to staff or written to a log
• Employee confidentiality and data-protection obligations

While we strive for industry-standard security, no method of transmission over the Internet is completely secure; we therefore cannot guarantee absolute security. If a data breach occurs, we will notify affected individuals and the Information Commissioner (Jamaica) within the statutory period.

13. Children's Privacy

Our Services are not directed to persons under 16 years. We do not knowingly collect Personal Data from minors. If we learn that a minor's information was collected without verifiable parental consent, we will delete it promptly and notify the guardian and relevant authorities as required by law.

14. Links to Other Websites

Our Services may contain links to third-party websites not operated by us. The customer portal, for example, links back to our public website and to our pages on Facebook, Instagram, and X. Following one of those links takes you to a site we do not control, and that site can see that you arrived from us. We are not responsible for their content or privacy practices. Please review the privacy policies of any external sites you visit.

The same applies to a maps application you open from our mobile application for directions to a branch (Section 8): the branch's address is all that is passed to it, and anything it then collects is governed by its provider's privacy policy.

15. Contact Us

For questions, requests, or to exercise your data-protection rights, please contact:

16. Changes to This Policy

We may revise this Privacy Policy periodically to reflect operational, legal, or regulatory updates. The latest version will always appear on our websites, and the "Last Updated" date at the top of this page is the date it took effect. If we make material changes, we will notify users by email or in-app notice before the new terms take effect.

The October 12, 2026 revision added home delivery, pickup-branch requests, and authorized collectors' identification details (Section 4 E), signed-in devices and two-step sign-in (Section 4 F), push notifications and maps applications (Section 8), and what happens when you close your account, including the reason you give (Section 10 A and B).