Privacy Policy

This Privacy Policy explains what Ahmad Salahaddin Saidq, operating as LedgerOne ("we", "us"), collects when you sign up for and use the hosted LedgerOne service, and what we do with it. It is part of our Terms of Service.

LedgerOne stores two different kinds of personal data, and we are not in the same position with respect to both — this matters enough to say up front:

• Your account data (Section 2) — your own name, email, phone and billing details, as the business that signed up. Here, we are the data controller: we decide why this is collected and are responsible for it under this policy.
• Your workspace's data (Section 3) — the customers, sales and records your shop enters into LedgerOne. Here, you are the data controller and we are your data processor: we store and protect it, but you decide what is collected and are responsible for having the right to collect it. If one of your own customers wants to know how their data is used, that is your policy to give them, not this one.

1. Who this applies to

This policy covers the hosted, multi-tenant version of LedgerOne at leadgerone.site and its subdomains. It does not cover a copy of LedgerOne self-hosted on someone else's own server — that installation is under that operator's own policy, not ours.

2. Data we collect about you, the account holder

2.1 What you give us directly

• Sign-up details: business name, the subdomain and sign-in username you choose, your email address, phone number, and password (stored hashed — we cannot read it back).
• Communications: anything you send us by email or otherwise when you contact us for support.
• Operator account profile: if you or your staff use the Telegram bot integration or link an account to it, the Telegram user ID and chat needed to deliver messages.

2.2 Collected automatically

• Device signal at sign-up: a hash built from your browser and device characteristics (screen size, timezone, language, and similar), used only to slow down repeated free-trial sign-ups from the same device. It is not a cookie, is not used for tracking, and is not shared with anyone.
• Basic activity timestamps: when your workspace was last active, used to power the operator dashboard and to know when a trial or subscription needs attention.
• Standard web server logs (IP address, browser type, request timestamps) kept briefly for security and troubleshooting.

2.3 Payment information

Subscription payments are handled by Wayl, a third-party payment processor. When you pay, Wayl processes your payment details directly — we do not receive or store your card or payment account number. We receive confirmation that a payment was made, its amount, and a reference we use to match it to your invoice.

3. Data inside your workspace

Once you are signed in, everything you or your staff enter — items and inventory, customer names, phone numbers and addresses, uploaded ID documents or contracts, supplier details, sales and purchase records, safe/cash ledger entries — is stored in a database created solely for your workspace, separate from every other customer's. As described above, you control what is collected here and why; we process it only to run the Service for you; store it securely; and do not access it except:

• when you ask us to (support requests, data recovery);
• when necessary to diagnose a fault affecting the Service;
• when the operator restores a backup you have provided into your own workspace, at your request;
• when required by law.

We do not read, sell, or use your workspace data to train anything, market to your customers, or for any purpose other than providing the Service to you.

4. Who else sees data, and why

Who	What they receive	Why
Wayl (payment processor)	Amount, currency, and a link back to your invoice — never your workspace data	To process your subscription payment
Telegram Bot API	Messages you or the system choose to send (e.g. daily reports, alerts) to an account you have linked	Optional notifications, only if you set this up
Our email delivery provider	Your email address and the content of transactional emails (sign-up verification codes, password resets, invoices)	To deliver account emails
Our hosting provider	Everything — the servers the Service and its databases run on	Infrastructure, under their own security terms

We do not sell personal data, and do not share it with anyone for their own marketing purposes. We may disclose data if required by a valid legal request, or to protect the rights, property, or safety of LedgerOne, our customers, or others.

5. Security

• Isolation: each workspace has its own database — there is no shared table that mixes one shop's records with another's.
• Encryption at rest for sensitive credentials: API keys and third-party secrets configured by the operator are encrypted (AES-256) before storage.
• Password hashing: account passwords are hashed, never stored or logged in plain text.
• Signed backups: automated and manual backups are cryptographically signed to the workspace they came from, so one workspace's backup cannot be silently restored into another's.
• Transport encryption: the Service is served over HTTPS.

No system is perfectly secure, and we cannot guarantee against every possible breach. If one occurs that affects your data, we will notify you without undue delay.

6. Cookies and local storage

We use a session cookie to keep you signed in, and local browser storage for interface preferences (such as your chosen language or a collapsed sidebar). We do not use third-party advertising or cross-site tracking cookies.

7. How long we keep data

• While your workspace is active or archived (cancelled but not deleted): your data is retained indefinitely, so you can pick up where you left off if you subscribe again. Cancelling a subscription does not delete anything.
• If you ask us to permanently delete your workspace, or if we terminate it under Section 6 of the Terms, we will drop its database and stored files. This is irreversible. We may retain minimal records (e.g. billing history, the fact an account existed) for as long as reasonably necessary for accounting, fraud-prevention, or legal purposes.
• Automated nightly backups are kept for a limited rolling window (currently 14 days by default) and are then deleted automatically, separately from the workspace itself.

8. Your rights

You can access, export (via the built-in backup/export tools), or request correction of your account data at any time. You can request permanent deletion of your workspace by contacting us — see Section 7 for what that does and does not remove. If you are located somewhere that gives you additional statutory rights over your personal data, those rights apply to the extent required by that law, in addition to what is offered here.

For data about your own customers stored in your workspace, requests from those customers should go to you, as the controller of that data (Section 3) — we will assist you in fulfilling a request if you ask.

9. Children

The Service is intended for business use by adults running or working at a shop. It is not directed at children, and we do not knowingly collect personal data from anyone under the age of majority as an account holder.

10. Changes to this policy

We may update this policy as the Service changes. For a material change we will make reasonable efforts to notify you before it takes effect, the same way as described in Section 10 of the Terms.

11. Contact

Questions about this policy, or a data request, can be sent to ahmadsadiqkhayat@gmail.com.