Privacy Policy

Last updated: November 2026

NetForge-AI is a browser-based network lab and networking course. This policy says what we collect, why, who handles it for us, how long we keep it, and what you can do about it. Questions: support@netforge-ai.com.

Information we collect

  • Account: Your email address and a display name. The display name is required when you sign up with email; if you sign in with Google or GitHub, we take it from that account. It appears on what you post in the community, on your profile and on your certificate. Passwords are hashed by our sign-in provider; we never see or store them. We also keep a record of which version of the Terms of Service and this policy you agreed to, and when.
  • Learning data: Which chapters you complete; the lab topologies you save, with everything you typed into their devices (private to you); your Final Weighted Exam attempts — each answer, the score, and whether the exam's anti-cheating checks ended the attempt; your certificate; and your 3D Live mission results (score, attempts and hints used).
  • Share links: Anyone with a lab's share link can open it, without an account. Before a share is stored, the passwords, secrets, keys and community strings typed into its devices are replaced with “redacted”; device names, descriptions and banners stay as you wrote them. Share pages are not indexed by search engines, and you can delete your links in Account → Shared lab links.
  • Forgy AI conversations: Forgy AI is included only with the Lab & AI Pass and All-Access Max. On those plans, when you send Forgy a message or run Agent Mode, we send your message, the recent conversation and a description of your current lab (devices, cables, configuration and recent simulator events) — or, in a course chapter on All-Access Max, an outline of the chapter you're reading — to our AI provider, Google (Gemini API), to generate the reply. We keep a log of your questions and Forgy's replies with your account so we can review Forgy's answers and improve the course; we delete it after 12 months, or sooner if you delete your account. Your open Forgy chats are also saved in this browser's local storage, so you can pick up where you left off on this device; clearing this site's data in your browser removes them. We also record how much of your monthly AI allowance each request uses, to enforce plan limits. On the Free plan, the Lab Only Pass and the Course & Lab Pass, no AI is included, and we send nothing to an AI provider; if you connect your own API key, your browser does, under your account (below). The course's pre-recorded Forgy narration is audio we produced in advance and serve ourselves.
  • Forgy with your own API key: When you connect your own API key, on any plan, your browser sends your questions and lab state directly to the provider you chose (Anthropic, OpenAI, Google or OpenRouter). NetForge-AI never receives your key or those conversations and keeps no log of them. The provider's privacy policy and terms apply. On Google's unpaid Gemini API tier, Google may use your prompts and responses to improve its products, outside the European Economic Area, the UK and Switzerland. Our servers only answer one check before each question or Agent run (whether own-key Forgy is on and whether you have a final-exam attempt open), which carries no content, and we record counts about its use — which provider, how many steps and tokens, whether it worked — never your key, your questions or Forgy's replies. Your chats stay in this browser's local storage, as above.
  • Live classes: If you join a live class, its host sees your name, when you joined and were last active, the work you submit and its results, and — while the class is live — the shared lab, its terminal output and your cursor. Class chat is seen by everyone in the class; a private message only by you and the person you sent it to. Files shared in a class are open only to its members. Live class updates go only to members of the class; if the host embeds the class on another website, visitors there see the shared lab only. When the host ends a one-off live class, or deletes their account, its roster, submissions, chat and shared files are deleted.
  • Classes you join: Anyone can create a class on the Classes page and becomes its teacher. Before you join one you are told what the teacher will see, and we record which version of that notice you agreed to and when. While you are in the class, its teacher sees your name; when you joined and were last active; how many course chapters and missions you have completed, including any from before you joined; the guided builds you finish after joining and your time in the lab from the day you joined; and your results on the class's assignments, check by check, with how many attempts you made; and anything you hand in for an assignment, such as a written answer or a screenshot. A teacher can give you a score and a comment on your work, which only you and they can see. Screenshots are kept in private storage and opened through short-lived links, and we remove any location or camera details from them when you upload them. The teacher also sees totals across the class of where students get stuck, such as builds left unfinished, quizzes not yet passed and common lab errors, with no names and nothing you typed. Your teacher does not see your email address, your plan, what you type in your own lab, your Forgy chats or any other class you are in. Other students can't see your progress, your results, what you hand in or your teacher's comments. You see your own results next to the class average, which leaves out grades a teacher gives by hand and appears only once three students are behind each figure. A class can hide lab tools in your browser while you are in it, and it never adds to what your plan includes. Leaving a class, or being removed from it, ends your teacher's view at once and deletes your results and everything you handed in for that class, screenshots included; messages you posted stay in the class chat until the class is deleted. If a teacher removes you, we keep a note of that so the class code doesn't let you back in, until they allow it or the class is deleted. A teacher can download a class gradebook, and a copy they already downloaded is theirs to keep and to look after, so ask them if you want it removed.
  • Community: The community is public. Anyone, signed in or not, can read questions, answers and comments with their author's display name, and your profile: name, photo, title, job, studies and bio if you add them, and the questions you've asked. Likes and connections are public records too: anyone can look up who liked a post and who is connected to whom, including connection requests not yet accepted. Direct messages are seen only by you and the other person. When someone comments on your post or messages you, their name and the first 140 characters appear in your notifications. Posts are checked by a keyword filter that runs on our own servers; nothing is sent to an AI provider for moderation. An image that a post links from another website loads from that website, which can see your IP address.
  • Uploads: Images you add to a post, comment, message or your profile are stored at a web address that anyone who has it can open; we remove location, camera and other hidden details from them first. When you delete a question, answer or comment, or delete a message for everyone, the images you attached to it are deleted too.
  • Lab sign-in box: If you're not signed in and give your email in the lab's sign-in box, we store that email, a one-way hash of your IP address, and a short summary of your lab session (how many devices you'd placed, what opened the box and how long you'd been working), and you're emailed a sign-in link that creates your account. We delete this record after 12 months, or when you delete your account.
  • Connected AI apps: If you connect an AI app to NetForge-AI Lab, our MCP server: a hash of each access token, the apps you approved, the working labs the app creates, and a record of each tool call it makes. See Connected AI apps below.
  • Signup country: When you create an account, we record the approximate country you signed up from, as a two-letter code (for example “DE”). Our hosting provider, Vercel, works it out from your IP address and passes us only the result; we don't store the IP address with it. It is recorded once and kept with your account.
  • Billing: If you subscribe to a paid plan, payment is processed by PayPal. We give PayPal your email address and account ID so the subscription is linked to your account. We store a PayPal subscription reference, your plan and its status, the current billing period's dates, any scheduled end date after you cancel, and one record per payment (amount, currency, status and date), plus PayPal's notifications about your subscription with names, emails and addresses removed. We do not receive or store your card number, bank details or PayPal login. You can see your billing history at Account → Billing.
  • Product usage (signed-in only): When you are signed in, we keep a record of how you use the product that is linked to your account: the pages you open, how long each is in the foreground, which features you use (adding a device, running a command, saving a topology, hitting a plan limit, joining a class, posting) and how much of a chapter video you watch. Saves and classes are recorded by their ID, not their name, and a page address that identifies a member, a certificate or a share link is recorded without that ID. For a lab command it records the first word, whether the simulator accepted it, and — for one it accepted — what it changed on the device (for example “interface address set” or “no change”). We also keep the command line itself (up to 120 characters) so we can see where the simulator confuses people: before it is stored, everything after a password, secret, key or community keyword is removed, any line that looks like a password, key, email address or phone number is dropped entirely, and for an accepted command the words you chose yourself — a hostname, description, banner or name — are replaced too. An accepted command’s line is kept once per visit. The command lines are deleted after 30 days, and the rest of this record after 13 months. It uses no cookie and doesn't depend on your cookie choice. We use it to see where learners get stuck and what to fix next.
  • 3D Live usage: In 3D Live (the 3D view of the lab) we record what you do there — entering a device or a cable, adding, moving or removing a device, plugging in a cable, using a tool, starting or giving up on a guided operation, opening the terminal and the commands you run in it (as above), saving to your lab — plus how many times you jumped and how long you ran, as totals rather than every movement. Signed in, it is part of the product-usage record above. Signed out, it is kept with a random identifier for that browser tab only (gone when you close it), never with your name, email, IP address or account, and without anything you type: for a command we keep only whether it was accepted and what kind of change it made. We keep these signed-out records for 90 days. They follow your analytics choice: if you decline in the cookie banner, or are in the EEA, the UK or Switzerland and have not accepted, nothing is recorded while you are signed out.
  • Voice chat in 3D Live games: In a 3D Live game you can switch your microphone on to talk with the other players. Your browser asks your permission first, and the microphone is used only while your mic is switched on. Your voice goes straight from your browser to the browsers of the players who have their sound on, encrypted. If two players' networks can't connect directly, it may pass through a relay run by Cloudflare, still encrypted, so the relay can't listen. We never receive, record or store it. Because the browsers connect to each other, a player you talk to or listen to can see your IP address. While you are in a game, the other players see whether your mic and sound are on and when you are speaking; none of that is kept.
  • Community views and searches: When you open a community post we record the page, the website you came from (its address only, not the full link) and, if you're signed in, your account; a cookie that lasts until you close the browser (nf_sid) stops one visit being counted twice. Searches you run in the community are recorded the same way. We keep these records for 90 days, signed in or not, whatever your cookie choice.
  • Site analytics: Vercel Web Analytics counts page views and a set of product events (for example: the lab was opened, a device was added, a command was run, a save was attempted, a plan limit was reached), without cookies and without linking them to your account. The events carry no name, email or account ID — only details such as your plan, whether you're signed in, the chapter, the device type, how you signed in, counts, and, for a lab command, which known command it was and whether it was accepted, never the rest of what you typed.
  • Google Analytics: We use Google Analytics 4 to see which channels bring people to the site and which of the product events above they complete. It sets _ga cookies to recognise a returning browser. Google receives your IP address, which it uses for an approximate location, and the address and title of each page you open — so a community search you typed, a member's profile ID or a member's display name can reach Google that way. We never send it your email or password or what you build. The only account details it receives are your plan on some events and whether this browser is signed in. We have not enabled advertising features or remarketing. In the EEA, the UK and Switzerland no Analytics cookie is set until you accept the banner, and until then Google receives only cookieless measurements; declining is remembered. Wherever you are, you can change your choice at any time with Cookie settings, or opt out for every site with Google's browser opt-out add-on.
  • Google AdSense: Outside the EEA, the UK and Switzerland, every page loads Google AdSense. AdSense sets advertising cookies (for example __gads, __gpi and DoubleClick's IDE) to choose and measure ads, and may use them to personalise ads based on your visits to this and other sites. Like Analytics, it receives the address of the page you are on, but never your email or password. In the EEA, the UK and Switzerland, AdSense is not loaded unless Google's own consent message is shown to you first, and no AdSense cookie is set until you agree there. You can opt out of personalised ads for every site at Google Ads Settings or aboutads.info.

How we use your data

  • Run your account and the features you use — the lab, the course, classes, the community, Forgy on the plans that include it, and connected AI apps — and apply your plan's limits. We do this to provide the service you signed up for.
  • Show your progress to the teacher of a class you joined, because you agreed to it when you joined. You can end that at any time by leaving the class.
  • Take subscription payments, show you your billing history, apply your cancellation on the right date, and keep the payment records tax and accounting law requires. We do this to perform our contract with you and to meet those legal obligations.
  • Keep the service secure, stop bots and abuse, and fix errors, on the basis of our legitimate interest in a working, safe service.
  • Learn where learners get stuck and what to build or fix next, from the product-usage, 3D Live and community records and the signup country, on the basis of our legitimate interest in improving the product. We never use these records for advertising and never sell them.
  • Measure visits with Google Analytics and show ads with Google AdSense — with your consent wherever we ask for it.
  • Answer your emails to support.

Cookies

An essential cookie keeps you signed in. nf_sid lasts until you close the browser and only groups community page views (see above). Google Analytics sets _ga and _ga_<id> (up to two years) and Google AdSense, where it loads, sets its own advertising cookies, as described above.

The site also keeps things in your browser's storage rather than in cookies, such as your lab workspace and its backup, Forgy chats, your course progress, mock-exam state, cookie choice and theme. Signing out removes the lab workspace, its backup and your copy of a class from this browser; the rest stays until you clear this site's data.

If you connect your own API key for Forgy, the key is kept by a separate NetForge-AI page, vault.netforge-ai.com, in that page's storage in your browser: by default only for this browser session (it is gone when you close every NetForge-AI tab), or, if you choose "Remember on this device", encrypted on this device until you remove it. Forget in Forgy's settings removes it everywhere in this browser, and signing out or deleting your account removes it too.

You can change or withdraw your Google Analytics choice at any time: . Declining also deletes the Google Analytics cookies already stored in this browser; AdSense cookies are controlled from Google Ads Settings. You can also block the Analytics and AdSense cookies in your browser; the site works without them.

Service providers

These companies handle data for us, each for the purpose listed:

  • Supabase: Our database, sign-in, file storage and live class updates. It also sends our account emails (confirmations, sign-in links and password resets).
  • Vercel: Hosting — it handles every request, so it sees your IP address — and the cookieless site analytics. See Vercel's privacy policy.
  • PayPal: Subscription billing and payment processing for the paid plans. PayPal is the controller of the payment data you give it directly (card or bank details, PayPal account) under its own privacy statement.
  • Google: Forgy messages on the Lab & AI Pass and All-Access Max are processed by Google's Gemini API solely to generate replies; Google may retain prompts and responses in accordance with its Gemini API terms. Google also runs Google Analytics and Google AdSense (see how Google uses data from partner sites), and our support mailbox, so the emails you send to support are stored in Google Workspace. We do not use your Forgy conversations to train our own models.
  • Cloudflare: Turnstile, the bot check on sign-up, sign-in, password reset and the lab's sign-in box. It sees your IP address and browser details to tell people from bots. In 3D Live games with voice chat, Cloudflare's servers also tell your browser its own internet address and, between players whose networks can't connect directly, relay the encrypted voice. They see your IP address but can't hear what is said.
  • Google and GitHub sign-in: Only if you choose to sign in with them: they tell us your email address and name.
  • Anthropic and OpenAI: The AI assistant our team uses to run NetForge-AI and answer support runs on their models. It can read account, usage and billing records, the emails you send to support and community posts, to help us operate the service and reply to you. It never sees passwords or card details, which we don't have.
  • Discord: Hosts our optional community server. What you post there is held by Discord under its own privacy policy, and our team's assistant can read it.

Most of these providers are US companies, so your data may be processed in the United States and other countries outside your own. Each handles it under its own terms and security controls. An AI app you connect yourself (see Connected AI apps) is not one of our providers: you choose it, and what it reads from your labs goes to its provider under that provider's terms. The same goes for an AI provider you connect with your own API key for Forgy: you choose it, and your browser talks to it directly. We do not sell your personal data to anyone.

Connected AI apps

You can connect an AI app of your own choosing — for example Claude, ChatGPT, Cursor or VS Code — to NetForge-AI Lab, our MCP server, so the app can build and test labs in your account. NetForge-AI runs no AI for this: the app you connected does the work, and its provider is responsible for it.

  • What goes to your AI app: The tool calls your app makes and their results — the contents of your working labs and the output of the devices in them — are sent to the AI service you connected, which handles them under its own terms and privacy policy. We do not receive your conversation with that app; we see only its tool calls.
  • What we store: A hash of each access token (never the token itself), which apps you approved and with which permissions, when each app or token was last used, the working labs your app creates, and a usage record for each tool call: the tool's name, whether it succeeded (and if not, a one-word reason such as "refused"), how many devices the lab held as a range such as 1–5, and how long it took. When the app types commands into a device, builds a lab or runs a connectivity test, the record also counts how many commands, steps or tests were accepted, refused (by a fixed category such as "unknown command") or changed nothing, and how many devices of each kind the lab holds; for up to five refused or no-op commands it keeps the command's shape with every value replaced, such as ip address <ip> <mask>. Never the conversation, and never the names, addresses, passwords or other values the app typed. We also count calls per minute and per day to apply fair-use limits.
  • Retention: An app approval lasts until you revoke it. Revoked approvals, and revoked or expired tokens, are deleted 30 days later. A working lab is deleted after 30 days without use — revoking the app that made it doesn't delete it sooner. The per-minute and per-day counts are kept for 30 days and the usage records with your product-usage record. Labs your app copies into My saves are ordinary saves. Deleting your account deletes all of it.
  • Your control: You can see and revoke every connected app and token at any time in Account → Connected AI apps; a revoked app or token is refused from its next call.

Data retention & deletion

We keep your data while your account exists, except where a shorter period applies:

  • the text of lab commands: 30 days;
  • the rest of your product-usage record: 13 months;
  • your Forgy log and the lab sign-in box record: 12 months;
  • community views and searches, and signed-out 3D Live records: 90 days;
  • community questions, answers and comments you delete: hidden at once, permanently deleted after 30 days;
  • PayPal's notifications: their details are cleared after 30 days (90 if never processed) and the record itself goes after 400 days;
  • connected AI app data: as described above;
  • your results in a class: until you leave it, you are removed from it, or it is deleted;
  • an account whose email is never confirmed: deleted after 7 days.

You can delete your account at any time from Account → Danger zone. It first cancels any active subscription (if PayPal can't confirm the cancellation, nothing is deleted), then deletes your profile, course progress, exam attempts, certificate, lab saves, share links, Forgy history, product-usage records, signup country, uploaded files, connected apps and your lab sign-in box record. Your community questions, answers and comments are removed from the site at once, shown as “Deleted member” and permanently deleted after 30 days; deleting a question removes the answers others gave to it. Your direct messages are deleted for both people in the conversation, and classes you host or teach are deleted with their rosters, assignments, students' results, chat and shared files. If you are a student in a class, you are removed from it and your results there are deleted.

What we keep: payment records, without your name or email and no longer linked to your account, for seven years after each payment, because tax and accounting law requires a record of payments taken; PayPal's notifications for the periods above; and community view records, no longer linked to your account, until their 90 days are up.

Security

Your private data — saves, progress, exam attempts, messages, Forgy history and billing — is protected at the database level with row-level security, so other members can't read it. What is public by design is described above: the community, share links, certificate pages and what a class host or teacher sees. Traffic is encrypted in transit, and our own keys are kept server-side only. An API key you connect for Forgy stays in your browser, on a separate NetForge-AI page that runs no third-party scripts, so neither our servers nor the analytics and ad scripts on our other pages can read it.

Your rights

You can view and update your profile, and delete your share links and your account, from your account page; you can delete saved topologies in the lab's My saves and community posts where you posted them. To get a copy of your data, to correct something you can't change yourself (such as your email address), or to object to or limit how we use it, email support@netforge-ai.com. Where we rely on your consent, you can withdraw it at any time. Depending on where you live, you may also have the right to complain to your data-protection authority.

Children

NetForge-AI is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us with personal data, please contact us at support@netforge-ai.com and we will delete it promptly.

AI providers set their own minimum age for API accounts, and several require you to be 18 or older. If you are under your provider's age, don't connect your own API key; Forgy on the plans that include it needs no account with a provider.

Changes & contact

We'll update this page when our practices change and revise the date above. Questions about privacy? Email support@netforge-ai.com. See also our Terms of Service.