hi.video
How it worksPricingOur StoryBlogMade by you
Say hiSay hi
Back to hi.videoHI.VIDEO / PRIVACY

A little privacy.

hi.video helps you record personal introductions and share them using unlisted links. We keep the information needed to make those links work.

Your account and recordings

We store your email, profile, introduction details, capture-session records and video metadata in Cloudflare D1. Your recording is encoded and played back by Cloudflare Stream: it either uploads while you record and Stream copies it when you stop, or it uploads directly to Stream when you publish. A small capture manifest is stored in Cloudflare R2. Email sign-in codes are delivered through Cloudflare Email Sending or the configured email provider.

Who can open an introduction?

Anyone with the link can view it and may forward it. Pages ask search engines not to index them; that is not an access-control guarantee. Private recipient names do not appear in social-preview metadata. The name in a link does not verify the viewer’s identity.

Viewing activity

We use a first-party random viewer identifier to count page openings, playback milestones and reply-button clicks. We do not identify the recipient from their IP address or use device fingerprinting. Activity and aggregate counts may be retained for investigations after an introduction is archived or deleted. Anonymous identifiers are scoped to each introduction on the server.

Reports and captions

Reports about a video are reviewed privately and are not shown to its sender. The owner can privately review uploaded videos to investigate misuse. Playback access and account moderation actions are logged. We retain report details, the reported media reference and review history for investigations. A keyed network identifier limits abuse; raw IP addresses are not stored with reports. Caption text and earlier caption versions are also retained after removal. Removing captions hides them from playback and the transcript.

Uploading while you record

So publishing doesn’t wait, your take uploads to hi.video while you record, before you decide to publish. It is stored in Cloudflare R2, and only your account can publish it. When you stop recording, Cloudflare Stream copies it from there and starts encoding it for playback, so it can be ready by the time you publish. If you retake or discard a take in the recorder, its upload and Stream’s copy are deleted straight away. Takes you don’t publish are deleted within a day, along with Stream’s copy. Unfinished uploads are deleted within two hours, and the stored upload of a published take within six hours of publishing. Your browser keeps its own copy until your video is processed, so publishing can still upload it if the stored copy isn’t available. With your browser’s Data Saver on, or while you’re offline, nothing uploads until you publish.

Draft captions

When you finish a recording, hi.video drafts captions from what you said so you can correct them before you publish. While you record, your browser keeps a separate sound-only copy of your microphone audio, with no video, on your device. When the recording ends, the web app sends that audio to hi.video, which passes it to Cloudflare Workers AI for speech recognition and returns the text. This happens as soon as you finish, before you decide to publish, and even if you later retake or discard the take. Cloudflare processes the audio to provide the service under its own terms.

We do not store the audio or the draft text on our servers, and our logs record only that a request happened, not what it contained. We keep a count of drafts per account for an hour to limit abuse. Draft captions are made automatically for takes with microphone audio when your browser supports it; there is no setting to skip the draft, and you choose only whether to publish it. Shared screen audio is not included.

The audio and the draft stay on your device with the unfinished recording until you publish or discard it. If “Publish with captions” is on when you publish, the captions as you left them are saved with the video, and anyone who can open the introduction can read them. Otherwise the draft is deleted with the local copy. You can edit or remove captions later from your introductions.

Reliability

To diagnose recording and upload failures, the web app sends a limited number of fixed error codes and request IDs to Cloudflare Workers Logs. These reports contain no video, email, recipient name, share link or free-form error message. Service logs also record request status, timing and registered route templates.

Advertising measurement

When advertising measurement is configured, it starts by default outside the EEA, UK and Switzerland unless you previously opted out. In those regions, or when your location is unavailable, automatic advertising measurement stays off. Browser Do Not Track and Global Privacy Control signals disable measurement. We use Meta, Reddit, X and TikTok to measure visits and email-verified signups, first published videos and first paid Pro subscriptions. LinkedIn receives email-verified signup and first-publication events through our server using a LinkedIn ad click ID when measurement is enabled. We do not install LinkedIn scripts or send email addresses to LinkedIn. Provider scripts run in a separate measurement frame and cannot read profile, recording, admin or recipient-page content. We send fixed event names and opaque event IDs, never videos, recipient names, emails, share links or camera-check results. The providers may receive browser and network information from their scripts. When measurement is enabled, first-party ad click IDs and one of our job, consulting or sales campaign categories are retained for up to 30 days. Server conversion events use these click IDs, with the same event IDs as browser events to avoid double counting. They are retried for up to 48 hours. Declining or withdrawing permission stops browser measurement, clears stored attribution on the server and cancels unsent deliveries. Data already delivered to an ad provider remains subject to that provider’s privacy policy. You can limit measurement using your browser’s Do Not Track or Global Privacy Control setting. Previously saved choices apply to this browser and domain.

Website analytics and session replay

Microsoft Clarity starts by default on our public pages unless you opt out or your browser sends a privacy signal. It measures interactions on our public marketing pages using heatmaps and session replays. It receives page URLs, clicks, scrolling, browser and network information, and public page content. We use Relaxed masking for public text; form inputs remain masked by Clarity. Clarity does not run on sign-in, account, recording, admin or recipient pages. We do not send account identifiers, videos or camera-check results to Clarity. Without an explicit choice, Clarity applies its project and regional cookie restrictions, including limited cookieless measurement where consent is required. Previously granted Analytics permission allows analytics storage and denies Clarity advertising storage. Disabling Analytics stops collection and clears Clarity cookies on this domain. Data already collected remains subject to the Microsoft Privacy Statement. Browser privacy signals disable collection. Previously saved choices expire after 30 days and apply to this browser and domain.

Subscriptions and payments

Stripe processes subscription payments. You enter card details on Stripe. We store billing identifiers, subscription status, paid billing periods and published usage to manage your plan and allowance.

Local recovery and deletion

Your browser may save an unfinished recording on your device so you can retry an upload. That copy, including its microphone audio and any draft captions, is removed after successful processing, deletion or sign-out. A retake replaces it only after the new recording is saved. Archive an introduction to hide it immediately, or delete it to remove its original video files asynchronously. Previously issued playback access can last up to five minutes after archive or deletion. Database records, capture metadata, viewing activity and audit records are retained for investigations. Monthly publishing usage and reserved username aliases are also kept. Cleanup retries if a provider is temporarily unavailable. You can delete your account from Profile: this blocks sign-in and all public links, removes original video files asynchronously, and retains database records for investigations.

Chrome extension for Gmail and Apollo

The extension adds a personal video to an individual email draft in supported Gmail and Apollo compose views. When you click “Record a hi”, it reads the selected recipient’s name and email from that one compose view and passes both to the authenticated hi.video page. The recorder’s backend saves only the recipient’s name with the introduction. The extension checks the recipient again before inserting a thumbnail and link into that draft. You review and send the email yourself.

The extension’s local recovery queue saves the recipient’s name and email, provider, random task and draft IDs, browser-session and tab IDs, owning hi account ID, introduction ID when assigned, timestamps, status, recovery notices and public share details when ready. It holds at most 50 entries in this browser, never in Chrome sync. Entries expire after seven days without use; cleanup runs on startup and use, and hourly while Chrome is open. Dismiss removes an entry. Uninstalling removes local extension data. Neither action deletes server videos or the web recorder’s separate saved takes.

Your connected hi account ID, name and email are kept in Chrome session storage and cleared when the browser restarts or you sign out of the extension. Session storage also holds a random browser session ID and a pending sign-in handoff, if any. Extension sign-out disconnects the extension; it does not sign you out of the hi.video website or delete the recovery queue.

The extension does not harvest your inbox or contact list, collect or transmit message subjects or body text, collect provider credentials, or use Gmail OAuth or Apollo API tokens. It checks links and images in the chosen editor to avoid inserting a duplicate thumbnail, without transmitting or storing the message body. It does not send emails or include an analytics SDK. Video capture, upload and captions happen on hi.video under the website practices described in this policy.

Screen recording

You choose a tab, window or screen using your browser’s picker. A full screen can include other windows and notifications; close private content before you start. Shared audio is optional and depends on your browser. The screen, camera and selected audio become one video, saved locally for review. As described under “Uploading while you record”, it normally uploads to Cloudflare R2 during recording and Stream starts copying it when you stop, before publication. With Data Saver on or while offline, upload waits until you publish. Draft captions come from your microphone, not from shared audio. We do not send screen text to an OCR service, and screen contents or window titles are not included in reliability reports.

Capture information

Ordinary video recording does not collect depth maps. Future native capture features will require their own privacy description before launch.

Camera checks

New accounts complete a short camera check before their first recording, and we may ask an account to repeat it for an account-safety concern. AWS Rekognition Face Liveness processes a short selfie video and facial measurements in the United States to assess live presence. You agree to this processing before each check. The challenge uses bright, flashing colors; contact support@hi.video before starting if this is unsuitable for you.

We do not enroll your face, match it to an identity, or keep selfie recordings, reference images or audit images. We retain consent version, session metadata, outcome and check date for account safety. Required checks cannot be bypassed by deleting an account. Rekognition’s service-improvement opt-out is enabled. AWS’s processing and retention terms apply separately to the information it processes to provide the check.

For privacy questions, contact privacy@hi.video. Account deletion is available in Profile. Updated November 10, 2026.

hi.video

A little more personal.

PricingBlogCompareEnterprisePrivacyTermsMade by you
© 2026 hi.video