Privacy Policy
Effective date: 4 November 2026
Who We Are
Kiosku is an order-management platform for small businesses that sell through chat channels such as WhatsApp and Instagram DM.
Who controls your data depends on where your store is registered. For stores registered in Indonesia, the data controller is PT Wahana Ciptaka Digital, a limited liability company established under Indonesian law and domiciled in Jakarta Utara. For stores registered anywhere else, the data controller is Sebastian Arthur Chua, a sole trader based in Sydney, New South Wales, Australia. This affects which data protection law governs your rights — see §7.
If you have any questions about this policy or how your information is handled, please contact us:
PT Wahana Ciptaka Digital
Jl. Ruko The Plaza, Jl. Pantai Indah Kapuk Blok 9AG
Kelurahan Kapuk Muara, Kecamatan Penjaringan
Kota Administrasi Jakarta Utara, DKI Jakarta 14460, Indonesia
NPWP 10.000.000.8-456.163
admin@kiosku.storeCounterparty for stores registered in Indonesia.
Sebastian Arthur Chua
Sydney, New South Wales, Australia
admin@kiosku.storeCounterparty for stores registered outside Indonesia.
What Personal Information We Collect
We collect different information depending on how you interact with Kiosku.
Merchant account information
When you sign up as a merchant, we collect your email address and, if you sign in with Google, your Google profile name and profile picture URL. We also store a hashed password if you use email and password sign-in.
Merchant business configuration
We store the information you enter to set up your store: your business name, contact details, operating hours, product catalogue, delivery zones, and payment configuration. This is business data you provide voluntarily to make Kiosku work for your store.
Merchant identity verification (stores in Indonesia)
If you apply to accept digital payments through DOKU, we are required to verify your identity and your business before your payment account can be created. For that purpose we collect:
- Your full legal name and your national identity number (NIK), together with a photograph of your identity card (KTP)
- A selfie photograph, used to check that it matches your identity document
- Your contact email address and phone number
- Your business category, a description of your business, your full business address (provinsi, kota/kabupaten, kecamatan, kelurahan/desa, kode pos, and street address), a photograph of your storefront, and links to the channels you sell through
- A record of your acceptance of the cooperation agreement (Perjanjian Kerja Sama): the version you accepted, a digital fingerprint of the exact document shown to you, the date and time, and the IP address and browser user-agent used
Your NIK and your selfie are specific personal data under Indonesian law (UU No. 27 of 2022 on Personal Data Protection). We collect them only for merchant verification and anti-money-laundering compliance, only from merchants who choose to apply for digital payments, and never for advertising, profiling, or any other purpose. Providing them is voluntary — but without them we cannot create your payment account.
These documents are stored in a private, access-controlled location. They are not readable by other users of the platform, not readable by your own staff members, and not served publicly; only our reviewers can open them.
End-customer information
When your customers place orders — either through a checkout link you share or manually entered by you — we collect:
- Name, email address, phone number, and delivery address
- Order details (items, quantities, special instructions)
- Payment metadata (payment status, reference numbers). We do not store raw card numbers or full bank account details — those are handled directly by our payment processors.
This information is entered on behalf of, or directly by, your customers. As the merchant, you are responsible for ensuring you have the appropriate basis to share your customers' data with us. When your customers visit your storefront or checkout, Sentry (see “Session and technical data” below) can also receive their IP address, browser and device type, and the request details of the page, and can replay their visit with on-screen text and media masked.
If a customer leaves “Save this address on this device” ticked while they enter a delivery address at checkout, their browser stores a first-party cookie holding that delivery address, any address details they entered (such as a building or unit number), the map coordinates, and a Google place identifier, as soon as the address is chosen and whether or not the order is placed. It holds no name, phone number, email, or payment information. The cookie is shared across Kiosku storefronts on kiosku.store, so the address is filled in at the next checkout with any Kiosku merchant. It is sent with requests to Kiosku's pages on kiosku.store, storefronts included, stays on the device for one year after it was last saved, and is deleted when the customer unticks the box at checkout or clears their browser's cookies. We remove it from the reports we send to Sentry. Scripts running on a storefront page, including a merchant's Meta Pixel (see “Marketing pixels on storefronts” below), can read it.
Session and technical data
We use essential session cookies to keep you logged in. These are set by our authentication provider (Supabase) and hold your signed-in session, which identifies you (it includes your user ID and email address); they contain no tracking identifiers. The Kiosku dashboard itself does not set analytics, advertising, or marketing cookies. The Kiosku home page, the welcome and hampers pages, and our sign-up, login, and password-reset pages do set a first-party analytics cookie, which we read once when you create a store; see “Product analytics on the home, welcome, hampers, and sign-up pages” below.
To find and fix faults, we use Sentry across Kiosku's pages, including the dashboard, storefronts, and checkout, and on our servers. It collects error reports and performance traces, which include the IP address, browser and device type, and request details of the page that failed. Sentry also records a replay of a sample of sessions, and of sessions in which an error occurs, with on-screen text and media masked. We do not tag reports with your account, but a report can include the cookies and request data of the page that failed.
The Kiosku mobile app
If you use the Kiosku app on your phone, it shows the same dashboard and collects nothing beyond what is described above, with two additions. When you allow notifications, the app registers a push notification token and your phone's platform (such as iOS), and we store them against your user and your store. We use them only to send you alerts about new orders, through Google's Firebase Cloud Messaging and Apple's push notification service. Each alert carries the order number, the customer's name, and the order total. The app uses Bluetooth only to talk to the receipt printer you connect; it does not collect any Bluetooth data, and nothing about your printer is sent to us.
Marketing pixels on storefronts
Individual merchants may choose to enable the Meta (Facebook) Pixel on their own storefront. This is off by default and entirely merchant-controlled — it loads only when a merchant has entered their Meta Pixel ID in their store settings. When enabled, the pixel runs in the visitor's browser on that merchant's storefront and reports a small set of standard shopping events to Meta: page views, viewing a product, adding an item to cart, starting checkout, and completing a purchase (including the order value and currency). This lets the merchant measure and target their Facebook and Instagram advertising. The pixel is not loaded on storefronts whose merchant has not enabled it, and never on the Kiosku dashboard. The data flows to Meta under Meta's own terms — see the Meta Privacy Policy.
A merchant may also connect Meta's Conversions API. When they do, once a customer's order is paid or proof of payment is uploaded, Kiosku's servers report that purchase (including the order value and currency) to the merchant's Meta dataset. We send the customer's email address and phone number in hashed form, along with the IP address, browser user agent, and Meta's own cookie identifiers (_fbp and _fbc) from checkout. We keep the IP address, user agent, cookie identifiers, and the checkout page address only until the purchase is reported, and delete all of them once it is reported or within 14 days at most. For those orders the browser pixel does not also report the purchase, so Meta receives it once.
Kiosku's own advertising pixel
We advertise Kiosku on Facebook and Instagram. To measure those ads, our own Meta Pixel runs on the Kiosku welcome and hampers pages that our ads link to. It reports a visit to those pages, a tap on a WhatsApp button, and a completed consult request to Meta. It never sends the name or Instagram account you type on the hampers page. When you submit the consult form, our server also reports the request to Meta directly, so it is counted even if your browser blocks the pixel. That report includes your WhatsApp number and email address in hashed form (a one-way code Meta can match against its own accounts but cannot turn back into the original), your IP address, your browser type, and Meta's cookies from your visit. We also record the ad campaign details from the page link (such as the campaign name and Meta's click identifier) alongside your request, so we know which ad reached you. This pixel does not run on merchant storefronts or on the Kiosku dashboard.
If you arrive at any Kiosku page from an ad link, we keep that link's campaign details in a cookie for 30 days. If you then create a store, we record them against it, so we know which ad brought you to Kiosku. When any merchant creates a store, our server also tells Meta that a sign-up happened, including your email address in hashed form, your IP address, your browser type, and Meta's cookies from your visit, so Meta can credit the ad that reached you.
Product analytics on the home, welcome, hampers, and sign-up pages
To understand how people find and use our home, welcome, hampers, and sign-up pages, and where signing up goes wrong, we use PostHog, a product analytics service. PostHog runs only on the Kiosku home page (including its Indonesian and Australian versions), the welcome and hampers pages, and our sign-up, login, and password-reset pages. On the Kiosku dashboard and on storefront checkout pages it runs only in the limited form described under “Feature usage on the dashboard and checkout” below. It does not run anywhere else on merchant storefronts or on our guides, and we do not use it for advertising.
On those pages, PostHog sets a first-party cookie and a matching entry in your browser's storage (named ph_…_posthog) holding a random identifier, so it can tell that several page views came from the same browser. It records the pages you visit and the link that brought you there (including any ad campaign details in it), how far you scroll, the buttons and links you tap, your browser and device type, and whether you are using an app's built-in browser (such as Instagram's). It also records which sign-up method you choose and, if signing up fails, a general reason (such as “email already registered”) — never what you typed. PostHog uses your IP address to estimate your approximate location (country and city), then discards it; your IP address is not stored.
PostHog also makes session recordings: a replay of how the page looked and responded while you used it, so we can see where it confuses people or breaks. Everything you type into a form field is masked in your browser before the recording is sent, and the free consult form is left out of recordings entirely.
If you create a store, we link this activity to your Kiosku account, so we can see which visits led to a store. We use PostHog's European Union region, so this data is stored in the EU (see §5).
Feature usage on the dashboard and checkout
To see how features are used, so we can improve them, the Kiosku dashboard and storefront checkout pages send PostHog a small number of named events. One records how a delivery or store location was set: whether it was found by search, a pasted map link or coordinates, current location, or the map, and how many metres the confirmed pin sits from the place first found. Another records whether a document sent straight to a printer printed, which kind of document it was, and how long it took. These events carry the store's name as it appears in its web address, the page address without anything after the “?”, your browser, operating system, device type and model, screen size, language, and time zone, whether you are using an app's built-in browser, and random identifiers that last only until the page is reloaded. They never include an address, coordinates, names, phone numbers, the page you came from, or anything you typed.
On these pages PostHog sets no cookie of its own and stores nothing in your browser, so it cannot recognise you between visits, and it records no page views, taps, or session recordings. If you reach the dashboard from our sign-up or login pages without reloading, these events use the identifier PostHog set there, and if you created a store, they are linked to your Kiosku account as described above. As on our other pages, PostHog estimates approximate location from your IP address and then discards it, and the data is stored in the EU (see §5).
Why We Collect It and How We Use It
We use personal information to:
- Provide and operate the service — authenticate your account, display your orders, process payments, and deliver the features you sign up for.
- Communicate with you — send transactional emails (password resets, order confirmations) when you or your customers trigger them.
- Improve reliability — diagnose errors and maintain the platform's performance.
- Comply with legal obligations — retain records as required under applicable law.
We do not sell personal information. We do not use it for behavioural advertising.
Where Data Is Stored and International Transfers
Your data is stored primarily in Supabase's Singapore region (ap-southeast-1). This means your data is hosted in Singapore by Supabase.
Some of our sub-processors operate infrastructure in the United States (Supabase's control plane, Vercel's edge network, Stripe's payment platform, and Sentry's monitoring service). By using Kiosku, you acknowledge that your information may be transferred to and processed in countries outside your own, including Singapore, the United States, and the European Union. PostHog, our product analytics provider, stores the data it collects in the European Union.
Merchant verification documents (§2) are stored in the same Singapore region, in a private storage bucket with no public access and no merchant-level read access — they are readable only by our reviewers through an authenticated, time-limited link. Where your verification data is transferred to DOKU, that transfer is to a recipient in Indonesia.
Where we transfer personal information internationally, we take reasonable steps to ensure it receives an equivalent level of protection. Our sub-processors are bound by their own privacy policies and applicable data protection laws.
How Long We Keep Your Information
We retain your personal information for as long as your account is active. If you request account deletion, we delete your account and its data within 30 days, except the records described below, which we keep for longer.
Your push notification token is deleted when you sign out of the app, when you are removed from a store, and when the token stops working.
End-customer order data is retained as part of your merchant account. When you delete your account, we delete your customers' details, except order, payment, payout, and invoice records, which we keep for as long as Indonesian tax and financial-record rules require.
Merchant verification documents. Your KTP image, selfie, and the other verification material described in §2 are kept for as long as your payment account is active, and for a period after it closes, because anti-money-laundering and payment regulations require us to be able to evidence who we onboarded. After that period we delete them, unless the law requires us to keep them longer. Your record of accepting the cooperation agreement is kept for as long as that agreement could still be relied on by either of us.
To request deletion, email us at admin@kiosku.store from the address you sign in with, or follow the steps on our support page.
Your Rights
Stores registered in Indonesia
Where PT Wahana Ciptaka Digital is the controller, your personal data is governed by Indonesian law, principally UU No. 27 of 2022 on Personal Data Protection (UU PDP). Under it you have the right to be informed about how your data is processed; to access and obtain a copy of it; to have inaccurate data corrected; to have your data erased or its processing ended; to withdraw a consent you previously gave; to object to certain processing; and to seek redress for a breach. Withdrawing consent to the verification data in §2 means we can no longer operate your payment account, but it does not affect your right to be paid out any balance in your sub-account.
Stores registered outside Indonesia
Where Sebastian Arthur Chua is the controller, your personal information is governed by the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Under these, you have the right to:
- Access — request a copy of the personal information we hold about you.
- Correction — ask us to correct information that is inaccurate, out of date, or incomplete.
- Complaint — if you believe we have mishandled your personal information, you can lodge a complaint with the Office of the Australian Information Commissioner (OAIC).
To exercise your access or correction rights, contact us at admin@kiosku.store. We will respond within 30 days.
Security
We take reasonable steps to protect personal information from misuse, loss, unauthorised access, modification, or disclosure. Our security measures include:
- Encrypted HTTPS connections for all data in transit
- Cookie-based sessions with HTTP-only, Secure flags set by Supabase's SSR library
- Row-level security (RLS) policies on our database, ensuring each merchant can only access their own store's data
- Authentication handled by Supabase, which manages credential hashing and token rotation
No method of transmission over the internet is 100% secure. If you believe your account has been compromised, contact us immediately.
Children
Kiosku is not intended for use by anyone under the age of 16. We do not knowingly collect personal information from children under 16. If you believe a child has provided us with personal information, please contact us and we will delete it.
Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the effective date at the top of this page. If the changes are material, we will notify merchants by email.
Continued use of Kiosku after a policy update constitutes acceptance of the revised policy.