Cookie & Tracking Notice — HomeKampung
v0.3.6 · Last revised 6 November 2026 · In force since 1 Nov 2026
What this notice covers. Everything below describes what the software does today. Where a feature is planned but not yet built, it says so in that row rather than being written in the present tense.
Cookies
HomeKampung sets up to four cookies, all strictly necessary. Three belong to
the sign-in system and are set only on the seller and operator consoles (the
sign-in page and /admin, /operator); the fourth is an order-throttle cookie
set when a buyer submits an order. We set no others.
| Cookie | Purpose | Expires | Basis |
|---|---|---|---|
authjs.session-token |
Keeps you signed in to a seller or operator account | 7 days for a seller, 12 hours for an operator - and sooner when idle: a seller is signed out after 2 hours without activity, an operator after 30 minutes | Needed for the service |
authjs.csrf-token |
Protects sign-in forms against cross-site request forgery | When you close the browser | Needed for the service |
authjs.callback-url |
Remembers which page to return you to after sign-in | When you close the browser | Needed for the service |
hk_did |
An opaque random id we generate (not derived from your device) to limit how many orders one browser places at a shop per day — never a fingerprint, never used for advertising, personalisation or measurement | 2 days | Needed for the service (abuse prevention) |
Over HTTPS the sign-in cookies carry the browser's __Secure- / __Host- prefix
in their names. All four are httpOnly (JavaScript cannot read them),
sameSite=lax, and marked secure when served over HTTPS.
A buyer who only browses a shop is given no cookie. The sign-in cookies are
set on the sign-in page and the consoles, not on shop pages. hk_did is set when
you submit an order, including an order the shop's limits refuse; the id is
stored on our server with that day's count, and with a refused attempt for 30
days (see the Data Deletion & Retention Policy).
Browser storage that is not a cookie
| Key | What it holds | How long |
|---|---|---|
hk.cart.<shop> |
Your cart at that shop, so it survives a reload | 7 days |
hk-orders-<shop> |
The last five order numbers this browser placed at that shop, so "Where is my order?" can offer them (the phone number is still required) | Until you clear site data |
hk.orders.statusHelp, hk.readyChecklist.collapsed.<shop> |
Seller-console preferences (a help box dismissed, a checklist collapsed) | Until you clear site data |
Nothing in browser storage is sent to us by itself. Before you place an order, the browser does send the cart's product ids, quantities and prices, and your postal code if you entered one, so that we can show the discount, the delivery fee and the shop's payment details; none of that is stored until the order is placed.
What we count
No third-party analytics, no advertising cookies, no cross-site tracking pixels, no sale of browsing data, no device fingerprinting. There is no Google Analytics, no Meta Pixel, no session recorder, and the page's security policy blocks any script that is not ours.
One first-party counter runs: each view of a shop page adds one to that shop's total for the day, and each tap on a shop's contact button adds one to its enquiries for the day. The totals are per shop, per day, and carry no visitor identifier of any kind. A seller's own visits to their shop are not counted.
Server logs and transit
Our web server keeps an access log (your IP address, the page requested, the time and your browser's identification string) for 30 days, for security and to diagnose faults. All traffic to HomeKampung passes through Cloudflare, which decrypts it at its edge to protect the site and sees the same information in transit; it does not store our data. Fonts and images are served from our own servers, so loading a page does not hand your address to a font provider.
Not built
- Self-hosted, aggregate analytics (for example Plausible or Umami). None is installed. This notice will be updated before any is switched on.
Managing cookies
Browser settings can block or clear cookies. The sign-in cookies are required for signing in; clearing them signs you out. Ordering works without cookies.