Terms of Service

Last updated: 30 March 2026

1. Acceptance

By accessing or using Earshots.io ("the Service") you agree to be bound by these Terms. If you do not agree, do not use the Service.

2. Beta status

The Service is currently in private beta. This means:

  • Features may be added, changed, or removed at any time without prior notice.
  • The Service may contain bugs, errors, or incomplete functionality.
  • Uptime, performance, and data durability are provided on a best-efforts basis and are not guaranteed.
  • We may reset, migrate, or restructure data during the beta period where operationally necessary. We will give reasonable notice before any planned action that affects stored content.
  • The beta period will end when we publicly announce general availability. These Terms will be updated at that time.

By using the Service during beta you acknowledge these limitations and agree that Earshots.io shall not be liable for any loss or disruption arising from them.

3. What Earshots does

Earshots.io is a collaboration tool for music supervisors, directors, and composers. It allows you to upload video and audio files, generate shareable review links, collect timestamped feedback, formally approve soundtrack selections, and share files with collaborators.

4. Your content

  • You retain full ownership of all video, audio, and other files you upload.
  • By uploading you confirm that you hold the necessary rights to the content, or have explicit permission from the rights holder to use it within this tool.
  • You grant Earshots a limited, non-exclusive licence to store and serve your files solely for the purpose of providing the Service to you.
  • We do not claim ownership of your content and will never use it for any other purpose.

5. Acceptable use

You agree not to upload content that is illegal, infringes third-party intellectual property rights, or contains malware or harmful code. We reserve the right to remove content and suspend or terminate accounts that violate these terms without prior notice.

6. Storage and limits

Each account is subject to a storage limit of 5 GB across all projects. Individual file limits apply: video files up to 4 GB and audio files up to 500 MB each. File Share links are limited to 10 GB total and expire after 8 days. These limits may change during the beta period.

7. Account security

You are responsible for maintaining the confidentiality of your account credentials. We are not liable for any loss or damage resulting from unauthorised access to your account.

8. Password-protected links

You may password-protect share links. You are responsible for the security of any passwords you create and for deciding who you share links with.

9. Service availability

We aim for high availability but do not guarantee uninterrupted or error-free service. During the beta period in particular, planned and unplanned downtime should be expected. We may modify, suspend, or discontinue features at any time.

10. Limitation of liability

To the fullest extent permitted by applicable law, Earshots.io is provided "as is" and "as available" without warranties of any kind, whether express or implied. We are not liable for any indirect, incidental, special, or consequential damages arising from your use of or inability to use the Service, including but not limited to loss of data, loss of revenue, or business interruption. This limitation applies with particular force during the beta period.

11. Governing law

These Terms are governed by the laws of England and Wales. Any disputes shall be subject to the exclusive jurisdiction of the courts of England and Wales.

12. Changes to these terms

We may update these Terms from time to time, particularly as the Service transitions from beta to general availability. We will notify registered users of material changes by email. Continued use of the Service after changes constitutes acceptance of the revised Terms.

13. Contact

Questions about these Terms: hello@earshots.io

Home Terms Privacy Feedback Beta© 2026 Earshots.io

Report a Bug or Suggest a Feature

Tell us what went wrong and we'll look into it.

Thanks! We've logged this bug and will investigate.