Trust centre

Where your data lives

• The Vidler app, its database, its job queue and all video processing run on one server that Refari rents from Hetzner Online GmbH in Germany. No other cloud platform or serverless service runs Vidler.
• Videos, camera tracks, thumbnails, captions and the nightly database backups are stored in Cloudflare R2. Cloudflare decides where R2 keeps them. Vidler doesn’t pin them to a region, and there is no choice of data location yet.
• Cloudflare also runs Vidler’s DNS and sits in front of the server. The server’s web ports accept connections only from Cloudflare.
• Hetzner and Cloudflare publish their own security certifications. Those cover their companies and data centres, not Vidler’s software.

Every company that processes data for Vidler is on the subprocessors page.

Encryption

In transit

• Every page, API call and upload uses HTTPS. Browsers are told to use only HTTPS for vidler.ai, for a year at a time (HSTS).
• Cloudflare encrypts the connection from your browser. The connection from Cloudflare to the server is encrypted too, and Cloudflare checks the server’s certificate before it sends anything.

At rest

• Cloudflare R2 encrypts every stored file at rest with AES-256, including videos and database backups.
• The database itself lives on the server’s disk. Vidler doesn’t add its own encryption to that disk; the backups of it are encrypted by R2 as above.

Inside Vidler

• Passwords are stored only as Argon2id hashes, never as the password itself.
• Sign-in tokens for apps you connect (such as Slack or Jira) and two-factor secrets are encrypted with AES-256-GCM, with a separate key for each purpose.
• Session tokens, API keys and SCIM tokens are stored only as SHA-256 hashes, so a copy of the database can’t be used to sign in.
• Vidler isn’t end-to-end encrypted. Its servers read your videos in order to process them: converting them for every device, making thumbnails and writing transcripts.

Who can see your videos

• For each video, its owner chooses who can watch: only people they add, the workspace, anyone with the link, anyone with the link and a password, or everyone (public and searchable). New videos start as “Anyone with the link” unless the workspace sets another default.
• Video files are never public in storage. They play through signed links that stop working after a few hours.
• Links can expire, embeds can be limited to listed websites, and downloads can be turned off. Workspace admins can turn outside links off, send them for approval, or allow them only for chosen groups.
• Archived and trashed videos open only for people who can edit them. A video held for review after a report opens only for them too, and a removed one for nobody.

Sign-in and workspace security

• Passwords need at least 8 characters. Common passwords, simple sequences and your own email address are refused, and you get an email whenever your password changes.
• Two-factor authentication with an authenticator app, plus recovery codes. Admins can require it for the whole workspace.
• Single sign-on (SAML). Admins can require it for everyone at the workspace’s verified email domains, and provision people with SCIM.
• An IP allowlist, a maximum session length and an idle timeout, set by admins.
• These workspace rules also apply when someone who is signed in to a different workspace opens this workspace’s videos, folders or playlists.
• Sign-in attempts are rate limited. You can see your signed-in devices and sign out of all of them.
• API keys have read, write or admin access, act only as the person who made them, and can be revoked at any time.

What admins can see and control

• An audit log of sign-ins and changes, with the IP address and browser for each entry.
• Legal holds, which stop videos from being deleted, and retention rules that archive or delete old videos.
• A data requests tool to find, export or erase a person’s data across the workspace.
• Reports about content in the workspace, and the actions taken on them.

AI and your data

Refari doesn’t use your videos, transcripts or AI results to train AI models, and doesn’t sell them.

• Providers process each request to return a result. How long they keep it is set by their own terms.
• Results are stored with the video and labelled “Generated by Vidler AI”. You can edit or remove them.
• Admins can turn Vidler AI off for the whole workspace, or stop viewers from asking questions about videos.
• Camera effects such as background blur run in your browser. Camera frames aren’t sent to Vidler or to any AI provider.

How long data is kept

• Videos and everything attached to them stay until someone deletes them, or until a workspace retention rule does.
• Deleted videos are removed for good straight away.
• Database backups are kept for 14 days, so deleted data can stay in a backup for up to 14 more days.
• The privacy policy has the full list.

If something goes wrong

• If a security incident affects your data, Refari tells the affected workspace owners without undue delay, with what is known and what to do.
• To report a vulnerability, see security and disclosure or email security@refari.co.
• To report a video or screenshot that breaks the rules, use “Report” on it or the report form. Intimate images shared without consent are removed within 48 hours of a valid request.

Chrome extension permissions

Chrome describes each permission in general terms when you install the Vidler extension. This is what each one is used for.

Not in place yet

Vidler is in beta. These are common in larger products and are not in place today.

Documents and contacts

• Privacy policy and terms of service.
• Subprocessors, with a feed of changes.
• Accessibility statement.
• Security reports: security@refari.co.
• Privacy questions and data requests: privacy@refari.co.

Changes to this page

• 16 October 2026: First draft, for legal review.