Application terms of service

The terms for the desktop app and browser extensions, and how distribution and automatic updates work.

These terms set out the conditions for using the Pulse desktop app and browser extensions (together, “the app”) provided by UNCHAIN, Inc. (“we”). They apply to anyone who installs the app on a device or uses it.

What these terms cover, and how to read them

These terms cover the macOS and Windows desktop apps and the browser extensions Pulse provides. Capturing meeting audio and transcribing it is done by the desktop app on your device. The web application used in a browser supports viewing and editing notes that are already saved, and is governed directly by the terms of service rather than by these terms. The fundamentals of the contract — accounts, charges, the scope of liability, governing law — are set out in the terms of service; these terms are a set of special provisions covering only what is specific to software installed on a device.

Article 1 (Purpose and scope)

  1. The purpose of these terms is to set out the rights and obligations between us and users in relation to use of the app.
  2. The app comprises the macOS and Windows desktop apps, the browser extensions we provide, and software provided alongside them (including the virtual camera and other components installed with the desktop app).
  3. These terms constitute standard terms of contract under the Civil Code. By installing or beginning to use the app, a user is deemed to have agreed to these terms forming part of the contract.
LegislationCivil Code, Article 548-2 (agreement to standard terms of contract)

A person who has agreed to enter into a standard transaction is deemed to have agreed to the individual provisions where they have agreed that the standard terms form part of the contract, or where the party who prepared the standard terms indicated to the other party in advance that they would. Paragraph 2 of that article provides that a provision found to unilaterally harm the other party's interests is deemed not to have been agreed.

Article 2 (Relationship to the other terms, and order of precedence)

  1. In addition to these terms, the terms of service apply to use of the app. Where the app is used for the API or for integrations with external services, the API and platform terms of service also apply.
  2. The terms of service are the body of the contract for use of the service; these terms are special provisions supplementing them in respect of matters specific to the app.
  3. Where these terms, the terms of service and the API and platform terms of service conflict or are inconsistent, the following order of precedence applies.
  4. An individual contract concluded between us and the contracting party
  5. Those provisions of these terms concerning the operation of the app, device permissions, distribution and updates
  6. The terms of service
  7. The remaining provisions of these terms
  8. Articles 26 and 27 of the terms of service apply mutatis mutandis to governing law and jurisdiction in the event of a dispute.

Article 3 (Licence granted and prohibited conduct)

  1. We grant users a non-exclusive, non-transferable and non-sublicensable right to use the app in accordance with these terms and the terms of service.
  2. The licence in the preceding paragraph is to use the app on devices the user owns or manages; it does not transfer any intellectual property rights in the app.
  3. A user must not do any of the following in relation to the app.
  4. Copy, distribute, lend, sublicense or sell it
  5. Decompile, disassemble or otherwise analyse it (other than research carried out within the scope and on the conditions set out in the vulnerability disclosure policy)
  6. Modify or adapt it, or create derivative works
  7. Remove or alter copyright notices or other notices of rights
  8. In addition to the preceding paragraph, the prohibitions in Article 12 of the terms of service apply to use of the app. The conduct listed in that article is prohibited when carried out through the app as well.

Article 4 (Distribution of the app)

  1. The desktop app may be obtained by downloading it directly from our website, and may also be distributed in bulk to the devices a company or other organisation manages using a device management tool (MDM) or other asset management mechanism.
  2. The browser extensions may be obtained from the extension store of the corresponding browser, and may also be distributed in bulk to managed devices using an organisation's browser management features.
  3. We publish the location from which installers may be obtained for distribution, and an endpoint for checking the current version. Where they are and how to use them are set out in Bulk installation and updates by an administrator.
  4. We do not warrant that a copy of the app obtained from anywhere other than the locations we publish is identical in content or safe to use.
About stating the distribution source

The installer distribution source, the version check endpoint and the browser extension identifiers are left as placeholders in the help centre. Replace them with the locations UNCHAIN, Inc. actually operates. Not identifying the distribution source weakens the effect of paragraph 4 of this article.

Article 5 (Automatic updates and supported environments)

  1. We update the app to add features, fix defects, maintain security and for other purposes.
  2. While running, the desktop app checks for updates at intervals and, where one is available, obtains it and applies it when the app can be restarted or when the user chooses to apply it. Browser extensions are updated by the browser's own update mechanism.
  3. Where the automatic updates in the preceding paragraph do not work because of restrictions on write permissions on the device, an organisation's distribution policy or for other reasons, updates are to be applied by the company or other organisation that manages the device. The steps in that case are set out in Bulk installation and updates by an administrator.
  4. For updates that matter for security, we may restrict use of versions to which the update has not been applied.
  5. We determine which operating system and browser versions the app is supported on and publish them in this help centre. On versions outside that, the app may not work correctly.
If you carry on using an old version

On a version to which updates have not been applied, defects and vulnerabilities that have been fixed remain. The scope of our liability for loss arising in that situation is as set out in Article 17 of the terms of service. What to check where updates are not arriving is covered in Uninstalling and reinstalling.

Article 6 (Device permissions)

  1. In order to provide its features, the app may ask for the following permissions managed by the device's operating system or browser.
  2. Use of the microphone (to capture what participants say)
  3. System audio capture or screen recording permission (to capture the audio the device is playing; on macOS this is requested as screen recording permission)
  4. Accessibility permission (to detect the state of meeting apps and to operate shortcuts)
  5. Sending notifications (to tell you a meeting has started, a note has finished generating and so on)
  6. Calendar access (to match meetings to notes)
  7. Network access
  8. For browser extensions, the permissions needed to work on a meeting app's screen (to obtain speaker labels and to post notices to participants)
  9. Permissions may be revoked at any time from the operating system's or browser's settings. Where a permission is revoked, the features that depend on it do not work.
  10. We use each permission only to the extent needed to provide the app's features. Information obtained is handled as set out in the privacy policy.
  11. The app captures audio only from meetings where the user has started transcription. It does not capture audio continuously while a permission is in force.

The steps for granting permissions are in Initial setup guide, and the conditions under which transcription begins are in Pulse basics.

Article 7 (Connectivity and offline operation)

  1. Users are to provide, at their own cost and risk, the devices, connectivity and other environment needed to use the app.
  2. Data charges arising from use of the app are borne by the user.
  3. Some features of the app may be available while disconnected. In that case, data stored on the device is synchronised once connectivity returns. Where the app is deleted or the device is reset before synchronisation completes, that data cannot be recovered.

Article 8 (Organisation-wide rollout)

  1. Where a company or other organisation distributes the app in bulk to the devices it manages, using a device management tool or otherwise, that company or organisation is responsible for ensuring the users it distributes to comply with these terms and the terms of service.
  2. How to distribute, pre-granting permissions, managing updates and default settings for a bulk rollout are set out in Bulk installation and updates by an administrator.
  3. Where the app is distributed in bulk to employees' devices, the company or organisation is to establish internal rules on recording meetings in advance and make them known to the users it distributes to. Our thinking on this is set out in How far you can go with AI minutes (a guide for teams).

Article 9 (Purchasing and cancelling a paid plan)

  1. Applications for paid plans, payment, the contract period and cancellation are as set out in Articles 9 and 10 of the terms of service and in Plans and payment and About cancellation. The conditions are the same whether or not the application is made from the app.
  2. Where you proceed to apply for a paid plan from a screen in the app, the plan, the number of seats, the contract period, the amount charged, whether it renews automatically and how to cancel are all shown before the application is confirmed.
LegislationAct on Specified Commercial Transactions, Article 12-6 (display when receiving a specified application)

When receiving an application in mail-order sales, the final confirmation screen must show the quantity of the service, the consideration, when and how payment is made, when it is provided, and matters relating to withdrawal or cancellation of the application, and must not display these in a way that misleads. On the paid plan application screen, the amount and billing cycle are shown before confirmation.

Article 10 (Discontinuing the app)

  1. We may discontinue the app for a particular operating system or browser. Where we do, we will give notice a reasonable period before the discontinuation date, by publishing it in this help centre or by sending notice to registered email addresses.
  2. Even where the app is discontinued, users may still be able to view, edit and export saved notes by other means we provide.
  3. Where the service as a whole is discontinued, Article 18 of the terms of service applies.
  4. The steps for deleting and reinstalling the app are set out in Uninstalling and reinstalling.

Supplementary provisions

  1. These terms take effect on Please contact us.
  2. The revision history of these terms is published on this page.

Related articles

← Post-mortem: unintended automatic joining of a workspaceAPI and platform terms of service →