How Ledgah handles your data

Last updated 8 October 2026

Who we are

Ledgah is run by [K: your full name or registered business name] in Lagos, Nigeria. For anything about your data, email [K: privacy email].

What Ledgah holds

Your login: the email address your business signs in with, and its password, which Supabase's sign-in service manages.

What your team types in:

• branches, menu items and prices, POS terminal and delivery-app names and reference numbers, and when each one pays out;
• each day's kitchen-book figures and channel totals, adjustments and their notes, the name of the person who closed, and manager notes;
• follow-ups: who is following up, the explanation, the evidence reference and the outcome;
• payout amounts, invoice figures, bank statement references, recovery-log entries, reasons given for voiding a close, and any platform advance balances you choose to track;
• settings such as your business-day cutoff and alert limit;
• when each close was saved, and which login saved each follow-up.

Some of this is about your staff: the name of whoever closed, the person following up a difference, and anything your team writes about people in notes and explanations. Write what the records show, and don't name anyone as responsible until the evidence has been checked.

Ledgah doesn't ask for your customers' details. Please keep customers' names, phone numbers and card details, and full bank account numbers, out of notes and reference fields — a short label or the last 4 digits is enough.

Where it's kept

• Online, in a database run for us by Supabase, located in [K: Supabase region, from Project Settings].
• In the browser on each phone or computer where Ledgah is used, so it keeps working without a connection. Signing out locks this copy but doesn't erase it.
• In anything you take out of Ledgah — backup files, CSV files and summaries you send on WhatsApp. Those are in your hands; keep backup files somewhere private.

Clearing this site's data in a browser's settings removes the copy in that browser — and it removes every business's copy on that device, including entries not yet uploaded. Before clearing a device, sign in to each business that has used it, wait for Cloud ✓, and download that business's backup.

While a device is set to "Work offline on this device", its records stay on that device and aren't sent to our database. If someone later signs in or creates an account on that device, those records upload to that business's account.

Who can see it

• Your team: anyone who signs in with your business's login, and anyone using a phone or computer where that login is still signed in. Each business has one shared login today, so everyone you give it to sees all its records. When someone leaves, change the password and sign out any device they kept: a password change may not sign out devices that are already signed in, and it doesn't remove the copy already in their browser.
• Other businesses: other Ledgah businesses can't see your records in the app — the database returns a business's records only to its own login. [K: remove this note once the Supabase security check is done] If two businesses share one device, each one's entries not yet uploaded stay in that browser's storage.
• Ledgah's founder, who runs the database, can see every business's records through Supabase's admin dashboard. We open a business's records only when that business asks for help, or to fix a fault.

Services we use to run Ledgah:

• Supabase, for the database, sign-in and sign-in emails.
• Netlify, which serves the app and this website. Your records go from your browser straight to Supabase, not through Netlify. Like any website host, Netlify keeps basic visit logs, such as internet address and page requested.
• Google Fonts: the website and app load their typefaces from Google, so Google receives your device's internet address and browser details when a page opens — not your records.
• Paystack, which handles payments. Card and bank details you enter go to Paystack, not to us; we see the payment record, such as the amount, the date and the email used.

We don't sell your data. We don't share your records with lenders, delivery platforms, POS providers or banks unless you ask us to in writing.

Cookies and tracking

The website and app contain no analytics or advertising trackers. The app keeps your records and your sign-in in your browser's storage so it can work offline.

Free payout check

Statements you send for a free payout check reach us by WhatsApp or email. Cover account and registration numbers first — we only need amounts and dates. We use them only for the check, and delete them within [K: number of days].

We may use Claude, an AI assistant made by Anthropic, to help read your statement and check the figures. We check every result ourselves before sending it to you.

How long we keep your records

Ledgah doesn't delete your records on a timer or because a payment is missed. If your trial ends without payment, or you stop paying, your records stay, and you can still sign in to view them and download your backup and CSV files. We delete a business's records only when its owner asks.

Getting a copy or deleting your data

Download a full backup and CSV files any time from History → Data safety in the app. CSV files cover one branch at a time; the backup covers every branch.

To delete your business's login and records, email [K: privacy email] from the login's email address. We'll remove them from the live database within [K: number of days]. Database backups made before then are deleted when they expire, after [K: period — from your Supabase plan]. Copies on your own devices, and backup files you downloaded, stay with you. Deleting can't be undone, so download a backup first.

Changes

If we change this page, we'll update the date at the top and tell paying customers by WhatsApp or email.