Credit Khata is a credit-ledger app for small shops. It is published by Abdohoo, which is the controller of the data described here. Write to support@abdohoo.app with any question about this policy or to exercise any of the rights below.

There are three kinds of user, and what we hold differs for each: a shopkeeper who runs a shop, a customer who keeps a credit account with that shop, and a staff login (a manager or a cashier) that a shopkeeper issues to people who work at one of their branches.

What we collect

Account information

• Your name, and the email address and password you sign up with. Passwords are stored only as a one-way hash — we cannot read yours.
• Optionally: phone number, WhatsApp number, address and city.
• For a shop: business name, business type, tax number and preferred currency.

Shop content you upload

• Logo and banner images, a tagline, a description, and links to your social profiles. These are shown to the customers linked to your shop, and the image files are served from a public address — anyone holding the link can open them.

Your profile photo

• Optionally, a photo of yourself. A customer sets one on each shop account they hold, and only that shop's owner and staff see it; they can also remove it. Shop owners and staff can set their own, which the shop owner sees on the staff list. Before it is stored it is re-encoded, which removes any location or device details the camera wrote into it. Like shop images it is served from a public address, and it is deleted when you remove it or delete your account.

Ledger information

• The entries a shopkeeper records: amounts owed and paid, currency, item descriptions, quantities and dates. Because these amounts are debts, we treat them as financial information.

Payments between a customer and their shop

Credit Khata never processes a payment and never holds money. A shop can list its own payment details — mobile-wallet numbers, a bank account or IBAN, and a QR image — which its customers see so they can pay the shop directly, in their own wallet or banking app. A customer can then tell the shop they have paid: the amount, the method, an optional transaction reference and an optional screenshot. Only that shop sees the claim, and it stays with the shop's ledger. Screenshots are re-encoded to remove hidden metadata such as location, and are deleted when the claim is.

A shop's own business records

A shop can also keep product names, prices, barcodes and stock levels, its expenses, and what it owes its suppliers. These stay with the shop's account and are never shown to customers.

Information a shopkeeper records about their customers

This is worth stating plainly. A shopkeeper enters their customers' details — name, and optionally phone, WhatsApp, address, city and notes — along with what each customer owes. Much of that is entered by the shopkeeper, not by the customer. The shopkeeper is responsible for having a proper basis to record it; we process it on their behalf so their shop works. A customer who has been given a sign-in can see their own credit account in the app.

Orders, family members and joining a shop

Where a shop takes orders in the app, a customer's order holds the items, quantities, an optional note and, for a delivery, the address they give; only that shop sees it, and it stays with the shop's ledger once the shop accepts it. A customer account can list the family members who buy on it — a name, and optionally a relation and phone number — so each entry can say who took it. Someone who scans a shop's sign-up QR code at its counter gives that shop their name and phone number; the shop then adds them as a customer or declines, and a declined or unanswered request is deleted after a few weeks.

Delivery

For a delivery order the shop and its rider see the customer's name, phone number, delivery address and landmark, and — only if the customer chose to add one — a map pin for the address. A customer can save addresses for later; they stay private to them until used on an order. The rider marks an order delivered with a short code from the customer's app, or a photo at the door when the code cannot be shown; that photo is re-encoded to remove hidden details and is seen only by the shop and the customer. Cash collected at the door is recorded as a payment on the customer's credit account.

My lending (personal records)

A customer can keep a private book of money they lent to or borrowed from other people: each person's name, an optional phone number and note, and the amounts and dates. Only the account holder can see it — no shop, and no one named in it, ever does — and it is deleted with their account.

Offers and notices

A shop can send short offers and notices to its own customers, which appear in their app and may arrive as a notification. A customer can report a notice they find abusive.

Device and technical information

• A push notification token for each device you sign in on, so alerts can reach you.
• Your IP address and browser or app user-agent string, recorded with sign-ins and other significant actions for security and abuse investigation.
• If a shop owner turns on two-step sign-in, a one-time code is emailed to them at each sign-in. Only a scrambled copy of the code is stored, and it expires after 10 minutes.

We do not track your location. The only location the apps read is a one-time position when a customer taps “Use my current location” to pin a delivery address; it is stored with that address and on the orders it is used for, nothing more. We do not collect your calendar or any advertising identifier, and the app never records audio. Your phone's contacts are read only if a shopkeeper chooses to import customers from them (see Contacts below). Photos reach us only when you choose to upload one: your profile photo, a shop logo or banner, a payment QR code, a payment screenshot, a photo of a bill attached to an entry, or a rider's photo at a delivery. There are no advertising SDKs anywhere, and the Android app carries no analytics SDK at all. Our web pages count visits with a cookieless beacon, described under Website analytics below. Our website, the counter app and the customer app may also record how they are used, with Microsoft Clarity, described under Session recordings. We do not sell your information, and we do not use it to build advertising profiles.

Camera

The app asks for camera access for four purposes: scanning a QR code to sign a customer in, taking your profile photo if you choose to, and — for shops — scanning a product's barcode at the counter, and photographing a paper bill to attach to an entry. When scanning, frames are read on your device to decode the code; no image is stored and none is uploaded. A bill photo is uploaded only when the shopkeeper chooses to attach one: before it is stored it is re-encoded, which removes any location or device details the camera wrote into it, and it is shown to the shop and to the customer whose entry it belongs to. You can decline camera access, and type the code, search for the product or pick a photo from your gallery instead.

Bluetooth receipt printers

In the Android app a shop can print receipts on a small Bluetooth printer. The app asks for the nearby-devices permission only when the shopkeeper chooses a printer, uses it only to list paired printers and send the receipt to the chosen one, and does not use Bluetooth to find or track anyone. Declining it only means receipts are shared or printed another way.

Contacts

In the Android app a shopkeeper can add customers from their phone's contacts. The app asks for contacts permission only when they choose to do this, and explains why first. The contact list is read on the phone so the shopkeeper can pick people; only the name and phone number of the people they pick are uploaded, as new customers of their shop. Nothing else from the address book is read, and nothing is uploaded for anyone they do not pick. Declining the permission only means customers are added by hand instead.

Imports and backups

A shopkeeper can import customers from a spreadsheet file (CSV or Excel). The file is read once to show the columns and is not kept; only the rows the shopkeeper imports are stored, as customers. A shop owner can download a backup of their business — their customers' names, phone numbers and balances, their entries, products, suppliers and expenses — and may choose to have it emailed to their own address every week. That file is theirs to keep safe; restoring it only adds back what is missing from their own business.

Voice entry

At the counter a shopkeeper can say an item instead of typing it. The app hands this to the speech-recognition service of your phone or browser (Google's on most Android phones and in Chrome, Apple's in Safari, Microsoft's in Edge), which turns the speech into text under its own terms; Credit Khata itself never receives, records or stores audio. The operator can switch voice entry off. The resulting text may be sent to the AI provider described below to split it into item, quantity and amount; when the assistant is off, the phone splits it by itself.

Text messages

If the operator has set up an SMS service and has approved a shop to use it, that shop's customers may receive text reminders about what they owe and a text when a new entry is added. The SMS provider receives the customer's phone number and the message. A customer can turn texts off in the app, and a shopkeeper can turn them off for any customer. Reminders a shopkeeper sends by WhatsApp or SMS from their own phone go through their own apps, not through us.

Website analytics

Our web pages — the site at ck.abdohoo.app, the counter app and the customer app — count visits using Cloudflare Web Analytics. It is measurement, not tracking: it sets no cookies, stores nothing on your device, uses no fingerprinting, and cannot follow you to anyone else's website. What reaches Cloudflare is the address of the page you are on, the address you arrived from, your browser and device type, your country, and how long the page took to load. Cloudflare states that it does not use your IP address, your user-agent string or anything else to fingerprint or identify you as an individual; these signals are counted, not attached to a person.

Two limits are built in. Pages whose address carries a one-time link — a password reset, an account-deletion confirmation — are never measured, because the beacon would report that address. And the Android app is not measured at all: the beacon is browser code and the app has no place to run it.

Analytics can be switched off for the whole platform, or for any one of those surfaces, from the site owner's settings; when it is off, nothing is loaded and no request is made to Cloudflare. If your browser sends a “Do Not Track” or Global Privacy Control signal and the operator has chosen to honour it, you are not counted either.

Session recordings

To find screens that confuse people, our website, the counter app and the customer app use Microsoft Clarity. It records how they are used — taps, scrolling, which screens are opened and in what order — together with your browser and device type, your country and the page addresses, and plays them back to the operator as anonymous session replays and heatmaps. Clarity sets first-party cookies so that the screens of one visit are grouped together.

Text on screen is masked before anything leaves your device: names, phone numbers, amounts and balances appear in a replay only as blank shapes. What you type is masked as well.

Nothing is recorded on the sign-in pages, the backoffice, the Android app or any link that carries a one-time code. The operator can switch recordings off for each of these places, or entirely, from the site owner's settings; when it is off, nothing is loaded and no request is made to Microsoft.If your browser sends a “Do Not Track” or Global Privacy Control signal, you are never recorded. Microsoft processes this data under the Microsoft Privacy Statement.

Who we share it with

We share only what a specific function requires:

Service	What reaches them	Why
Google Firebase Cloud Messaging	A device push token and the alert text	To deliver notifications about your credit account
Cloudflare Web Analytics	The address of the page you are viewing, the page you came from, your browser and device type, and your country	To count visits to our web pages, without cookies
Microsoft Clarity	How our website, the counter app and the customer app are used (taps, scrolling, screens opened), with on-screen text and typing masked, plus browser and device type, country and page addresses	To find and fix confusing screens
Cloudflare Turnstile	Signals from your browser or device during a sign-in challenge	To tell people from automated abuse
An AI provider, where the shop has the writing assistant enabled	The item text being typed or spoken, plus the shop's country, city and business type	To suggest an item description, and to read a spoken entry
The same AI provider, only when a shop owner or manager asks a question about their books	The question, and a summary of that shop's own books: customer names and balances, recent entries, daily totals, best-selling items, expenses and day closes	To answer the question (“Ask your books”)
Google Play, when a shop owner subscribes to Pro in the Android app	Google handles the payment itself; we receive the subscription's plan, status, renewal date and order number from Google — never card or bank details	To switch Pro on and keep it in step with renewals, cancellations and refunds
An SMS provider, only where the operator has set one up and approved the shop	The customer's phone number and the text of the message	To deliver reminders and balance updates by text

The writing assistant is off unless it has been configured. Typing and voice suggestions send no customer name or ledger balance. Asking a question about the books does send that shop's own customer names and balances, and only when someone at the shop asks one; nothing from any other shop is ever included. We also disclose information where the law requires it.

How it is protected

All traffic between the apps and our servers uses HTTPS. Passwords are hashed. Sign-in tokens are stored per device and can be revoked individually. The app does not include its local data in Android backups or in a phone-to-phone transfer, so a copy of your ledger does not travel to a new device without a fresh sign-in.

How long we keep it

• Account and ledger information is kept for as long as the account is open.
• Security records — the IP address and user-agent attached to significant actions — are kept for 24 months and then deleted automatically.
• Records of text messages sent are kept for 90 days.
• An entry the shop voids stays on the record, marked as voided, with the account; a bill photo is deleted with its entry, its customer or the shop's account.
• When an account is deleted, see the next section.

Deleting your account

You can delete your account from inside the app, or without the app at https://creditkhataapp.com/legal/delete-account. What happens depends on which kind of account it is.

Your rights

You can ask us to give you a copy of your information, correct it, or delete it. Shopkeepers can edit most of their own and their customers' details directly in the app, and export everything their account holds as one file. For anything else, write to support@abdohoo.app and we will respond within 30 days. Depending on where you live you may also have the right to complain to a data protection authority.

Children

The app is for people running or trading with a business and is not directed at children. We do not knowingly create accounts for under-18s. If you believe a child has an account, write to us and we will remove it.

Where your information is held

Our servers and the services listed above may process your information in countries other than your own, including where Google and Cloudflare operate, and where the AI and SMS providers chosen by the operator operate. We use these services under their standard terms for the purposes described here.

Changes

If this policy changes materially we will update the date at the top and, where the change affects how your information is used, tell you in the app.

Contact

Abdohoo
Email: support@abdohoo.app