CONTENCE / LEGAL

Privacy Policy

Last updated October 26, 2026

Contence connects a team’s media services to one workspace so the team and its AI agents can work with them. This policy explains what we collect, why, and how to remove it.

Who we are

Contence is operated by Shoal Research. Contact: gabe@shoalresearch.xyz.

What we collect

Account details. When you sign in with Slack or Google we receive your name, email address and account identifier, and for Slack your workspace. We use them only to sign you in and to match you to your workspace.

Connected services. When a workspace admin connects Frame.io, YouTube or Typefully, we store the access credential that service issues, encrypted, and use it only to perform the actions your workspace requests: reading projects, files, comments and analytics, and, where you approve it, uploading files or updating video details.

Workspace data. Metadata, transcripts and records produced by those actions are stored in your workspace and are visible only to its members and the agents they authorize.

Request logs. We log each API and agent request (time, action, status, duration) to operate and secure the service. Logs do not contain your credentials.

Cookies and device data. Contence sets one cookie, a sign-in session cookie, so you stay signed in. It also remembers small display preferences (such as a collapsed sidebar) in your browser’s local storage. We use no advertising or tracking cookies and do not collect device identifiers. Contence does not serve third-party content or ads.

Google user data

This section describes exactly what Contence does with data it receives from Google, including YouTube.

Google sign-in

If you sign in with Google, Contence requests the openid, email and profile scopes and receives your name, email address and Google account identifier. We use them only to sign you in and to match you to your Contence workspace. We store your email address and account identifier with your workspace membership.

YouTube

When a workspace admin connects a YouTube channel, Contence requests these scopes and uses each only as described:

• youtube.readonly: to read the connected channel’s details, its uploads playlist and its videos’ titles, descriptions, thumbnails and statistics, so your team and its agents can see what is published.
• yt-analytics.readonly: to read view, watch-time and engagement analytics for the connected channel and its videos, so your team can compare performance.
• youtube.upload: to upload a video file to the connected channel, only when a named person in your workspace approves that upload. Uploads are private unless that person chooses otherwise.
• youtube.force-ssl: to set a video’s thumbnail and update its title, description and other details, only when a named person in your workspace approves the change.

Storage. We store the OAuth refresh token Google issues, encrypted at rest, scoped to your workspace. Video titles, publish times and thumbnails we read are kept in your workspace so your team can see what was published; we refresh them from YouTube at least every 30 days and delete any YouTube no longer returns. Analytics are read live and not stored. We do not store copies of your video files after an upload completes.

Sharing. Google user data is shown only to members of the workspace that connected it and to the agents those members authorize. We do not sell it, use it for advertising, share it with data brokers, or use it to train AI or machine learning models. We do not transfer it to third parties except as needed to provide the features above, to comply with law, or as part of a merger or acquisition with notice to you.

Human access. No Contence staff read your Google user data unless you ask us to for support, it is needed for security, or the law requires it.

Retention and deletion. Disconnecting a YouTube channel in Contence deletes its stored token at once. The YouTube data Contence read from it (video titles, publish times and thumbnails) is removed from view immediately and deleted within 7 days. If you reconnect the same channel before then, that data is restored. You can also revoke Contence’s access at any time on Google’s security settings page at https://security.google.com/settings/security/permissions; Contence then deletes that channel’s data within 30 days. To ask for deletion sooner, or with any privacy question, email gabe@shoalresearch.xyz.

Limited Use. Contence’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

YouTube API Services. Contence uses YouTube API Services. By connecting YouTube you agree to be bound by the YouTube Terms of Service, and the Google Privacy Policy applies to that data.

What we do not do

We do not sell personal information, use it for advertising, or use data from connected services to train AI models.

Sharing

We share data only with the services you connect, to perform your requests, and with infrastructure providers that host Contence under confidentiality obligations. We disclose data when the law requires it.

Retention and deletion

Disconnecting a service deletes its stored credential. To delete your account or workspace data, email gabe@shoalresearch.xyz and we will delete it within 30 days.

Security

Credentials are encrypted at rest, API keys are stored only as hashes, and every connection is scoped to one workspace and the access level its admin granted.

Changes

We will update this page when our practices change and revise the date above.