Privacy & Google data

Information we access

AssHats uses YouTube API Services. Operators can look up public channel details, including the channel ID, handle, title and description. When you choose Google verification, we request Google identity (openid) and read-only YouTube access to check the IDs of channels owned by the account or Brand Account you select.

We use the Google account identifier to derive a one-way hash that binds your verified claim. We do not request your Google email address or profile scopes. We do not receive your Google password, read your Gmail, upload videos, change your channel or manage comments.

How verification works and what we retain

The check compares your owned channel IDs with the permanent ID in your private invitation. Other channels returned during this check are processed temporarily and are not saved as your claim. Google access credentials are used on the server for this check, not persisted as an ongoing connection, and revocation is attempted when the check finishes.

We retain the invited channel ID, a hash of the verified Google account identifier, verification method and time, and a versioned consent record. These support secure reauthentication and an audit trail. We also keep private preview content and operational records. Ending your browser session does not delete the saved claim.

Cookies and duration

An encrypted, HTTP-only verification-attempt cookie lasts up to ten minutes. A separate encrypted creator-session cookie lasts up to 24 hours. Invitation links expire after 30 days unless renewed; renewal invalidates earlier invitations. Operators use separate authentication cookies. Cached YouTube profile fields and saved Google verification proofs are cleared by hourly cleanup once they are 29 days old. A fresh lookup or verification renews the relevant data. The channel identifier can remain linked to existing operational records until withdrawal; ending a browser session alone does not erase saved records.

Use and sharing

We use verification data to establish channel control and protect private creator features. Authorized AssHats operators can review claim status. Hosting and database providers Vercel and Supabase process data to run the service. If you separately choose a sample payment, Stripe processes payment information; payment and shipping records are separate from Google verification.

Google identity, access tokens and private ownership responses are not sent to OpenAI or another creative model, sold, used for advertising, or used to train a generalized AI model. Public channel research and any later creative workflow are distinct from private Google verification.

Our use of Google user data is limited to the ownership-verification feature described here and the permitted uses in the Google API Services User Data Policy, including Limited Use requirements.

Disconnect or request deletion

Use “End creator session on this browser” to remove local creator access. You may also revoke AssHats access through Google Account permissions. Google revocation does not itself submit a request to delete records held by AssHats.

To request access, correction, disconnection or deletion of your AssHats data, email asshats.promo@gmail.com with your channel handle or URL and the request. Do not send passwords, access tokens or payment-card details. We may ask for proof of channel control before changing or deleting private records. From a verified creator session, use “Disconnect and request data deletion.” It immediately removes the saved Google verification and cached profile and closes private AssHats links. The support page displays a case reference. A human reviews other copies and records any required retention for payment, security, disputes or legal obligations.

We retain a protected do-not-contact fingerprint so the same channel cannot be saved for outreach again, even if its handle changes, plus a minimal case record. We aim to resolve remaining in-scope copies promptly and within seven calendar days. Deletion from AssHats does not delete data from YouTube. You can manage YouTube data in YouTube itself. The pilot is not yet open for general Google verification.

Questions and Google policies

Contact asshats.promo@gmail.com with privacy questions or complaints. See the Google Privacy Policy for Google’s practices. This notice may be updated as the service changes; review the current version before granting permission.