Privacy Policy

Last updated: October 27, 2026

This policy describes information handled by the Dummy Scripts website, key service, store and GhostDummy reporting features. Dummy Scripts is the name used by the operator of this service. To ask about your information, join our Discord and open a private support ticket.

Keys, accounts and service security

We store key records, including a key hash, product, issuance and expiry times, activation status, revocation status, download counts and last-use time. First successful activation binds a key to the Roblox account ID supplied by the client. Account IDs and purchase records can identify or be linked to a person; this information is not all anonymous.

The service processes IP addresses for request handling and abuse prevention. Application rate limits use secret-derived hashes and short-lived counters. Key-provider flows use browser cookies, verification tokens and completion records to associate your browser with a completed task and prevent reuse. These records support access delivery and security.

Purchases and recovery email

Stripe handles checkout and payment details. Our service stores order identifiers, selected product and plan, amount, payment status, payment references, timestamps and the associated key record. We receive the checkout email for purchase delivery and recovery. Our database stores an encrypted email and a derived email lookup value; paid key recovery also requires an encrypted copy of the key.

Resend processes recipient email addresses and purchase or recovery messages on our behalf. We store email job and delivery-attempt information. Stripe and Resend also process information under their own policies. Our website does not receive your full payment-card number.

Cookies and local storage

Essential cookies keep key-task sessions, purchase recovery, report forms and authorized administrator sessions working. Clearing cookies can interrupt a task or remove this browser's access to an order; email recovery is available for paid purchases. The script can save your key locally when executor file storage is available, or remember it for the current executor session. Reloading revalidates the key with the server. Use the script's saved-key controls, where available, or your executor's storage controls to remove a local copy.

Website activity and hosting

Cloudflare hosts the website and backend and processes connection and request information to deliver and protect the service. We use Cloudflare website analytics and application counters to understand visits and service use. Application counters record aggregate daily page requests and recognized source tags, such as a tagged Discord link; they do not store full URLs, IP addresses or browser identifiers in those counters. These counts can include repeat visits and bots. Cloudflare's own processing is described in its privacy policy.

Script usage analytics

After unlock, ScriptBlox records script sessions, five-minute heartbeats, a hashed Roblox player ID, game IDs, locale, device category and executor details. It determines country from the connection. A hashed player ID is a persistent identifier; it is not anonymous. Keys and owner credentials are not passed to this analytics integration. ScriptBlox processes this information to provide usage analytics under its own privacy practices.

Bug reports and support

If you submit a report, we store your description, category, report reference and any supplied technical details. Website reports include the Discord username you enter; it is not verified. In-script reports are associated with the key record. Please avoid including passwords, access keys, billing details or unrelated private information. Automated redaction cannot guarantee removal of every sensitive detail you type.

In-script reports can optionally attach a sanitized technical snapshot and the key-bound Roblox user ID to private staff Discord. The snapshot is limited to supported diagnostic fields such as version, executor, feature state, capability indicators and recent state or error events. This attachment feature does not collect native console, process-crash logs or chat. Report summaries and references can also be sent to staff Discord. Discord processes reports and support tickets under its own policies.

Service providers and external sites

Information is processed by the providers needed for the functions above: Cloudflare, Stripe, Resend, Discord and ScriptBlox. If you choose a free-key provider, your browser visits LootLabs, Work.ink or Linkvertise and that provider receives information about your visit and tasks. We exchange verification information to confirm completion. Those providers may use their own cookies, advertising and analytics; review their policies before completing tasks. Their practices are separate from this website's.

Retention and requests

Application cleanup makes bug reports and report history eligible for deletion after 90 days. Some expired non-purchase key records become eligible after 30 days, and temporary flow and rate-limit records have separate expiry rules. Cleanup runs in batches, so eligibility is not an exact deletion deadline. Purchase, payment, recovery and support records can remain for service administration, resolving disputes and applicable recordkeeping. Discord report copies remain until staff deletes them. Other copies held by external providers follow their retention practices.

You can ask about access, correction or deletion, or raise a privacy concern, by opening a private Discord support ticket. Describe the request and use an order ID or report reference where possible. We may need to verify that the information belongs to you. Do not post keys, recovery links or payment details publicly. What we can delete or provide depends on the records involved and applicable requirements; deleting access records may affect key recovery or support.

We use access controls, hashing and encryption for relevant service records, but no online service can guarantee absolute security. We may update this policy as the service changes; the date above identifies this version.