Privacy Notice

Last updated: September 24, 2026

Who is responsible for your data

The controller is Kamal Mohammad, trading as RuleAscend, Borrweg 60, 8055 Zürich, Switzerland. For privacy questions and requests, email ruleascend@gmail.com.

What RuleAscend processes

We process account information and the information you choose to record, including readiness inputs, trading rules, session reviews, results, notes and uploaded trade screenshots. The service generates process metrics and patterns from your entries. We also process subscription references and status, records of terms acceptance, timestamps needed to operate the service, and information you send when contacting support.

Why it is used

Your data is used to provide your private execution workspace, calculate process metrics, show patterns in your own history, manage access and subscriptions, keep the service secure and respond to requests. RuleAscend does not sell your personal data.

Authentication and browser storage

Account authentication is provided by Supabase. If you choose Google sign-in, Google supplies basic account information such as your verified email address and profile name to create or access your RuleAscend account. Authentication uses browser storage to maintain your session and complete sign-in.

Optional website measurement

If you allow measurement, we record a random visit reference, the referring marketing channel, visit time, and whether you start or complete the demo. A first-party cookie groups visits for 30 minutes; a second remembers the first measured visit for up to 30 days. Your choice is stored in your browser for 180 days. We do not use advertising pixels, session recordings or device fingerprinting, and our measurement records do not store IP addresses or full browsing URLs.

When you sign in or proceed to checkout after allowing measurement, the visit can be linked to your account and first successful subscription payment to evaluate our marketing. The account attribution and measurement records remain until deleted following a request or until we no longer need them for this purpose. Stripe payment records are processed separately to operate subscriptions; first-purchase counts without an attributed visit appear as direct / unknown. Hosting providers may process technical access logs separately.

You can decline optional measurement and still use the demo and product. Changing your preference stops future optional measurement on this browser and removes the measurement cookies; it does not automatically erase previously collected records. Contact us to request deletion.

Hosting and account separation

The website is hosted through OpenAI Sites. Journal records are stored using Cloudflare D1 and uploaded screenshots using Cloudflare R2. Supabase provides account authentication. These service providers process data needed to deliver their respective services.

Records are associated with your authenticated account. Server-side authorization is designed to prevent other users from accessing your journal or screenshots.

Payments and terms acceptance

Stripe processes subscription payments. RuleAscend stores Stripe references and subscription status, but not complete card details. When you agree to the terms before checkout, the accepted terms version, acceptance text and timestamp are recorded in Stripe checkout and subscription metadata. Stripe also processes payment and transaction data under its Privacy Policy.

Your choices and requests

Contact ruleascend@gmail.com to request access, correction, an export or deletion of your personal data. Where applicable, you may also request restriction of processing, object to processing or withdraw consent for future processing. We may need to verify your identity before acting on a request and will respond within the period required by applicable law.

Cancelling your subscription does not itself delete your account. When handling a deletion request, some records may need to be retained to meet legal obligations or resolve outstanding transactions. We will explain any applicable exception when responding to your request.

Readiness information

Readiness inputs can reveal sensitive information, including information about health. Calling these features non-medical does not remove that sensitivity. Agreement to the Terms and Conditions does not constitute separate explicit consent to health-data processing. Avoid including unnecessary health information or sensitive information about other people in notes or screenshots.

Questions and complaints

You can contact us using the details above and may raise a concern with the Swiss Federal Data Protection and Information Commissioner or another competent data protection authority.