Last updated: 16 August 2026 JustLimit monitors aggregate mobile-data usage and can locally block cellular traffic at a safety target chosen by the user.
JustLimit stores the configured allowance, reset day, safety-reserve choice, monitoring status, aggregate cellular byte totals, notification milestones, and up to 62 days of hourly usage totals. The interface language is not among them: JustLimit follows the language iOS gives it and keeps no preference of its own. This information stays in the app's local shared container and is excluded from backup.
JustLimit does not collect or store browsing destinations, domain names, packet contents, app identities, account details, contacts, precise location, advertising identifiers, or payment data. It does not use analytics, advertising, tracking, or crash-reporting services. JustLimit does not sell, use for secondary purposes, or disclose user or usage data to third parties.
JustLimit uses Apple's Packet Tunnel Provider capability to apply routes locally. Traffic is not sent to a JustLimit server or another VPN server. In blocking mode, matching traffic is dropped on the device.
If enabled, JustLimit schedules local notifications at 80%, 95%, and the blocked state. Notification permission is optional and can be changed in iOS Settings.
Hourly totals are retained for no more than 62 days. Users can clear history or reset the current counter in the app. Removing the app removes its local app data, subject to iOS behavior for shared containers and installed VPN configurations.
Canonical state and local history use iOS file protection after the first device unlock. Cellular counters and route changes can be delayed by iOS, so JustLimit cannot guarantee prevention of all outside-bundle usage or charges. Users should also verify usage with their mobile provider.