dagstack privacy policy

Optional dagstack Cloud · internal TestFlight

Current internal TestFlight build: 1.2 (18). It is available to invited internal testers and includes optional Settings → Feedback. Build 1.2 (12) has been submitted for App Review and is awaiting Apple’s review. It is not yet publicly available on the App Store. Free use remains local and needs no account. Optional dagstack Cloud offers personal cloud sync and shared groups through a one-month auto-renewing Apple subscription. The US price is $2.99 per month; Apple shows the localized price before purchase.

What cloud use sends

Apple handles sign-in. Supabase processes the Apple account identifier, the email Apple supplies (including a private relay address if chosen), session credentials and the content you synchronize. The service also retains an encrypted Apple authorization credential so account deletion can revoke the app’s Apple authorization. The two apps have separate accounts and data stores; using the same Apple Account does not share your content with the other app or Mantinomia.

To verify dagstack Cloud, Apple and the service process Purchase History: the product and original/latest transaction identifiers, subscription state and expiry, StoreKit environment, and the App Account Token that binds the purchase to the signed-in dagstack account. The service also retains a one-way hash of the Sign in with Apple subject so the purchaser can safely restore after deleting and recreating an account. Raw signed transaction payloads are not stored.

Cloud content includes task and event titles, notes, subtask checklists, dates, status, intention, order, daily-focus and retention settings, identifiers and synchronization metadata. Shared spaces also store group names, membership, invitations, creator and assignment identifiers. Personal account tasks are private to your account; accepted members can access the tasks in their shared space. Data created while signed in synchronizes automatically when the app is open and connected. Copying the original device library requires a separate confirmation.

Providers, access and purpose

Supabase provides authentication, the database and server functions. The database is configured in Frankfurt, Germany. Access controls restrict ordinary app users to their own data and shared spaces they have joined. This is not end-to-end encryption: the service provider and authorized operator can process hosted content to run, secure and support the service.

Ordinary cloud library information is used to provide the account and sync service you request, not for advertising, tracking or AI processing. The legal basis is providing that requested service. Security, abuse prevention and necessary operational logs are handled for the legitimate interest of keeping the service reliable. Providers may process connection and diagnostic information, such as IP addresses, request times and errors. A Frankfurt database does not mean every provider operation takes place in the EEA. See Supabase’s privacy information and Apple’s privacy policy for their processing and international-transfer information.

Retention and deleting content

Tasks follow the app’s Done, Archive and seven-day Recently Deleted rules. After recovery expires, cleanup replaces removed task content with deletion markers so an older device cannot restore it. Cleanup depends on app activity and successful sync. Archive has no automatic expiry. Shared members may retain previously downloaded copies while offline.

To delete the account, open Settings → dagstack Cloud, choose Delete cloud account and data, complete fresh Apple authentication, then review the final deletion confirmation. Successful deletion removes your personal cloud tasks and every shared space you own for all members. In spaces owned by someone else, your membership and account attribution are removed; the shared tasks remain for that space’s members. The account cache on the requesting device is removed. Apple authorization is revoked. If the app reports deletion pending, keep it installed and use its retry or finish-deletion action. Contact support if completion remains blocked.

Deleting a dagstack account does not cancel the Apple subscription. Cancel it separately in Apple subscription settings. A minimum purchase-binding record remains after account deletion so the same Apple purchaser can restore and another account cannot claim the subscription. It contains the transaction identifiers, product, state, expiry, environment, App Account Token, and one-way Apple identity hash; it is no longer linked to the deleted Supabase account. There is currently no automatic deletion schedule for that record.

The separate device-only library is retained. Signing out preserves an isolated account cache and unsynced work for your next sign-in; uninstalling removes local data but does not delete the cloud account. Other offline devices, exports, shared copies and device backups are not erased remotely. A limited deletion-completion record containing the account identifier and a hashed operation identifier remains to let interrupted clients confirm the outcome. It expires for this purpose after 30 days and is removed during later cleanup.

Backups and your privacy requests

Provider-managed database backups and operational logs may retain information after deletion from the live service until those copies expire. Supabase documents seven days of database backups for its standard Pro plan; this is disaster recovery, not an in-app restore promise. Database backups do not include original attachment bytes. dagstack has no export or individual backup-restore feature. See Supabase’s backup documentation.

Contact mantinomia@gmail.com to request access, correction, deletion or a portable copy of your cloud data, or to exercise applicable rights to restriction or objection. We may need to verify the account before acting. You may complain to Datatilsynet. Content stored only on your device cannot be accessed by the developer.

The browser desk

At dagstack.app, signing in opens the same dagstack Cloud account. This browser stores personal task snapshots, daily-focus settings and unresolved changes separately for each account. Recovery keeps your attempted change and the server version when they conflict; retrying sends the original request until its result is confirmed. Shared task snapshots remain in memory, and a successful membership update removes content from groups you can no longer access.

Signing out retains the account-specific personal cache and pending changes on this browser. Clearing this site's browser data removes those local copies, including unsent work; it does not delete cloud tasks. Avoid signing in on a shared browser if you do not want these local copies retained. No advertising, analytics or AI processing is added by the browser desk.

Who is responsible

dagstack is provided by Ola Oldernes Hårstad. For privacy questions, contact mantinomia@gmail.com. This website is operated by Ola Oldernes Hårstad.

The local library and existing iCloud sharing

The following storage, sharing and lifecycle sections describe the original local/iCloud library. The local personal library remains available when signed out. Earlier 1.1 builds also expose the iCloud sharing described below; version 1.2 hides sharing controls without an active dagstack Cloud subscription but does not automatically delete old local or CloudKit data. The separate Supabase account follows the cloud rules above.

dagstack stores task titles and notes, whether a task is in Stack, Today, Done, or Archive, its intention and order, dates, and identifiers needed to manage changes. It also keeps your display preferences, notification choices and daily-focus schedules, Done limits, and information needed to connect to your shared space.

In the original device library, private tasks and archives remain in local storage. They are not sent to partners or synchronized through dagstack’s CloudKit sharing. Personal preferences for including or hiding shared tasks also remain on your device.

Neither mode has advertising, tracking SDKs, analytics SDKs or AI processing of tasks. Device-only and iCloud mode do not send task contents to the developer’s Supabase service.

Optional partner sharing through iCloud

If you use sharing, dagstack uses Apple’s CloudKit service. The owner’s shared space is stored in their private CloudKit database and is made available to invited participants through CloudKit’s shared database. dagstack keeps a local copy so you can work offline and synchronize changes later.

Shared records contain task titles and notes, status and intention, dates, order, assignment and creator identifiers, and information needed to synchronize edits, archiving, recovery, and deletion. The shared Done limit is stored with the space. CloudKit account and participant identifiers are used to recognize members and keep data connected to the correct Apple Account. Participant names supplied by CloudKit may be shown to other members.

Sharing is invitation-only. You choose recipients using Apple’s sharing interface. Members can read, edit, complete, archive, recover, and delete shared tasks. A task’s shared state applies to everyone. The app sends private tasks to the shared space only when you explicitly share them; tasks created directly in Shared belong to that space.

Apple processes iCloud information under its terms and privacy policy. Invitation delivery may use a messaging or email service you choose, whose privacy practices apply to that message. Share only information you intend the other members to receive.

Daily focus schedules

Your optional Personal reset schedule stays on your device. The Shared schedule is stored with the shared space in iCloud and is managed by its owner. It includes the chosen time, time zone, and dates needed to apply the same reset on each device. Resetting daily focus does not delete tasks or generate task-edit alerts.

Optional notifications

You can choose separate alerts for shared task additions, edits, completion, and deletions. Notification preferences stay on your device and save immediately. The former daily review reminders are no longer scheduled.

Apple’s push notification service can wake dagstack to synchronize shared changes. After synchronization, dagstack creates enabled shared-task alerts on your device; their previews may show shared task titles. You control notification permission and preview visibility in iOS Settings. dagstack does not send device push tokens or notification contents to a developer-operated server.

iOS may delay or combine background updates, so these alerts are not a complete event history. Opening dagstack or tapping its sync status requests an immediate check.

Keeping, archiving, and deleting tasks

Active tasks stay until you change or delete them. Done has a configurable age or count limit, with a default of 30 days. Private and shared limits are separate. Only the shared-space owner changes the shared limit; all members can archive tasks. Archive has no automatic expiry, but archived tasks can still be deleted.

Tasks removed by a Done limit or manual deletion remain recoverable in Recently Deleted for seven days. After that period, cleanup removes private tasks and clears shared titles, notes, assignments, and creator information. Small deletion markers, including task identifiers and synchronization metadata, remain in the shared space to prevent an older offline copy from restoring deleted content.

Making a shared task personal creates a new private copy and removes the former shared version for everyone. That old shared copy remains recoverable for seven days. Future changes to the private copy are not synchronized to partners.

Cleanup runs during app use and successful synchronization. Connected shared cleanup requires the owner’s device to complete a successful sync, so shared content may remain longer while that device is offline or inactive. Other devices receive the removal when they next synchronize; an offline or disconnected device may retain its downloaded copy.

Removing the app deletes its local data but does not itself delete the shared space in iCloud or copies on other devices. Manage shared tasks and access before removing the app. Copies saved elsewhere and existing device backups are handled separately.

Leaving a space or removing access

Use Partners → Manage partners to access Apple’s sharing controls. The owner can change participation or stop sharing. An owner keeps the local shared tasks after stopping sharing. A participant who explicitly leaves removes the shared cache from that installation; private tasks remain.

Revoking access prevents future synchronization but cannot retrieve previously downloaded copies. A removed participant may retain a local copy until they leave or remove the app, and may have saved information elsewhere. Changes made without access cannot synchronize with the space.

Backups and device services

Your operating system may include dagstack’s local app data in device or cloud backups, depending on your settings. Apple may process diagnostics or analytics under your Apple and device settings and Apple’s privacy policy.

Archive is part of the app’s storage, not an independent backup. dagstack 1.0 has no export or restore feature. The developer does not operate a backup service and cannot recover your private or shared task collection for you.

Support and this website

In internal TestFlight 1.2 (18), Settings → Feedback sends the title and message you enter, together with the app version/build, project and category, through oohaa to the developer’s private dagstack pipeline in mempit. No task contents, account details, device identifiers or email address are attached automatically. Your draft and retry request stay on this device until delivery is confirmed; editing creates a new message. No cloud account or subscription is needed.

oohaa retains a separate private delivery copy so interrupted sends can be retried; mempit stores the message for private review. Feedback is kept while useful for support and improving the app. Ask support to remove it from both services. Deleting a dagstack account does not remove feedback. Avoid sensitive information in your message.

If you email support, we use your email address and the information you send to respond. Include only what is needed to explain the issue. Correspondence is handled through Gmail (Google) and kept as needed to resolve the request, meet legal obligations, or establish, exercise, or defend legal claims.

This website uses no advertising or analytics. An essential cookie keeps the owner signed in to the private feedback inbox. If you submit feedback on this website, the message and optional contact details are stored separately from your app data. Vercel processes connection information to deliver and secure the pages. The shared feedback and website privacy information explains the legal basis, retention, international transfers, and your rights.

You can contact mantinomia@gmail.com to ask about or request access, correction, or deletion of support correspondence, or to exercise other applicable privacy rights. You may also complain to Datatilsynet, Norway’s data-protection authority. Use dagstack and Apple’s sharing controls to manage task data; we cannot access tasks stored only on your device or change your shared space on your behalf.

Changes to this policy

This policy covers the local/iCloud library and the dagstack 1.2 Cloud subscription flow. If these data practices change, we will update this page and provide any required notice or choices.