Privacy Policy

Last updated: November 9, 2026

Your Privacy Matters

At HyperDevs, we believe privacy is a fundamental right. This policy explains how we handle data. We designed HyperDevs to collect as little data as possible, and we never sell your information to anyone.

If you have questions about this policy, please contact us at privacy@hyperdevs.app.

API Keys

We never see your API keys.

When you add an API key for Claude, Gemini, OpenAI, or any other provider, that key is stored locally on your device in encrypted storage. The key is never transmitted to our servers.

Calls made with your key go directly from your computer to that provider's servers. We act as a local client, and they never pass through our infrastructure. (Hyper 30, our hosted model, needs no key and goes through our proxy instead: see Your Prompts and Generations below.)

A Roblox Open Cloud key is optional: it is needed only to upload rigged characters from the Animation tab. It is stored the same way and sent only to Roblox: to upload, and to ask Roblox which account the key belongs to, which the app then shows you.

Your Prompts and Generations

This works differently for chat than for image, 3D and animation generation, so we describe them separately rather than make one blanket promise.

Chat and code (the AI assistant)

We do not store these. Your messages go straight to the AI provider you selected — with your own key, directly from your computer to that provider; with Hyper 30, our hosted model, streamed through our proxy to the model and back. We keep no transcript, and there is no copy of your conversation on our servers — unless you choose to attach part of it to a bug report you send us. Your chat history is saved on your computer, kept separately for each account that signs in on it.

Hyper 30. It runs either on our own server or at providers we reach through OpenRouter, a service that sends each request to one of several companies that run the model. Either way, your requests go through our proxy, which may read a request to prepare it for the model and then passes it on. It does not store or log what you or the AI wrote, or your IP address. On our own server, we keep only the time of each request, its size, its status and how long it took, so we can diagnose problems. Through OpenRouter, we send your requests under our own account, without your email, your account details or your IP address, and we only use providers that keep no copy of your requests or the replies after answering them (zero data retention) and don't train on them. One exception: OpenRouter screens requests for child sexual abuse material and may keep a flagged request for review, reporting and preservation where the law requires.

Hyper 30 usage records. For each Hyper 30 message that runs through OpenRouter, and each call to the model it makes, we keep a usage record with your account: when it was made, whether it came from the chat or a Memory scan, whether it was free or paid, how many tokens it used, what it cost, any credits charged, which provider answered it and how it ended (for example, finished or stopped). It also holds technical identifiers that link it to the call, such as OpenRouter's ID for the call and one-way hashes used to recognise a repeated message or step, and the name of the software that made the call. It never includes what you or the AI wrote, or your IP address. We use these records to measure your free daily use, to charge credits if you keep going with them, and to look into problems. They are deleted after 90 days, or with your account if you delete it sooner.

Image, 3D and animation generation

For these, we do keep a record of the request. Each generation creates a job row that includes the prompt text you submitted, which model was used, the credits charged, and a link to the finished file at the provider.

We keep it because these jobs are asynchronous and paid for in advance: the record is how we deliver the result back to you, how we refund your credits when a job fails, and how we answer you if you tell us something was charged incorrectly. It is retained while your account exists and is deleted when your account is deleted.

We do not use it to train anything, we do not sell it, and we do not review it except when investigating a specific problem you have raised, a suspected policy violation, or a legal obligation.

Your project files

Your game files, scripts and assets stay on your computer, apart from what Send to Game saves to your Roblox account (see Your Game Data below), and we have no access to your project. What the AI reads to help you, such as a script, your project's layout or, when the model can see images, a screenshot of your game, is sent to the AI model you use the same way as chat, above. So is each script a Memory scan summarises (see Your Game Data below).

Your Game Data

Your game files stay on your computer, except what is sent to the AI model you use and what Send to Game saves to your Roblox account.

HyperDevs reads your Roblox project, and imports assets into it, through Roblox Studio on your computer. Send to Game has Studio save the model and its texture to your own Roblox account, the one you use in Studio. What is uploaded with your Roblox Open Cloud key instead, such as a rigged character from the Animation tab, goes to the account the key belongs to (see API Keys above). Either way, it goes to Roblox, not to us. To list your recent games in the Game tab, the app reads Studio’s list of recently opened games on your computer and asks Roblox’s public game API for their names and icons: only the games’ IDs go to Roblox, and nothing goes to us. The Memory feature builds its knowledge graph of your game on your computer and keeps it there. Once you confirm a project in the Memory tab, the AI gets a summary of it with your chat messages, to help it understand your project.

To summarise your scripts, a Memory scan sends each script's source to the AI model chosen for the Memory tab, the same way chat does: with your own key, straight from your computer to that provider; with Hyper 30, through our proxy (see Your Prompts and Generations). With a model that runs on your computer, such as Ollama or LM Studio, it stays on your computer.

Usage Data (HyperDevs Cloud Only)

If you use HyperDevs Cloud (our hosted AI services), we collect minimal data to operate the service:

  • Email address: if you create an account, we store your email securely and use it to send you account emails, such as the codes that confirm your address when you sign up and let you reset a forgotten password. Those are sent through our email delivery provider and are never used for marketing.
  • Birth year: collected at sign-up to enforce our 13+ age requirement, and used to ask a buyer who may be under 18 to confirm that a parent or guardian agreed. We keep the year only, not the full date.
  • Request count: how many requests you have made today, for rate limiting.
  • Hyper 30 use: the usage records described above, kept for 90 days, and, for each day, what your free and paid Hyper 30 use cost in total, kept with your account. That is how your free daily use and your daily credit cap are measured.
  • Credits and payments: your balance, purchases, and a ledger of grants and spends, including credits spent on Hyper 30. When we ask a buyer to confirm that a parent or guardian agreed, the purchase records that confirmation. If you turn on continuing with credits for Hyper 30, we keep that setting and your daily credit cap.
  • Generation job records: as described above — for image, 3D and animation jobs only.
  • Interaction events: which screens you open, how far you get in the guided tour, when you send a chat message and how the reply ends (finished, stopped by you, or failed), the thumbs up or down you give a reply, when you start a generation or open checkout, when your free Hyper 30 use runs out and what you choose about continuing with credits, how each Send to Game goes, and when Studio connects and how the Game tab shows it. See below.
  • Install ID: when you sign in, and each time the app starts while you're signed in, the app sends the random ID it made for your install, the one described under App Usage Analytics below. It is sent even if you have turned usage data off. We keep only a one-way hash of it, with your account, and use it to enforce suspensions: if an account is suspended for breaking our Terms, accounts created after the suspension that are used on the same install can be refused HyperDevs Cloud, wherever they were created. Accounts that existed before the suspension are not affected.

Interaction events

The app records a small set of named events so we can tell where people get stuck. A typical one is "opened the Coder tab" or "the first message failed with a 401" — the kind of thing that told us a whole group of new users had hit a bug on their very first prompt and left without saying anything.

These events carry only fixed labels, numbers and yes/no values. They never carry your prompts, the AI's replies, your code, your file paths, or the text of an error message — the app has nowhere to put that in an event, by design.

Nothing is sent unless you are signed in. If you use HyperDevs with your own API keys and never create an account, no events leave your machine at all. You can also turn this off at any time in Settings → General → “Share usage data”; switching it off also discards anything still queued on your device.

We still do not collect, in the app:

  • Your chat messages, the AI's replies, or the code you write
  • The contents of your project files
  • Your screen, keystrokes, or mouse movement — there is no session recording of any kind. The only picture taken is a screenshot of your game's view in Studio: for the AI model you use, when it can see images (see Your Prompts and Generations above), or for your clipboard, when you press the Game tab's Screenshot button
  • Your IP address, beyond what is necessary for DDoS protection. Our sign-in provider does keep the IP address and the app and browser details (user agent) of each sign-in session, for security. We don't use IP addresses to suspend accounts or installs.
  • Location data
  • Device fingerprinting

App Usage Analytics (v0.1.22 and later)

From v0.1.22 the desktop app can record a small amount of interaction data, so we can find first-run experiences that are broken. We added this because we genuinely could not tell whether people were getting stuck, or where. The thumbs up and down under the AI's replies tell us which replies helped and which did not. Send to Game results and the Game tab's view tell us where sending a model to Studio, or showing Studio in the Game tab, goes wrong.

What it records:

  • When the app opens and how long it stays open, with the app version, your operating system, whether it is a new install, and whether you were already signed in when it opened
  • When you sign in or out, whether the account is brand new, and your credit balance at the time
  • Which tabs, screens, dialogs and Settings sections you open
  • Whether you were offered the guided tour, how far you got, and whether you finished or skipped it
  • When you send a chat message: which AI provider, model and tab, how long the message is, and whether it is the chat's first message — never what it says
  • How each reply ends: finished (how long it took from when you sent it, any time it spent waiting to be sent, how long until the first output, and how many tools the AI used), stopped by you (after how long, and whether anything had come back yet), or failed, with a category for why (never the raw error text)
  • When a message cannot be sent, and why, as a category (for example, the daily limit was reached)
  • The thumbs up or down you give a reply, the reason you pick from a fixed list (such as “Didn't work”) if you pick one, and which AI provider and tab the reply came from, how long it took from when you sent it, how many tools it used, and whether it answered the chat's first message. There is no text box, and the reply itself is never sent.
  • When you start an image, 3D or animation generation, with the model, its credit cost and your balance
  • When you open the checkout to buy credits, the amount, and whether you opened it to keep going with Hyper 30
  • When the app sees that your free Hyper 30 use for the day has run out, and in which tab's chat
  • The offer to keep going with Hyper 30 on credits: when the chat shows it, and whether you open it, accept it or close it, in the chat or in Settings
  • When you turn continuing with credits on or off, or change its daily cap: the new setting, the cap in credits, and whether you did it in the chat or in Settings
  • When you don't have enough credits to keep going with Hyper 30, and whether you opened Buy credits from there
  • Each Send to Game: which tab it came from (3D Models, Viewer, Optimize or Animation), how it went, as a category (for example, built in Studio, or left for you to drag in), whether the model is kept for good, kept until Studio restarts or only a preview, how its texture got there, whether Studio refused to save the model or its texture to your Roblox account, whether the model was reduced first, how many pieces it went in as, how long it took and, if it failed or wasn’t sent, a category for why — never the model, its name, or any Roblox asset or place ID
  • When you switch the Game tab between Game view (only Studio’s 3D view) and All of Studio, and whether you used the switch or the “Script open” hint
  • When Game view can’t be shown, so the Game tab shows all of Studio, with a category for why
  • The first time Studio connects after the app opens: whether through the HyperDevs plugin or Roblox’s built-in connection, how long after the app opened, whether HyperDevs opened Studio, and whether the Game tab is set to Game view
  • When you release Studio from the Game tab into a window of its own, or bring it back
  • Once per install, which features are set up, as yes or no answers (for example, a provider key or a project), and how far the tour got

Each event also carries a random ID made for your install, and another for the current launch, so we can tell one launch from another. Neither is derived from your hardware. The install ID is also sent when you sign in, and each time the app starts while you're signed in, even with usage data off. It is used to enforce suspensions (see Usage Data above). Clearing the app's data gives your install a new ID.

What it never records — and structurally cannot:

  • Your prompts, or anything you type into the AI
  • The AI's replies, including the ones you rate
  • Your code, scripts or generated assets
  • File paths, project names or anything identifying your game
  • Your API keys

Events carry only categories, numbers and true/false values. There is nowhere in the payload to put your content, which is how that guarantee stays true rather than being a promise we ask you to trust.

Signed-in users only, and stored with your account. Each event is stored with your account, which is also how deleting the account deletes them. Nothing is ever uploaded without an account session — the database rejects any event not tied to a signed-in user, so this is enforced by the server and not just by the app.

It is on by default, and you can turn it off at any time in Settings → General → “Share usage data”. Switching it off also discards anything still waiting to be sent, and hides the thumbs up and down under replies, since a rating would not be sent.

Website Analytics

This website (hyperdevs.app) uses Cloudflare Web Analytics to understand which pages people find useful. It is privacy-first by design:

  • No cookies. It sets none, and stores nothing in your browser.
  • No fingerprinting. It does not build a device or browser signature to follow you.
  • No cross-site tracking. It cannot see anything you do on other sites.
  • Aggregate only. We see page views, referrers, countries and browser types in aggregate — never individual people.

Because it sets no cookies and stores nothing on your device, it does not require a consent banner — which is exactly why we chose it over a conventional analytics product.

This applies to the website only, and the desktop app does not use Cloudflare Web Analytics or any third-party analytics product. What the app itself records is described under Usage Data above, it goes only to our own database, and it never includes your browsing.

Contact Form Bot Check

The contact form can use Cloudflare Turnstile to check that you're not a bot. When it's on, you'll see the check above the Send button. It runs on the contact page only, and it looks at signals from your browser and connection, such as your IP address and browser details. Cloudflare uses them to detect bots and to improve its bot detection, not to identify, profile or target you, as its Turnstile Privacy Addendum explains.

We Never Sell Your Data

Period.

We don't sell your data to third parties. We don't use your data for advertising. We don't build "shadow profiles" for sale. Our business model is simple: provide great tools, charge fair prices for optional features.

Account Deletion

If you create a HyperDevs Cloud account, you can delete it at any time from Settings → Account → Delete Account in the app. You will be asked for your password, and the deletion happens straight away.

If you cannot sign in, or the app asks you to contact us, email legal@hyperdevs.app from the address on the account and ask us to delete it. We will action it within 30 days and confirm when it is done.

Deletion removes your email, birth year, credit and payment ledger (apart from the purchase record described below), generation job records (including the stored prompts), Hyper 30 usage records and settings, interaction events (reply ratings included), the bug reports you have sent us, and the hashed install IDs kept with your account. It is permanent and cannot be undone. Unspent credits are forfeited when you delete your account, so spend them first if you want to use them.

If a request from your account was ever blocked under our content policy, or your account is suspended when you delete it, we keep a record of that, so it still applies if the same email address is used to sign up again. The record holds the date of each blocked request and the rule it broke (never what you typed), the suspension's date and reason, and a one-way hash of your email address made with a secret key, not the address itself. If an account is created with that address later, the record moves to it. The record has no end date. If you think a suspension was a mistake, email legal@hyperdevs.app. If your account is suspended when you delete it, its hashed install IDs are kept too, without your email, until the suspension is lifted.

If you bought credits, we keep a record of each purchase for 120 days after the deletion, in case a payment is disputed: the payment's ID at our payment processor, its date, the amount charged and any refund, the credits it bought and how many were used, and, if we asked for it, your confirmation that a parent or guardian agreed. It holds no email or other contact details, and it is deleted automatically after 120 days. Our payment processor keeps its own records of payments, as the law requires.

You can also ask us for a copy of the data we hold about you at the same address.

Data Security

We take security seriously:

  • Local API keys: Kept in the app's settings on your device, encrypted with Windows' built-in data protection (DPAPI) through Electron's safeStorage
  • HyperDevs Cloud accounts: Email and usage data stored securely with encryption at rest
  • HTTPS: All connections use TLS 1.3 or higher
  • Minimal logging: Beyond what security monitoring needs, such as the IP address and app and browser details of each sign-in session (see Usage Data), we keep only the Hyper 30 records described under Your Prompts and Generations (request timings on our own server, usage records through OpenRouter), with no IP address or message content

Children's Privacy

HyperDevs is not intended for children under 13, and we do not knowingly collect personal information from them. Please do not create an account or submit personal information through this site if you are under 13. If we learn we've collected data from a child under 13 without verifiable parental consent, we will delete it promptly. Parents or guardians can contact us at privacy@hyperdevs.app.

Changes to This Policy

If we change this privacy policy, we will:

  • Update the "Last updated" date at the top
  • Notify users via the app (if the change is significant)
  • Never retroactively apply new terms to past data collection

Questions or Concerns?

If you have questions about this privacy policy or how we handle your data, please contact us at privacy@hyperdevs.app. We typically respond within 1-2 business days.