Privacy Policy

Last updated: July 19, 2026

This policy is authored in Japanese. Translations are for reference only; if there is any discrepancy, the Japanese version prevails.

RideRIX handles user data only to the extent necessary for training management, Intervals.icu integration, AI integration, and payments.

Information we collect

RideRIX collects or stores the following information.

Account information: email address, authentication credentials, plan, Terms of Service acceptance status, and information needed for login and integration
Training information: activities, planned workouts, workout library, training load, power, heart rate, cadence, distance, time, elevation gain, RPE, notes, tags, and activity type
Upload data: FIT files and activity time-series data. During bulk FIT imports, original files are stored only for as long as processing requires.
Condition information: weight, resting heart rate, HRV, sleep, subjective fatigue, stress, mood, readiness, and entries about injuries or poor condition
Goal and coaching information: goals, training phases, weekly reviews, and AI suggestions or saved notes
Integration service information: activities, plans, settings, and wellness information retrieved from external services the user has permitted, such as Intervals.icu
Technical information: OAuth tokens, connected app information, API usage history, error information, and logs necessary to maintain security

Purpose of use

We use the collected information for the following purposes.

When you sign up, we collect your initial referring domain, UTM parameters, pages visited, and broad categories for device type, operating system, browser, and language to improve the service and analyze usage. We do not store IP addresses, raw User-Agent values, screen resolution, device-specific IDs, or query parameters from referrer URLs for this measurement. Details linked to an individual are deleted after 90 days, and anonymous daily aggregates are deleted after 24 months.

To display and manage training records, plans, goals, condition, and analysis results
To sync with external services the user has permitted, such as Intervals.icu
To provide RideRIX data within the permitted scope to MCP-compatible AI clients the user has authorized via OAuth, and to perform create/update operations based on the user's instructions
To provide auxiliary features such as AI training consultation, weekly reviews, plan creation, note creation, and condition recording
For troubleshooting, maintaining security, preventing misuse, improving the service, and responding to inquiries
To manage plan limits, usage limits, billing, and contracts

MCP-compatible AI client integration

RideRIX provides data within the permitted scope and plan range from MCP (Model Context Protocol)-compatible AI clients only when the user has explicitly authorized it via OAuth.

With MCP integration, AI clients can reference activities, planned workouts, condition, FTP, weight, goals, weekly reviews, and more. In addition, on the Standard plan or higher, they may be able to create, update, and delete planned workouts, assessments of completed activities, goals, condition records, and more based on the user's instructions.

RideRIX cannot control whether data provided to external AI clients via MCP integration is stored, used, used for training, or shared on the external AI client's side. If you use an external AI client, please also review the provider's terms of service and privacy policy.

Users can revoke MCP integration authorization from Connected Apps on the RideRIX settings screen. Once revoked, the target AI client can no longer access RideRIX data.

Data sent to AI services

In RideRIX's in-app AI consultations, your question and the contextual information needed to answer it, such as training, plan, and condition data, may be sent to OpenAI, L.L.C., the AI model provider.

When you select an activity and choose to continue in ChatGPT or Grok, a prompt containing the selected activity's summary, notes, and any additional question is sent to the destination AI service. This occurs only through your explicit action.

For these AI services and MCP-compatible AI clients, the storage, use, use for model training, and sharing of data after it is sent are governed by each provider's terms and privacy policy. RideRIX cannot control how external AI services handle the data.

Intervals.icu integration

When a user permits Intervals.icu integration, RideRIX retrieves, within the permitted scope, activities, planned workouts, workout library, settings such as FTP, and wellness information such as weight, resting heart rate, HRV, sleep, and subjective fatigue, and uses them for training records, plan management, analysis, and AI consultation.

Planned workouts created or edited by the user in RideRIX may be sent to Intervals.icu depending on the user's actions or settings. Intervals.icu integration can be disconnected from the RideRIX settings screen, and you can also revoke the app's permission on the Intervals.icu settings screen.

Provision to third parties

RideRIX does not provide personal data to third parties except where required by law, where the user has explicitly permitted integration, or where a subcontractor necessary for providing the service handles it to the minimum extent necessary.

Parties that may receive or process data include MCP-compatible AI clients and Intervals.icu when authorized by the user; OpenAI, L.L.C. for in-app AI; Stripe, Inc. for payments; Supabase, Inc. for storage of FIT files and activity time-series data; and providers required to operate services such as authentication, hosting, databases, email delivery, and log monitoring.

RideRIX does not sell user data for third-party advertising or third parties' own marketing purposes.

The providers listed above may include parties that process data outside Japan. RideRIX limits such processing to what is necessary to provide the service and enables users to review the relevant service's policies when sending data directly to an external service.

Use of cookies and similar technologies

RideRIX uses cookies and similar technologies to keep users signed in, prevent misuse, save language preferences, and optimize display. Cookies used to maintain login sessions are stored for up to 60 days, and language preference cookies for up to one year. Disabling cookies in your browser may prevent login and certain other features from working.

Google reCAPTCHA may be used when an account is created to prevent misuse. Information processed by reCAPTCHA is governed by Google's Privacy Policy and Terms of Service.

Retention period

RideRIX retains user data required to provide the service while an account is active. For Free plans, core account information, training information, integration tokens, and saved data are deleted after account closure is completed. For Standard plans, they are deleted after the subscription period ends. This does not apply to information that must be retained for legal compliance, billing, misuse prevention, dispute handling, or backup integrity.

OAuth tokens and external service integration information are deleted or invalidated upon disconnection, expiration, account deletion, or when no longer needed, except to the extent necessary for operating the service.

User control

Users can view, update, and delete their own training records, plans, goals, condition, and integration settings within RideRIX. Integration with MCP-compatible AI clients and Intervals.icu can be disconnected from the settings screen.

You can delete your account from Settings. Requests concerning data deletion, disclosure, correction, suspension of use, or privacy can be submitted through the contact form. We may ask you to verify your registered email address or provide other information to confirm your identity.

Operator and contact

RideRIX is operated by Monohito (Masahiko Kaimori). For the operator's address and other business information, see the Legal Disclosure under Japan's Specified Commercial Transactions Act.

Security management

RideRIX protects authentication credentials, OAuth tokens, external service integration information, and training data through access control, permission management, log monitoring, and granting the minimum necessary privileges.

Notes

Output from RideRIX's AI features and MCP integration is reference information to assist training decisions. It is not intended for medical diagnosis, treatment, or emergency response. If you have concerns about your health, please consult a professional such as a physician.

Changes

RideRIX may change this policy as needed. When there are significant changes, we will notify you by posting on the service or by other appropriate means.

Contact

For privacy-related inquiries, please contact usContact formhere. General usage is also summarized in theFAQ.