Akasente

What this app collects

Every kind of data the app touches, and where it ends up.

Last updated 4 October 2026 · Version 1.7

Read this next to the store listing

Google Play's Data safety section and Apple's privacy labels are summaries. This page is the long form of the same answers, so you can check one against the other.

Collected and kept on the device

Business and owner details
Business name and type, district, address, owner's name, phone, email and National ID. Entered at registration, used to identify the business on receipts and reports.
Staff details
Name, phone, email, role, branch and working area for each officer and cashier the owner hires. Used to assign work and attribute money.
Customer details
Name, phone, gender, date of birth, National ID, address down to village, occupation, business and stated income. Used to identify the borrower and assess a loan.
Guarantor and next of kin
Name, phone, relationship, and for a guarantor also address, National ID, photograph and a photograph of their signature. Used to secure the loan.
Photographs and documents
Customer photos, identification documents, signed agreements, receipts and proof of cash handovers. A customer's file can also hold documents chosen from the phone, a PDF or Word file such as a bank statement or a utility bill, which are copied into the app and kept with the rest of their record. Opening one of those hands it to whichever app on the phone reads that kind of file. Stored as files in the app's private area on the device.
Financial records
Loans, repayment schedules, payments, penalties, office charges, savings, expenses, cash handovers and the daily cash position. This is the ledger.
Work records
Field visit notes, reminders sent, and who recorded each entry with the time they recorded it.
Working hours and after-hours access
The days and times the business works, set by the owner. If a field officer is let into the app outside those hours, a record of it: who, when, who let them in, for how long, and the reason if one was given.
Sign-in details
The password for each account on this device, and which account is currently signed in. If you signed in with Google or Apple, the email address and account identifier they gave us, never your password to them.
Where this list goes

Every row here is written to the phone's own storage first, and the app reads it back from there. If your business uses sync, every row here is also copied to your business's database on Google Cloud. Sign-in passwords are the exception to the shape of that: they are not on the phone at all, only on the server, and only as a scrambled form that cannot be turned back into the password.

What is shared, and with whom

No advertiser, no data broker, ever
The app has no advertising, no analytics and no tracking software, and nobody buys, rents or receives your borrowers' details from us.
Google or Apple, if you sign in with them
Signing in tells them you used this app, the same as signing in to any other app with those accounts. They receive nothing about your clients, your loans or your money. This is optional, a password works instead.
Google (Firebase), if sync is on
Your business's records and photographs are stored on Google Cloud in the European Union, as our processor and on our instructions. This is the one place a copy of your book exists outside your own phones. See "If your business uses sync" in the Privacy Policy.
Apps you choose
When you share a receipt, print a report or send a reminder, the content goes to the app you picked, WhatsApp, your messaging app, your dialer, your email, a Bluetooth printer. That is a share you make deliberately, each time.
Expo (update service)
The app checks for a newer version. That request carries the platform, app version and the device's IP address, and none of your records.
Expo, Google and Apple (notifications), if sync is on
When a colleague records something you need to know about, a short message is sent to your phone through Expo's notification service and then through Google's or Apple's, whichever your phone uses. Those messages carry the words you see on the notification, which can include a client's name and an amount, so a repayment or a cash handover passes through those services on its way to you. Nothing else about the client goes with it, no photograph, no National ID, no address, and the reminders your own phone raises for you go nowhere at all. Turn notifications off for this app and none of it is sent.
Google / Apple
The store you installed from may collect crash and performance data under its own policy. We do not receive your records from it.

Permissions, and what happens if you say no

Camera
Asked the first time you take a photo. Refuse it and every screen still works — the photo slots stay empty.
Notifications
Asked once, after you first sign in. It lets the phone remind you each morning who you are collecting from, tell a cashier to open and close the day, and pass on what a colleague has just recorded. Refuse it and nothing stops working, every one of those is also a line on the Notifications screen in the app. You can change your mind later in your phone's settings.
Nearby devices (Bluetooth)
Asked the first time you print a receipt. It lets the app send the receipt straight to the printer you paired with this phone, as text, over a connection it opens and closes for that one receipt. It does not search for devices and cannot see what else is nearby. Refuse it and printing falls back to the phone's own print dialog.

The app asks for nothing else, and what it cannot ask for is worth naming. It holds no permission to read the photographs on your phone and none to read or write the phone's shared storage: both are stripped out of the build. Attaching a picture you already have still works, because it never needed them — tapping Gallery opens the phone's own photo picker, which runs outside this app; you choose one file, and that file is all the app receives. Nothing else in your gallery is visible to it. There is likewise no location permission, no contacts permission, no call-log or SMS permission, and the microphone permission is blocked so that no library can quietly add it.

Encryption

Records sit in the app's private storage area, which the operating system keeps other apps out of, and are covered by the phone's own disk encryption when the device has a screen lock set. On top of that, the app encrypts everything it stores, customers, loans, payments, staff and sign-in details, with AES-256 before it is written down. The key is generated on the phone and held in the platform keystore (Android Keystore, iOS Keychain); it never leaves the device and is not in the records themselves. A copy of the app's data taken off the phone, a backup, a file pulled over a cable, is unreadable without it. Since nothing is transmitted, there is nothing in transit to encrypt.

So set a screen lock

Encryption protects the records at rest, not a phone left unlocked in somebody else's hands: the app itself can always read its own data, so whatever the app can show, whoever is holding it can see. On a phone with no PIN or pattern, a signed-in app is the whole of your loan book, open. Signing in is checked properly, on the server, but it is only checked when somebody signs in.

In a web browser

The app can also be opened in a web browser, and there the same records are kept in that browser's own storage for this site, encrypted the same way. A browser has no keystore, though, so the key is kept in the browser's storage too, beside the records it protects: anybody who can use that browser profile can read them. Use the web version only on a computer you control, and sign out when you have finished on one that other people use. Signing out keeps the records in that browser, so that work not yet sent to the office is not lost; to remove them, clear this site's data in the browser's settings once everything has been sent.