Privacy Policy

RodiumAI, Inc. ("we", "us", "our") operates an AI infrastructure platform at https://rodiumai.io. RodiumAI, Inc. is a corporation organized under the laws of the State of Delaware, United States. Registered office: 251 Little Falls Drive, Wilmington, New Castle County, Delaware 19808. We are the controller of the personal data described in this Policy. We are committed to handling your personal data responsibly.

This Policy covers all our services (the "Services"): the website and dashboard, the API Gateway, Forge (our AI site and app builder), RodiumAi Code (the command-line tool, the desktop app and the VS Code and Cursor extension), the MCP server, our SDKs and our support channels.

Privacy inquiries: legal@rodiumai.io

2.1 Account registration

When you create an account we collect: full name, email address, country of residence, and password (stored only as a one-way cryptographic hash, never in plaintext). Optional: phone number and profile details you choose to provide.

2.1.1 Sign in with Google or GitHub. When you choose social sign-in we receive from the identity provider (via Google Firebase Authentication): email address, display name, provider user identifier, and profile photo URL if available. We use this solely to authenticate your account without a RodiumAI password. Google (policies.google.com/privacy) and GitHub (docs.github.com/en/site-policy/privacy-policies/github-privacy-statement) process your sign-in under their own policies.

2.1.2 Sessions and security. When you sign in we record the IP address and the browser or device identifier (user agent) of the session, and we set a device cookie. We use them to detect unusual sign-ins, to ask for an email verification code when you sign in from a new device, and to revoke sessions when needed. These records are kept with your account for security and fraud prevention.

2.2 Billing and payments

When you purchase RODI credits or a paid plan we collect transaction amounts, timestamps, country and local currency, payment method type, and operator or gateway reference numbers where applicable. We do not store full card numbers or wallet credentials, and we do not keep a payment method on file: regulated payment processors handle sensitive payment credentials.

2.2.1 Automated recharge (checkout). When you pay through our integrated checkout, you complete payment on the payment provider's page or in your Mobile Money operator's flow. To start the payment we send the provider the amount and your name, your email address and, for Mobile Money, your phone number. Depending on your country and method we use providers such as FedaPay, KPay, Moolre (Ghana) and IzichangePay (crypto-asset payments). We receive confirmation metadata (amount, status, gateway reference) after payment. Providers and operators process wallet credentials on their own systems.

2.2.2 Manual recharge (where offered). If you transfer funds to a displayed account and submit proof, we collect: sender name as shown on your mobile wallet, external transaction ID from your operator, and a screenshot or image of your payment proof, stored in our object storage (Amazon S3). Proof images may show additional personal data visible on your phone screen (balances, phone numbers, third-party names). Authorized RodiumAI staff review proofs solely to validate or reject the recharge.

2.2.3 Promotional programs. When you redeem a promo code we store the code entered and credit applied. For referrals we store the referral code used and the link between referrer and referee accounts. These programs do not involve your API Gateway prompt content.

2.2.4 LinkSell (beta). If you use LinkSell to pay a third-party checkout link, you give us that link and your country. Our systems open the link to read the merchant, product, billing interval and amount, and an AI vision model may read a screenshot of the checkout page to extract them. Our team then completes the merchant-side payment for you. The link and the extracted details are stored with your request, next to the payment and invoice records.

2.2.5 Plans. Paid Forge and RodiumAi Code plans are prepaid. We store your plan, its period, and your FRODI allowance and usage. Plans do not renew automatically.

2.3 Usage and analytics

• API request metadata (timestamps, model slug, token counts, latency, status, RODI or FRODI cost).
• API key activity logs (key identifier, not the secret, which we keep only as a one-way hash).
• Gateway request logs: IP address, user agent, request path, status code, model and error code. Never the request or response body.
• Technical error logs: status codes and short error messages returned by upstream providers, used to fix incidents. They are not designed to contain your prompts.
• Browser type, device type, and IP address for security and fraud prevention.
• Product analytics on the web apps (website, dashboard and Forge), only if you accept analytics: PostHog (EU cloud) and, on the website, Google Analytics. We look at pages viewed, clicks and form submissions on interface elements (never what you type), page load performance, errors, and your account identifier and role once you are signed in. We do not send your name or email address to PostHog, we do not record sessions (session replay is off), and the page addresses we send are stripped of tokens, codes and fragments. See section 8.
• Product analytics in RodiumAi Code (see section 2.5).
• Session data and cookies (see section 8).

2.4 Forge (AI site and app builder)

When you use Forge we store the content needed to provide the product, including:

• Your Forge account details (name, email, avatar) and the link to your RodiumAI account, including the encrypted access credentials we use to read your wallet and API key list.
• Builder chat history and prompts you send to generate or edit projects.
• Project source files, assets, and generated code.
• Preview and published site content.
• Custom domain configurations and related DNS or SSL status metadata.
• Attachments and uploads you add to a Forge project.
• Agent run metadata (status, steps, errors) used for debugging and support.

Forge generations that call models are routed to upstream providers under the same catalogue rules as the API Gateway. Upstream vendors may process that content under their own policies. Authorized RodiumAI staff can access Forge project content, including chat messages, only to provide support, investigate abuse or security incidents, and operate the service.

Published sites are public by design. A generated site may load libraries from public CDNs (such as esm.sh) and integrations you add (maps, analytics, payment widgets); those services receive your visitors' data under their own policies, and you are responsible for informing your visitors.

2.5 RodiumAi Code (command-line tool, desktop app, VS Code and Cursor extension)

RodiumAi Code runs on your device and shares one agent across its three forms. It reads the folders you open, edits files and runs commands there.

• What stays on your device: your project files, your session history, checkpoints and settings, stored in a RodiumAI folder in your home directory and in the project you open. We do not receive them. If you use your own API key, it is stored on your device.
• What is sent to our Gateway when you ask something: your messages and the files, command outputs and other context the agent includes in the request, so a model can answer. The Gateway forwards it to the upstream and does not store it (see the callout above). Do not open folders containing data you do not want sent to a model.
• Sign-in: you sign in with your RodiumAI account through our login page. The session tokens are stored on your device. Usage is metered in RODI or FRODI like any other API use.
• Updates: the desktop app checks GitHub Releases for new versions; the command-line tool and the extension are updated through npm and the extension marketplaces, whose operators see ordinary download information.
• Third-party tools: MCP servers, plugins and skills you add run under their own terms and receive whatever data you send to them.

Product analytics. By default RodiumAi Code sends usage events to PostHog (EU cloud) to find bugs and improve the product: app start, sessions started, the outcome of sign-in and sign-out, the provider selected, tasks started, completed or cancelled, the model used and token counts, the names of tools used (tools from MCP servers are only counted as "mcp"), scheduled runs, and error categories (never the error text). The first time you run each app, a notice tells you this and how to turn it off. Each event carries the app (CLI, desktop or extension), its version, your operating system, and either your RodiumAI account identifier (once you are signed in) or a random identifier generated on your device. We never collect your prompts or the model's answers, file names or paths, code, command lines, git remotes or branches, error message text, your email address or your API keys, and IP geolocation is turned off.

2.6 MCP server and SDKs

The rodiumai-mcp package runs on your machine, talks to the API Gateway with your own API key, and saves the files it generates on your machine. It does not send analytics to us. Our official SDKs (JavaScript, Python, Laravel) only make the API requests you ask for and do not send analytics either.

2.7 Support and contact

When you contact us (support ticket, assistant, contact form, enterprise or ambassador inquiry) we collect your name, email address, company, your message and attachments, the history of the conversation, and the technical context you send. Support conversations are stored in our database and copied to Google Firebase (Firestore) to deliver messages in real time. Our team may use AI models, through our own gateway, to help read, translate or draft replies, so the text of a ticket can be processed by a model.

We do not collect government ID numbers, biometrics, or sensitive categories (health, religion, political opinions) unless you voluntarily include them in support messages or Forge project content.

• Account management and authentication.
• Delivering the Services: API routing, RODI and FRODI billing, usage dashboards, Forge project building, preview and publishing, and RodiumAi Code.
• Transactional email (verification, team invites, recharge submitted/approved/rejected, low RODI balance, promo and referral credits credited).
• Customer support.
• Security, fraud prevention, and abuse detection.
• Product analytics and platform improvement.
• Legal compliance where required.

We do not sell, rent, or trade your personal data to third parties for their marketing, and we do not use your API or Code content to train models.

• Contractual necessity: to provide the Services you requested.
• Legitimate interest: security, fraud prevention, and improvement of our products, including the usage events of RodiumAi Code, which you can switch off at any time.
• Consent: analytics on our web apps (PostHog and Google Analytics), marketing email, and any other case where the law requires it. You can withdraw consent at any time.
• Legal obligation: where applicable law requires processing.

5.1 Model routing (OpenRouter, Azure, Amazon Bedrock, and direct upstreams)

Requests to https://api.rodiumai.io/v1 are routed to a healthy upstream configured for your selected catalogue model. Depending on the model, execution goes through OpenRouter (openrouter.ai/privacy), a direct API integration (Anthropic, OpenAI, Google, DeepSeek, Groq), Microsoft Azure AI Foundry (azure.microsoft.com/products/ai-foundry) or Amazon Bedrock (aws.amazon.com/bedrock). Your API prompts and inputs are transmitted only to the upstream that runs the call. RodiumAI does not retain that API content. Each upstream and underlying model vendor processes data under its own privacy policy.

Two features pass part of a request to one more model than the one you selected. Automatic model selection (for example the rodiumai/smart model) sends up to the first 4,000 characters of your prompt to a small classification model, through our own gateway, to pick the best model for the task. Custom models with a knowledge base use an OpenAI embedding model to index your documents and to search them with your latest message.

5.2 Underlying model providers

Depending on the model you select, your data may be processed by the original provider or aggregator, including:

• OpenRouter: openrouter.ai/privacy
• OpenAI: openai.com/policies/privacy-policy
• Anthropic: anthropic.com/privacy
• Google (Gemini, Vertex AI): policies.google.com/privacy
• DeepSeek: deepseek.com/privacy
• MiniMax: minimax.io/privacy-policy
• Microsoft (Azure AI Foundry): privacy.microsoft.com/privacystatement
• Amazon Web Services (Amazon Bedrock): aws.amazon.com/privacy
• Mistral AI: mistral.ai/privacy
• Meta: www.facebook.com/privacy/policy
• xAI: x.ai/legal/privacy
• Groq: groq.com/privacy

Our catalogue includes models from the families above and evolves over time. Some models (e.g. Meta Llama, Mistral, xAI Grok) may execute via Azure, Amazon Bedrock, OpenRouter, or another configured upstream. Review each vendor's policy before sending confidential data.

5.3 Payment processors and billing infrastructure

• Payment providers such as FedaPay, KPay, Moolre and IzichangePay: collect and confirm payments under their own privacy policies.
• Mobile Money operators (e.g. MTN, Orange, Wave, Airtel, depending on your selection): process wallet transactions under their own terms.
• Amazon Web Services (S3): stores payment proof images you upload for manual recharges, and profile avatars.
• Authorized RodiumAI personnel: limited access to payment proofs and transaction records for validation, support, and fraud prevention.

5.4 Infrastructure, analytics, and transactional email

Transactional email is delivered through Amazon Simple Email Service (SES) (aws.amazon.com/privacy). Content is limited to account and billing notifications (verification codes, recharge status, low balance, team invites), never your API Gateway prompt content.

• Amazon Web Services (aws.amazon.com/privacy): hosting in the Europe (Ireland) region for the platform API, the AI gateway and Forge (containers, PostgreSQL database, Redis cache, S3 object storage, CloudFront delivery, Amplify for the web apps), and Amazon SES for email.
• Google Firebase (firebase.google.com/support/privacy): sign-in with Google or GitHub, a real-time copy of support conversations (Firestore), and, only if you accept analytics, Google Analytics on the website.
• PostHog, EU cloud (posthog.com/privacy): product analytics on the web apps if you accept analytics (see section 8), and in RodiumAi Code unless you turn it off (see section 2.5).
• Exchange-rate sources (exchangerate.host, open.er-api.com and the rates of our payment aggregator): foreign-exchange rates used to quote local-currency prices. No personal data or prompt content is sent.
• Google Fonts (fonts.google.com): the Forge website loads a typeface from Google, which therefore receives your IP address.
• Distribution platforms (npm, GitHub Releases, Visual Studio Marketplace, Open VSX): where RodiumAi Code and our packages are downloaded. They apply their own policies to downloads.

5.5 Legal disclosure

We may disclose personal data when required by law, court order, or governmental authority, or when necessary to protect rights, prevent fraud, or protect user safety.

RodiumAI, Inc. is a United States company and our infrastructure runs in the Amazon Web Services Europe (Ireland) region. Most of our users are in Africa, and the model providers and other processors listed above operate in several countries, including the United States. When personal data crosses borders we rely on the safeguards that applicable law requires, such as contractual protections with our processors.

• Account data: while your account is open; after closure, only what we need for legal, accounting, security and dispute purposes.
• Transaction records and invoices: for the period required by financial regulation (at least five (5) years).
• Payment proof images: with the related transaction record, or until a dispute is closed, then deleted or anonymized where feasible. Pending manual recharge metadata: until the transaction is approved, rejected, or otherwise finalized.
• API usage metadata (no API prompt content), gateway request logs and security logs: as long as needed for billing, support, security, fraud prevention and statistics.
• Custom-model data you enable: conversation memory for the memory period set on the model (24 hours by default, between 5 minutes and 7 days), knowledge-base documents until you delete them.
• Forge project content (chats, files, published sites, domains): while the project and account remain active. Deleting a project removes its files, published site and custom domain from our active systems; some uploaded attachments and backups may persist for a limited period.
• Support communications: as long as needed to handle your request and meet our legal obligations.
• Product analytics events: as long as needed to analyse and improve the products, and for no other purpose.

When data is no longer needed, we delete or anonymize it securely, subject to backups and legal holds.

We use cookies and similar technologies (such as your browser's local storage) on our web apps. Some are strictly necessary and always on. Analytics only run if you accept them.

8.1 Strictly necessary (no consent needed)

• rd_access and rd_refresh: keep you signed in. They are HttpOnly; the refresh cookie lasts 30 days, is rotated on use and is only sent to the refresh endpoint.
• rd_device: recognises your device so we can ask for a verification code on a new one (one year).
• rd_locale: remembers your language (one year).
• Your analytics choice, and interface preferences such as theme, collapsed menus and documentation navigation, kept in your browser's local storage.
• Forge keeps its sign-in token and preferences in your browser's local storage instead of cookies.

8.2 Analytics (only with your consent)

• PostHog (EU cloud), on the website, the dashboard and Forge: cookies and local storage entries starting with ph_ identify your browser. It records pages viewed, clicks and form submissions on interface elements (never the text you type), page load performance and errors. Once you are signed in it uses your account identifier and role to tell visits apart. It does not receive your name or email address. Session replay is off. Page addresses are stripped of tokens, codes and fragments before they are sent, and only a few harmless parameters (such as utm_ campaign tags) are kept.
• Google Analytics (cookies starting with _ga), on the website only: aggregate audience measurement. Google signals and advertising personalization are turned off, and page addresses are stripped of tokens, codes and fragments in the same way.

8.3 Your choices

The first time you visit, a banner asks you to accept or refuse analytics. Until you answer, no analytics script is loaded and nothing is stored or sent. You can change your mind at any time with "Cookie settings" in the footer, or in Settings > Preferences in your dashboard. Refusing analytics does not limit any feature. You can also block or delete cookies in your browser settings, but the strictly necessary ones are needed to stay signed in.

8.4 What we do not do

We do not use advertising cookies, we do not track you across other sites, and we do not sell data collected through cookies.

• Passwords are hashed with a modern one-way algorithm.
• API keys are shown in full only once at creation; we keep only a one-way hash, so we cannot read them back.
• HTTPS/TLS for data in transit.
• Expiring access tokens, rotating refresh tokens, and one-time email codes for new devices and sensitive actions.
• Credentials of services connected to Forge are encrypted at rest.
• Role-based access and least privilege for internal operations.
• Audit logging of administrative actions.

No system is perfectly secure; we cannot guarantee absolute protection. Report vulnerabilities at security@rodiumai.io.

Depending on your jurisdiction you may have rights to access, rectify, erase, restrict, port, or object to processing of your personal data, and to withdraw your consent at any time without affecting the processing done before.

• Consent: change your analytics choice with "Cookie settings" or in Settings, and turn off RodiumAi Code analytics as described in section 2.5.
• Access and portability: your usage history can be exported as CSV and your receipts as PDF from your dashboard; write to us for a copy of other personal data.
• Erasure: you can close your account in Settings (it asks for your password). Closing disables access. We keep what the law requires us to keep, such as transaction records. Write to us to have the remaining personal data erased or anonymized.
• Forge: you can delete your projects at any time.
• Complaints: you can lodge a complaint with the data protection authority of your country of residence or work.

Contact legal@rodiumai.io to exercise these rights. We typically respond within 30 days.

The Services are not for anyone under 18. If you believe we collected a minor's data, contact legal@rodiumai.io and we will delete it promptly.

We may update this Policy. Material changes will be notified by email at least fourteen (14) days before they take effect. The effective date at the top reflects the latest version.

• Controller: RodiumAI, Inc.
• Registered office: 251 Little Falls Drive, Wilmington, New Castle County, Delaware 19808
• Email: legal@rodiumai.io
• Website: https://rodiumai.io