Privacy Policy

Who we are

This policy covers the Rudr website, desktop app, and Rudr account services. Rudr is operated by Austin Medina while the Rudr LLC formation filing is pending.

For privacy questions or requests, contact support@rudr.app.

Information Rudr handles

Account information. When you sign in, our authentication provider, Supabase, processes your sign-in identity, email address, and available profile information such as your name and avatar. We also store profile fields you choose to provide.
Synced preferences and usage. While signed in, the desktop app syncs selected app preferences and aggregate counts of the models and coding providers you use. This account sync does not upload your API keys, prompts, transcripts, or local project files.
Local work. Conversations, project references, app settings, and activity records can be stored on your device. Local storage does not mean all processing stays on your device: the services you use receive the data needed to carry out your requests.
Support reports. When you submit an issue, we receive your description, reproduction steps, account identifier, app/platform information, and the diagnostic snapshot included with that report. Review reports before sending and avoid including secrets or unnecessary personal information.
Website and service requests. Hosting, authentication, and download providers process technical information such as IP addresses, browser/device information, request times, and security logs. The website uses cookies needed to maintain sign-in and return you to the page you selected.

Profiles are private by default. If you choose to make your profile public, your public profile fields can be read by other people, including visitors without an account. Email addresses, synced preferences, and usage statistics are not part of that public profile.

Sign in with Google

Google sign-in is used to authenticate your Rudr account. It requests basic identity information: your Google account identifier, email address, and profile information such as name and picture. Signing in to Rudr does not itself grant access to your Gmail, Google Drive files, or Calendar.

We use this information to create and maintain your account, display your profile, and support account security. Supabase processes this information for authentication and account storage. We do not sell Google user data, use it for advertising, or use it to train generalized AI models.

Rudr's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

You can revoke Rudr's access through your Google Account connections. Revoking Google access does not by itself delete your Rudr account or its stored data.

AI and connected services

When you use an AI model, coding agent, voice feature, browser tool, or connected integration, the relevant provider may receive your prompts, selected files, conversation context, audio, tool inputs, and other information needed for that feature. What is sent depends on your chosen provider, enabled tools, permissions, and task.

Those providers apply their own terms, retention rules, and data-use policies, including any model-training settings on your account. Review those policies before sharing sensitive information. Features identified as on-device process the supported task locally; selecting a cloud feature sends the required information to that provider.

Storage, retention, and security

Account information is stored in Rudr's hosted services; local app data remains on your device unless a feature sends it to a provider or you share it. Service providers may process information in the United States and other countries where they operate.

We retain account information while needed to provide your account and the purposes described here. Support and operational records may be retained as needed to resolve issues, maintain security, or meet legal obligations. Retention depends on the type of information and purpose; deleted information may remain in limited backups or records until their normal expiry.

The desktop app uses operating-system encryption for persisted sign-in sessions where supported and refuses to persist a session when that encryption is unavailable. We use access controls and encrypted network connections, but no system can guarantee absolute security.

Your choices and account deletion

You can download Rudr and read these pages without an account. You can sign out to stop account sync, disconnect integrations, change provider permissions, and manage local conversations and files separately.

In desktop Settings → Account, you can export your synced profile, preferences, and aggregate usage as a JSON file, or request deletion of your cloud account. Cloud account deletion removes the account and associated synced profile, preferences, statistics, and issue reports. It does not remove local files or data retained separately by AI or integration providers.

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, object to or restrict certain processing, withdraw consent, or complain to a privacy authority. Contact support@rudr.app to make a request, including requests for information not covered by the in-app export. We may need to verify your identity.

Children and policy changes

Rudr is not directed to children under 13. If you believe a child has provided personal information, contact us so we can investigate and address it.

We may update this policy as Rudr changes. The date above identifies the latest revision. We will provide additional notice of material changes where required. You can also read our Terms of Service.