Privacy Policy

Last updated: July 5, 2026

This policy explains how BloxPilot handles information when you use the BloxPilot browser extension, website, subscription service, and support channels.

Data stored locally

The extension may store settings, preferred location, server history and notes, watchlists, cached Roblox game or friend information, notification state, diagnostics, a randomly generated browser installation ID, and cached subscription status in the browser's local extension storage. This information remains in the browser profile unless a feature described below sends a limited request to a remote service.

Data processed by the BloxPilot subscription service

When you check subscription status, start Checkout, open the billing portal, or manage authorized browsers, BloxPilot may process a browser installation ID, a derived device identifier, device creation and last-seen times, billing email received from Stripe, Stripe customer and subscription identifiers, price identifier, subscription status, billing period, renewal date, cancellation state, and processed webhook identifiers.

BloxPilot uses this information only to provide billing, enforce the authorized-browser limit, prevent abuse, restore access, and support subscription questions.

Roblox and browsing activity

BloxPilot runs on supported Roblox pages and requests Roblox endpoints needed for user-facing server discovery, joining, game information, friend cards, presence, watchlists, and notifications. The extension may read the current Roblox game or page context to provide these features. BloxPilot does not use this access to build an advertising profile or sell browsing activity.

Roblox cookies and account passwords are not stored by BloxPilot or sent to the BloxPilot subscription service. Friend names, avatars, game presence, and similar Roblox information are displayed and cached locally for the requested social features; BloxPilot does not upload a user's friend graph to its subscription database.

Payment data

Payments are handled on Stripe-hosted Checkout and Customer Portal pages. BloxPilot does not receive or store complete card numbers, card security codes, or bank credentials. Stripe may provide BloxPilot with billing email, customer and subscription identifiers, payment status, invoices, and subscription dates needed to provide Pro access.

Services BloxPilot communicates with

Retention

Local extension information remains until it is cleared, replaced, or the browser removes the extension's storage. Subscription and authorized-browser records are retained while needed to provide the subscription, handle billing or support, prevent fraud, and satisfy applicable recordkeeping requirements. Records that are no longer required may be deleted or de-identified.

Your controls

You can change extension settings, remove watchlist entries and server history, revoke an authorized browser from an active BloxPilot installation, manage or cancel billing through Stripe, and uninstall the extension. You may contact BloxPilot to request access to or deletion of subscription records associated with your billing email. Some transaction records may need to be retained for legal, accounting, fraud-prevention, or dispute purposes.

Security and sharing

BloxPilot uses encrypted HTTPS connections and keeps Stripe secret keys and entitlement-signing keys on the Cloudflare backend rather than in the extension. BloxPilot does not sell personal information. Information is shared only with the service providers described above when necessary to operate the requested features, protect the service, process payments, or comply with law.

Changes to this policy

This policy may be updated when BloxPilot's features or data practices change. The updated date at the top of this page identifies the current version.

Contact

For privacy questions or data requests, email customerreplytemplates@gmail.com. Do not send passwords, full payment-card details, or Roblox authentication cookies.