Privacy Policy

Established: October 29, 2026. Last revised and effective: November 3, 2026. If this English translation differs from the Japanese original, the Japanese version prevails.

ZenLab Inc. ("we") handles information in Eizeno (the "Service") as follows.

Information we collect and why

• Email address and sign-in records: to verify you, send sign-in links, show your account and answer inquiries. If you sign in with Google, we receive your verified email address and identifier from Google (never your Google password).
• Profile (only if you answer it in Settings): your role, company, full name, how you heard about Eizeno, what you hoped to get when you signed up, and the problem you would like AI to solve, used to improve the service, send you relevant information and manage the free-tier grant. It is never shown to other users, and you can edit it at any time in Settings.
• URLs you specify, your requests and exploration records: to run explorations, show results and investigate problems.
• Recordings, screenshots, lists of features, summaries and introduction videos: delivered to you as Deliverables. Your editing requests and the edit plans the AI makes are used to create and revise introduction videos.
• Previously extracted sales meeting notes and draft messages can be deleted from the corresponding production.
• Exploration and recording through the Chrome extension: When you request a video in chat, the extension automatically connects with the Eizeno page and opens the specified URL in a dedicated new tab. Links needed for your video may open in that same tab, including links to another domain or links that normally open a new tab. For these pages as well, we receive that tab’s URL, screenshots, page text and structure, and the types, positions and timing of actions to create and revise your introduction video. Screens and action results are encrypted between the extension and our production process and decrypted by that process. If sign-in is needed, AI control and recording pause. With your consent, you sign in yourself in the same dedicated tab. AI control and recording resume only after you explicitly resume exploration and protections have been checked. Your existing tabs are not operated. We do not extract and transmit passwords saved in Chrome or the Target Site’s authentication cookies. Your signed-in state remains in your Chrome browser; we do not delete it when production ends. For videos, images and embeds published on public pages before sign-in, we receive their URLs and nearby descriptive text (alternative text, headings, notes), and our server fetches only the files on the same site, without your cookies, to use them as material for the introduction video.
• Share pages (pages you publish for the people you send them to): the settings you choose (product name, description, button text and link, expiry and the version shared) and, if you use a passcode, its hash (we do not store the passcode itself), used to show the page and restrict access. For people who view the page, we record only totals of page opens, plays started, how far the video was watched and button clicks, by day, source and version, and show them to the user who published the page. Viewers' IP addresses and cookie identifiers are not stored in these totals. To avoid counting the same action twice within one viewing, a random number is issued each time the page is opened and deleted after 6 hours (it is not linked to a person). After a passcode is accepted, the viewing permission is kept only in the viewer's browser memory (not in a cookie) and expires after 12 hours.
• Outcome tracking on share pages (when you issue a sending key): each time the button on a share page or embed is clicked, we create a random reference ID that does not identify anyone and add it to the button's link. We store a hash of the reference ID with the version shown, the channel and the time of the click, and do not link it to the viewer's IP address or cookie IDs. From your server, we receive the outcome type, your outcome ID, the reference ID, when it happened and the reported amount and currency, and use them only to show you totals. There are no fields for names, email addresses and the like, and we do not accept them. Whether you link the reference ID to customer information on your site, and how you obtain consent for that, is for you to decide under your own site's privacy policy.
• Balance, purchase and usage records, and payment status: to manage top-ups and usage, for accounting and tax, and to answer inquiries. We do not handle card numbers; Stripe does.
• Slack connection (only if you connect it): to notify you when a video is ready, fails or needs your action, and to take revision requests and approvals in a Slack thread, we store the workspace name and identifier, the name and identifier of the notification channel, the Slack app's authentication token (encrypted), the identifiers of Slack users you link, the mapping between productions and Slack threads, and the text of revision requests and approval records (who, when and which version) received from Slack. We do not collect ordinary Slack conversations.
• Access records (IP address, time, errors and so on): for secure operation, preventing misuse and investigating failures.

Transfers and storage

• During an exploration, screenshots, page text and structure of the Target Site, and your requests are sent through our servers to Anthropic (Claude) for AI processing. Do not display personal or confidential information you are not authorized to record and transmit. Personal information visible in the dedicated tab may be transmitted and stored if it is not detected. In signed-in explorations, password fields and text in the form of email addresses, phone numbers and card numbers are hidden or masked in the screens and text sent to the AI and in the recording, but we do not guarantee that all personal information, including names, addresses, free text and text inside images, is hidden; please use demo data. The sign-in screens and inputs while control is handed to you by the Chrome extension are not sent to us or to the AI.
• When using our servers to read an external example or demo, our servers request the linked page and send public information read from it to Anthropic for video production. We do not send your browser cookies or credentials to the linked site.
• When editing an introduction video, frames taken from the recording, the list of features and summary, the action log and your requests are sent through our servers to Anthropic (Claude), and narration text and the instructions for generating music and opening shots are sent to Google (Gemini API).
• In the support chat, what you type and the account details needed to answer (your balance, and the URLs and status of your recent explorations) are sent through our servers to Anthropic (Claude) to generate replies. Apart from temporary storage while you confirm a message to our team, we do not store support chat conversations on our servers. If you choose to send a message to our team, the AI-written summary, the recent conversation, your account email address, and the status of your recent explorations are emailed to our support team.
• Payments are handled by Stripe. We receive the payment status and amounts.
• If you connect Slack, we send to the channel you choose, through Slack (Slack Technologies), the domain of the production's target URL, version numbers, the status of approvals and revision requests, and links to Eizeno (and, if you choose, links to share pages you have issued). The videos themselves are not sent. Members of the channel can read the notifications.
• Accounts, records and recordings are stored on Amazon Web Services (Tokyo region), and sign-in emails are sent with Amazon SES.

Use of information obtained through the Chrome extension

Information obtained through the Chrome extension is used only to create and revise the product introduction videos you request and for operations and security necessary to provide that service. We do not use or sell it for advertising. We handle it in accordance with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Cookies

We use only a cookie that keeps you signed in. We do not use advertising or analytics cookies.

Retention and deletion

• Recordings, screenshots, introduction videos and their assets, and exploration and editing records: deleted 6 months after creation.
• Share page settings and viewing totals: like the original introduction video, deleted 6 months after the video was created. Until then, the publishing user can still see the totals after the page expires or is stopped.
• Account and balance: kept until you ask us to close your account.
• Purchase and payment records: kept for as long as needed to meet legal obligations and handle disputes.
• Outcome tracking on share pages: reference IDs are deleted the day after their attribution window (1 to 30 days, 7 by default) ends, and individual outcome records 45 days after they are received. Daily totals are deleted with the video, like the share page's other totals. You can delete the outcome data at any time.
• Slack connection: the token, linked accounts and thread mappings are deleted when you disconnect (in Eizeno Settings or by removing the app in Slack). Approval and revision request records are kept with the production's records for the same period.
• Sign-in links and sign-in sessions: expire after 15 minutes and 30 days respectively, then are deleted.
• Chrome extension relay data: Encrypted relay packets are deleted after processing or when the connection ends. Decryption keys are held only in the memory of the extension and the production process. The retention periods above apply to completed recordings, videos and production records. The Target Site’s signed-in state stored in your Chrome browser is not covered by this deletion.

We respond to requests for disclosure, correction, deletion or suspension of use within 30 days after verifying your identity and the information concerned. Backups expire within 35 days.

Security

Communications are encrypted, and access to stored data is limited to the staff and processes that need it. Exploration and editing are processed in a separate environment that holds no payment keys.

Contact

ZenLab Inc., Park Front Shinjuku 202, 2-8-15 Shinjuku, Shinjuku-ku, Tokyo 160-0022, Japan
Representative Director: Yuhi Hatada
Please contact us through our Contact page.