Privacy policy

Last updated October 19, 2026

heds ops is the internal operations dashboard for heds, used by the heds team to track carRADIO episodes from shoot to release. This policy explains what information heds ops collects, how it is used and stored, and how to have it removed. heds ops is operated by heds. Contact: mike@heds.io.

Who can use heds ops

Only members of the heds team with a heds.io Google account can sign in. heds ops is not offered to the public.

Information we collect

Google sign-in

When a team member signs in with Google, heds ops receives their name, email address and email verification status (Google scopes openid, email, profile). These are used only to confirm the person has a verified heds.io account and to show who is signed in. Email addresses are also recorded next to changes a team member makes in the app, such as linking a video to an episode.

YouTube data

With the channel owner’s permission, heds ops connects to the heds YouTube channel using the read-only scope https://www.googleapis.com/auth/youtube.readonly. Through the YouTube API Services it reads, for the heds channel only:

• the channel’s ID, name and list of uploads
• for each upload: video ID, title, privacy status (public, unlisted or private), publish date, scheduled premiere time and duration

heds ops cannot upload, edit, delete or comment on videos, and it does not read viewers’ data, comments, subscribers or analytics.

Jira data

heds ops reads the team’s own Jira tickets for carRADIO shoots and edits: titles, statuses, due dates, subtasks, links and assignee names.

How we use information

Information is used only to run heds ops for the heds team: showing each episode’s progress and deadlines, and matching YouTube drafts, premieres and published videos to the episodes they belong to. We do not use it for advertising, we do not sell it, and we do not use it to train AI or machine-learning models.

Google API Services: Limited Use

heds ops’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. YouTube data is handled in line with the YouTube Terms of Service and the Google Privacy Policy.

Sharing

Information is visible only to signed-in heds team members. It is not shared with or sold to anyone else. It is processed by the services that host heds ops: Netlify, which hosts the app and its database, and Google, which provides sign-in, the YouTube API and web fonts.

Storage and security

• Data is stored in the app’s database on Netlify and sent only over HTTPS.
• The YouTube access token is encrypted (AES-256-GCM) before it is stored.
• Every page and API requires a signed-in heds.io account. Sign-in sessions end after 7 days.
• heds ops uses one sign-in session cookie and no tracking or analytics cookies.

Retention and deletion

• YouTube video details are kept while the channel is connected so episodes stay linked to their videos. Disconnecting YouTube in heds ops deletes the stored token and stops all reading.
• To have stored YouTube or account information deleted, email mike@heds.io. We delete it and confirm by email.
• You can also revoke heds ops’ access to your Google account at any time at myaccount.google.com/permissions.

Changes

If this policy changes, we update the date at the top of this page.

Contact

heds · mike@heds.io