Your lists can be personal.

This explains the current beta’s privacy boundaries. We want you to understand them before deciding what to put here.

What the app stores

Your account, saved routines, schedules, run progress and history, and any reflections you choose to save are stored using Supabase. The web app is hosted on Vercel. Account and hosting services also process technical information needed to operate the service.

Unsaved builder drafts stay in the current browser page. They are not cross-device backups. The welcome-page example is temporary, is not saved to an account, and resets when the page is reloaded.

Private from other users is not the same as private from the operator

Normal app access is restricted to your own routines and runs. Starter-management access does not grant access to other people’s private lists.

The service is not end-to-end encrypted against its operators. People with sufficiently privileged database or project access can access stored content. Do not treat this beta as a place to store passwords, sign-in codes, or information that requires that stronger protection.

Your notes are for you

To help refine your own saved list, Runs can compare matching item wording in its last five completed runs and show you repeated additions or skips. This happens within your account using existing history, not through an AI service or a shared analytics dataset. Skips do not tell us why you left something out. Suggestions never change your list without your approval.

The app does not automatically send your routines or reflections to an AI assistant, or include them in a product-analytics feed. Saving a note is not consent to research, training, or founder review.

There is no session-replay tool in the application. That does not mean the hosting and account services keep no technical logs. A complete provider-log and retention review is still a beta launch prerequisite.

Deleting a run and deleting a routine are different

Deleting a run removes that run’s stored progress and reflection from the application database. It does not delete its reusable routine.

Deleting a routine hides the reusable definition and its edit history, removes its schedule, and prevents new runs from starting from it. Existing run snapshots remain available. The deleted definition is retained in the database; this is not full account erasure.

These actions do not promise immediate removal from provider backups. Full account export and account erasure are not self-service features in this beta. A complete retention schedule and a tested process for handling those requests still need to be established before inviting beta testers.

Questions or requests

Contact veeraydev@gmail.com about access, privacy, or deletion. Please don’t include passwords, sign-in codes, or private list contents in your first message. We’ll clarify what is needed and what can be done.