R0 · WEBSITE & DESKTOP IDE

Privacy Policy

Draft · last updated October 29, 2026

This is a product-specific draft, not a final privacy notice. The project operator must complete the marked details and verify the actual production, desktop, hosting, and provider data practices before relying on or publishing it.

1. Scope and who is responsible

This notice describes information handled through the r0 website and r0 desktop development environment (together, “r0”). It does not replace the privacy notices of Google, GitHub, Supabase, AI providers, extension publishers, or other services you choose to connect. The responsible operator is [operator: insert legal name and contact address] (“r0,” “we,” or “us”).

2. Information associated with website accounts

If you use the website account page, Supabase Auth processes your email address and authentication information to send sign-in links, confirm your address, maintain your session, and support sign-out. If you choose Google or GitHub sign-in, the provider and Supabase may share account identifiers and profile information needed to complete authentication. The current site does not create a separate profile database.

3. Browser storage and website requests

The website stores your selected theme preference in browser storage. Supabase’s browser client also persists the authentication session in browser storage to keep you signed in and complete email-link or OAuth redirects. You can sign out from the account panel or clear site storage in your browser. Website hosting and security infrastructure may process request and device information, such as IP address, browser details, and access logs, to deliver and protect the site. The operator must confirm the hosting provider’s logging, retention, and analytics settings before publication.

4. Desktop app, settings, and project files

r0 is a desktop development environment for editing and navigating code, using terminals, Git workflows, database tools, extensions, language integrations, and AI or agent features. Project files and editor settings are used on your device for local development. The website account feature does not upload local source code. This statement does not cover content you choose to send through an AI provider, GitHub, a remote workspace, collaboration, a database connection, an extension, or another connected service.

The desktop IDE currently manages an account session separately from the website account. Signing into the website does not by itself sign you into the desktop app or connect an AI provider or GitHub.

5. AI providers and agent features

If you use an AI or agent feature, information you provide and project context you choose to include—such as prompts, selected files, code, terminal output, or tool results—may be sent to the provider or service configured for that feature. The provider may process that information under its own terms and privacy notice. Local model use may send requests to a local runtime or to an endpoint you configure. Review the selected provider, model, permissions, and provider data controls before using these features with confidential or personal information.

Agent features may read or change files and may use tools according to the permissions and confirmations available in your r0 version. Review proposed actions and outputs. Do not include secrets or personal information in prompts unless you have determined that the selected processing is appropriate.

6. GitHub and other integrations

GitHub repository browsing, Git operations, pull requests, and other connected-service features require separate authorization. When you connect an account, r0 and the provider process the account and permission information needed for the requested feature. Repository contents or related metadata may be transmitted to GitHub or another service when you use its features. The access granted and the provider’s use of information are governed by that provider’s privacy notice and your authorization choices.

7. Why information is used

Information is used to provide and secure account sign-in, respond to support and privacy requests, operate and maintain the website and desktop features you choose to use, prevent abuse, and meet legal obligations. The operator must identify any additional analytics, product improvement, marketing, or diagnostic purposes and the applicable legal basis before collecting data for them.

8. Service providers and sharing

Information may be processed by providers needed to deliver a feature you use, including Supabase for website authentication, website hosting and delivery providers, Google or GitHub when enabled, and the AI, database, extension, or collaboration services you connect. We do not sell account information through the website account feature. The operator must replace this summary with a complete current provider list and explain any other disclosures, including legal requests or a change in ownership.

9. International processing

r0’s providers may process information in countries other than your own. The operator must identify the Supabase project region, hosting region, provider locations, and any transfer safeguards required by the laws applicable to the service.

10. Retention and account deletion

Authentication records are retained by the configured Supabase project under its settings and policies. Information sent to third-party providers is subject to their retention practices. The project operator has not documented final retention periods or an account-deletion workflow in this repository. Contact [operator: insert privacy contact] to ask about access, correction, or deletion; the operator must implement and document the applicable process before production launch.

11. Security

We use the security controls available in the application and its service providers to protect information. No internet transmission or storage system can be guaranteed secure. Keep your email account, provider credentials, and device secure, and report suspected account compromise using the contact details below.

12. Your choices and rights

You can choose whether to use a website account, connect an external provider, or use an AI feature. You may sign out, disconnect providers where the relevant feature supports it, and control browser storage through your device. Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing, or to complain to a regulator. Contact the operator to make a request; the operator must add the correct rights, legal bases, response process, and regulator details for the jurisdictions served.

13. Children

r0 is a software development tool and is not directed to children who are not legally able to use the service in their location. The operator must set and publish the applicable minimum age and process for handling information collected from children before public launch.

14. Changes and contact

We may update this notice when r0 or its data practices change. The date above indicates the latest revision. For questions or privacy requests, use the contact method listed on the project maintainer’s website, or contact [operator: insert privacy email or address].

Before publication, fill in the legal operator, contact, age, project and hosting regions, complete provider list, purposes and legal bases, retention periods, account deletion process, applicable user rights, and diagnostic/analytics behavior. Confirm the statements above against the shipped desktop builds and production configuration.