Privacy Policy

1Data we collect

• Account data: your email address when you sign up (through Sign in with Google or a 6-digit code we email you), and your Google account ID if you sign in with Google; see Data from your Google account. We also note where you first came from before signing up (a link or campaign code, the referring site, and your first page on kedaify.com, for example a free tool) to learn which channels bring new stores. One account can have several stores; if you move a store to another account, the receiving account's email address is kept for up to 7 days for the move link, then deleted.
• Store data: what you fill in yourself: business name, menu or products, prices, opening hours, WhatsApp number and payment details.
• Order data: a short record of each order that comes through your store (time, channel, items, total) for the dashboard. For ordinary orders (cart and checkout) we don't store your end customers' personal data.
• POS and stock: sales the Merchant records at the POS (items, quantities, discounts, payment method, time), open bills with the customer's name or table number if the Merchant enters them, end-of-day records, and stock, ingredients and recipes. Expenses the Merchant records (amount, category, note, date, and a photo of the receipt if uploaded) only show in that store's dashboard; receipt photos are kept at a random address that isn't linked from the store page. The record and its photo are deleted when the Merchant deletes that expense. So that the dashboard and POS still open without a signal, a copy of the store's menu, prices and stock is kept on the Merchant's own device (browser storage) and removed when the Merchant signs out of the dashboard. A digital receipt made from the store or the POS keeps the order's contents and total, plus a scrambled daily visitor ID like the one in visitor statistics.
• Team (Business plan): if a Merchant invites staff, we store the name, email and role the Merchant enters, the Kedaify account the staff member uses to accept the invite, and their POS PIN as a hash (we don't keep the PIN itself). Each POS sale records who entered it, and the store's activity log records who voided a sale, gave a large discount, changed a price or changed the team. A shared POS device keeps a random marker in its browser (a cookie) that is only sent to that store's dashboard. When the Merchant removes a staff member, their access stops at once and their PIN is deleted; their name stays on the sales they recorded.
• Branches (Business plan): if a store has several branches, each order, POS sale, open bill, end of day and expense records its branch, and staff can be limited to the branch they work at. The branch a customer picks is remembered on the customer's own device (browser storage) so they don't have to pick again; it's only sent with their order to that store.
• Delivery addresses (only for stores that turn on delivery): if a customer chooses delivery, the recipient's name, WhatsApp number, address, landmark and location pin (if the customer chooses to share it) are stored on behalf of the store so they appear in that store's orders; only that store can see them. The address is kept while the store's account is active and is deleted when the customer or the store asks. If the customer chooses, the address can also be kept on the customer's own device (browser storage, up to 3 addresses) so it needn't be typed again; that copy isn't sent to us and the customer can delete it from the cart at any time.
• Leads (only for service and booking stores): if your store uses an enquiry or booking form, what the customer sends (name, WhatsApp or phone number, and notes or needs) is stored on your behalf so it appears in the Leads tab of your dashboard. You are the controller of that customer data and we process it only to run the service; the customer is told when they send the form.
• Customers a store saves: if a store chooses to save its customers to send them bills and bill links, the customer's name and WhatsApp number are stored on behalf of the store so they appear in its dashboard, together with the bills sent to them. The store is the controller of that data. A customer's bill link only shows the bills and amounts, without a name or number. This data is deleted when the store deletes that customer, or when the customer asks the store or us.
• Creator pages: files the Merchant uploads to share (kept in Cloudflare storage) and how many times they're downloaded. For free downloads we store the details the Merchant asks for on that item (name, WhatsApp number and/or email) and whether the person agreed to be contacted again, on behalf of the Merchant so they appear in the dashboard. The Merchant is the controller of that data.
• Customer reviews: a customer who has ordered can leave stars, a name (optional) and a comment. Reviews show publicly on the store page, are linked to the order so only real buyers can review, and can be hidden by the store.
• Feedback and problem reports: if a Merchant sends a feature idea or problem report from the dashboard, we store the message, a screenshot (if attached), and technical details that help us trace the problem: the last dashboard tab, the screen width, the app version and the browser type.
• Inbox: conversations between the Merchant and Kedaify in the dashboard, meaning the messages and their times. For messages from Kedaify we also record when they were opened and read, what they were opened in, and which links were tapped, so we know which letters are useful. Letters sent by email carry a small invisible image that tells us when the email was opened. Kedaify's letter emails can be turned off in Settings or through the link in the email.
• Interest list for a new plan: if you fill in the interest form for a plan before it opens (used for Kedaify Business until November 2026), we store your name, email, business name, the options you ticked, your note, the store you opened it from if you came from the dashboard, and your account if you were signed in. This is only used to tell you about that plan and to count interest, and isn't shared with anyone; ask for it to be deleted at any time through the contacts in section 9.
• Ajak Tetangga (a store-invite program in Indonesia): if you join, we store the membership, the stores made through your link, and the rewards. To make sure each store is run by its own owner, we record the store owner's browser (a random ID in a cookie, see Cookies) and network (a hash, not the IP address) per day, and the checks only use the last 90 days of records. On a store made through a link, for its first 60 days, each order or booking gets a one-way scrambled buyer marker (from a random ID in the buyer's browser, or the phone number on a booking) with a hash of its network, to tell real buyers from made-up orders. A member only sees the names of the stores they invited and three ticks (ready to sell, in use, has buyers), never orders, sales or buyer data; the owner of an invited store sees who invited them and can leave at any time in Settings → Plan.
• Deleted accounts: so the trial and the program can't be misused by signing up again, we keep a one-way hash of the email, account ID and WhatsApp number of a deleted account or store. The hash can't be turned back into the original data, only counts for 12 months after the deletion, and we delete it if you ask.
• Dashboard use: how many times each dashboard feature is opened per day (counts only), and the devices that open the dashboard: a random ID kept on that device, the device type, operating system, browser, whether it was opened as an installed app, and the country, without IP addresses. We use this to improve the service and to show Merchants which features they have and haven't used.
• Visitor statistics (without cookies): for the Traffic feature we record the page opened, the referring site, campaign parameters (UTM), country and device type, plus the name of the internet provider for visits from outside Indonesia, so we can tell people from automated programs. Visitors are counted with a daily ID scrambled (hashed) from the IP address and browser type; this ID changes every day, and the IP address itself isn't stored.
• Free tools (kedaify.com/alat): the numbers and text you enter are worked out in your browser and not sent to us; your entries are kept on your device so you can open them again. We only record that a tool was used or its sign-up button was tapped, with the page, the referring site and the campaign source (UTM).
• Spam prevention: to limit excessive orders, forms, reviews and sign-in attempts, the sender's IP address network is kept briefly as a counter, for about 1 hour at most (for sign-in attempts, until the lock period ends).
• Order notifications: if a Merchant turns on notifications on a device, we store that device's push subscription address so new orders can be announced.
• Technical data: the usual logs from our hosting provider, for security and to keep the service running.

2How we use data

• to provide and run the service (showing your store, processing subscriptions);
• to show your sales dashboard, pass leads and bookings to your inbox, and send notifications about your account and orders;
• to keep the service secure, prevent misuse, and meet legal duties;
• to contact you about the service (for example a subscription renewal reminder);
• to tell you when a plan you registered interest in opens;
• to run Ajak Tetangga: counting the stores that became active, giving rewards, and preventing cheating. The program's emails can be stopped from the link in them.

3Sharing data

We don't sell your data. We only share it as far as needed with the providers that help run the service:

• Hosting, database and storage: Cloudflare (serving the site, the database, and files such as product photos).
• Payment providers: Duitku (payments in rupiah) and Polar (payments from outside Indonesia), to process your subscription fee.
• Email: Resend, to send sign-in codes and account and subscription notices.
• Sign in with Google: Google, if you choose that way of signing in.
• Ad platforms a Merchant chooses: Meta, TikTok or Google, only for stores that add their own pixel (see section 1).
• Law enforcement: when the law requires it.

4Cookies

We use the cookies and local storage that are needed: a session cookie to keep you signed in, a kd_dev cookie with a random ID for a store owner's browser (it stays after signing out, for two years, only for store owners who sign in, and is used to prevent misuse), and storage on your device for preferences, your store's dashboard key, delivery addresses you save, a random buyer ID per store, and your choice about ad pixels. Kedaify's own visitor statistics don't use cookies. Kedaify doesn't set third-party advertising cookies; ad pixels only exist on stores that add them, after the visitor agrees.

5Security

We take reasonable security measures (for example encrypted HTTPS connections and hashed dashboard credentials). No system is entirely free of risk, but we work to protect your data.

6How long we keep data

We keep data while your account is active, or as long as needed to run the service and meet legal duties (for example payment records for tax). Customers' delivery addresses are kept while the store's account is active, unless the customer or the store asks for them to be deleted. Store owners' browser and network records and the hashes of deleted accounts are also kept until you ask for them to be deleted. Spam counters are deleted after about 1 hour, and the daily visitor ID changes every day. You can ask for your account and your data to be deleted.

7Your rights

Under Indonesia's Personal Data Protection Law (Law No. 27 of 2022), you have the right to see and correct your personal data, ask for it to be deleted, and withdraw consent (for example for the ad pixels on a store). Send a request through the contacts below and we'll follow it up as the law requires. For customer data a store manages (orders, addresses, leads, download details), that store is the controller: contact the store first, and we'll help if needed.

8Changes to this policy

This policy may be updated from time to time. The latest version applies from when it's published on this page.

9Contact us

Questions about privacy can be sent through the contacts at the bottom of this page.