Privacy policy
Updated October 14, 2026
Account information and purposes
Gmail access includes the owner's email address, message headers, recipients, subjects, bodies, labels, threads, drafts and attachments. The bridge uses these to display and search mail, download attachments, save or discard drafts, send messages and apply the owner's mail-organization actions. It requests Google's Gmail modify permission; it does not implement permanent deletion of received mail.
YouTube access includes the selected account's email address and channel identity, subscriptions, playlists and playlist entries, liked videos, ratings and relevant video/channel/comment metadata. These supply the visible account features on the S2. Optional YouTube controls use a broader Google permission for the owner's ratings, subscriptions, playlist changes and comments. Google groups additional account-management capabilities into that permission; the bridge exposes only its implemented controls.
Where data goes
The Pixel makes authorized HTTPS requests to Google APIs. Relevant mail and YouTube information passes through the owner's paired phone connection to the S2. Sending mail submits the chosen recipients, body and attachments to Gmail for delivery. Posting a comment or other YouTube action sends that action to YouTube and may make it public according to that service's settings.
The bridge does not send Google authorization credentials to the S2. It has no developer-operated mail server, advertising, behavioral analytics, data sales or AI-training feature. This public website does not receive mailbox contents, attachments or account tokens. Google and YouTube process the requests necessary to provide their services under their own policies.
Storage and retention
Google's authorization service on the Pixel manages authorization. The companion stores the chosen account identity, service preferences and action receipts privately on the Pixel; access tokens are used there for API requests. The S2 stores a local mail cache and pending operations. The phones may cache attachments and YouTube metadata for their visible features. There is no promised automatic expiry for all local data.
Outgoing Gmail uploads are staged privately on the Pixel with size limits; old staging files are eligible for removal during later upload activity. Downloaded attachments saved to the S2's Downloads folder remain there until the owner removes them. Development diagnostics may be inspected by a helper only when the owner authorizes troubleshooting; no routine remote reading service is built into the app.
Google API data use
Information obtained from Google APIs is used only for the app's visible mail and YouTube features and the transfers described here. Its use and transfer follow the Google API Services User Data Policy, including its Limited Use requirements. Account data is not used for advertising, resold or supplied to data brokers.
Control, revocation and deletion
The owner can remove Galaxy S2 Services access in Google Account connections. Revocation prevents further authorized requests but does not erase existing mail or previously cached files. To remove local copies, separately clear or uninstall the relevant phone apps and delete saved Downloads and any owner-created backups. Clearing companion data can also remove pairing information and requires setup again. Removing local data does not delete mail or YouTube data held by Google.
Website and contact
These pages contain no sign-in form, tracking script, embedded media or analytics code. Cloudflare hosts the pages and may process ordinary request information, including IP addresses, to deliver and protect the site. The developer support contact is shown on Google's consent screen. For Google's data handling, see Google's Privacy Policy.