Public privacy policy
QuotaLK Privacy Policy
Effective date: September 13, 2026
QuotaLK uses provider-specific access only for providers the user connects. Usage snapshots, preferences, refresh state, and alerts are stored locally; provider credentials are not sent to a QuotaLK-controlled backend.
Provider access
QuotaLK retrieves supported usage information directly from first-party Dialog, SLT-Mobitel, and Starlink services using the browser's existing authenticated provider sessions. Provider host access is requested separately so users can grant only the providers they want to use.
QuotaLK does not ask the user to enter provider passwords into a QuotaLK server and does not relay provider credentials through a QuotaLK-controlled backend.
Data stored locally
QuotaLK normalizes supported provider responses into local cached snapshots so usage can appear immediately and survive temporary provider failures. It also stores product settings and refresh state locally.
- Usage and allowance snapshots needed for the popup.
- Connection display identifiers and provider metadata needed to distinguish configured connections.
- Enabled or disabled providers and selected connection state.
- Background polling preference, refresh status, and retry timing.
- Alert settings and dismissed-alert identifiers.
Background refresh and alerts
Background refresh is controlled by the user's polling setting and uses chrome.alarms. Failed requests retain the last complete cached snapshot, use retry backoff, and pause automatic requests after authentication or permission failures until the user reconnects or refreshes.
Quota alerts are computed from locally stored usage snapshots. Dismissing an alert changes local extension state; it does not modify the ISP account or delete the usage snapshot.
Third-party providers
Dialog, SLT-Mobitel, and Starlink are third-party services and process authenticated requests under their own terms and privacy policies. QuotaLK is an independent tool and is not an official application of those providers.
Data deletion
Removing QuotaLK or clearing its extension storage removes locally cached snapshots and preferences. Revoking a provider's optional site access prevents QuotaLK from making further requests to that provider until permission is granted again.
SLT-Mobitel session handling
When an SLT-Mobitel connection is enabled, QuotaLK can bootstrap from an already signed-in MySLT page. It reads the MySLT username, refresh token, access token, and selected account needed to make the supported first-party usage requests.
The SLT refresh token, username, selected account, and capture time are stored in chrome.storage.local so the connection can refresh without keeping MySLT open. The shorter-lived access token is stored in chrome.storage.session. These credentials are used only for SLT-Mobitel requests and are not sent to a QuotaLK-controlled backend.
QuotaLK clears the stored SLT credentials when refresh authentication is rejected. Removing the extension or clearing its extension storage also removes the locally stored credentials.
Permissions used
The following permission descriptions reflect the current extension manifest and product behavior.
storageStores normalized usage snapshots, preferences, provider settings, refresh status, alert dismissals, and selected connection state locally.
alarmsRuns user-selected background refresh intervals and restores polling after browser or service-worker restarts.
scriptingSupports QuotaLK provider-specific browser-context integration where required. OrbitMeter does not request this permission.
Dialog host accessoptionalRequested for Dialog connections so QuotaLK can use the user's existing signed-in Dialog session to retrieve first-party usage data.
SLT-Mobitel host accessoptionalRequested for SLT-Mobitel connections so QuotaLK can retrieve supported usage information from the provider's first-party services.
Starlink host accessoptionalRequested for Starlink connections so QuotaLK can retrieve supported account and usage information from starlink.com using the user's existing session.
Changes to this policy
If the extension's data practices materially change, this policy will be updated before or alongside the release that introduces those changes.
Contact
Questions about this privacy policy can be sent to anukamithara@gmail.com.
Developer: Anuka Mithara