Source in, artifact out, nothing kept.

Azure Obfuscator (“the service”) is operated by [OPERATOR LEGAL NAME - PLACEHOLDER]. The legal operator name is still to be confirmed; it's shown as a placeholder until then.

The fastest contact route is the Azure Discord community. Privacy messages should describe the request in plain terms; there is no account identifier to include because the service has no accounts.

Submitted source: the Lua or Luau text pasted or dropped into the workspace, plus the selected runtime and the two transformation toggles. The file name shown in the workspace stays in the browser and is used only to name the downloaded artifact.

Abuse prevention: request rate is limited to 60 requests per 60 seconds per connecting IP at the Cloudflare edge. The site keeps no IP log of its own.

Error diagnostics: if the upstream service cannot be reached, the site Worker writes a server-side log entry so the failure can be diagnosed. The entry carries no submitted source.

Nothing else is collected. There are no accounts, no contact form, no newsletter, no analytics beacons, and no advertising pixels.

The browser sends source and settings to /api/obfuscate on this site. The site Worker validates the request and forwards the source text to the Azure obfuscation service over a private service binding; the generated artifact, byte counts, content hash, and request ID come back over the same path.

Submitted data goes nowhere else: no third-party form provider, no analytics endpoint, no advertiser. Data is never sold and never used for marketing. No marketing consent is requested because no marketing exists.

The site stores nothing: source and artifact exist in transit and in page memory only. Reloading the page clears both.

Rate-limit counters expire automatically at the edge. Server-side error log entries live only in the Worker runtime logs.

Each successful response includes the upstream request ID. Keep it when reporting a bad artifact so the faulty request can be identified.

The site sets no cookies, uses no browser storage, and runs no optional tracking, so no consent banner is required and no separate cookie policy applies.

Selecting the submit button is the consent for that single transformation: the workspace states where source goes before anything is sent. If optional tracking is ever introduced, this policy will be updated first and consent controls will be added before the tracker loads.

Privacy questions go through the Discord community link above. Because the service keeps no stored personal data, correction and erasure requests have nothing to act on; questions are still welcome through the same contact route.

Material changes are announced on the changelog. Continued use of the service after the posted update date constitutes acceptance of the revised policy.