Rushed AI

This Privacy Policy explains how Rushed AI ("Rushed", "we", "us", or "our") collects, uses, stores, and shares information when you use the Rushed AI website, dashboard, coding workspace, billing flows, GitHub import/export features, and related services (collectively, the "Services").

1. Scope

This Privacy Policy applies to information processed through:

the public website and landing pages;
account creation and authentication;
project creation, storage, editing, preview, and export features;
AI conversation and quick-edit features;
subscription billing and credit-pack purchases;
support, contact, and product communications.

2. Information We Collect

We collect the following categories of information.

A. Account and identity data

When you sign up or sign in, we process account and identity information provided through our authentication provider, including:

your user identifier;
your email address, if available from the identity provider;
basic account state needed to authenticate and authorize access.

B. Billing and subscription data

If you subscribe or purchase credits, we process billing-related records such as:

customer identifiers from our payment processor;
subscription identifiers;
plan tier, subscription status, and renewal period data;
purchased credit pack information;
transaction history, including credits granted, used, or refunded;
billing metadata needed to reconcile purchases with your account.

We do not intend to store your full payment card number in the application database. Payment details are handled by our payment processor.

C. Project and workspace data

When you use the coding workspace, we process:

project names and metadata;
project settings such as install and development commands;
files and folders you create, upload, import, or edit;
file contents, including source code and other text content;
binary files stored through our backend storage layer;
repository import/export status and repository destination URLs.

D. Conversation and prompt data

When you use AI features, we process:

prompts and instructions you submit;
AI-generated responses;
conversation titles;
message processing state;
token usage and credit-consumption metadata associated with AI requests.

E. GitHub-related data

If you connect GitHub or use GitHub import/export features, we may process:

GitHub OAuth access tokens made available through your connected account provider;
repository owner, name, visibility, description, and tree structure;
repository file contents needed to import into your workspace;
repository URLs created when you export a project.

F. URL and documentation scraping inputs

If you provide URLs in prompts or quick-edit instructions, we may retrieve and process content from those URLs in order to answer your request or apply edits.

G. Usage, logs, and technical data

We may process technical and operational data such as:

request timestamps;
error logs;
task and webhook payloads needed for billing and background job handling;
approximate usage metrics tied to credits, tokens, and feature access;
browser and device data typically made available through web requests.

3. How We Use Information

We use information to:

provide authentication and secure access to your account;
create, store, update, display, and delete projects, files, and conversations;
generate AI responses and code edits;
import repositories from GitHub and export project files to GitHub;
run browser-based previews of your project;
meter usage, deduct credits, enforce plan limits, and administer subscriptions;
process checkout and customer-portal requests;
detect failures, debug issues, maintain service integrity, and prevent abuse;
communicate with you about product use, support, billing, and account issues;
comply with legal obligations and enforce our terms.

4. AI and Automated Processing

Rushed AI includes AI-powered coding features. To provide those features, we may send prompts, code snippets, file contents, conversation context, and related instructions to third-party model providers and tooling providers that support the Services.

This can include:

AI message processing for project conversations;
quick-edit requests for selected code;
title generation for conversations;
retrieval of external documentation or URLs you provide.

You should not submit sensitive information unless you are comfortable with that information being processed for these purposes.

5. Service Providers and Third Parties

Based on the current implementation, the Services rely on third-party providers that may process information on our behalf or as independent service providers, including:

Clerk for authentication and connected account access;
Convex for application backend, database, storage, and server-side functions;
Anthropic-backed model APIs and related AI tooling for code generation and editing;
Inngest for background job orchestration;
GitHub for repository import/export functionality;
Firecrawl for scraping URL content you provide;
Dodo Payments for checkout, subscriptions, customer portal, and payment webhooks;
WebContainer technology to run project previews in the browser.

We may share information with these providers to the extent reasonably necessary to operate the Services.

6. GitHub Access

If you connect GitHub, we use the access made available through your authenticated connection to:

read repository contents you choose to import; and
create repositories and upload project files when you choose to export.

We do not need GitHub access unless you choose to use those features.

7. Credits, Usage Tracking, and Internal Records

We maintain internal records to track:

current credit balance;
monthly plan credits;
daily credit and token limits;
credit pack balances;
transaction history describing credits granted or deducted;
plan status and renewal state.

We use this information to deliver the product, enforce plan restrictions, and support billing operations.

8. Data Retention

We retain information for as long as reasonably necessary to provide the Services, maintain legitimate business records, resolve disputes, enforce agreements, and comply with legal obligations.

Retention may vary by data type. For example:

active project, file, and conversation data may be retained while your account is active;
billing and transaction records may be retained for accounting, audit, tax, and fraud-prevention purposes;
logs may be retained for shorter operational periods unless needed longer for security or legal reasons.

If you delete a project through the product, the current implementation attempts to delete the associated project records, files, conversations, and messages from the application database. Some data may persist temporarily in backups, logs, or provider systems.

9. Data Security

We use technical and organizational measures intended to protect information from unauthorized access, loss, misuse, or alteration. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

You are responsible for maintaining the security of your account credentials and for controlling what content you submit to the Services.

10. International Processing

Your information may be processed in countries other than the country where you live, depending on the location of our infrastructure and service providers.

11. Children

The Services are not intended for children under 13, and we do not knowingly collect personal information from children under 13.

12. Your Choices

Depending on your location and applicable law, you may have rights to:

access certain personal information we hold about you;
request correction of inaccurate information;
request deletion of certain information;
object to or restrict certain processing;
request portability of certain information.

You may also be able to:

disconnect third-party integrations such as GitHub through the relevant provider;
stop using billing features;
delete projects and other content from within the product.

13. Cookies and Similar Technologies

The application may rely on cookies or similar technologies through the framework, authentication provider, theme preferences, or embedded providers to keep you signed in, maintain security, and support basic site functionality.

If we introduce analytics, advertising, or other optional tracking technologies in the future, we will update this Privacy Policy as required.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we may revise the "Last updated" date and take additional steps if required by law.

15. Contact

Questions, requests, or complaints about this Privacy Policy may be submitted through the contact page provided with the Services.