Terms of Service

Mercur lets developers expose local HTTP, WebSocket, and raw TCP services through relay-managed public endpoints, inspect certain request activity, configure access rules, and connect local agents or desktop apps.

Some features may be experimental, beta, limited, or changed as the product develops. We may add, remove, or modify features to improve reliability, security, legal compliance, or product fit.

You must be at least 18 years old and legally able to enter into these Terms. You must provide accurate account information and keep your credentials, session devices, agent authentication tokens, and per-server tokens secure.

Guest mode may create a temporary guest customer identifier and default endpoint. Guest access is limited and may be removed, migrated, or deleted at any time.

You are responsible for the services, data, files, requests, responses, payloads, headers, secrets, credentials, personal data, and other content that you send through Mercur or make available through a Mercur endpoint.

HTTP log modes may save request metadata and previews, including method, path, query, headers, body preview, content type, source IP, user agent, status, latency, and timestamps. Do not enable logging for traffic that contains secrets, authentication cookies, private keys, health data, payment card data, or other sensitive personal data unless you have a lawful basis and have taken appropriate precautions.

You must obtain all notices, consents, permissions, and rights needed for Mercur to process tunnel traffic and customer content on your behalf.

Subject to these Terms, we grant you a limited, revocable, non-exclusive, non-transferable license to download and use Mercur agent or desktop software only to connect your local services to Mercur.

You may not reverse engineer, modify, distribute, sublicense, or create derivative works from Mercur software except where applicable law gives you a non-waivable right.

Mercur provides controls such as authenticated sessions, agent tokens, server tokens, runtime controls, and optional IP/CIDR whitelist rules. These controls reduce risk but do not replace your own security review.

You are responsible for choosing what to expose, restricting access where needed, rotating leaked tokens, disabling endpoints you no longer need, and protecting local services that receive proxied traffic.

Mercur may offer free, trial, beta, and paid plans. Pricing, limits, billing cycles, renewal terms, and included usage will be shown in the product or order page when you subscribe.

The payment processor is currently to be confirmed. When paid plans are enabled, you authorize us and our payment processor to charge the payment method you provide for recurring fees, usage fees, taxes, and other amounts you agree to pay.

Unless the product or applicable law says otherwise, paid subscriptions renew automatically until canceled, cancellations take effect at the end of the current billing period, and fees are non-refundable and non-prorated.

You are responsible for taxes, payment failures, chargebacks, and keeping billing information current. We may suspend or downgrade access for non-payment.

We and our licensors retain all rights in Mercur, including software, interfaces, designs, documentation, names, logos, and service materials. You retain rights in your customer content and tunnel traffic.

If you provide feedback, suggestions, or ideas, you grant us permission to use them without restriction or compensation.

Mercur may depend on hosting, database, payment, analytics, advertising, support, or infrastructure providers. Third-party services may have their own terms and privacy practices.

Examples mentioned in product copy, such as Stripe, GitHub, Linear, Postgres, or Redis, may be use cases rather than integrations unless the product explicitly connects to them.

You may stop using Mercur at any time. We may suspend or terminate access if you violate these Terms, create security or legal risk, fail to pay amounts due, or use the service abusively.

After termination, we may delete or retain data as described in the Privacy Policy, DPA, product settings, legal obligations, backups, and legitimate business records.

Mercur is provided on an "as is" and "as available" basis to the maximum extent permitted by law. We do not guarantee uninterrupted service, error-free operation, permanent endpoint availability, successful delivery of every request, or that the service will meet every requirement.

You are responsible for testing Mercur before relying on it in production workflows.

To the maximum extent permitted by law, we will not be liable for indirect, incidental, special, consequential, exemplary, punitive, or lost-profit damages, loss of data, business interruption, security incidents caused by your configuration, or costs of substitute services.

To the maximum extent permitted by law, our total liability for all claims related to Mercur will not exceed the greater of USD 100 or the fees you paid for Mercur in the three months before the event giving rise to the claim.

You will defend, indemnify, and hold us harmless from claims, damages, liabilities, costs, and expenses arising from your tunnel traffic, customer content, exposed local services, breach of these Terms, violation of law, or infringement of third-party rights.

We may update these Terms from time to time. If changes are material, we will provide reasonable notice through the website, dashboard, email, or another appropriate channel. Continued use after changes take effect means you accept the updated Terms.

These Terms are governed by [Governing law and courts], except where mandatory consumer or data protection laws require otherwise.

Questions about these Terms may be sent to [privacy@your-domain.com].