This Application collects some Personal Data from its Users.
This document can be printed for reference by using the print command in the settings of any browser.
We are storing following information of users that are being tracked by stima.app and splitbee (Website Analytics)
🔒 Data stored
| Application |
Name |
Description |
| stima.app |
✉️ Email |
If user provides and is willing to subscribe for a monthly high level stats |
| stima.app |
# Meter/Account Number |
If user provides and is willing for a subscribe for a monthly high level stats |
| splitbee.io |
⏱ Usage Duration |
Time spent on a page |
| splitbee.io |
🔑 Unique ID |
Random generated ID. Is not tracked across domains |
| splitbee.io |
🏳️ Country |
Country of the user |
| splitbee.io |
📄 Page Views |
We automatically track all page views a user did |
| splitbee.io |
🔗 Referrer |
We store the referring page if it is available |
| splitbee.io |
🖥 User Agent |
We parse the User Agent to get infos about the browser & operating system |
For more on Splitbee’s privacy policy check out here
Owner and Data Controller
David Amunga
Nairobi,Kenya
Owner Contact Email : [email protected]
For compliance according to the Data Protection act. stima.app operates under the following framework as provided in the Policy Brief here:
- Fairness and lawfulness. Personal data should be processed for a lawful purpose, and those
whose data is being collected should be notified as to why their data is being collected. Further, how it will be stored and used.
- stima.app only processes name + meter number from the application. Respective Payments/Unit data are only fetched directly from the KPLC API to the User. Optional Subscription collects Email + Meter Number to later on share monthly statistics based on the 2 data which are not cached.
- Stated purpose. Those who collect data should use it for the stated purpose and data should not be further processed in a manner incompatible with the purpose for which it was collected.
- stima.app processes bill transactional data to only derive high level statistics over what was returned from the KPLC API. No processing happens beyond that.
- Adequacy. Those who collect data should only collect what is adequate and the minimum needed for the stated purpose
- stima.app scrapes off unnecessary / sensitive data particularly the name,servicepointno and relies entirely on the transactional specified in the KPLC API
- Accuracy. Personal data should be accurate. Data subjects have a right to have their data updated, corrected and erased.
- stima.app provides precise results as returned from the KPLC API as specified in the payments tab. Any inconsistency specified can be directly communicated to the support email.
- Retention. Personal data should not be kept for longer than necessary
- All data stima.app processed from the KPLC API is not retained in any data store.