Side Shop AI

Privacy Policy

Last updated: November 8, 2026

This policy describes the Side Shop AI website and the Side Shop AI — Uhura YouTube connection. Questions or privacy requests: [email protected].

Information you send us

The contact form asks for your email and the problem you want help with. You may also provide your name, tools you use, what a better week would look like, and the kind of help you want. Emailing us provides your email address and whatever you include in your message. We use this information to respond, discuss your request, and arrange any work you choose to pursue. Please do not send passwords, access tokens, payment-card details, or unnecessary sensitive information through the contact form.

If you choose to subscribe, the website sends your email address and the page where you signed up to beehiiv to handle the subscription and confirmation email. You can use the unsubscribe option in newsletter emails or contact us for help.

Website delivery and security checks

The website uses Cloudflare for hosting and delivery. The contact form uses Cloudflare Turnstile to check for automated abuse; the form handler sends the security-check token and your IP address to Cloudflare for verification. Network requests also expose technical information, such as your IP address and browser request details, to the services receiving them. Cloudflare and Turnstile may set or read cookies or similar technologies needed for security and delivery; the website’s own code does not set advertising cookies. Resend processes contact-form emails, including the note sent to Side Shop AI and the confirmation sent to you.

Google and YouTube connection: Uhura

Uhura is an owner-operated desktop application for Side Shop AI’s own YouTube channel. It is not currently offered as a public Google-account connection service. Authorization may be in place, but no posting or comment features are currently implemented; this section will be updated before they are.

If enabled and authorized by the channel owner, the connection will use Google OAuth credentials and access tokens to use YouTube API Services. The intended work involves the authorized channel’s identifiers, video and comment identifiers, comment text, and API results needed to prepare, post, and check owner-approved comments. A refresh token may be issued by Google to maintain authorization. The requested permission, youtube.force-ssl, can also permit editing and deleting YouTube content; the permission is broader than posting comments. Permission from Google does not replace the owner’s approval for an action.

Uhura runs on Side Shop AI's own Grok Bot computer. Google receives the OAuth authorization and YouTube API requests. Grok Bot hosts the program, its stored files, and the assistant that operates it; channel identifiers may appear in assistant chat so the owner can confirm the correct channel. OAuth client settings and authorization tokens are kept in a restricted folder on that computer. Other Side Shop AI assistants and programs running under the same account can technically reach that folder; file permissions do not separate individual assistants. The program does not save fetched comments or raw API results. It keeps the channel identifier the owner approved, so it can refuse any other channel. Authorization is checked each weekday morning and before every use. Authorization that has not been successfully checked for 30 days is deleted on the next invocation rather than used. If authorization is invalid or lacks the needed permission, access is turned off and local tokens are deleted. Once the owner’s channel restriction is configured, a channel mismatch during a check also deletes local tokens; an attempt to set a mismatched channel restriction is refused. If access cannot be validated for four days, local tokens are deleted before any further use; outages or missed checks may need manual action. Disconnecting asks Google to revoke the grant and deletes local tokens right away, even if Google cannot be reached; in that case the owner is told to revoke access in Google account permissions. Disconnecting keeps the owner's client registration and channel restriction unless the owner asks for those to be deleted too. Local cleanup does not delete content published on YouTube or assistant chat history, which is managed through the owner's Grok Bot account. Google's permission never replaces the owner's approval of each posting action.

Do not send OAuth client secrets or tokens through this website.

If the Uhura connection is enabled, its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Who receives information

Information is processed by Side Shop AI and the services described above for website delivery, security checks, contact email, and a newsletter subscription you request. If the YouTube connection is enabled, requests and approved comment content will be sent to Google/YouTube. Comments posted on YouTube are public under YouTube’s settings and rules. Following an external link takes you to a service with its own privacy practices.

Storage, security, and your choices

Contact notes are delivered through email, and newsletter subscription records are handled through beehiiv. HTTPS protects the website connection in transit, but no transmission or storage method is guaranteed secure. For questions about information held about you, or to request a correction or deletion, email [email protected]. We will review what records we control and explain any limits, including records we need to keep for an ongoing service or legal obligation. This policy does not promise a fixed automatic deletion period.

The Google account owner can revoke the app’s access at Google account permissions. Revocation stops future authorized access; it does not itself remove a comment already published on YouTube or erase records already held elsewhere. Contact us about deletion of records under our control, and manage published content through YouTube.

Related policies and updates

See Google’s Privacy Policy and YouTube’s Terms of Service. We will update this page when the practices described here change. The date above identifies the latest revision. See also our Terms of Service.