← Back to LedgerLite

Privacy Policy

Last updated: 21 October 2026

1. Who I am

LedgerLite is a personal portfolio project created and run by Booker Ochieng Okumu ("I", "me"), a software developer based in Nairobi, Kenya. I am the person responsible for the personal information described in this policy. You can reach me at [email protected].

2. What LedgerLite is

LedgerLite is a demonstration of a double-entry accounting ledger: accounts, journal entries, reversals and a trial balance. It is not a financial service, it holds no real money, and the data in it is fictional.

Please do not enter real personal or financial information into LedgerLite. Signed-in visitors can only view the demo data. Only the project owner can add entries.

3. Information I handle

InformationWhyWhere it lives
Your account identifier from Google or GitHub (an opaque ID, not your email) To recognise you while you are signed in In your sign-in cookie, in your browser
Your public display name (your name on Google, or your username on GitHub) To show who is signed in In your sign-in cookie, in your browser
Your role in LedgerLite (Owner or Visitor) To decide whether you can add entries or only view In your sign-in cookie, in your browser
Technical data: IP address, browser type, pages requested, time of request Security, protection against abuse, and troubleshooting Briefly in the application's memory for rate limiting, and in standard web server and Cloudflare logs

What I do not collect. When you sign in with Google I ask only for the basic openid and profile permissions. I do not request your email address, contacts, files, calendar, location or any other data from Google or GitHub, and I do not keep your profile picture or any other profile details. LedgerLite has no user database: your identifier and name are not stored in the LedgerLite database.

4. How I use it

I do not sell your information, use it for advertising, or build profiles about you.

5. Sign-in with Google and GitHub

When you choose to sign in, you leave LedgerLite and authenticate on Google's or GitHub's own site, under their privacy policies: Google, GitHub. They tell LedgerLite who you are; LedgerLite never sees your password.

6. Cookies

LedgerLite uses only cookies that are necessary for it to work. It has no analytics or advertising cookies.

7. Who I share information with

I share information only with the services needed to run LedgerLite:

These providers may process data in countries other than Kenya.

8. How long I keep it

9. Your choices

10. Security

The site is served over HTTPS, the sign-in cookie is protected from scripts, requests are rate limited, and visitors cannot change any data. No system is perfectly secure, but I take reasonable steps to protect what little information is involved.

11. Children

LedgerLite is not directed at children under 13, and I do not knowingly collect information from them.

12. Changes to this policy

If I change how LedgerLite handles information, I will update this page and the "Last updated" date above.

13. Contact

Booker Ochieng Okumu · [email protected] · bkokumu.com · Source code on GitHub