The details

Privacy Policy

Last updated: September 22, 2026

Core blocking works without a TezBlock account. This policy explains local data, optional account features, purchases, and the website newsletter.

Local blocking data

Profiles, schedules, preferences, NFC/QR identifiers, and focus history are stored on your iPhone. Apple's Family Controls picker represents selected apps, categories, and websites as tokens. TezBlock does not upload those selections to its servers or share them with friends. Website domains that you type yourself are stored as text in the local profile.

Local app data may be included in device backups according to your Apple settings. Core blocking does not require analytics, advertising IDs, or advertising trackers. TezBlock has no ads.

Optional account and Friends

If you register or sign in with Apple, Google, or email, Supabase provides authentication and stores your account identifier and authentication information. This may include your email address and account information supplied by your sign-in provider. For email sign-in, Supabase processes the email address and password you submit; TezBlock's public profile tables do not store your password. Sign in with Apple's relay address is used when supplied instead of your real email.

For Friends and synced session history, Supabase also stores:

• Your display name and invite code.
• Focus-session identifiers, profile names, and start/end times.
• Friend connections and session reactions.

Connected friends can see your display name, shared sessions, weekly focus activity, and reactions. They do not receive your email or blocked-app selections through Friends. A profile name is shared, so choose one you are comfortable showing to friends.

Optional Mac sync

Mac sync is disabled by default and can be enabled in each profile's Domains settings. When enabled, TezBlock publishes the profile name and identifier, session identifier, custom website domains and block/allow mode, session state, and update time to your private Apple iCloud key-value storage. The Mac companion reads this state to mirror explicit website blocklists. Family Controls tokens and NFC/QR identifiers are not included. This is separate from Supabase and does not require a TezBlock account.

The Mac network extension checks connection hostnames and, when needed, initial TLS handshake data locally to enforce the blocklist. It does not decrypt HTTPS content or upload browsing traffic to TezBlock servers. Disabling sync for a profile stops sharing its future active state; an inactive update replaces the active snapshot when the phone publishes the next transition. iCloud delivery can be delayed while offline.

The Mac companion keeps local setup, filter, and sync diagnostics for troubleshooting. These records omit profile names, website domains, and browsing history, and rotate at seven days or a combined five-megabyte limit. Export Diagnostics… saves a ZIP to a location you choose. Nothing is uploaded automatically; sharing that file is your choice.

Account deletion

Use Settings → Delete Account to request deletion of your account and associated synced data, including your profile, friend connections, reactions, and focus sessions. The app also clears its local data after successful deletion. Device backups remain subject to Apple's settings and retention. If your account uses Sign in with Apple, the app asks you to confirm with Apple so TezBlock can revoke that authorization as part of deletion. Deleting an account does not cancel an App Store subscription or delete Apple's purchase records.

Permissions

• Screen Time / Family Controls: used to enforce app and website restrictions through Apple's framework.
• NFC: reads and writes tags for NFC strategies on the device.
• Camera: processes QR codes locally; scanning does not record or save camera footage.
• Notifications: optional reminders about focus sessions.
• Mac network extension and content filtering: enforce synced website blocklists locally after macOS approval.

Purchases

Apple processes subscriptions and optional tip payments. TezBlock verifies StoreKit records such as product and transaction identifiers, purchase/expiration dates, offer and payment information, and revocation/entitlement status to unlock or restore access. TezBlock does not receive your payment card details or billing address from StoreKit. This is separate from any email supplied when creating a TezBlock account.

New subscriptions include all features and automatically renew. Eligible new subscribers receive a one-month free trial after approving the subscription with Apple; billing begins afterward unless canceled. Apple determines introductory-offer eligibility. Old and new subscriptions provide access while active; past subscription payments do not grant lifetime access. Manage or cancel subscriptions in Apple's subscription settings.

RevenueCat receives purchase and subscription records to report trials, renewals, cancellations, billing issues, and expiration. These records use an anonymous identifier or your TezBlock account identifier when signed in. Apple still processes payments; RevenueCat does not receive your card details from TezBlock.

Superwall delivers subscription paywalls and measures their performance. It receives an anonymous RevenueCat identifier or the signed-in account UUID, membership state, onboarding-completion status, paywall interactions, and SDK-provided app/device metadata. When the RevenueCat integration is configured, RevenueCat forwards subscription lifecycle events to Superwall. TezBlock sends no names, emails, blocked-app selections, or profile/NFC links to Superwall. Paywall-preview links are handled by Superwall. Apple remains the payment processor.

Product analytics

PostHog receives a limited set of events: app opening, onboarding steps and completion, paywall views, selected plans, approved Superwall paywall lifecycle events, purchase and restore outcomes, and focus-session starts/ends observed by the app. Events include anonymous installation/device identifiers or signed-in account identifiers, event times, and SDK-provided app/device context such as app version, device model, and operating system. RevenueCat also forwards subscription lifecycle events and revenue information to PostHog, linked by the same identifier. We use these to understand onboarding, subscription conversion, and feature usage.

We do not send blocked-app selections, website domains, profile names, screen-time reports, NFC/QR values, email addresses, or display names to these analytics services. Session replay, automatic screen/tap capture, surveys, and automatic error capture are disabled. App-generated PostHog events disable IP-based geolocation enrichment. These services process network requests and may receive IP addresses as part of transport. We do not use analytics for advertising.

Account deletion removes the synced account data described above. For deletion of records held by our analytics providers, contact support; automated provider erasure is not yet connected to the in-app account deletion flow. Apple's purchase records and required financial records are subject to separate retention requirements.

Service providers

• Supabase: authentication, Friends, and synced focus-session history. Privacy policy.
• Apple / Google sign-in: the provider you choose processes authentication.
• Apple StoreKit and iCloud: purchases, device backups, and optional Mac sync described above, according to your Apple settings.
• External links: opening a tag store or social link takes you to that provider's service and policy.

• RevenueCat: subscription validation and reporting. Privacy policy.
• Superwall: subscription paywall presentation, targeting, and paywall analytics.
• PostHog (US region): product analytics and subscription conversion analysis. Privacy policy.

The app does not include advertising SDKs or enable session recording.

Website and newsletter

The website does not use advertising trackers. If you subscribe to updates, the email you submit is sent to Loops for the product and focus emails you requested. This is separate from app data and is not used to determine which apps or websites you block. Unsubscribe using the link in any newsletter email. Loops privacy policy.

Children's privacy

TezBlock is not directed at children under 13 and does not knowingly collect their information. Contact us if you believe a child has supplied personal information.

Changes and contact

Updates will be posted at the same URL with a new date. For privacy questions, use the contact links at TezBlock Support: X and Instagram @tezblockapp, or Threads and Telegram @un1t900.