Privacy

FD uses Discord OAuth2 to identify accounts and verify membership in the required FD Discord server. The application stores the Discord account ID, username, display name, avatar reference, server-membership verification state, account timestamps, plan status, session records, deobfuscation metadata, quota state and security audit events.

Uploaded files

Uploaded source files and generated outputs are stored in the server runtime workspace for the configured retention period. They are accessible only to the authenticated account that created the deobfuscation, except server administrators who operate the service.

Discord authorization

FD requests the identify and guilds OAuth scopes. The OAuth access token is used during sign-in to request your Discord profile and server list so FD can verify that you belong to the required server. FD does not persist the OAuth access token in its database.

Free monetization unlocks

When free-use monetization is enabled, FD may redirect free users to Linkvertise or LootLabs before a deobfuscation starts. FD stores a short-lived unlock-session record tied to the authenticated FD account, selected provider, deobfuscator and pending upload. Provider completion identifiers and keyed IP fingerprints may be stored for replay/fraud prevention. Linkvertise and LootLabs process the provider-side visit under their own privacy policies. Provider API keys and verification tokens remain server-side and are not sent to the FD browser.

Premium

Premium access is recorded on the FD account with its source, duration and expiration time where applicable. Purchases advertised by the current website are handled through the FD Discord server; FD does not collect card details through the website.

Security

Session tokens are stored only as hashes server-side. Security telemetry uses keyed fingerprints rather than storing raw IP addresses in the application database.