Effective date: July 13, 2026
Last updated: September 1, 2026
Nitro Type Mod Suite is a Chrome extension that enhances the Nitro Type website with user-controlled settings, race options, garage and shop tools, racer badges, optional bot-flag indicators, stats views, leaderboards, and racing music controls. This policy explains what data the extension handles and how that data is used.
The extension may process the following data to provide its features:
Data is used only to provide Nitro Type Mod Suite's enabled user-facing Nitro Type enhancement features. The extension does not collect analytics or telemetry, does not sell user data, does not use user data for advertising, and does not transfer user data for unrelated purposes.
Settings, selected pools, music configuration, feature state, and bounded caches are stored locally in the user's browser using extension-owned Chrome storage. These values remain on the user's device until the user changes settings, clears browser or extension data, or uninstalls the extension. Rebuildable caches may be removed automatically when they expire or when browser storage space is needed; settings and durable feature state are not removed by that cache cleanup.
The extension keeps one checksummed, size-bounded, non-authoritative early-boot snapshot in Nitro Type page storage so enabled interface choices can apply before Chrome storage finishes loading. The snapshot contains settings and durable feature state, but no authentication values, caches, or migration metadata. The authoritative extension store replaces it on each page load.
When upgrading from an earlier Mod Suite release, the extension performs a one-time local migration of known Mod Suite settings and durable state from earlier browser-storage locations. It verifies the new values before removing old suite-owned keys and keeps a temporary extension-local recovery record for up to 14 days. Rebuildable old caches are discarded. Data owned by Nitro Type or separately installed companion userscripts is not migrated or removed.
Nitro Type session tokens are not intentionally stored in extension storage. The extension reads the current Nitro Type token from the Nitro Type page only when needed for Nitro Type API requests, rejects expired tokens, and blocks known Nitro Type authentication keys from being saved in extension storage.
Temporary Spotify access tokens used for metadata and track-list requests are kept only in memory. They are not written to extension storage.
The extension does not send data to a developer-operated server. It may send data directly from the user's browser to the following services when needed for user-facing features:
The extension uses HTTPS endpoints for network requests. The extension's typed background data service only accepts requests from Nitro Type extension contexts and permits fixed, validated operations on explicitly listed HTTPS services. Third-party data requests omit browser credentials. Temporary provider tokens are sent only to the provider that issued them, and Nitro Type authentication is sent only to Nitro Type.
Nitro Type Mod Suite does not load remote JavaScript into extension execution contexts and does not execute remotely fetched code. Remote responses are used as data for Nitro Type, leaderboard, Bot Hunter version checking, and music features. YouTube and Spotify playback use provider iframes for user-selected media.
Users can disable extension features from the Nitro Type Mod Suite settings interface. Users can also clear stored extension data through Chrome's extension/site data controls or by uninstalling the extension.
Questions about this policy can be sent to ntpd1nitrotypepolice@gmail.com. You can also contact the developer on Discord at c.loveridge.