Introduction
This policy describes how the Momento Android app (“Momento”, application ID
com.ApterApps.momento, version 1.1.4, versionCode 48) handles information.
Momento is provided by APTECH. Momento has no user accounts and no Momento backend that
receives your pause history, selected apps, usage statistics, or Accessibility events.
What Momento does
Momento helps you pause before opening apps you find distracting. You choose which apps to limit. When one of those apps becomes active, Momento can show a pause screen you configured. Settings, selected apps, and pause records stay on your device unless you back up the device yourself.
Information processed on the device
Momento processes information on your device so the pause experience can work. That includes selected-app package names, foreground-app identity for detection, local screen-time calculations, settings, pause records, and disclosure consent. Processing on the device is not the same as “no information is handled.” Momento does not upload that information to APTECH servers in this build.
Usage Access / UsageStatsManager
Usage Access is required for Momento’s core pause and blocking functionality.
With your permission, Momento uses Android Usage Access
(PACKAGE_USAGE_STATS / UsageStatsManager) to identify which
apps were in the foreground and for how long. This powers:
- foreground-app detection used to show the pause screen when a selected distracting app becomes active; and
- screen-time / app-usage information shown in the app.
Usage information is processed on your device and is not sent to Momento servers. Momento does not use Usage Access to read the content inside other apps. You can turn Usage Access off in Android special app access settings. Without it, Momento cannot reliably detect selected apps or calculate screen-time information.
Usage Access is distinct from Accessibility Service. Usage Access is required for core pause/blocking. Accessibility is an optional enhancement for faster detection.
Display over other apps
Display over other apps (SYSTEM_ALERT_WINDOW) is required for Momento’s core pause experience.
If granted, this permission lets Momento show its pause screen while another app is in the foreground. It is not used to read the content of other apps or to show ads. Without it, Momento cannot display the pause screen over selected apps.
Android Accessibility Service
Momento is not an accessibility tool for people with disabilities. Accessibility access is optional.
If you enable Momento’s Accessibility Service, it is used only to detect when an app you
selected becomes the active app. The service receives Android window-change events
(TYPE_WINDOW_STATE_CHANGED) and the package identifier of the active
application. Momento compares that identifier with the list of apps you chose to limit.
If it matches, Momento shows Momento’s own pause interface.
The Accessibility Service does not:
- read screen contents;
- inspect the accessibility node tree / view hierarchy of other apps;
- read messages;
- read passwords;
- read typed text;
- read browser URLs;
- inspect notifications;
- take screenshots;
- perform automated clicks;
- perform gestures;
- filter keyboard input;
- change Android settings;
- perform Accessibility actions on your behalf.
Foreground package identifiers from Accessibility events are processed on the device in memory to decide whether to show the pause screen. Momento does not store an Accessibility event history. The list of apps you selected to limit is stored locally because you configured it.
Accessibility-derived information is not transmitted to Momento servers. It is not sold or shared for advertising.
You can disable Accessibility access at any time in Android Settings → Accessibility → installed services → Momento. Momento never turns the service on by itself. Without Accessibility, Momento can still detect selected apps using Android Usage Access, but detection may be slower or less immediate on some devices. Accessibility allows more immediate detection when you open a selected distracting app.
Selected applications
You choose which apps to limit. Momento stores those choices, including Android package
names, in local app storage. Installed launchable apps may be listed on the device so
you can pick them; that list is not uploaded. Momento does not declare
QUERY_ALL_PACKAGES; it uses a narrow package-visibility approach for the
installed-app picker.
Local storage
Momento stores on the device: your settings (pause length, language, whether blocking is on), selected apps, local pause/stop events and reasons, disclosure consent (accepted, version, timestamp), native blocking state (including temporary unlock windows and pause countdown), and a local count of completed pause sessions used only to decide when to show Android’s in-app review prompt. Reset all data in Settings, or uninstall Momento, to remove this information from the app.
Notifications, foreground service, and battery exemption
Notification permission is used so Momento can show an ongoing focus-session
notification while the blocking service is running. A foreground service of type
specialUse polls Usage Access while you have focus/blocking enabled so
pause detection can continue when Momento is not visibly open. You start this by
enabling blocking/focus in the app; you can stop it by turning blocking off. The
ongoing notification shows that the service is running. This is not hidden background
surveillance.
An optional battery-optimization exemption reduces the chance that Android or a device manufacturer stops that service in the background. Momento does not silently change this setting. You remain in control and can skip it. Without it, pause detection may become unreliable after Momento has been in the background, especially on devices that aggressively stop apps. These features do not send your content to Momento servers.
Network connections
This build does not send pause history, selected apps, usage statistics, or Accessibility events to APTECH. The app may open the Privacy Policy in a browser (HTTPS) when you tap the link, and may open Google Play’s in-app review interface after several completed pauses on the device. Those connections are not used to upload your pause or usage data from Momento’s own code.
Retention, reset, and uninstall
Local Momento data remains on the device until you change it, use Settings → Reset all data, clear Momento’s storage in Android Settings, or uninstall Momento. Uninstalling removes the app’s local storage. There is no Momento cloud account to delete.
Third-party libraries
Momento is built with Expo and React Native. It uses on-device storage (AsyncStorage / Android SharedPreferences) and may use Google Play’s in-app review interface after you complete several pauses on the device. This build does not include advertising SDKs, analytics SDKs, crash-reporting SDKs, or a Momento user-data backend. Production onboarding analytics helpers do not send events off the device.
No advertising or analytics data collection
Momento does not sell your information. It does not use Accessibility, Usage Access, or selected-app data for advertising. It does not share that information with third parties for advertising or analytics in this build.
Children
Momento is not directed at children and is not a parental-control or device-admin app.
Changes
If this policy changes, the date at the top will be updated. Material changes to Accessibility use will also be reflected in the in-app disclosure, which may ask for consent again.
Current last updated date: 23 August 2026.
Contact
Questions about this policy: use the developer contact details listed on the Momento Google Play listing for APTECH / Momento.
- Developer / company
- APTECH
- Email (from this website)
- ronzapter@gmail.com
- Application
- Momento (
com.ApterApps.momento), version 1.1.4 (versionCode 48) - Website
- Momento product page