TapLab is designed to work without requiring personal information. This starter policy describes the current build and should be updated if analytics, advertising or other third-party services are enabled.
← Back to TapLabTapLab may store nickname, test bests, sensitivity preferences, daily streak, achievements, XP, color preset and tool settings in browser local storage.
If the optional leaderboard backend is configured, the nickname you choose and your best Reaction, CPS and Aim values may be stored in the shared leaderboard.
The current nickname system does not require your real name, email, phone number or password.
This package contains reserved ad areas but no live ad network code. Add appropriate consent and update this notice before enabling analytics or advertising.
You can remove local TapLab data by clearing this site’s browser storage.
When a production Supabase backend is enabled, TapLab can create an anonymous authentication session in your browser. That session has a random account identifier managed by Supabase Auth. Your public leaderboard entry contains your chosen nickname and best scores; the public leaderboard RPC does not expose that auth identifier.
If you clear browser storage, an anonymous account may no longer be recoverable. Do not use a nickname that reveals information you do not want public.
The launch package keeps optional ad and analytics code disabled until configured. For regions where consent is required, production deployment should use a certified consent-management platform before optional advertising or analytics scripts are enabled.