No sign-up.
Just block the apps.
Install Fella, grant Apple’s Screen Time permission, choose the apps that distract you and start blocking. No Fella username, password or extra login to faff about with.
No sign-up.
Does Fella need an account?
No. A Fella account isn’t required for the core blocking flow. You can complete onboarding, pick the apps you want to restrict, purchase Fella+ and start a session without creating a Fella profile or signing in.
No extra Fella email or password field. You also don’t need Sign in with Apple or Google. Optional account features may still be offered, but they’re separate from the blocker itself.
Your Apple ID is different. Apple still uses the Apple ID signed in to the App Store to process a subscription and check whether a purchase is eligible to be restored. That’s not a Fella account.
| Step | What you do |
|---|---|
| 1 | Download and open Fella |
| 2 | Complete the short intro |
| 3 | Grant Apple’s Screen Time authorisation |
| 4 | Choose the apps or categories you want to block |
| 5 | Pick a Fella+ plan via the App Store |
| 6 | Start a session or create a scheduled routine |
From download to blocked — without a sign-up step
The job is app blocking, not profile building. Fella doesn’t need a social identity, cloud dashboard or another set of credentials before it can tell iOS which chosen apps to restrict. See the full Fella blocking flow.
| Identity or data | Required for core blocking? | What it’s used for |
|---|---|---|
| Fella username or profile | No | Optional connected account features, if you use them |
| Fella password | No | Not required for onboarding, purchase or blocking |
| Apple ID | For App Store purchases | Apple processes the subscription and provides receipt info |
| RevenueCat app-user identifier | For subscription management | Links purchase and entitlement without being a Fella login |
| Analytics and diagnostics identifiers | Used by the app | Help measure use and diagnose reliability; not a Fella profile |
| Support email | No | Provided only if you contact support or use an account flow |
| Selected-app tokens | For blocking chosen apps | Stored in Fella’s local shared app container for the app and its extensions |
No account doesn’t mean no software plumbing
These are different kinds of identity. A subscription system needs a technical way to recognise paid access. Analytics and diagnostics also use technical identifiers. Neither requires you to invent a Fella username.
No-account isn’t the same as no data at all. Fella uses RevenueCat for subscriptions, PostHog for analytics and Sentry for diagnostics. See the full Privacy Policy and plain-English privacy philosophy.
Your app choices use Apple’s privacy-preserving tokens
Fella uses Apple’s native Screen Time picker. When you choose apps or categories, iOS represents them with system tokens rather than handing Fella a simple behavioural profile. Fella stores those tokens in its local App Group so the main app and extensions can apply the same restriction.
The tokens are part of the blocking rule, not an analytics payload. Fella doesn’t send the chosen-app tokens as PostHog analytics properties.
Screen Time permission is still required. Accountless doesn’t mean permissionless. You must approve Apple’s Screen Time authorisation before Fella can restrict apps on your iPhone.
How subscriptions work without a Fella login
Apple handles payment; RevenueCat handles entitlement. Fella doesn’t receive your full card number or Apple ID password. Apple completes the App Store transaction, whilst RevenueCat provides the info to decide whether Fella+ is active.
The purchase still has an app-user identifier. That identifier lets the subscription infrastructure associate a transaction with app access. It’s a technical record, not a Fella email-and-password account.
Restore Purchases is built in. Fella can ask Apple and RevenueCat to recover an eligible entitlement. Restoration depends on the relevant Apple ID, App Store receipt eligibility, connectivity and third-party availability.
Purchase recovery and app setup are separate
Restoring Fella+ doesn’t automatically promise to restore every local choice. Your subscription entitlement, chosen apps, routines, settings and progress are different data. Restore Purchases is designed to recover eligible paid access; it shouldn’t be read as a guarantee that every local configuration will return after deleting the app or moving to a new iPhone.
Plan to recreate local setup when needed. Without relying on an account-based cloud profile, a reinstall or new handset may require you to grant Screen Time permission again, reselect apps and rebuild routines. That’s the practical trade-off of a lighter account footprint.
| Decision | No-account approach | Account-based approach |
|---|---|---|
| Onboarding | No profile or login before the core task | Usually includes registration or sign-in |
| Credentials | No extra username or password to keep | Can support password or SSO recovery |
| Cloud recovery | Local setup may need to be recreated | Can restore configuration when the service supports it |
| Cross-device features | Fewer identity-linked features by default | Can make sync, dashboards and shared management easier |
| Purchase restoration | Can use App Store purchase restoration | May combine App Store restoration with an app account |
No-account blocker or account-based blocker?
Accounts aren’t automatically bad for privacy. They can provide useful backup, cross-device sync, family or organisation management, web dashboards and support recovery.
Fella fits the simpler job. It’s for self-managed iPhone blocking: choose distracting apps, start a session yourself or use a scheduled routine, and get one 5-minute Emergency Unlock per active session before Fella reblocks.
Who this setup is — and isn’t — for
Choose Fella if you want to start quickly and don’t need another profile. It suits people who want fewer credentials, no mandatory registration, self-managed iPhone blocking and a focused product instead of a cloud dashboard.
Choose something else if account features are the point. A service built around cross-platform sync, family or organisation management, a web dashboard or guaranteed account-based configuration recovery may be a better fit. Fella’s iPhone app blocker is deliberately narrower.
7-day free trial
Fella, up close.
- Built with Apple’s Screen Time controls.
- One 5-minute emergency unlock per session.
- Apps stay blocked by default.
No-account app blocker FAQ
No. You can complete the current onboarding, purchase a subscription, choose apps and start blocking without creating or signing in to a Fella account.
No email address or Fella password is required for the core app-blocking flow. You may provide an email if you contact support or choose an optional account feature.
No. Neither sign-in method is required to complete the core onboarding and purchase flow.
You need an Apple ID for App Store purchase and restoration services. That Apple ID is managed by Apple and is not a Fella account.
Apple handles the transaction and RevenueCat manages the Fella+ entitlement using an app-user identifier. This is a technical purchase identity, not a Fella username or password.
Fella includes Restore Purchases, which asks Apple and RevenueCat to recover an eligible entitlement. Restoration depends on the relevant Apple ID, receipt eligibility, connectivity and service availability.
You can request restoration of an eligible Fella+ purchase. Local setup is separate: you may need to authorise Screen Time again, reselect apps and recreate routines or preferences.
Fella stores Apple’s privacy-preserving selection tokens in its local shared app container so its blocking extensions can apply the rule. Those tokens are not sent as analytics properties.
Yes. Fella uses product analytics and diagnostics services. No-account means no mandatory Fella login; it does not mean no technical identifiers or no data processing.
No. Apple, RevenueCat, analytics and diagnostics can still use technical identifiers for purchases, product operation, measurement and reliability.
