Privacy Notice

Information used by MethodMark

MethodMark uses account identity details, an age self-attestation, access requests, journal records, screenshots, preferences, and feedback that a user chooses to submit so the web beta can provide and secure its stated features.

Feedback includes the report text and basic build, page, and browser diagnostics. Journal contents are not attached automatically. To track fixes, MethodMark may copy a feedback report and basic diagnostics into a private issue tracker hosted by GitHub. Your username and account email address are not attached, and email addresses written in the report are removed.

Cloud and browser storage

MethodMark uses Supabase for authentication, its cloud database, and private object storage (file storage). Journal data and screenshot files are kept behind account-scoped access controls and are not shared with other MethodMark users.

A user-scoped browser cache supports responsiveness and recovery; it is not the authoritative store and does not make the web beta device-only.

Operation, administration, and support

MethodMark is operated from Luxembourg. The operator and infrastructure providers may process information where technically necessary to run, secure, troubleshoot, and support the beta.

Staff administration runs in separate tools and does not expose personal trading records, balances, notes, screenshots, passwords, tokens, recovery secrets, or raw authentication metadata to owners or moderators during routine administration. Staff access requires two-factor authentication.

MethodMark does not claim end-to-end encryption or zero-knowledge storage. Contact support@methodmark.app with product, account, or privacy questions.

Deletion and founding continuity

The account-removal flow removes the account identity, cloud journal, settings, and feedback, and attempts to remove available screenshot data. If screenshot cleanup cannot finish after identity deletion, MethodMark records that cleanup as pending rather than reporting complete removal. Feedback already copied into the issue tracker is not removed automatically; contact support@methodmark.app to have it removed.

If a permanent founding grant exists, it is kept separately as a pseudonymous founding continuity record so deletion does not erase or reissue that place. Retained continuity and audit identifiers are pseudonymous operational records, not anonymous data.

A founding tester must create and retain a recovery certificate before deleting an account so the permanent grant can later be linked to a new account.

Questions and changes

Contact support@methodmark.app with questions or requests. Material changes to this notice require a new version before new acceptance records are collected.