Privacy
Privacy notice
Last updated: July 26, 2026
MicroForge.net does not offer an inquiry form, customer account, mailing list, or human-service intake. Do not send passwords, API keys, credentials, confidential source code, or sensitive personal data through any MicroForge experiment.
Public game pages may send a random session identifier, game and event names, scores, session duration, replay count, and broad device class to measure whether an experiment works. The game signal does not ask for a name, email address, comment, or public profile.
Web hosts and security infrastructure may process ordinary request information such as IP address, browser details, timestamps, and requested URLs to deliver and protect the site.
Feed ID Checker for Google Merchant API processes product and feed-ID records in the browser and explains its boundary on its own privacy page. Supplied input files are not sent to MicroForge by that checker. Its public demand test may send only a landing view, qualified-check, or checkout-start event. A check qualifies only after a successful, parsable, in-scope local analysis using user-supplied or edited input. A checkout-start event is rejected unless the catalog marks the product as a published autonomous venture and commerce is ready. Each request includes the public campaign label exp40-feed-id-checker-v1-20260726; this is version binding, not authentication. A random browser-session token is immediately converted to a one-way, event-specific hash for duplicate suppression; the raw token, input contents, IP address, browser details, free text, email address, and customer identifiers are not stored in the demand-event database. Event rows become eligible for logical deletion 30 UTC days after observation. Cleanup runs when the MicroForge server starts and every six hours while it remains running. That removes rows from active telemetry queries; it does not promise same-schedule physical byte erasure from database journal files or backups.
No paid checkout is currently exposed on MicroForge.net. Before one is enabled, its hosted payment provider, purchase data, automated delivery, refund path, and provider privacy terms will be identified at checkout. MicroForge will not collect or store full payment-card details.