rand0m.ai BETA

Privacy

Privacy Policy

rand0m.ai launched June 6, 2026. This policy takes effect on the day the production release that carries it publishes this page, and it is not backdated.

rand0m.ai is run by Random Knights, LLC ("we" or "us"). This policy covers the rand0m.ai web app. It says what the app collects, why, where it is kept, who else sees it, and how to have it deleted. It does not cover other websites that rand0m.ai links to.

The short version

Signing in

Without signing in

When you first open rand0m.ai, the app signs your browser in anonymously with Firebase Authentication, a Google service. This creates a random account id with no name or email attached. Our servers need that id to answer requests for weather, Earth data, and AI, and to apply fair-use limits.

Sign in with Google

If you choose Google, Google shares your basic profile with us: your email address, your name, your profile photo, and your Google account id. We do not ask for access to your Gmail, Google Drive, contacts, calendar, or any other Google data.

Sign in with GitHub

If you choose GitHub, GitHub shares your public profile (name, photo, and account id) and, with your permission, your email address, so a private primary address can still reach us. We do not ask for access to your repositories.

Email link

If you sign in with an email link, you give us your email address and Firebase Authentication emails you a one-time sign-in link. While you wait for the link, your browser remembers the address so you do not have to type it again. The app erases it when sign-in finishes or fails.

Where it is kept, and why

Your sign-in details are stored in Firebase Authentication in our Google Cloud project. We do not copy your name, email address, or photo into our own database. We use them to keep you signed in, to show who is signed in, and to decide which features your account can use. For example, some test features open only to verified @rand0m.ai addresses or to addresses we have invited as testers.

How rand0m.ai uses Google user data

Your AI keys

You can add your own API key for an AI provider: OpenAI, Google Gemini, Anthropic Claude, xAI Grok, or Hugging Face. The key is saved in your browser's storage on this device. It is not saved in your account, and it does not follow you to another device.

When you send a prompt, the app sends the key with that one request to our server. The server uses it to call the provider you picked and keeps it only for that request. We never store or log the key. Our logs record only whether a request used your key or ours.

To remove a key, clear it in the app's settings, or clear this site's data in your browser.

Prompts and AI answers

When you use an AI feature, the text you send goes through our server to the AI provider for that request. That provider handles it under its own terms and privacy policy. Our servers do not save your prompt or the answer.

For each AI answer we do save a cost record under your account id: the provider, the model, the number of tokens, the estimated cost, and the estimated energy, carbon, and tree-time. This is our AiEDs disclosure. It is a cost estimate, not the content of your chat. When an AI agent uses a built-in server tool, such as web search, a Wikipedia or arXiv lookup, or opening a web page, our server sends the search words or the page address to the service that answers. We name each one under "Who else handles data" below. We record the account id, the tool, and whether it worked, but not what was asked.

Your chat history, notes, and settings are saved in your browser on this device, not on our servers.

Your data

Everything in rand0m.ai is free during the beta, and we do not sell your data. Here is what is kept, where, and how you can see and delete it.

On your device

Your AI keys, chat history, agent prompts, notes, favorites, and settings live in your browser's storage. We cannot read them. Clear a key in the app's settings, or clear this site's data in your browser to remove all of it.

On our servers

Our servers do not hold your prompts, your answers, your AI keys, or your chat history.

See it, delete it

You can delete your account in the app: open the profile pop-out and use Delete account, under Account controls. You can disconnect a connected account on the c0nnect page, and remove an AI key in settings. To see a copy of what we hold under your account, or to leave the beta list, email privacy@rand0m.ai from the address you used. Delete account also removes your tester bug reports, their attached files, and your daily-limit counters. A copy of a bug report that we already filed on GitHub stays there until you email us and we remove it. The app does not yet list your server records on a page of their own.

Some of this section describes our server code as it will behave once our next server release ships: the 41-day limit under Community totals, Tavily searches on your own key, the 24-month limit on cost records, and Delete account removing bug reports and counters. Until that release ships, our servers may still work the older way.

What we count

We count how the app is used, such as which screens and features are opened, with Google Analytics. We do not send it your email address, your keys, or what you type. We plan to replace it with a counter of our own that records only the event, the page, and the day. We do not sell data, and we do not use it for advertising.

Location

Weather, tide, and local map features need a location. By default the app rounds your device position to about 11 km (roughly city level) before any feature sees it. The app uses your precise position only if you turn that on in the app.

The app sends the location to our server, which asks weather and map data services for results. Our server keeps those results in temporary memory caches, not in your account. The data services see a request from our server, not your name or account.

Usage analytics

We collect anonymous usage events so we can tell which parts of the app people actually use. Things like which lab you opened, which agent ran, whether the benchmark completed, and which sign-in method was used. Events never include your email address, your API keys, the text of your prompts, or your location beyond a county name.

We use Google Analytics to collect these events. On the web, that may set a cookie in your browser. On phones, it uses a device identifier instead. Either way, it only tells one visit apart from another; it does not carry your name. Google Analytics receives browser language and broad browser, device, and platform categories. It derives country plus broader region, subcontinent, and continent from the IP address before Google discards it. Granular location and device collection is turned off for every region, so it does not collect city or city coordinates, the browser user-agent or minor version, device brand, model, or name, operating-system or platform minor versions, or screen resolution. Random Knights, LLC is the entity responsible for this data. Google's own privacy policy is at policies.google.com/privacy.

Community totals (optional, off by default)

If you turn on contributing in the terminal, we receive one small summary for each day: the day, the model name, the tool name, whether token counts were reported or estimated, and counts of tokens and responses. We work out energy, carbon and water ourselves. We do not receive prompts, replies, file or folder names, keys, your computer's name, your location, or the time of any response.

We can match what you sent to your account for up to 41 days, or up to 91 days if our monthly job fails to run. We do that to stop double counting and to let you delete it. The daily rows themselves are deleted within 9 days. When the monthly total is built, your numbers are added to it with other people's and no longer point to you. We show a total only when at least 50 people are in it, and we round counts.

You can stop any time with aieds contribute off and delete numbers not yet added into a total with aieds contribute delete. Numbers already added into a total cannot be taken out. This is separate from connecting your account and from site analytics: contributing sends nothing to Google Analytics. You must be 13 or older.

Our hosting provider keeps standard request logs (such as network address) for a limited time for security. We do not use them to build the community totals.

Connected accounts

On the c0nnect page you can connect a GitHub, Slack, Atlassian (Jira), or Hugging Face account. The provider then sends us an access token. We store it in our database under your account id. No browser can read it back, not yours and not ours: only our server uses it. We use it only for what you ask, such as an AI request billed to your Hugging Face account. When you disconnect, we delete the token and, where the provider supports it, revoke it.

Bug reports from testers

Invited testers can send bug reports and feature requests from the app. The text and any files you attach are filed in our private GitHub repository so we can fix the problem.

Who else handles data

We use these services to run rand0m.ai. Each one gets only what it needs for its job.

We may also share data if the law requires it, or to protect people from harm.

Cookies and browser storage

We do not use advertising cookies. You can clear cookies and site data in your browser at any time. That signs you out and removes any AI keys and chat history saved on this device.

How long we keep data

We keep your account and your connected-account tokens until you delete your account, disconnect the account, or ask us to delete them. We keep each AI cost record for up to 24 months, or until you delete your account. Deletion finishes within 30 days. After a deletion we keep a short note that it happened, with a one-way scramble of your account id instead of the id itself, and counts of tool use with your account id removed. Our server logs record the account id, provider, and model for each AI request, and errors. Google Cloud keeps those logs for 30 days, then deletes them.

Your choices

Children

Part of our K13 mission is to make AI friendly and safe for every age group. You must be at least 13 years old to use rand0m.ai. If you are 13 to 17, you may use it with the consent of a parent or guardian. We recommend rand0m.ai for people 18 and older.

rand0m.ai is not directed to children under 13, and we do not knowingly collect personal data from them. If you think a child under 13 has given us personal data, email privacy@rand0m.ai and we will delete it.

Security

The app talks to our servers over encrypted connections. Our database rules stop anyone else from reading your account's data, and they stop every browser, including ours, from reading connected-account tokens at all. No system is perfectly secure, so we cannot promise that data will never be exposed.

Changes to this policy

If we change this policy, we will update the effective date at the top of this page. If a change is significant, we will also post a notice in the app.

Contact

Random Knights, LLC
8735 Dunwoody Place, Suite R
Atlanta, GA 30350

Privacy requests: privacy@rand0m.ai
Email: knights@rand0m.ai
Phone: (678) 740-9575

See also our Terms of Service.