Privacy Policy

ACCESS — Screen Time Locks · Last updated September 25, 2026

ACCESS provides screen-time controls on the iPhone where it is installed. There is no ACCESS account, advertising, analytics service or ACCESS server. The app processes settings, selected-app information and protection events locally to provide its features. Apple separately provides Screen Time, the App Store and device backup services under its own policies.

What ACCESS can and cannot see

ACCESS uses Apple's FamilyControls, ManagedSettings and DeviceActivity frameworks to count use of selected apps and apply restrictions. App selection is represented by Apple's opaque tokens. Apple's Screen Time report extension processes selected-app usage and display information locally to present names, icons and usage totals in Stats. ACCESS also keeps local counters and events needed to apply and explain its rules. It does not read the contents of messages or other activity inside the selected apps, or upload selected-app information or usage to the developer.

What stays on your device

ACCESS stores selected-app tokens, use allowances, Lock durations, Quiet-hours schedules, Daily limit settings, current restriction state, subscription-access state and local protection history. These records are stored in app storage and the App Group used by ACCESS and its extensions. Unfinished setup may retain non-secret choices so you can continue later; it does not save entered PINs, backup-code text or approval sessions in that setup record.

If you create an ACCESS passcode, the app stores a salted passcode verifier, backup-code verifier, a viewable copy of the generated backup code when available, and retry-throttling information in the iOS Keychain. It does not store the six-digit passcode itself in its credential record. These Keychain items use a device-only accessibility setting and are available to ACCESS when the iPhone is unlocked. They are not shared with family members or synchronized by ACCESS to another phone.

You can view or replace the backup code after passcode authentication. Choosing Copy uses the local clipboard with a two-minute expiration request; a copy you save or paste elsewhere is then governed by that destination. Keep it private. Changing the passcode or replacing the backup code invalidates the previous backup code. Older installations may have only a verifier, so an old code may remain usable without a viewable copy.

Retention, backups and removing the app

ACCESS does not keep a server copy of these records. Local app records and Keychain credentials have different storage lifecycles. Deleting or offloading the app is not a promised method for erasing every credential, saved backup or copy you made. Keychain items may remain after deleting the app, and this release does not include a separate credential-erasure control. Apple's backup and restoration behavior also applies: device-only Keychain items do not migrate to a different device, but may be restored to the same device. Do not assume reinstalling ACCESS will clear its passcode or recover a forgotten code.

The developer cannot recover a forgotten passcode from a server. The local recovery flow requires the saved backup code and creation of a new passcode; there is no email, Apple Account or remote passcode-reset service. Without the passcode or valid backup code, ACCESS cannot verify a protected change.

What we collect

ACCESS does not send the developer app-selection tokens, passcodes, backup codes, Screen Time usage, device identifiers, analytics or automatic diagnostic reports. Local Protection Health messages and the Activity log are not an automatic upload service. If you independently contact support by email, the developer receives the information you choose to include in that message; do not send passcodes, backup codes or unnecessary private device information.

Purchases

Apple processes Individual Pro and Pro Family subscriptions through the App Store. ACCESS uses StoreKit on the device to verify entitlement information and enable the purchased or shared features; the developer does not operate a receipt-validation server. App Store payment details are handled by Apple, not entered into ACCESS. Apple's handling of purchase and account data is described in Apple's Privacy Policy.

Children and parent use

ACCESS supports personal use and a parent configuring local settings on the phone being used. The parent can create an optional ACCESS passcode to protect settings and early-release actions on that phone. ACCESS does not provide remote monitoring, account linking or remote unlock, and does not transmit a child's selected apps or usage to a parent's device. Local setup does not require an Apple child account. The app uses individual Screen Time permission; its passcode cannot prevent deleting ACCESS or revoking that permission.

Data sharing

Pro Family shares the subscription entitlement through Apple Family Sharing, not ACCESS passcodes, selections, rules, usage or Screen Time authorization. Each member sets up ACCESS separately on their own device. ACCESS does not sell app usage or use Screen Time information for advertising. A backup code or other information you independently copy or send outside ACCESS is a separate choice, not subscription sharing.

Changes to this policy

If a future version of ACCESS ever changes what data is handled, this page will be updated before that version ships, and the change will be called out in the App Store release notes.

Contact

Questions about privacy? Email shaikhjamir@gmail.com.