_Last updated: July 9, 2026_
RepLedger is built local-first. The short version: your data never leaves your
computer, and we couldn't read it if we wanted to.
Lines (brands and their commission terms), accounts (your retail customers),
orders, commission payments, and your settings. All of it is stored in
chrome.storage.local inside your browser profile on your computer.
Nothing. There is no server, no account, no sign-in, no analytics, no
telemetry, and no tracking of any kind. RepLedger never asks for, stores, or
transmits brand-portal logins.
The single exception is payments: if you buy Pro, checkout is handled by
ExtensionPay and Stripe on extensionpay.com. We
never see your card details. The extension stores only a cached paid/unpaid
flag locally. ExtensionPay's privacy policy:
https://extensionpay.com/privacy
RepLedger bundles ExtensionPay, which handles the
optional paid upgrade. So a purchase is recognised on this device, RepLedger asks
ExtensionPay for your licence status automatically when your browser starts, and
again when you open the extension's own pages — this happens whether or not you
have ever paid. That request carries a random per-installation identifier and
nothing else: no page content, no URLs, no file names, and nothing you have
created in the extension. If you buy Pro, ExtensionPay and Stripe handle the
payment on their own page and your email is held in your ExtensionPay account;
we never see or store your card details. Everything you make with RepLedger stays
on your computer.
(if you opted in) fires an alert.
Settings.
RepLedger requests no host permissions and runs no content scripts on any
site, with one exception: the ExtensionPay checkout bridge runs only on
extensionpay.com so a purchase can be confirmed back to the extension.
Export a full JSON backup or delete everything at any time from Settings.
Uninstalling the extension removes all stored data.
breezyapps.support@gmail.com · https://breezylifeapps.com/repledger/