Your attention. Your controls.
Development preview, updated 20 October 2026. This is not yet a public subscription service.
What the portal stores
If you enable app sharing on a phone, its selectable app names and Android package identifiers are synced to your private account. You can turn sharing off to remove this list and stop remote app selections. App icons and page content are not uploaded. Blocked-attempt insights can be shared separately, as described below. Gift records store sender/recipient account IDs and trial dates; gift secrets are hashed. Up to five paired devices are allowed per ordinary preview account; gift trial accounts are limited to one and cannot send gifts. Offline paired devices count toward these limits. Disconnecting frees a slot. Your account identifier, device names and models, saved app and website blocklists, recurring schedules, emergency-use timestamps, session requests, device confirmations, and last connection times are stored to provide device management. Device credentials and pairing codes are stored as hashes on the server. General browsing history and page content are not uploaded by the Android app.
Optional Focus insights
History collection starts off. You can enable local history in the Android Insights section and separately consent to share it with your paired portal account. Records contain blocked app names and package identifiers, blocked website domains, attempt times and completed focus-session durations. Full URLs, searches, page content, background network packets and activity outside focus sessions are excluded. Unknown destinations are not recorded as website attempts. Repeated blocks of the same target within 30 seconds in a session are grouped. Counts describe detected blocks, not time saved or continuous enforcement. Local history keeps up to 5,000 records and removes expired records when the app next runs. Shared records expire after 90 days, with daily server cleanup. Turning off sharing removes the server copy on the next successful phone sync. You can delete history from the app or portal; deletion reaches offline phones when they reconnect. Future records can continue if collection or sharing stays enabled. Anyone signed into the same portal account can view its shared insights. Completed minutes are recorded when sessions finish; each device is counted separately.
Beta feedback
When you submit feedback, we store your account identifier, report type, message, optional device reference and submission time. Only your account can read its reports through the portal; the service owner can review stored feedback to improve the beta. No screenshot, device log or calendar detail is attached automatically. Reports are saved for review; replies and automatic notifications are not connected. Please avoid including passwords, pairing codes or other sensitive details.
How devices connect
Pairing is voluntary and uses a single-use code that expires after five minutes. A paired phone syncs its named blocklists and recurring schedules in both directions while the app or accessibility service runs. Offline edits are queued; changed revisions are reviewed as drafts rather than silently overwriting another edit. Server deletion markers prevent offline edits from restoring deleted items. Battery restrictions and network loss can delay delivery. The portal shows reported state and cannot guarantee continuous enforcement.
Optional phone calendar
The Android app requests calendar read access only when you choose Connect phone calendars. Meetings and classes can be viewed locally. If you separately enable Share busy times with my portal, only event start and end times for the next 14 days are uploaded to your account. Event titles, attendees, locations and descriptions stay on the phone. Turning sharing off removes the uploaded snapshot after the next successful sync. Adding a routine to a calendar opens your calendar app for confirmation; calendar edits do not change blocking schedules. The portal can export the next 90 days as an ICS file.
Internet focus
All-internet lists require Android VPN permission. A local packet sink discards IPv4 and IPv6 network traffic from other apps while the session is active; no traffic is forwarded to a VPN server or logged. Selected app exceptions, FocusAnchor and essential phone controls bypass it. From Android app version 0.13, non-exempt apps are also covered by a focus screen during all-internet sessions. Android supports one active VPN. Website exceptions require supported browsers to bypass the packet sink and then use accessibility address-bar checks; this is not network-level domain filtering. An exempt browser app allows all its websites. In-app browsers, hidden address bars and background traffic do not have a complete domain-filtering guarantee. Android can revoke VPN or accessibility permissions.
Device controls
Disconnect a device from the dashboard or Android app. Downloaded sessions keep their original local timer after disconnection. Synced routines pause when the phone learns it has been disconnected. Commitment mode disables ordinary early-stop controls. One emergency end is available every seven days across the paired account; paired phones require internet to authorize it. Unpaired phones keep a local allowance. Offline devices receive a portal emergency cancellation on their next sync; Android settings, permission revocation, and uninstall remain available.
Preview limitations
The landing page, Android download page and beta APK, and device connection endpoints are public for development testing. Customer dashboards and account APIs require verified customer sign-in through Supabase. Devices authenticate with their own credentials. QR invitations contain only the portal address and a short-lived pairing code; the scanner uses Google Play services. Billing, account self-deletion and push delivery are not available in this beta. Customer email/password login and recovery require the configured Supabase project and verified email delivery. The new portal does not automatically import accounts or devices from the earlier ChatGPT preview. Android 0.11 caches synced schedules and runs them locally with inexact alarms. Internet is needed to receive new changes and cancellations; offline devices can retain older schedules until their next sync.