Privacy Policy
What Sentinel stores, why, and who else sees it.
Last updated: November 2026
1. Who this policy covers
Sentinel is billing and network-management software for internet service providers (ISPs). It is run by the operator of this Sentinel service. Two groups of people have data in it: the ISPs that use it, and the ISPs' own customers (subscribers).
For a subscriber's data, the ISP decides what is collected and why; Sentinel stores and processes it on the ISP's behalf. If you are a subscriber, your ISP is the first place to ask about your data.
2. What is stored
ISP account: company name, staff names, email addresses and phone numbers, country, currency, timezone, and each person's password (stored only as a one-way hash).
Subscribers: name, phone number, email, address and city, national ID if the ISP enters one, notes, customer number, plan and subscription details, PPPoE username, wallet balance, invoices and payments (amount, date, gateway and reference), usage sessions (start and stop time, IP address, data volume), support tickets and their messages.
Records of activity: a log of messages sent (recipient and text) and an audit log of staff actions (who did what, when, from which IP address and browser). Request bodies are not written to the audit log.
3. How it is used
To run billing, control the network (create, suspend and reconnect customer logins on the ISP's routers), take and confirm payments, send reminders and receipts, answer support requests, and keep the service secure.
We do not sell personal data and we do not use it for advertising. The apps contain no analytics or advertising trackers.
4. Who else receives data
Only the services the ISP chooses to connect:
Payment gateways (such as M-Pesa, Pesapal, Flutterwave, ClickPesa, Paystack): when a customer pays online, the payer's name, email, phone number and the amount go to the gateway the ISP enabled. Message providers (SMS, WhatsApp, email): the recipient and the text of each message go to the provider the ISP configured. Routers: usernames and passwords are sent to the ISP's own MikroTik routers to create customer logins.
Each of those providers has its own privacy policy and handles the data under its own terms.
5. How it is protected
Customer and staff passwords are stored hashed. Router and payment-gateway credentials are encrypted before they are saved. Each ISP's data is kept separate from every other ISP's. Staff roles limit who can change settings, money records and routers, and sensitive staff actions are recorded in the audit log. Sign-in attempts are rate-limited.
Whether connections are encrypted (HTTPS), where the servers are, and how often backups are taken depend on how this Sentinel service is deployed by the operator of this Sentinel service. No security certification is claimed by this policy.
6. Keeping and deleting data
Data is kept while the ISP's account is active. A customer who leaves can be marked as terminated; ask the ISP, or use the contact details your provider gave you, if you want information corrected, exported or deleted. Deleting records may be limited where invoices and payments must be kept for accounting or legal reasons.
7. Your rights
Depending on your country's data-protection law you may have the right to see, correct or delete your personal data, to receive a copy of it, and to object to how it is used. Subscribers should ask their ISP first; to reach the operator of this Sentinel service, use the contact details your provider gave you.
8. Cookies
See the Cookie Policy for the small number of cookies the apps set. There are no tracking or advertising cookies.
9. Changes to this policy
If this policy changes, the date at the top is updated. Material changes should be communicated to ISPs by the operator of this Sentinel service.