PUBLIC BETA · UPDATED 17 SEPTEMBER 2026
Your information
in LOOPING.
This notice describes the current website, beta accounts, newsletter signup, and local browser workspace.
Reading the website
The landing page, Program tour, research notes, and free manual can be viewed without registering. This site does not add advertising trackers or third-party analytics. Its hosting and sign-in providers process technical information needed to serve and protect the site under their own policies.
Your beta account
Email-and-password login uses Supabase Auth. Your password is processed by the authentication service; LOOPING does not save plaintext passwords in its profile database. Secure session cookies keep you signed in. We store your account identifier, email, optional display name, registration dates, and acceptance of the beta terms. Existing beta members can also use their original ChatGPT sign-in.
Use your account page to change your display name, change newsletter preferences, or delete your beta profile and newsletter entry. Deleting a beta profile removes its profile and newsletter records. It does not delete the Supabase email/password login or your ChatGPT account.
Your daily workspace records
Plans, focus records, progress notes, and optional work or sleep observations in the browser workspace remain in that browser’s local storage. Beta registration does not upload or sync those daily records. Clearing browser data may erase them. Export a backup before changing browsers or devices.
Backups are plain JSON files and may contain personal information. They remain wherever you choose to save or share them. Account deletion does not remove local workspace records or exported files; use the workspace’s Your data controls for that.
Newsletter requests and consent
If you request updates, we store your email address, request and confirmation times, signup source, consent status, and private confirmation/unsubscribe tokens. We use this information for LOOPING program and product updates. Signup is optional and separate from beta registration.
A public signup begins as a pending request. Confirmation emails can be sent once the sender is configured; we do not send newsletters to unconfirmed requests. If you opt in while signed in, your verified email and explicit selection confirm that preference.
When email delivery is connected, the email provider receives the destination address and message needed to deliver it. The owner can export consented newsletter records for the chosen email service. Current confirmation-email integration uses Resend when configured. Requests remain pending if it is not connected.
Unsubscribe and removal
Every newsletter must include an unsubscribe link. Signed-in beta members can also turn off updates in account preferences. Unsubscribing stops future newsletters while retaining a minimal record of the preference so the address is not accidentally re-added. Account deletion removes the associated beta and newsletter records from the active database.
Anonymous subscribers can use the private link in their email to unsubscribe. If you have only submitted a pending request and no email has arrived, it has not yet become an active newsletter subscription.
Security and retention
Account and newsletter records are stored on the hosted service and accessible through owner-controlled administration. Signup requests are validated and rate limited. Short-lived hashed request identifiers are used for abuse prevention; raw IP addresses are not stored in the signup database. Active account and subscription records are retained while needed to provide the beta and respect your choices.
Mobile apps
Android and iPhone downloads are marked Coming soon. Any future public mobile release will have privacy information reflecting its actual features. The existing Android test build stores its records locally and has no automatic cloud sync.