Tube ROI

Privacy policy

This policy explains how Tube ROI handles information in the invitation-only beta. People who previously used the personal edition can also use the contact and Google permission controls below.

Your identity and workspace

When you sign in with Google, Firebase Authentication identifies your account. Tube ROI uses your account identifier, verified email address and display name to match an invitation and associate you with the workspace and your role.

Cloud Firestore stores membership, invitations and the records your team enters. These may include channel IDs, names and languages, expenses, credits, currencies, notes, production dates and links to working files. Members can see their workspace’s channels and editorial plans. Owners, administrators and finance members can see cost records. A Google Drive link opens under Drive’s own sharing permissions.

When issuing an invitation, the workspace owner or administrator enters the recipient’s email address and assigns a role. Tube ROI generates a link for that person. The person who issued it copies the link and shares it directly with the recipient through a channel of their choice. To accept, the recipient signs in with the Google account matching the invitation.

When you email support, the Tube ROI operator receives the address you use and the contents of your message.

What the beta reads from YouTube

Tube ROI uses YouTube API Services. When a member requests a lookup and a restricted API key is configured, the browser sends the channel, playlist or video IDs to the YouTube Data API. The response may include a channel name, public counts, video titles, dates and thumbnails. Loading a thumbnail contacts YouTube’s image servers.

Pilot accounts can authorize read access to YouTube Analytics for a selected channel. Tube ROI uses this permission to display views, watch time, subscribers, countries and retention where YouTube makes them available. The person who connects the channel can see its reports. In a team workspace, that person can also select individual owners or administrators who may see them.

The server encrypts the channel authorization so the connection can be used in another session. The authorization becomes unusable after 28 days without a successful renewal. Report results are kept in memory during use. Firebase preserves the sign-in session in the same tab when it reloads. Manual records and the sign-in account are stored separately until deleted. A CSV that you download stays on your device until you remove it.

Google services and use of data

Google and Firebase process requests for sign-in, data storage and delivery of the site. The browser may cache files, and Google may use cookies for its own sign-in session. Google describes these practices in its Privacy Policy and its Firebase privacy information.

Tube ROI uses Google API data to identify members and display the information they request. Its use and transfer of this data follow the Google API Services User Data Policy, including Limited Use. Tube ROI does not sell user data or use it for advertising. Google API Services User Data Policy.

Sign out, revoke access or request deletion

Contact for privacy and support

For access, correction or deletion requests, or help with an invitation, write to the Tube ROI operator at emerson.rocco@gmail.com.