Permissions & Screen Time Access
This page explains why Slipstop may request access to certain Apple system capabilities, how app-selection and interruption features work, what the app can and cannot access, and what depends on iPhone system support.
Developer: Dzianis Huletski
Country: Poland
Contact: d.h.emservice@gmail.com
This page explains what device permissions Slipstop may request, how distracting app selection and interruption-related flows may work, what data stays on your device, and what depends on Apple’s supported iOS capabilities.
1. Why the App Requests Permissions
Slipstop requests only the permissions and system access needed to provide the features you choose to use.
Screen Time / App Selection Access
Slipstop may request access to Apple system capabilities related to Screen Time, distracting app selection, and interruption flows so that you can choose which apps you want to protect yourself from and enable supported focus-related restriction logic.
Notifications
If notifications are used in the released version, Slipstop may request notification permission in order to support reminders, focus-session completion notices, or app-related status updates.
If you do not grant a required permission, the related feature may not work or may be limited.
2. What the App Needs Permission For
Depending on the version of the App and your iPhone setup, Slipstop may use supported Apple system frameworks to help with things such as:
- letting you select apps that you consider distracting;
- supporting interruption or pause flows when those apps are opened;
- temporarily delaying or allowing access as part of the product’s focus logic;
- tracking local app states related to rescue moments and focus sessions.
3. What the App Does Not Access
Slipstop is not designed to inspect or read the private content inside the apps you select as distracting.
For example, selecting Instagram, TikTok, YouTube, or another app as distracting does not mean Slipstop is intended to read:
- your messages or chats;
- your photos or videos inside those apps;
- your browsing content inside those apps;
- your account passwords or payment information;
- the private content of third-party apps merely because they were selected.
Slipstop is intended to rely on Apple-supported system behaviors for interruption and protection, not on reading the internal content of the apps you choose.
4. How Distracting App Selection Works
In supported iOS workflows, Slipstop may allow you to choose distracting apps through Apple-provided system interfaces or supported app-selection mechanisms. The App may then store the resulting selection locally on your device so it can apply the interruption or focus logic you configured.
Depending on Apple’s current APIs and system behavior, these selections may be represented through opaque system references rather than human-readable app data.
5. How Interruption or Blocking Features Work
Slipstop is designed around the idea of interrupting impulsive app opens and redirecting attention into a calmer next step, such as a short focus session or a short delay.
However, the exact behavior of interruption, pausing, shielding, temporary delay, or app-blocking flows may depend on:
- your iPhone model;
- your iOS version;
- whether the required permissions were granted;
- whether those permissions were later revoked;
- Apple platform limitations or framework behavior;
- future changes made by Apple to iOS or Screen Time-related capabilities.
This means some features may behave differently across devices or may be partially limited by the platform itself.
6. Temporary Delays and Focus Flows
If Slipstop offers options such as “Focus 15 min”, “Open anyway”, or “Skip for 5 min”, those flows are intended to support more intentional use of your device. Depending on current platform support, some of these flows may rely on supported iOS restriction logic, local app state, or related system behaviors rather than on unrestricted custom overlays.
Not every concept shown on product pages, prototypes, or future roadmap materials should be interpreted as guaranteed system behavior on every iPhone configuration.
7. What Stays on Your Device
Slipstop is designed as a local-first app where possible. In normal supported workflows, the following may remain locally on your device:
- selected distracting app references;
- focus session history;
- rescue statistics;
- timer state and app settings;
- onboarding and feature preference state.
8. What Can Stop a Feature from Working
Features may stop working fully or partially if, for example:
- you deny or revoke a required permission;
- your iOS version does not support a needed framework behavior;
- Apple changes the way a system-level permission or interruption flow works;
- the selected app is removed from your device;
- your current device setup conflicts with the feature’s required conditions.
9. Notifications
If notifications are enabled in a future or current release, Slipstop may use them for things like reminders, completed focus-session messages, or support for interruption-related UX. You can manage notification permissions in iOS Settings.
10. Deleting Permissions and Data
You can generally review, revoke, or change app permissions through iOS Settings. You can also stop using Slipstop, remove the App from your device, or delete local app data through supported app or device controls where applicable.
11. Questions
If you have questions about permissions, Screen Time access, or interruption-related behavior in Slipstop, please contact:
Dzianis Huletski
Poland
d.h.emservice@gmail.com
You can also review: