Privacy policy
Last Updated: November 3, 2026
UNCHAIN, Inc. (“we”) handles personal information in the meeting-notes service “Pulse” (the web app, the desktop apps, our sign-in service “Pulse ID” and this website; together, the “Service”) in accordance with Japan's Act on the Protection of Personal Information (the “APPI”) and other applicable laws, as set out in this policy.
1. Our two roles
Some personal information in the Service we handle for our own business, and some we process on behalf of customer organisations. Our responsibilities differ for each.
(1) Information we handle for our own business
Users' account details, sign-in records, billing information, usage analytics and enquiries are handled by us as the business responsible for them (the controller). This policy mainly governs this information.
(2) Information we process on behalf of customer organisations
Meeting audio, transcripts and notes, imported calendar events, email and chat, library files, the facts extracted from them, and information about people outside the organisation such as the other side of a meeting (“external people”) — together, “Customer Data” — are processed by us on behalf of the organisation that subscribes to the Service (the “Customer”), which entrusts us with it. For Customer Data, the Customer is the business responsible under the APPI (the controller): it specifies and communicates the purposes of use, obtains consent where the law requires it, and answers requests from the people concerned.
We process Customer Data only to provide the Service and never use it to train AI models. As set out in our Terms, we may also use it to evaluate and improve the Service, and the Customer's admins can turn this off in Settings (see “3. Purposes of use”). We do not provide Customer Data to third parties for our own purposes.
2. Information we collect
- Account details: name, email address, the name of your organisation and your role in it, your password (stored in a form that cannot be reversed), your Google account identifier if you sign in with Google, settings such as language and time zone, your two-step verification settings, and the versions of the terms and policies you accepted at registration
- Sign-in and security records: the time and result of each sign-in attempt, IP address, browser and operating system, and audit logs of administrative actions
- Billing information: the payer's email address, plan, number of seats, and invoice and payment records. Card details are entered on the screen of our payment processor (Stripe); we never receive them
- Usage information: actions in the web app and the desktop apps' window (pages viewed, clicks and use of input fields, with all on-screen and typed text masked), session recordings with all text masked, error details, browser, operating system and screen size, and an identifier stored in a cookie or local storage. After you sign in, this is linked to your user ID, name, email address, and your organisation's ID and name
- Desktop app logs: records of how the app runs (counts, reasons, error codes, the connection type of audio devices). They never contain names, meeting titles, note text or the names of audio devices
- Customer Data: meeting audio (deleted after transcription), transcripts, live captions, notes, memos, meeting events and their participants, events, email and messages imported from services a user connects (such as Google Calendar, Gmail, Microsoft 365 and Slack), files uploaded to the library, the people, companies and facts extracted from these, and information about external people and companies gathered from public web pages before a meeting (an organisation can turn this off)
- Enquiries: the name, company, email address, role and message you send through this website's form or by email, and the parameters showing how you reached this website (such as utm_source)
3. Purposes of use
We use the information above only for the following purposes.
| Information | Purposes |
|---|---|
| Account details | Identifying and authenticating you; providing the Service; inviting and managing members of an organisation; managing plans; sending important notices (changes to the terms or this policy, incidents, confirmation of account deletion); answering your questions |
| Sign-in and security records | Preventing and detecting unauthorised access; investigating security incidents; operating the Service securely |
| Billing information | Charging and collecting fees; accounting; keeping the records the law requires |
| Usage information (PostHog) | Understanding how the Service is used; finding and investigating bugs; improving features and usability; detecting outages and misuse |
| Desktop app logs | Investigating problems; making recording more reliable |
| Customer Data | Providing the Service (transcription; writing notes, summaries and briefs; answering questions; drafting follow-up emails and CRM updates; sending to the integrations the Customer directs); support at the Customer's request; keeping the Service secure; evaluating and improving the Service (below) |
| Enquiries | Answering you; guiding you through downloads and adoption; understanding how people find us |
Improving the Service: as set out in our Terms, we may use Customer Data to evaluate and improve the quality of the Service (for example, checking the accuracy of transcription and extraction, or investigating bugs). We never use Customer Data to train AI models. When our staff access Customer Data, the access is recorded in the Customer's audit log. The Customer's admins can turn this use off in Settings; the change takes effect within 30 days.
We do not use personal information for advertising and we do not sell it.
4. Sensitive personal information
We do not ask for special care-required (sensitive) personal information as defined in Article 2(3) of the APPI, such as race, creed, medical history or criminal record. Depending on what is said in a meeting, however, transcripts and notes may contain it.
The user who records a meeting, and their organisation, are responsible for telling participants that the meeting is recorded and transcribed and for obtaining their consent where the law requires it. Obtaining sensitive personal information generally requires the person's own consent (APPI Article 20(2)). Also follow any industry rules (for example in healthcare or finance) and agreements with the other side.
At registration we record that the user has understood and accepted this responsibility, together with the versions of the terms and policies they accepted.
5. Provision to third parties
We do not provide personal data to a third party without the person's prior consent, except:
- where required by law, or in the other cases listed in Article 27(1) of the APPI (for example, to protect a person's life, body or property when consent is difficult to obtain, or to cooperate with a public authority performing duties prescribed by law)
- when we entrust its handling to a service provider as described in “6. Service providers and third parties in foreign countries”
- when the business is succeeded through a merger or otherwise
When a Customer turns on an integration (such as HubSpot, Salesforce, Slack, Notion or Google Docs) and exports a note or applies a CRM update, the data is sent on the Customer's instruction. How the recipient handles it is governed by the Customer's agreement with that provider.
When we provide personal data to a third party, we keep a record as the law requires.
6. Service providers and third parties in foreign countries
We entrust the handling of personal data to cloud and other service providers to the extent needed to provide the Service. They are listed on our subprocessor list. We choose them after checking how they protect personal information, require appropriate handling through contracts or terms of service, and supervise them as necessary.
Where data is stored
The Service's database (including Pulse ID), the application runtime, the storage for meeting audio and library files, and the database backups are all in Japan (Tokyo). These providers (Supabase, Vercel and Wasabi) are US companies.
Information handled in the United States
AI processing (transcription, live captions, notes and summaries), usage analytics, payments and email delivery are carried out by US providers in the United States. The purpose and the information for each are on the subprocessor list.
- Country: the United States of America (Anthropic, OpenAI, Google, ElevenLabs, AssemblyAI, PostHog, Stripe and Resend, including Vercel's AI Gateway, which routes calls to the AI providers)
- Its personal information protection system: the United States has no comprehensive federal law equivalent to the APPI; personal information is protected by Section 5 of the Federal Trade Commission Act, sector-specific federal laws, and state laws such as the California Consumer Privacy Act. For details, see the Personal Information Protection Commission's survey of foreign personal information protection systems (United States, federal; in Japanese).
- Measures the providers take: our contract or terms with each provider (including their data processing terms) require them to handle the data only for the purposes we entrust, to keep it secure and to manage their own subcontractors. We use Anthropic, OpenAI and Google under terms under which data sent through their APIs is not used to train their models. Data is sent over encrypted connections (TLS), and we send only what each task needs.
On request, we will provide the information set out in Article 28(3) of the APPI, including details of these measures.
This website's contact form
Enquiries sent through this website's form reach us through Web3Forms, a form delivery service operated by Web3Creative (India), whose servers are in the United States; its terms and privacy policy govern how it handles them. For India's personal information protection system, see the Commission's report on India (in Japanese). You can also email contact@the-unchain.com directly instead of using the form.
7. How long we keep information
We keep personal information for as long as its purposes require and then delete it. The main periods are:
| Information | Retention |
|---|---|
| Notes, transcripts, imported email and chat records | The organisation's retention period (12 months by default; an admin can choose 6, 12, 24 or 36 months, or keep forever). Notes past the period move to the trash and are permanently deleted 30 days later; email and chat records past the period are deleted |
| Extracted people, companies and facts | Until every note, email and chat record they came from is deleted, or earlier when an admin deletes the person or the organisation is deleted |
| Notes in the trash | Permanently deleted after 30 days (the owner or an admin can delete them sooner) |
| Meeting audio | Deleted right after transcription. Pieces of a failed upload are deleted within 24 hours (the desktop app keeps the original file of a recording it could not send on your computer) |
| Sign-in records (Pulse ID) | 90 days |
| Audit logs | 2 years |
| AI usage records (time, feature, cost and similar metadata; never the content) | 13 months |
| Notifications | 90 days |
| Desktop app logs (PostHog) | 14 days |
| Usage analytics (PostHog) | PostHog's retention period. When you delete your account, we also delete your data in PostHog |
| Billing records | As long as the law requires |
| Accounts | Deleted after a 30-day grace period from the deletion request (you can cancel during it). Notes shared in the organisation's spaces and other business records stay with the organisation, attributed to a former member |
| Backups | Encrypted and kept for 30 days. Deleted data disappears from the backups within 30 days |
| Enquiries | As long as needed to deal with them |
8. Security measures
We take the following measures to prevent leaks, loss or damage of personal data and otherwise keep it secure.
Basic policy
This policy is our basic policy for handling personal data properly, including compliance with the law and a point of contact.
Rules for handling personal data
Our internal rules and design documents set out how personal data is handled at each stage (collection, use, storage, provision and deletion) and who is responsible.
Organisational measures
- We have appointed a personal information protection manager and made responsibilities for handling personal data clear.
- Only staff who need it can access Customer Data, and access is recorded. When our staff access Customer Data, the access is recorded in the Customer's audit log.
- We have a process for reporting and responding to incidents such as leaks.
Human measures
- We train staff who handle personal data and bind them to confidentiality.
Physical measures
- Customer Data is stored in our cloud providers' data centres (Tokyo), whose physical security they manage.
- We protect the devices we use for work against theft and loss.
Technical measures
- All connections are encrypted (TLS), and stored data is encrypted at the infrastructure level.
- Credentials for connected services (such as access tokens) are additionally encrypted by the application.
- Each organisation's data is kept separate, with row-level access control in the database so that no organisation can reach another's data.
- Users can turn on two-step verification with an authenticator app. Our admin tools are limited to authorised staff and require two-step verification.
- Sign-in attempts are recorded and repeated failures are detected. Repeated wrong two-step verification codes lock the account for a while.
- We regularly scan the software the Service depends on for vulnerabilities.
- We back up the database daily with encryption and practise restoring it.
Understanding the foreign environment
Personal data is stored in Japan. Information handled by US providers in the United States is described in “6. Service providers and third parties in foreign countries”. We take our security measures with each country's personal information protection system in mind.
9. Incidents
If personal data is or may have been leaked, lost or damaged, we act at once to contain it and investigate the cause. Where the APPI requires it, we report to the Personal Information Protection Commission and notify the people affected.
If the incident concerns Customer Data, we notify the Customer without undue delay and give it the information and help it needs to meet its own legal obligations to report and notify.
10. Your rights and requests
If you have an account
For personal data we hold about you (such as your account details), you can ask us to tell you the purposes of use; to disclose it (including records of provision to third parties); to correct, add to or delete it; to stop using it or erase it; and to stop providing it to third parties.
- You can change your name and other account details in the app's settings (Profile) at any time.
- You can download your data from the app's settings.
- You can request deletion of your account in the app's settings (it is deleted after a 30-day grace period).
- For other requests, email privacy@the-unchain.com. After confirming your identity, we will respond without delay as the law requires, normally electronically. We charge no fee.
If you are an external person (for example, the other side of a meeting)
Information about people outside an organisation that uses Pulse, such as meeting participants or business contacts, is that organisation's Customer Data. Please send requests for disclosure, correction, deletion or suspension of use to the organisation that recorded the information. If you contact us directly, we will pass your request to the organisation concerned and help it respond.
An organisation's admins can export the data about a specific person (as JSON) and delete everything about that person in the Service. A deleted person is excluded from further recording so that their information is not rebuilt from later meetings.
11. Cookies and external transmission
This website (www.pulse.co.jp) uses no cookies for analytics or advertising. It keeps the parameters showing how you reached it (such as utm_source) in your browser's session storage while you browse, and sends them with an enquiry.
The web app and Pulse ID use cookies to keep you signed in and to remember display settings. The web app also uses PostHog's cookies and local storage for usage analytics. If you turn cookies off in your browser, you may not be able to sign in.
The information sent from your device to outside providers, the recipients and the purposes are published in our notice on external transmission.
12. Changes to this policy
We may change this policy when laws or the Service change. Changes are posted on this page with the date of the last update. We announce material changes in the Service or by email before they take effect.
13. Company details and contact
- Company: UNCHAIN, Inc. (UNCHAIN株式会社)
- Address: Oyster Building 2F, 1-5-1 Nihonbashi Kakigaracho, Chuo-ku, Tokyo, Japan
- Representative: Lui Ebina, Representative Director
- Personal information protection manager: privacy@the-unchain.com
Please send questions, comments, complaints and requests about personal information to the personal information protection manager by email.
This policy is written in Japanese, and this English version is a translation for reference. If they differ, the Japanese version prevails.