Last updated: September 27, 2026

Privacy Policy

This policy explains what Cyrway processes when you use the service.

1. Information you provide

Cyrway may receive your access key, account/profile details, script name, submitted Luau source, webhook configuration, and script-run event fields such as username, user ID, HWID, game name, and executor.

2. Script source processing

When you submit a script for obfuscation, Cyrway uses the source only to perform the requested runtime obfuscation workflow and create the protected output. Cyrway does not use your source for unrelated purposes or intentionally retain the original source after processing completes. Source may be present temporarily in server memory while the request is running.

The source is sent to the configured third-party obfuscation provider to complete the request. The provider's own privacy terms and retention practices may apply.

3. Stored data

Cyrway stores account/license records, script metadata, protected loader outputs, usage counters, analytics events, and webhook configuration needed to operate the service. The original submitted source is not stored as part of normal operation. Debug mode can intentionally write diagnostic source files; keep it disabled in production and delete those files after testing.

4. Webhooks

Webhook destinations are stored server-side. Relay requests are forwarded to your configured destination. Cyrway stores a hashed relay token rather than the raw token in the database. Event rate limiting uses a hashed IP address.

5. Security

Do not submit secrets inside scripts unless necessary. Keep access keys, webhook URLs, and relay tokens private. No Obfuscation service can guarantee absolute security.

6. Third parties

Cyrway relies on infrastructure and processing providers such as Supabase, the configured obfuscator, and Pastefy. Information needed to provide the requested workflow may be sent to those providers.

7. Changes and contact

This policy may be updated as Cyrway changes. By continuing to use Cyrway after an update, you accept the revised policy.