Privacy in Sidst.

Who is responsible and what this notice covers.

This privacy notice applies to the Sidst iOS app published by Steffen Aspe under the SABONEX brand. In this notice, references to SABONEX mean Steffen Aspe operating under that brand.

For personal data that SABONEX actually receives or otherwise controls — for example support correspondence — Steffen Aspe is the data controller. Sidst itself does not require a user login or SABONEX account, and neither version described here has a Sidst-specific backend that receives the user's activity history.

Visits to this page or the wider SABONEX website are covered separately by the SABONEX website privacy notice.

Your activity history is stored in Sidst's local app container.

Sidst stores the activities and history you create, together with categories and related app settings, locally in the app's iOS container. The main activity data uses guarded JSON persistence in the app's Application Support area; ancillary settings are kept in local app settings.

The persistence layer includes validation, storage-safety checks and an internal recovery backup so a failed or interrupted write is not silently treated as an empty first launch. These recovery files remain part of Sidst's local app data.

Neither version described here automatically uploads or synchronizes this local activity history to SABONEX. Protection therefore relies on iOS app sandboxing and the security of the user's device.

Reminder notifications are scheduled locally through iOS.

If you choose to use reminders, Sidst asks for the notification permission required by iOS. Reminder schedules are created through Apple's local notification system on the device.

Neither version uses a SABONEX push-notification server. Notification messages include the activity title and emoji, which may appear on the Lock Screen depending on your iOS notification preview settings. You can change permission and preview visibility in iOS Settings.

Calendar integration is optional and restricted to Sidst's own calendar.

If you enable Apple Calendar integration, Sidst requests full calendar access from iOS to inspect available calendar sources and maintain its dedicated calendar. This iOS permission is broader than Sidst's use: the app creates, updates and removes events only in the calendar it created and identifies as its own.

Sidst can create, update and remove matching events in the dedicated calendar. Other writable calendars are not exposed as Sidst sync targets, and the app does not adopt another calendar solely because it has the same name.

Calendar access is handled through Apple's EventKit. The dedicated Sidst calendar is created in an available calendar source on the device. If that source belongs to an account that synchronizes calendars, the resulting calendar events may also be processed or synchronized by the calendar provider selected on the user's device. SABONEX does not operate that calendar account.

Internal recovery backup and user-exported backup are different things.

Sidst maintains an internal local recovery backup as part of its guarded persistence and restore-safety design. It remains inside Sidst's app data and is used to recover from local storage problems.

Separately, you can choose to export a JSON backup through Apple's file interface and later import a selected JSON backup. The app validates backup data before restore.

Once an exported backup is saved outside Sidst's app container, its storage, synchronization and deletion depend on the location or file provider you chose. Depending on device backup settings, iOS backups may also contain app data; removing an activity in Sidst does not necessarily remove older backup copies. SABONEX does not receive a copy merely because you exported one.

The CloudKit foundation is passive in the versions described here.

The Sidst codebase contains technical foundations for possible later cloud sharing or synchronization, but neither the released 1.0.0 app nor the prepared 1.1.0 candidate automatically moves, uploads or synchronizes local activity history to CloudKit.

If active cloud synchronization or sharing is added later, the privacy notice and relevant App Store privacy information will be reviewed before or alongside that feature.

Sidst Plus uses StoreKit; there is no subscription or advertising.

Sidst Free allows up to five non-deleted activities; archived activities count toward that limit. Sidst Plus removes the limit through a one-time, non-consumable App Store purchase. Existing, restored or imported activities above five are preserved. Plus does not use a subscription.

Apple handles the purchase and associated account and payment information through the App Store. Sidst uses StoreKit to load the localized product and price, complete a purchase, check verified entitlement at launch and when transactions change, and let you use Restore purchases in Settings. SABONEX does not receive payment card details or operate a Sidst purchase server.

The reviewed 1.0.0 (5) and 1.1.0 (6) candidate source has no third-party analytics SDK, advertising network, AdSupport integration or external package dependency for tracking.

Sidst does not sell local activity history to advertisers or data brokers.

Separately, Apple can provide developers with app crash and usage diagnostics according to Apple's sharing settings and distribution channel. This is Apple-platform reporting, not an analytics SDK embedded in Sidst. Such reports may help identify technical faults; Sidst itself does not upload activity history to a SABONEX analytics server.

The upcoming widget uses a limited local display cache.

The previously released 1.0.0 (5) app does not include a Home Screen widget. The prepared but not yet distributed 1.1.0 (6) candidate adds one configurable small widget for Sidst Plus. You choose one activity for each widget. It can show that activity's emoji, title and calendar-relative time since the most recent registration; on supported displays, tapping it opens Sidst. The widget cannot register or edit an activity itself.

To provide this display, Sidst writes a versioned local App Group cache with activity identifiers, titles, emoji, latest registration dates, archived status and a limited Plus-access state. The widget reads only this display data, not full activity history, backup or recovery files, or App Store transactions. No SABONEX server receives this cache.

Widget content can appear on the Home Screen and may be visible to people using your device. Sidst marks it as privacy-sensitive for system-controlled redaction, but this is not a guarantee that names will be hidden in every situation. iOS controls refresh timing, so previously displayed information may persist temporarily until the app and WidgetKit update it.

Widget content can also appear on connected displays, such as CarPlay and Apple HomeView. The activity name, emoji and time since the last entry may therefore be visible to others. HomeView's shared Modular face is visible to the whole household. Only choose activities you want others to see; locking your iPhone does not guarantee that content is hidden.

On iOS 26 and later, Sidst marks the widget as not optimized for CarPlay. This does not prevent you from choosing to display it. Tapping can only open Sidst on supported displays; Sidst has no app interface in CarPlay. The system controls display and update timing, so previously displayed content may remain temporarily.

Retention depends on where the data lives.

Local Sidst data: remains in the app container until you change or delete the relevant data, remove the app's local data or uninstall the app. Internal recovery files are managed as part of the local persistence system.

Internal backup and recovery copies may still contain earlier activity information after an activity has been changed or deleted. Sidst 1.1.0 (6) records metadata about recovery archives but does not yet perform automatic time-based review or deletion of these copies.

Exported backups: remain in the file location or provider you selected until you or that provider remove them.

Apple Calendar events: events created by Sidst in its dedicated calendar can be removed through Sidst's calendar controls or Apple Calendar. Copies synchronized by a configured calendar provider are governed by that provider/account.

Support email: When you contact SABONEX at info@sabonex.com, we retain your enquiry while it is being handled and afterwards only when follow-up, security, necessary documentation, a dispute or a legal obligation makes this necessary. We review closed support cases at least once a month and delete messages and attachments that are no longer needed. Requests for deletion are assessed as they arrive and do not wait for this review.

Support email backups: Simply.com states that email is normally backed up daily and that backup copies are generally kept for 30 days. Deleted messages may therefore remain in backups for a period; the 30 days are not a guaranteed final deletion deadline.

Your privacy rights and choices.

You control Sidst's locally stored activity history through the app and can also create your own portable JSON backup. Because SABONEX does not receive a server copy of the local activity history, SABONEX cannot remotely inspect, export or erase those local records on your behalf.

For personal data that Steffen Aspe/SABONEX actually holds, such as support correspondence, applicable privacy law may give you rights including access, correction, deletion, restriction, objection and, where applicable, data portability.

The info@sabonex.com support mailbox is hosted by Simply.com A/S, which processes correspondence stored there on SABONEX's behalf under a signed data processing agreement. Your email address, message content and any attachments are included in this processing. Other email services may be involved in delivering messages. Sidst does not automatically send local activities or backups to support. Please avoid sending sensitive activity details or backups unless necessary for your request.

Support correspondence is processed to answer the request, troubleshoot the app and keep necessary follow-up or records. Depending on the context, this may be based on steps requested by you or performance of an agreement, legitimate interests in providing and securing support, or a legal obligation.

For privacy questions or requests, email info@sabonex.com. You may also have the right to complain to the competent data protection authority where you live or work, or where an alleged infringement occurred. In Denmark, the supervisory authority is Datatilsynet.

If Sidst changes its data handling, this page will be updated.

This notice covers the previously released 1.0.0 (5) app and the prepared but not yet distributed 1.1.0 (6) candidate, including its Home Screen widget. Sidst is currently unavailable for new App Store downloads while its release and privacy information is reviewed. If a later version activates cloud synchronization, account/server features, analytics, advertising or other material data sharing, this notice and relevant App Store information will be reviewed and updated.

The latest version of this privacy notice will remain available at this address.