Privacy Policy

Information We Collect

When you create an account, authentication is provided by Clerk. Clerk may process account identifiers such as your user ID, email address, profile name, avatar, authentication providers, and account security events.

When you use the app, we store the knowledge journal data you create: technique or system logs, partners, personal knowledge nodes, notes, timestamps, and related app metadata.

If you report a problem with public match data, we store your account user ID, the report category and explanation, any supporting URL you provide, review status, and timestamps. Reports are private to administrators and are used to investigate and correct reference data.

The public website uses Vercel Analytics and Speed Insights. With your permission, the website also uses PostHog product analytics, privacy-masked session replay, and JavaScript error diagnostics. The mobile app's optional PostHog product analytics starts off. If you allow it, the app sends lifecycle events and privacy-sanitized screen names. These optional events use a device/install identifier and are associated with your account user ID when you are signed in.

Separately, the mobile app sends minimized JavaScript crash reports to PostHog for operational reliability regardless of the product analytics choice. These reports use a new random identifier each app process launch and include app/build, operating-system, device-class, exception-type, and stack-frame data needed to diagnose the failure. They are not intentionally linked to your account. Exception messages, source context, local variables, console logs, replay, account properties, email, journal contents, notes, partner names, search text, and route parameters are removed before JavaScript crash events are queued. Native crash reports remain disabled because their current vendor path cannot enforce the same filter.

PostHog processes mobile telemetry in its EU region. Like other internet services, PostHog can receive network connection data such as an IP address when a report is delivered. Retention, access, and IP-handling settings are reviewed before release. Website inputs and visible text are masked in session replays before they leave your browser.

Legal Bases and Your Choices

We process account and journal data to provide the service you request. Optional mobile product analytics is processed on the basis of your consent. You may decline it without losing app functionality, enable it later, or withdraw consent at any time under Settings → Share Analytics. Withdrawal stops future optional analytics collection on that device and does not affect the lawfulness of processing performed before withdrawal.

Minimized mobile crash diagnostics are processed separately to maintain app reliability and are not controlled by the product analytics preference. You may object to this processing or ask a privacy question using the contact address below. The operational lawful basis and retention period are subject to final legal review before this mobile release.

For access, deletion, objection, or other privacy requests concerning data already held by our service providers, contact us using the email below.

How We Use Information

We use your information to authenticate your account, sync your journal data, show personal knowledge patterns, support account deletion, review reported match-data problems, understand product usage, improve reliability, and respond to support requests.

Data Sharing

We do not sell your personal information. We use service providers that are necessary to run the product, including Clerk for authentication, Supabase for app data storage, PostHog for product analytics and reliability diagnostics, and Vercel for hosting and website analytics.

Account Deletion

You can request account deletion in the mobile app Settings screen. Deletion is intended to remove your logs, partners, personal knowledge edges, and personal knowledge nodes before deleting the authentication account.

Contact

For privacy questions or support requests, email jiujitsureference@gmail.com.