Privacy Policy
Updated 11 November 2026
Who we are
Verno (“Verno”, “we”, “us”) builds content studios inside organizations such as hospitals, and makes Verno Web, the app at app.verno.io where those organizations review, approve and publish what they record. This policy covers verno.io, Verno Web and the studio software we install.
If your organization has a written agreement with us, including a HIPAA business associate agreement, that agreement controls how we handle what your organization records. Nothing in this policy loosens it.
What we collect
- Account details. Your name, work email, organization and role. Your organization or Verno creates your sign-in; you cannot sign up on your own.
- What your organization records and makes with us. Video, audio, transcripts, pictures, notes, replies and approvals.
- Records of use. When you sign in, what you open, play or download and when, and the network address it came from. We keep these to protect your organization’s content and to show who did what.
- Settings in your browser. Verno Web keeps your sign-in and a few small settings (for example, which product updates you have seen) in your browser’s storage. We use no advertising or tracking cookies and no third-party analytics. verno.io sets no cookies at all.
How we use it
To run Verno for your organization: to record, edit, review and deliver its videos, to keep its content secure, and to help you when you ask. We do not sell your information, we do not use it for advertising, and we do not use your organization’s content to train AI models.
Who sees it
- People in your organization, according to the role your organization gives them.
- Verno staff and the editors who work on your organization’s videos. Editors only see the pieces they are working on.
- Companies that run Verno for us, under contract: Amazon Web Services hosts and stores everything, in the United States. Anthropic’s Claude helps us pick clips and write edit notes, under a business associate agreement.
- YouTube or Vimeo, only when someone in your organization publishes a video there (see below).
- Anyone the law requires, and only what it requires.
YouTube and your Google data
Verno Web uses YouTube API Services so your organization can publish approved videos to its own YouTube channel. By using this feature you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is covered by the Google Privacy Policy.
When someone connects a channel, Google asks them to allow two things. This is all Verno does with them:
- Manage your YouTube videos (
youtube.upload). Used only to upload a video someone in your organization chooses to publish, with the title, description and privacy setting they chose in Verno, and to set that video’s cover picture as its thumbnail. - View your YouTube account (
youtube.readonly). Used only to read the connected channel’s name and ID, and whether it may upload videos longer than 15 minutes, so Verno can show which channel is connected and stop a video the channel cannot take.
Verno never reads, changes or deletes your other videos, comments, playlists, subscribers or analytics.
What we keep. The long-lived key Google gives us (a refresh token), encrypted in Amazon Web Services Secrets Manager and never sent to a browser. The connected channel’s name and ID, who connected it and when. For each video published, its YouTube video ID and link. The short-lived keys used during an upload are never stored.
Who sees it. The channel’s name and the published links are shown to people in your organization and to Verno staff who support it. We do not sell Google data, share it with anyone else, use it for advertising, or use it to train AI models.
Verno’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting. Your organization can disconnect the channel at any time from Connected accounts in Verno Web. We then revoke Verno’s access at Google and delete the stored key; Amazon Web Services erases it for good after a 7-day recovery window. The record that the channel was connected, by whom and when, and the links of videos already published, stay in your organization’s history. You can also remove Verno’s access yourself at any time from your Google security settings: security.google.com/settings/security/permissions.
Vimeo
Vimeo works the same way: someone connects your organization’s Vimeo account once, Verno keeps its key encrypted the same way, and Verno uploads only the videos your team chooses to publish. Disconnecting revokes the key at Vimeo and deletes it. See the Vimeo Privacy Policy.
How long we keep things
Your organization’s content is kept and destroyed as its agreement with us says. Account details are kept while your sign-in is active and as that agreement requires. Records of use are kept as long as we need them to protect your organization’s content.
How we protect it
Everything is encrypted in transit and at rest, and stored in the United States. Each person sees only what their role allows, and every time someone opens or downloads a video, we write down who, when and from where.
Your choices
You can ask us to show, correct or delete your information by emailing nick@verno.io. Content that belongs to your organization may need your organization’s say before we change or delete it.
Children
Verno is for organizations and their staff. It is not meant for children under 13, and we do not knowingly collect their information.
Changes
When this policy changes, we update the date at the top. If a change matters, we tell your organization first.
Contact
Questions about privacy: nick@verno.io.