Privacy, clearly.
Kenzuro is a video editing service. This page explains the information used to provide your account, private workspace, and edits.
Last updated 14 October 2026
Account information and Google sign-in
If you create an account with email, we store your name, email address, and a password hash. Your password is not stored as readable text.
If you choose Google sign-in, Google sends a signed identity token. Kenzuro verifies it and stores your name, verified email address, and Google account identifier to create or recognize your account. We use this Google information for authentication, linking the sign-in method you select, and keeping your workspace associated with your account.
Kenzuro does not request access to your Gmail, Google Drive, contacts, or other Google files. Google passwords are never provided to Kenzuro. The Google identity token is verified during sign-in; it is not saved as a reusable Google access token.
Account emails
Account messages include welcome emails, email verification, and password recovery. To deliver these messages from hello@kenzuro.com, Kenzuro uses Resend, which processes the recipient address and email content. Account emails do not include your uploaded footage or editing briefs.
Verification links expire after 24 hours. Password reset links expire after 30 minutes. Both can be used only once. Resetting your password signs out your other sessions. Essential account emails are separate from marketing messages.
Your video projects
We store the footage and optional reference videos, links, captions, B-roll, creative briefs, preferences, project messages, and finished files you submit or receive. These are used to prepare, edit, deliver, and support your requested project.
Your workspace requires sign-in. The people fulfilling and supporting your edit can access its files and brief. Editing and rendering tools may process the footage and instructions needed to complete your request. Customer uploads are not automatically published in our public examples.
Hosting and service providers
The website uses OpenAI Sites hosting and Cloudflare infrastructure for the application and private file storage. Google provides the optional sign-in interface and identity verification. Those providers process the information needed for their respective services and may maintain operational or security logs.
Kenzuro does not send your uploaded videos to Google as part of sign-in. Google identity information is used for the account features described above, rather than advertising or sale to data brokers.
Cookies, browser storage, and security
Essential cookies keep you signed in and protect sign-in requests. A sign-in session lasts up to seven days; signing out revokes that session. Short-lived sign-in protection cookies expire after ten minutes. Kenzuro also stores editing preferences and unfinished brief details in your browser so you can continue a draft.
Sign-in attempt limits use hashed email and IP-related identifiers to reduce abuse. Hosting providers may process network and device information to deliver and protect the website. No advertising or analytics trackers are configured by Kenzuro in this version.
Keeping and deleting information
Accounts and project information remain stored while needed for your workspace and the editing service; this version does not have an automatic account or project deletion schedule. Where a project offers a Delete action, it removes the project's stored files and record. Projects currently being edited cannot be deleted through that action.
For account deletion, help deleting an active project, or access or correction requests, contact us at the address below. We may ask you to verify that you own the account before making changes. You can also remove Kenzuro's Google connection in your Google Account settings; doing that does not itself delete your Kenzuro workspace.
Contact and changes
Kenzuro's privacy contact is aibymariochris@gmail.com. Use this address for questions about your account or project data.
Changes to these practices will be reflected on this page with an updated date. If we request additional Google data, we will explain the new purpose and request authorization before accessing it.