Your data, plainly.
SubCounter is currently a development test for a YouTube subscriber display. This page describes the app as it works today.
This policy covers the SubCounter app and counter-management service. For shopping, hardware orders and checkout, see the SubCounter store privacy policy.
Signing in
Google verifies your identity. We store your Google account identifier and verified email to create your SubCounter account. We use an essential, secure account cookie so you can stay signed in. Basic sign-in does not grant access to your YouTube channel, Gmail or Drive.
Connecting YouTube
Channel access is a separate Viewer (limited) invitation in YouTube Studio. The collector account uses that permission to read your exact subscriber total. We store your selected channel, count, connection status and invitation confirmation records. The collector’s Google session is encrypted on the server. We do not ask for or store your Google password.
Your counter
We store counter names, account/channel associations, a hardware identifier, display settings approximate connection timestamps, and firmware version/update status. Updates are signed and downloaded over HTTPS; your saved count remains visible during recovery. Device keys and pairing credentials are hashed in the database. Your home Wi-Fi password is entered on the counter’s local setup page and stays on the device.
Camera scanning
If you choose to scan a pairing QR code, your browser asks for camera permission. Images are processed on your phone and are not uploaded. The camera stops when you close setup, leave the page or finish scanning. You can always enter the code instead.
Connection alerts and support
Connection problems appear in your signed-in dashboard. You can turn off email alerts in Alerts & account settings. Email delivery requires activation of the sending service; until then, alerts remain available in the app. Support requests, including the text you send, are stored with your account for the operator to review. Do not include passwords or credentials.
Services and retention
The app runs on Cloudflare. Google supplies sign-in and YouTube access. There are no advertising pixels or marketing analytics installed in this test. Account sessions expire after fourteen days, pairing codes after ten minutes, and invitation challenges after seven days. Channel/account bindings and device records remain until an operator removes them; disconnecting or removing a counter revokes access but is not full account deletion.
Control and questions
You can sign out, remove a counter, and revoke the collector’s permission in YouTube Studio. During this limited test, contact the person who invited you to request account removal or ask about your data. Use Help in your signed-in dashboard to request support or account removal. Service checks are retained for thirty days. Cloudflare database backups may retain data for their configured recovery window.