Features:
- 5-hour window + weekly status (simple gauges). Makes easy to plan your workload across providers
- reset countdown timers
- Home Screen + Lock Screen widgets
- configurable alerts (e.g. 75%, 90%)
- multi-provider tracking
Privacy / how it works:
- no accounts, no analytics, no servers; everything runs on-device
- API-key providers: paste an API key (stored in iOS Keychain)
- dashboard-only providers: sign in via an embedded web view OR paste an existing session token; the app reads the same usage info shown in the provider dashboard
- connectors may break if dashboards/endpoints change
Not a bypass — it only provides status + alerts so you can plan sessions.
I’d love feedback on:
- which thresholds are actually useful
- % remaining vs time remaining
- security/UX tradeoffs: embedded login vs session-token paste
afonsoduarte•1h ago
- No backend: no accounts, no analytics, no server-side storage. Data stays on the device.
- Not a bypass: it only shows usage status + alerts + reset timers.
- Storage: credentials/tokens/keys are stored in iOS Keychain.
- Integrations:
- No MITM, no proxying traffic through any servers (it's local!). If a provider changes their dashboard/endpoints, that connector can break until updated.