Terms of Service

EarBox is currently in early access. By using the service, you agree to the terms below.

Effective date: May 2026

Service scope

- EarBox turns newsletters into audio briefings.
- Features may change, be paused, or be removed during early access.

Eligibility

- You must be able to form a binding contract to use the service.
- You are responsible for complying with applicable laws.

Accounts

- You are responsible for keeping access to your account secure.
- You can disconnect Gmail at any time from the product settings.

Email safety

- EarBox is designed to process newsletters, not personal email.
- We apply filtering to minimize data collection, and discard non‑newsletter mail.

Acceptable use

- Don’t use the service to break the law or violate others’ rights.
- Don’t attempt to disrupt, reverse engineer, or abuse the service.
- Don’t use the service to access someone else’s email account.

User content

- You retain rights to your content. You grant EarBox permission to process your newsletter content solely to provide the service to you.
- You are responsible for ensuring you have the right to use the content you connect to EarBox.

No warranties

- The service is provided “as is” without warranties of any kind.
- We are not responsible for missed emails or delivery delays.

Limitation of liability

- To the maximum extent permitted by law, EarBox will not be liable for indirect, incidental, special, consequential, or punitive damages.
- Our total liability for any claim will be limited to the amount you paid to EarBox for the service in the 3 months before the event giving rise to the claim, or 0 if you have not paid anything.

Termination

- You can stop using the service at any time.
- We may suspend or terminate access if we reasonably believe the service is being abused or used unlawfully.

Changes

We may update these terms from time to time. Continued use of the service after changes means you accept the updated terms.

Contact

For support, contact us via the email address listed on the OAuth consent screen.