PRIVACY POLICY

Who this policy covers

FB Mods operates fbmod.com, its licensing API, and the private administration dashboard at stats.fbmod.com. This policy describes those services and FB Frame Counter's licensing requests. It does not describe every data practice of Geometry Dash, Geode, other mods, or external websites.

Information collected

• Free installations: a randomly generated installation ID, a protected authentication token, mod version, registration time, and last contact time. You do not need to create an FB Mods account. The installation ID is pseudonymous; it is not a verified count of individual people.
• Recording access: request IDs, installation ID, date and time, plan, whether the request was allowed, and a denial or administrative reset reason. These records show whether the free daily allowance has been used.
• Paid licenses: the email and name supplied at checkout, Stripe customer and payment references, plan, license creation and expiry, activation, transfers, revocation, and email delivery status. License keys are stored as hashes and encrypted copies for fulfillment.
• Support: messages, your TikTok username, and any purchase reference, error information, or files you choose to send.
• Website and network requests: hosting and payment providers may process IP addresses, browser/device information, request metadata, and security or error logs to deliver and protect their services.

The current licensing requests do not send gameplay recordings, level contents, individual gameplay inputs, Geometry Dash usernames, or hardware serial numbers to the FB Mods licensing database. Recordings remain on your device unless you choose to share them for support.

Why we use it

We use this information to issue and email licenses, verify payment and activation, enforce one active installation and daily recording limits, handle transfers and refunds, prevent misuse, diagnose problems, and understand aggregate installation and access statistics. Where privacy law requires a legal basis, processing is based on providing the service you request, legitimate operational and security interests where permitted, legal obligations, or consent where required.

Without installation and authorization requests, online recording access cannot be verified. Without checkout contact information, we cannot email or support a paid license. We do not sell personal information or use this licensing database for targeted advertising.

Providers and overseas processing

We use Cloudflare for hosting, security, and the licensing database; Stripe for payments; and Resend for license emails. Resend receives the recipient email address and license email content, including the code. Stripe handles full card details; we do not store full card numbers in the FB Mods database.

These providers may process information outside Australia, including in the United States and other countries in their international infrastructure. Their linked policies explain their processing and safeguards. If you contact us on TikTok, that platform also processes your profile and messages under its own privacy policy. We may disclose information when legally required or to address fraud, security incidents, or legal claims.

Cookies, security, and retention

The public FB Mods pages currently do not include our own advertising cookies or advertising trackers. Providers such as Stripe and Cloudflare may use cookies or similar tools for checkout, fraud prevention, or security. The private dashboard uses a sign-in session. The mod saves its installation credentials locally.

We restrict access to the private dashboard, use encrypted network connections, and protect license credentials. No service can promise perfect security.

We retain license and purchase records to provide access and handle support, refunds, accounting, and legal obligations. Installation and access audit records currently have no automatic fixed deletion period. Contact us for a retention or deletion request; we assess what can be removed and what remains necessary for active licenses, fraud prevention, unresolved claims, or legal requirements. Provider logs and backups follow their own retention arrangements.

Support uploads

When you use the support upload page, we store your file, filename, size, submission time, reference number and your selected paid or free status. That selection is self-reported and does not verify a purchase. Support files are stored with Supabase, whose infrastructure may process them outside Australia. Staff can access files privately to investigate your issue and test fixes. Files and their submission records are deleted after 30 days. We temporarily store a hashed network address and upload count for abuse prevention; we do not show your network address to staff. Share only files you have permission to share, and remove sensitive information before uploading.

Your choices and complaints

Contact FB Mods by private message on TikTok @fbmod.com ↗. Tell us whether your request concerns support, a refund, or privacy. Do not post payment details or license codes publicly, and never send your full card number or password.

You can request access, correction, or deletion of information associated with your installation or purchase, and raise a privacy complaint. Share your installation ID or purchase reference privately so we can identify the record. We may need reasonable verification before disclosing or changing personal information.

We aim to acknowledge requests within five business days and explain the response or any lawful reason a request cannot be fully met. Deleting active licensing information may prevent verification of access; we will explain that before taking action. Depending on the laws that apply, you may have additional rights, including objection or restriction, and can complain to your relevant privacy authority. In Australia, see the OAIC privacy complaints guidance ↗.

Changes

We update this notice when our information handling changes and show the update date above. Material changes will be brought to users' attention through the website or another appropriate channel. Where consent is required for a new use, a policy update alone is not consent.