Last updated 2026-10-09. This explains what Pallet King stores, where it is stored, who else is involved, and what you can ask us to do about it. It is written against this application’s actual behaviour, not a template.
| Question | Answer |
|---|---|
| Do you upload my booking files? | No. Excel, CSV and PDF booking lists are parsed in your browser. There is no upload path in the application. |
| Do you see my cargo data? | No. Build records and parsed lines live on your device. They reach our servers only if you use a save or share action that sends them. |
| Are there advertising or analytics trackers? | No. There are no third-party analytics, advertising, social or session-replay scripts on this site. |
| Are there cookies? | No cookies are set. We use browser storage instead — listed in section 4. |
| Do you sell or rent personal data? | No. |
| Is payment data handled here? | Paid checkout is not live. When it is, a third-party merchant of record processes payment; we do not receive card numbers. |
珠海市香洲区卓浚零售和批发商行 (Zhuojun Retail and Wholesale Firm, an individual business operator registered in Zhuhai, Guangdong, China) operates https://www.aircargo.hk. Contact for privacy matters: support@aircargo.hk. Registered or place of business: Xiangzhou District, Zhuhai, Guangdong, China (个体工商户 / individual business operator).
If you register, we store the identifier you sign up with and the minimum needed to authenticate and gate features:
| Data | Why | Basis |
|---|---|---|
| Phone number (SMS sign-in) or email and a password hash (email sign-in), or the profile from a third-party sign-in provider | Creating and authenticating your account | Performance of a contract — you asked for the account |
| Display name, if provided | Showing who is signed in | Performance of a contract |
| Access and refresh tokens, held in your browser | Keeping you signed in | Performance of a contract |
| Entitlement record: plan level, trial end date, quota used and total | Deciding which features you may use | Legitimate interests — operating the plan you signed up for |
Cargo lines, dimensions, weights, pallet build plans, completion records, unit and theme preferences are written to your browser’s own storage — local storage, session storage and IndexedDB. They are not transmitted to us. Practical consequences you should know:
No cookies are set. The storage keys, all first-party, are:
| Key | Where | Purpose | Necessary? |
|---|---|---|---|
| pka-locale, pka-unit, pka-mode, pka-role | local storage | Your language, metric/imperial, office/field and role choices | Yes — you set them |
| pka_trial_record | local, session storage and IndexedDB (AES-GCM encrypted) | Counting guest build-plan usage so the free tier works | Yes — for the free tier as offered |
| pka-fp-v1, pka_fp, pka_fp_legacy | session storage | A device identifier used with the trial count; recalculated when the tab closes | See section 5 |
| pka-analytics-session | session storage | A random session id so funnel events can be grouped within one visit | No — but see section 6 |
| pka-lead-fallback | local storage | Holds a contact request locally if the network fails, so you can retry | Yes — protects what you typed |
To count a guest’s free build-plan uses when there is no account, the application computes a device identifier from slowly-changing browser characteristics: the user-agent family, language, platform, time zone, CPU and memory tiers, a canvas rendering signature, a WebGL renderer signature, and screen dimensions and colour depth. It is hashed in the browser, kept in session storage, and sent to our own backend only as an opaque identifier when the trial quota is checked.
We call this out because it is the one item here that a reader should reasonably object to. Our stated purposes are limited to free-tier accounting and basic abuse prevention. Our legal basis is legitimate interests, weighed against the fact that the signal is coarse, not persisted across browser sessions, and not combined with advertising data. We do not use it to identify individuals, and we do not treat it as a security boundary — it is deliberately a soft measure.
Pricing-page interactions are recorded in our own database, not in a third-party service. The event set is fixed and small: pricing_view, plan_card_click, billing_toggle, cta_click, lead_form_open, lead_form_submit, lead_form_abandon, feature_table_scroll, free_limit_hit, paywall_view. Each row may carry the plan and billing cycle involved, your interface language, a session id, and your user id if you are signed in.
Basis: legitimate interests, in understanding whether the pricing we offer is workable. This is not cross-site tracking and no analytics script from another domain runs on this page.
If you submit the “request access” form we store the email you give us, and optionally your company name, contact name, the plan and billing cycle you chose, a seat estimate, your message, and your interface language. Purpose: to reply and to prepare a quote. Basis: your request. We do not add you to a marketing list on the strength of a contact request.
An optional error-reporting endpoint can be configured by the operator. When configured, client-side errors are sent with a message, a truncated stack trace and the page URL. These fields are scrubbed before sending, because a stack trace can contain values parsed from a booking file and a URL can contain sign-in tokens. When no endpoint is configured, nothing leaves the browser.
| Provider | Role | What they see |
|---|---|---|
| Vercel | Hosting and content delivery | Requests for pages and files, including IP address and user-agent in platform logs |
| Supabase | Authentication, database and serverless functions | Account data, entitlements, leads and analytics events described above |
| Cloudflare | DNS and the contact mailbox | Mail sent to the contact address |
| A merchant of record (not yet enabled) | Payment processing, invoicing, tax | Your billing details at checkout, under their own terms |
We do not maintain a separate list of sub-processors beyond these, and we will disclose changes here before using a new provider for personal data.
Account, lead and analytics data are stored in the Supabase project backing this application, in ap-south-1 (Mumbai, India) — that is, on infrastructure physically located in India. Booking and build data is stored only on your device and never reaches this region.
Stated plainly, because it is the part an operator would otherwise gloss over: India is not covered by an adequacy decision of the EU, the United Kingdom or Switzerland. For a user in those jurisdictions, therefore, personal data associated with an account, a contact request or an analytics event is a third-country transfer rather than a domestic one.
| Your location | What applies | What we rely on |
|---|---|---|
| EEA / UK / Switzerland | GDPR or UK GDPR, including its Chapter V transfer rules | The standard contractual clauses published by Supabase and by our hosting provider, plus the minimisation described in sections 2 to 8 |
| China (mainland) | PIPL, including cross-border transfer rules | We keep the personal information we hold to the account, contact and event fields listed above |
| Elsewhere | Local privacy law as it applies to you | The same disclosures and the same deletion route in section 11 |
We do not currently run an automated deletion schedule for contact requests or analytics rows. Account data is kept while the account exists. Device-side data is kept until you clear it, and session-scoped items disappear when the tab closes.
On request we will delete your account, your contact request, and any analytics rows tied to your user or session identifier. Contact ${CONTACT()} and we will confirm when it is done.
Depending on where you are — including under the EU/UK GDPR, California’s CPRA, and China’s PIPL — you may be able to access, correct, delete, or port your personal data, object to or withdraw consent for processing, restrict processing, and complain to your supervisory authority. Where we rely on legitimate interests, you can object and we will assess our grounds against yours.
There is no self-service export yet, so these are handled by email. We will not require more identity information than we need to confirm the request, and we will not ask you to create an account in order to exercise a right.
A GPC or DNT signal is honoured in substance because there is nothing to opt out of: no third-party trackers, no advertising, and no sale or sharing of personal data for cross-context behavioural advertising.
Row-level security gates database access so a signed-in user cannot read another user’s records; the content security policy restricts which scripts and connections the page may make; device trial records are encrypted before being written to browser storage. No system is perfect, and browser storage is readable by anyone with access to the device or its profile — which is why the sensitive material, your cargo data, is never sent to us in the first place.
This is a business tool for air cargo professionals and is not directed at children under 16; we do not knowingly collect their data. If material changes are made to this policy we will update the date above and, for changes that reduce rights, announce them in the application.