Cookie Policy

RuleGate uses cookies and similar browser storage for secure sessions, account continuity, local Demo Preview data, theme preferences, checkout integrity, and consent choices. Some storage is necessary for the Service; optional categories require your choice.

The current consent version is 1.2. A material change to purposes or categories will increment this version and request a new choice.

Always active. This category supports authentication, session continuity, account security, checkout integrity, fraud and abuse prevention, consent storage, and essential local application state.

Rejecting optional categories does not disable Supabase authentication or prevent use of RuleGate. The first-party consent cookie is named rulegate_consent_v1 and normally lasts up to 180 days unless replaced, cleared, or a new consent version is required.

Optional preference storage may remember display, theme, timezone, or convenience settings that are not essential. User-requested settings saved as part of an account or Demo Preview may still be needed to provide the requested feature.

With Analytics consent, RuleGate loads Google Analytics 4 to measure sanitized page views and the demo, sign-up, and confirmed-purchase funnel. The Google tag stays unloaded before consent. It does not receive email addresses, names, trading records, broker credentials, or full page query strings.

GA4 may set first-party _ga cookies for measurement. RuleGate disables the tag and clears its accessible analytics cookies when you withdraw Analytics consent or the consent record is no longer valid. Advertising storage and personalization remain denied.

With Marketing consent, RuleGate may load the Meta Pixel to measure our own advertising campaigns, such as the RuleGate Challenge. It records page views and the challenge funnel events “application submitted” and “free access started”. The Pixel stays unloaded before consent.

For the same consented events, RuleGate's server may also send the event to Meta's Conversions API with a hashed (SHA-256) email address, IP address and browser user agent, so that Meta can match the event and count it only once. Server events are sent only when your Marketing consent is recorded.

Meta may set first-party _fbp and _fbc cookies. RuleGate revokes Pixel consent and clears these cookies when you withdraw Marketing consent. Private journals, trading behaviour, screenshots, and integration credentials are never sent to Meta or other advertisers, and RuleGate does not use private trading data for behavioural targeting.

• Accept all enables Preferences, Analytics, and Marketing.
• Reject non-essential leaves every optional category off.
• Customize lets you choose each optional category separately.
• No optional category is preselected for a first-time visitor.
• You can reopen Cookie settings and withdraw consent at any time.

When Analytics consent is withdrawn, RuleGate disables GA4, stops new analytics events, and clears accessible first-party GA4 cookies. Strictly necessary authentication, security, and consent storage remain. Browser controls may be needed to clear copies already held by external providers.

You can also clear cookies or local storage in browser settings, which may sign you out, reset consent, remove Demo Preview data, or reset preferences. For consent questions, use the RuleGate Contact page or email privacy@rulegate.app.