Privacy and data use

Practice sessions

Filters and the random seed are included in your session URL. Sharing that URL also shares those settings. The practice tool does not upload your drawings or access your camera or microphone.

Browser-saved poses

Saving without an account stores pose identifiers and save times in this browser. Clearing browser data may remove them. When browser storage is unavailable, changes last only for the current page session. A browser-owned practice round stores a separate list of pose identifiers in tab storage; it does not preserve timer progress. Account-owned rounds stay in page memory and cannot be restored after a full page reload.

Optional accounts and sync

When account sync is enabled, Google provides authentication through Supabase Auth. The application associates the verified Google identity with a drawing account and stores saved pose identifiers, server save times, collection versions, import receipts and session status. Google and Supabase may process identity information, including profile or email information, as part of authentication. No marketing subscription is created.

Browser-saved poses are uploaded only after an explicit import confirmation. Import adds to your account and leaves the browser list unchanged. Account lists are kept in page memory, not copied into the browser-saved list. Cloud changes require a connection; they are not queued for later offline replay.

After you confirm an import, this tab may temporarily store your drawing account identifier, the import receipt identifier and its expiry so you can check the result after refreshing. This marker contains no pose list, email or authentication token. It is cleared when the import is resolved, you sign out, your session expires or the account changes; expired markers are discarded when read. Checking a receipt does not submit another import. Retrying requires an explicit action.

Signing out and deleting an account

The account page provides sign-out and deletion. Deletion requires a fresh Google sign-in for the same identity and a final confirmation. It removes the drawing account, cloud-saved poses, import receipts and application sessions. Separate browser-saved poses and the Google account itself are not deleted. If the same authentication identity is needed for a separate site-administration role, that identity is retained for that role.

A deletion that cannot finish remains pending and blocks cloud access until cleanup succeeds. A browser-only deletion ticket permits retries for seven days; contact the site operator if it expires while deletion is pending. A minimal completion receipt, without the user identifier, supports retries until expiry. Import receipts are accepted for seven days; expired receipts and completed deletion records are removed through operational cleanup. Provider logs and backups follow the providers’ configured retention schedules and are not promised to disappear immediately.

Image reports

A report stores the pose identifier, reason, optional note, and submission time. The server uses a keyed hash of the source IP address to limit repeat submissions; the report record stores that hash rather than the raw IP. Do not put personal or sensitive information in a report note. Reports are restricted to the site’s backend and authorized administrators.

Analytics, when enabled

Production deployments may use Google Analytics for page and practice events, and Microsoft Clarity for interaction analysis and session playback. These services may use cookies or identifiers. Practice events include configuration, pose identifiers, and active practice time; report notes are not included in these events.

See Google Analytics data information and Microsoft Clarity’s collection details. Browser privacy controls can block or remove analytics cookies.

The account page does not initialize analytics or session replay. Authentication callbacks return server redirects without rendering tracking scripts. New account events do not include account identifiers, names, email addresses, authentication tokens or whole saved-pose lists.

Hosting and administration

Hosting, image delivery, and database services process requests to operate the site and may keep operational logs, including connection information. Administrator sign-in uses authentication cookies. Provider retention settings and any legal requests are handled by the site operator; this page does not promise a retention period that has not been configured.

Questions

Available support channels and image-reporting steps are listed on the contact page.