Privacy

A shop’s records belong to that shop. SysLedge stores and processes them so the shop can use them; we do not treat a shop’s customer list as ours to use for anything else.

If you are a customer of a water shop and your details are in SysLedge, the shop put them there. Requests to see, correct or remove those details should go to the shop you buy from, because it decides what it keeps. We will help the shop act on such a request.

• Account details for signing in — name, email address or phone number, and role (owner or staff).
• Which parts of the system a staff account is permitted to use.
• The shop’s own details: business name, contact number, delivery areas, and subscription status.
• Basic technical records created by using the service, such as the times an account signs in.

Sign-in is handled by Firebase Authentication, a Google service. Passwords are managed there and are never visible to us.

This is business data the shop enters and controls. It typically includes:

• Customer name, phone number and delivery address or area.
• Whether they are a walking customer or on a monthly schedule, and their delivery pattern.
• Deliveries made, bottles delivered and empties returned.
• Payments received, the method used, and any outstanding balance.
• Bottles the shop has out with that customer, and any deposit held against them.
• Invoices generated for the customer.

A shop’s customer can be given a link to view their own account and place an order. That link asks for a PIN the shop sets, and it shows only that customer’s record.

We use it to run the service: to show a shop its own data, calculate balances and monthly bills, produce invoices, and keep accounts secure. We also use aggregate, non-identifying information about how the product is used to decide what to build and fix.

We do not sell shop or customer data, and we do not use it to advertise to anyone.

SysLedge runs on services we rely on to operate: Vercel hosts the application, Supabase hosts the PostgreSQL database, and Firebase provides authentication. These providers hold the data in the course of running the service and are not permitted to use it for their own purposes.

Inside SysLedge, access is limited to the people who operate the platform and is used for support, billing and keeping the service working — for example, restoring a shop’s account or investigating a fault it has reported.

We may disclose information where the law requires it. If we are asked to hand over a shop’s records, we will tell that shop unless we are prevented from doing so.

Accounts are protected by sign-in, and every request for shop data is checked against the account making it, so one shop cannot read another’s records. Connections to the site use HTTPS. Signing out, or an account being disabled, ends existing sessions.

No system is perfect. If we discover a breach that affects a shop’s data, we will tell that shop what happened and what we are doing about it.

A shop’s data is kept for as long as its account is active, because the business needs its own history — last year’s deliveries and payments are the ledger. If a shop closes its account and asks us to delete its data, we will do so; tell us and we will confirm when it is done.

If this page changes in a way that affects how information is handled, we will update the date at the top. For anything on this page, or to make a request about data we hold, write to sysledgee@gmail.com.