Privacy policy
Moss - Focus with Arlo
By Michael Norman
This policy describes the current Moss iOS app. Moss does not require an account and has no developer-operated server, advertising, analytics SDK, or other third-party SDK.
Information stored on your device
Moss saves information locally so it can remember your choices and show your focus history and companion’s progress:
- Your preferences, including your companion’s name and session settings.
- A focus journal with session records and distraction check-ins.
- Assignment details, such as titles and due dates, and completion you confirm yourself.
- Screen Time selections represented by Apple’s opaque selection tokens, and information needed to coordinate an active focus session.
This information is stored in the app’s local storage or its shared on-device container, which lets Moss and its Screen Time extensions work together. Moss does not upload these records to the developer or an external service.
Optional Calendar access and assignments
Calendar access is optional. If you grant permission, Moss can preview calendar events on your device and let you select which ones to import as assignments. You can deny access or choose not to import an event. Previewing and importing happen on your device; Moss does not change your calendar events.
Imported assignment details and completion status are saved in local app storage or the shared on-device container. A completed assignment means you marked it complete yourself. Moss does not verify schoolwork, grades, submissions, or completion with a school or calendar provider.
Moss does not upload assignments, school records, calendar event notes, locations, or attendees to the developer or an external service. The current version does not connect directly to Canvas or use Google sign-in. Events from calendars already synced to your device can be previewed and selected for import; those calendar providers have their own sync and privacy practices.
Screen Time permissions and check-ins
Apple handles Screen Time authorization and the system picker used to choose apps, categories, or websites. Moss uses the selection tokens to apply the focus protection you request.
Moss does not collect your messages, browsing history, total Screen Time usage reports, or a general stream of app-opening events. A distraction check-in records an interaction with Moss’s demo control or its Screen Time shield button. It does not mean Moss observed every time another app was opened.
You can revoke individual Screen Time authorization through iOS. A demo session does not block apps.
Local storage and retention
Moss keeps local journal records, assignment details, completion status, and preferences to preserve your history and settings. Ending a session does not erase earlier journal records. The current version does not include a dedicated delete-history control or a cloud account to delete.
Some local app data may be included in device backups according to your iOS settings. Backups and system-level storage are managed by Apple and your device settings. Moss has no developer-operated database from which these local app records can be retrieved or remotely deleted.
Testing through TestFlight
TestFlight is an Apple service with its own data practices. Apple automatically collects beta-app crash logs and usage information and shares them with the app developer. Feedback you choose to submit is also shared with the developer and may include your comments, screenshots, name, email address, and device details. What is visible can depend on how you joined the test.
TestFlight collection is separate from the local app storage described above. For details about Apple’s collection, sharing, retention, and privacy controls, see TestFlight & Privacy.
Privacy questions
For privacy questions, visit Moss support or email lubbers.27.adverts@icloud.com. Please do not send diagnostic reports or private assignment, Calendar, or Screen Time details.
If you are testing Moss through TestFlight, you can contact the developer using TestFlight’s beta feedback option. Information you include in that feedback is sent through Apple’s TestFlight service.