Terms of Service

1. Acceptance of Terms

By accessing or using Metro Remote ("the Service"), operated by Metro Stack Limited (trading as Metro Remote — "we", "us", "our"; a private company registered in England & Wales, company no. 17195789, registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ), you agree to be bound by these Terms of Service and our Privacy Policy. If you do not agree, do not use the Service.

You must be at least 18 years old to use the Service. By using the Service, you represent that you are at least 18 years of age and have the legal capacity to enter into this agreement.

2. Description of Service

Metro Remote is a development platform for React Native iOS applications. Depending on the plan and features you use, the Service may include:

• A private device connection that carries development traffic (such as the Metro bundler, live reload, logs and app installs) between your computer and your own registered iOS device over an encrypted-in-transit connection, so the two do not need to be on the same network.
• Cloud builds (optional, paid per build): you upload an archive of your project’s source, and we arrange for it to be compiled and code-signed on macOS build machines operated by our build provider, using Apple Developer credentials that you supply. This is what allows a Windows user to produce a signed iOS build without owning a Mac.
• Over-the-air installation of the resulting app onto devices you have registered with your own Apple Developer account.
• Optional AI device control (Metro Remote MCP): an interface that lets an AI coding assistant you choose and control (such as Claude, Cursor or Codex) read your running app and interact with it on your device.
• The Metro Remote CLI, the web dashboard, and the associated APIs.

Not every feature is available on every plan, and some features are in beta. We may add, change, or withdraw features; where a change is material and adverse to you, section 18 applies.

2a. Cloud Builds: Your Content, Your Credentials, Your Apple Account

This section applies if you use cloud builds. It is the most important section for that feature, because you are sending us your source code and your Apple signing credentials.

You warrant that you are entitled to send us what you send us

You represent and warrant that you own, or are authorised to use and to submit to us and to our build provider, all source code, assets, dependencies, credentials, certificates and provisioning profiles you provide, and that doing so does not infringe anyone else’s rights or breach any licence, confidentiality obligation, or law that applies to you.

You remain responsible for your Apple relationship

• You are responsible for holding an Apple Developer account in good standing, for your compliance with Apple’s terms and programme rules, and for having authority to sign applications on that account.
• When you upload an App Store Connect API key, you authorise us and our build provider to use it, on your behalf and solely to deliver the builds you request, to create or reuse a signing certificate and provisioning profile on your Apple Developer account and to sign your app.
• You are responsible for the content, licensing and legality of the app you build, and for compliance with export-control laws (see section 14).
• You may revoke the key at any time in your Apple Developer account. Doing so will cause your builds to stop working.

Ownership, confidentiality, and the licence you give us

You keep all ownership of your source code, your credentials and the app we build for you. We claim no rights in them. You grant us and our named processors only the limited, non-exclusive licence to host, transmit, decrypt, compile, sign and store that material to the extent necessary to provide the specific build or service you requested, and for no other purpose. We do not use your source or your app to train machine-learning models. We treat your source and credentials as confidential.

Do not send us secrets you do not intend to send

The CLI attempts to exclude common secret files (such as .env files, keys and certificates) from the archive it uploads. That is a safeguard, not a guarantee. You are responsible for what is in your source tree; do not commit credentials into it.

Builds can fail, and not every project will build

Cloud builds depend on third parties — our build provider, Apple’s services, package registries and your own dependencies. We do not warrant that any particular project, dependency, or build will succeed, or that a build will complete within any particular time. See section 2b for what happens to your credits when a build does not succeed.

2b. Cloud Build Credits, Charges and Refunds

Cloud builds are charged using build credits, separately from your subscription. Cloud builds require a Pro plan or above.

• The metering unit is one build. Submitting a cloud build reserves one credit. Build duration, project size and the number of retries within a single build do not change the price.
• You are only charged for a build that succeeds. If a build fails, is cancelled by you, times out, or cannot be started, the reserved credit is returned to your balance automatically. If a check fails before the build starts, no credit is reserved at all.
• Buying credits. Credits may be purchased as a one-off pack, or included with a monthly build add-on. Current prices and pack sizes are shown on the pricing page and at checkout — those, and the amount shown to you before you confirm, are what you pay.
• Expiry and rollover. Credits from a one-off pack do not expire while the Service continues to offer cloud builds. Credits granted by a monthly add-on roll over month to month up to a maximum balance of 15 credits; a monthly grant that would take you above that cap is reduced to fit it. If you are a founding member or private-beta user, Beta Terms §8b also sets out the notice we must give before changing or withdrawing an add-on. Where these Terms and §8b differ on credit validity, whichever is more favourable to you applies (see section 19a).
• Refunds of a credit purchase. If we refund a purchase, we may remove the corresponding unused credits from your balance. We will never reduce your balance below zero.
• Concurrency and fair use. A limited number of your builds may run at the same time; further submissions are refused until one finishes. We may apply reasonable limits to protect the Service.
• Tax. Prices are exclusive of VAT and other applicable taxes, which are added at checkout where required.
• Credits are tied to your account, are not transferable between accounts, and have no cash value except as set out in sections 5a and 13.

Keep your own copies

The app file we produce is made available to you for a short time so you can install it, and is then deleted. It is not an archive. The install link expires. You are responsible for retaining your own source code and any build output you need to keep, and for your own backups. We are not a backup or storage service.

3. Account Registration

• You must sign in via GitHub to create an account
• You are responsible for maintaining the security of your account credentials and API keys
• You must notify us immediately if you suspect unauthorised access to your account
• You may not share your account or API keys with others unless on a Team plan
• One person or entity may not maintain more than one account

4. Subscriptions, Billing, and Auto-Renewal

• The Service is offered on monthly and annual subscription plans. Current pricing is displayed at metroremote.dev/pricing.
• Payments are processed through Stripe and billed in advance (monthly or annually depending on your plan).
• Auto-renewal: All subscriptions automatically renew at the end of each billing period (monthly or annually) at the then-current price unless you cancel before the renewal date. You will be charged automatically via the payment method on file.
• How to cancel: You can cancel your subscription at any time by running metro-remote billing in your terminal, which opens the Stripe billing portal. From there, click "Cancel plan". You can also cancel by emailing support@metroremote.dev. Cancellation takes effect at the end of your current billing period - you retain access until then.
• You may upgrade or downgrade your plan at any time through the billing portal. Downgrades take effect at the end of the current billing period.
• Confirmation: After subscribing, we will send you a confirmation email on a durable medium containing your subscription details, cancellation rights, and a copy of your right to cancel.
• Refunds: Refunds may be granted within 48 hours of payment under exceptional circumstances (e.g., accidental duplicate payment, service was completely unavailable). To request a refund, email support@metroremote.dev within 48 hours of the charge. After 48 hours, refunds are at our discretion. This does not affect your statutory rights (see Section 5).
• Payment method: You are responsible for keeping a valid payment method on file. If a scheduled payment fails, we will attempt to retry the charge. If all retry attempts fail, we may suspend your account until payment is resolved. Once payment is successfully collected or you update your payment method, your account will be reinstated and full access restored. Your data will be preserved during any suspension period. You can update your payment method at any time via the billing portal (run metro-remote billing).
• Payment disputes: If you believe a charge is incorrect, please contact us at support@metroremote.dev within 30 days of the charge appearing on your statement, before filing a dispute or chargeback with your bank or card issuer, so we can try to resolve it quickly - but you are not required to contact us first and may exercise your chargeback or Section 75 rights at any time. We aim to acknowledge billing queries within 2 business days and resolve them within 14 business days. If a payment is reversed through a chargeback or bank dispute, we reserve the right to suspend your account and revoke access to the Service pending resolution, and will notify you by email before or promptly after any suspension. Your data will be preserved during any suspension period. If the dispute is resolved in our favour, your account will be reinstated, access restored, and the original charge will stand. If resolved in your favour, or if we determine the charge was made in error, we will issue a full refund within 14 days using the original payment method, and you will not be penalised. Nothing in this clause affects your statutory rights under the Consumer Rights Act 2015, your rights under Section 75 of the Consumer Credit Act 1974, your right to seek chargeback through your card issuer, or any other rights you have under applicable law.
• Renewal reminders: For annual plans, we will send a reminder email at least 7 days before your annual renewal charge.
• VAT: All prices displayed are exclusive of VAT. UK VAT at 20% will be added at checkout for UK customers where applicable, in accordance with UK digital services VAT rules.
• We reserve the right to change pricing with 30 days advance notice. Price changes do not affect your current billing period.

5. Your Right to Cancel (Cooling-Off Period)

Under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, if you are a UK or EU consumer, you have the right to cancel your purchase within 14 days of subscribing, without giving any reason.

However, because Metro Remote is a digital service that begins immediately upon subscription (tunnel provisioning starts as soon as you run setup), by subscribing you:

• Expressly consent to the digital content being supplied before the end of the 14-day cancellation period
• Acknowledge that you will lose your right to cancel once the service has been fully provided during the cancellation period

If you have not yet used the service (i.e., you have not run metro-remote setup), you may cancel within 14 days for a full refund by emailing support@metroremote.dev. If you have used the service but cancel within 14 days, you are entitled to a refund for the unused portion of the billing period, minus a proportionate charge for the days of service you received (in accordance with CCR 2013 Regulation 35(5)).

To cancel after the cooling-off period, use the billing portal (run metro-remote billing) or email us. Your access continues until the end of your current billing period.

Model Cancellation Form

(As required by the Consumer Contracts Regulations 2013, Schedule 3, Part B)

5a. Cancelling a Build-Credit Purchase (Consumers)

Build credits are bought under a separate contract from your subscription, so they have their own cancellation rules. If you are a consumer in the UK or EU, you normally have 14 days to cancel a purchase of digital content and get a refund.

• If you have not used any of the credits: you may cancel within 14 days of purchase and we will refund you in full, within 14 days of you telling us.
• If you have used some of them: when you buy credits you are asking us to make them available to you immediately. If you then start a build, you have asked for supply to begin within the cancellation period, and you acknowledge that you lose the right to cancel in respect of the credits you actually consume. You keep the right to cancel the rest: we will refund the credits you have not consumed, at the price you paid for them.
• To cancel, email support@metroremote.dev or use the model cancellation form in section 5.

Nothing in this section affects your rights under the Consumer Rights Act 2015 if the Service is faulty or not as described.

6. Acceptable Use

You agree not to:

• Use the Service for any unlawful purpose
• Attempt to bypass device limits or other plan restrictions
• Reverse engineer, decompile, or disassemble the Service
• Use the relay for traffic unrelated to React Native development (e.g., general VPN use, torrenting, proxying)
• Interfere with or disrupt the Service infrastructure
• Resell access to the Service without our written consent
• Use the Service from any country or territory subject to comprehensive sanctions by the UK, EU, or US
• Automated scraping or systematic downloading of API templates or endpoints
• Circumventing, disabling, or interfering with rate limits or abuse detection systems
• Creating multiple accounts to evade suspension or rate limiting
• Sharing API keys with third parties outside of authorised Team plan usage
• Submitting for a cloud build any source, dependency or asset that you are not entitled to submit, that contains malicious code, or that is designed to attack, exploit, mine cryptocurrency on, or otherwise misuse the build machines
• Uploading Apple Developer credentials that are not yours or that you are not authorised to use, or using the Service to sign an application on an Apple account you do not control
• Using cloud builds as general-purpose compute, or submitting builds in a pattern designed to consume disproportionate build resources
• Using automated tools to generate artificial API traffic patterns

6a. Confidentiality of technical implementation

This section applies to new users on acceptance; existing users are bound after the 14-day notice period under §18 elapsed on 2026-06-14, or sooner upon dashboard re-acceptance.

The Service's internal architecture, proprietary algorithms, server-side code and runtime-served code templates, protocol details, network-level transport mechanisms, isolation and tenancy mechanisms, internal data structures, and API request and response payload shapes beyond what is documented at /docs are non-public confidential information of Metro Stack Limited. By using the Service, you agree:

• You may publicly share: your subjective experience using the Service, the outcomes you achieve, screenshots of the user-facing interface, the publicly-documented feature set, and word-of-mouth endorsements at the outcome level.
• You must keep confidential: any non-public technical implementation details that you reasonably understand to be non-public information through your use of the Service or through analysis of network traffic, binaries, or logs (including without limitation: internal architecture, proprietary algorithms, server-side code and runtime-served code templates, protocol details, internal data structures, network-level transport mechanisms, and isolation/tenancy mechanisms). This obligation covers what a reasonable person in your position would understand to be confidential; it is not intended to restrain ordinary inference or general speech about the Service's outcomes.
• No public speculation about internals: you will not publicly publish, blog, tweet, post, present, or broadcast accurate or speculative descriptions of the Service's internal technical implementation that purport to describe internal implementation as factual or reverse-engineered, without our prior written consent.

Statutory exceptions preserved: nothing in this clause prevents you from (i) making a disclosure specifically protected under the UK Public Interest Disclosure Act 1998 (where you are a worker as defined in that Act and the disclosure qualifies under s.43A-43L of the Employment Rights Act 1996, as amended; nothing in this section expands PIDA to disclosures otherwise unprotected); (ii) exercising data-subject rights under UK GDPR / Data Protection Act 2018; (iii) complying with a lawful court order, regulatory request, or statutory disclosure obligation; (iv) consulting your own legal advisors under privilege; (v) disclosure required to enforce your own statutory consumer rights under the Consumer Rights Act 2015; or (vi) any other non-waivable statutory right.

Pre-existing public disclosures excluded: this Section does not apply to technical details that were already public at the time you accepted these Terms (e.g., information already disclosed in our public documentation, npm package READMEs, marketing copy at metroremote.dev, prior press coverage, or third-party public reverse-engineering published before your acceptance).

Survival and sunset: these confidentiality obligations survive termination of your account and continue until the earlier of (i) five (5) years from the date the relevant detail first became known to you, or (ii) the date the detail enters the public domain through no breach by you of this Section. Public disclosure by Metro Stack Limited of any particular detail (e.g., a granted patent publishing) extinguishes the obligation as to that specific detail immediately.

Remedies: where breach results in loss of patent rights in jurisdictions with absolute novelty requirements, damages may be difficult to quantify. Metro Stack Limited may seek such remedies as a court of competent jurisdiction may award on standard equitable principles, including where appropriate injunctive relief, damages, and an account of profits, subject to the proportionality requirements of the Civil Procedure Rules and any applicable consumer-protection law. In respect of business-to-business users, this clause is subject to the reasonableness test under UCTA 1977 s.3.

US-resident users: publication of non-public technical implementation details may additionally constitute trade-secret misappropriation under the Defend Trade Secrets Act of 2016 (DTSA, 18 U.S.C. § 1836) and applicable state law (including but not limited to the California Uniform Trade Secrets Act and the New York common law of trade secrets), enforceable in U.S. federal and state courts in addition to any remedies available under English law.

7. Account Suspension & Appeals

We use automated systems to detect unusual API usage patterns that may indicate abuse. If our systems detect a pattern that exceeds our usage thresholds, your account may be subject to progressive enforcement:

1. Warning tier: A 2-second delay is applied to API responses for 15 minutes
2. Rate-limit tier: API requests are temporarily blocked (HTTP 429) for up to 1 hour
3. Suspension tier: Your account is suspended (HTTP 403) pending human review

Escalation is progressive within a 24-hour rolling window. If you receive a warning and continue the pattern within 24 hours, the next tier is applied.

New accounts receive a grace period of 24 hours with doubled thresholds to accommodate initial setup and testing.

You will be notified of any enforcement action via the API response (HTTP status code and error message). Suspended accounts receive a clear message explaining the suspension and how to appeal.

To appeal a suspension

• Email support@metroremote.dev with your account email and a description of your usage
• We aim to respond to all appeals within 24 hours
• Appeals are reviewed by a human - not by the automated system
• If the suspension is found to be a false positive, your account will be reinstated and thresholds may be adjusted

We reserve the right to permanently ban accounts engaged in deliberate, repeated abuse after human review.

For the specific metrics and thresholds used in abuse detection, see our Privacy Policy Section 14.

8. Intellectual Property

• Your content: You retain all ownership and intellectual property rights to your source code, app binaries, and development data. We claim no ownership over any content you transmit through the Service.
• Limited licence to us: By using the Service, you grant us and our named processors a limited, non-exclusive licence to process your data solely to provide the Service you requested — for example, routing your development traffic, temporarily storing an app file so it can be installed, and (if you use cloud builds) hosting, transmitting, compiling and signing your source archive as described in section 2a. This licence is limited to that purpose, and terminates when you stop using the Service.
• Our content: The Metro Remote service, CLI tool, website, dashboard, documentation, and all associated intellectual property are owned by us. We grant you a limited, non-exclusive, non-transferable, revocable licence to use the Service for its intended purpose while your subscription is active.

9. Data and Privacy

• Your use of the Service is governed by our Privacy Policy
• All tunnel traffic is encrypted in transit using industry-standard encryption
• We do not inspect, log, or store the content of your tunnel traffic (hot reload data, Xcode build data)
• OTA deploy: compiled app binaries (IPA files) are temporarily stored on our server for up to 30 minutes to enable installation, then automatically deleted. The most recent successful deploy per app is retained for up to 2 hours to support rollback, then automatically deleted

10. Service Availability

• We strive for high availability but do not guarantee 100% uptime
• We may perform scheduled maintenance with reasonable advance notice
• We are not liable for downtime caused by factors outside our reasonable control, including but not limited to: internet outages, cloud provider failures, natural disasters, pandemics, government actions, or other force majeure events
• We monitor service health and display current status at metroremote.dev/status
• Planned maintenance will be communicated in advance where possible
• We reserve the right to modify rate limits and usage thresholds to protect service quality for all users

11. Digital Content Rights and Limitation of Liability

Your Statutory Rights (UK Consumer Rights Act 2015)

If you are a UK consumer, the Service (as digital content) must be:

• Of satisfactory quality (CRA 2015 s.34)
• Fit for a particular purpose (CRA 2015 s.35)
• As described (CRA 2015 s.36)

If the Service does not meet these standards, you have the right to:

• A repair or replacement of the faulty digital content (CRA 2015 s.43)
• A price reduction if repair or replacement is not possible or does not resolve the issue (CRA 2015 s.44)
• The right to treat the contract as at an end and receive a refund if a single repair or replacement does not bring the digital content into conformity (CRA 2015 s.44(2)-(4))

Limitation of Liability

Subject to your statutory rights above, and to the maximum extent permitted by applicable law:

• We are not liable for any indirect, incidental, special, consequential, or punitive damages
• Our total aggregate liability shall not exceed the amount you paid us in the 12 months preceding the claim
• We are not responsible for lost data, lost profits, or business interruption

Nothing in these Terms excludes or limits our liability for: (a) death or personal injury caused by our negligence; (b) fraud or fraudulent misrepresentation; (c) breach of the terms implied by CRA 2015 ss.34-36 (satisfactory quality, fit for purpose, as described); or (d) any other liability that cannot be excluded or limited under applicable UK or EU law.

12. Indemnification

If you are a business user, you agree to indemnify, defend, and hold harmless Metro Remote from and against any claims, liabilities, damages, losses, and expenses (including reasonable legal fees) arising out of or in connection with: (a) your use of the Service in violation of these Terms; (b) your violation of any applicable law; or (c) any third-party claim arising from your use of the Service or content you transmit through it. This indemnification clause does not apply to UK or EU consumers, as it would be considered an unfair contract term under the Consumer Rights Act 2015 Part 2 and/or the Unfair Contract Terms Act 1977.

13. Termination

• You may cancel your subscription and close your account at any time via the billing portal or by emailing us
• We may suspend or terminate your account for violation of these Terms, with notice where practicable
• Your account may also be suspended during an active payment dispute or chargeback as described in Section 4. Suspension under that clause does not constitute termination, and the data deletion timeline in this section does not begin until the dispute is resolved and any resulting termination takes effect
• Termination without cause by us: If we terminate your account without cause (e.g., discontinuation of the Service), we will refund any prepaid subscription fees on a pro-rata basis for the unused portion of your billing period.
• Data deletion: Upon termination, your tunnel configurations, device data, connection keys, any stored Apple Developer credentials, any source archive still held, and your build records will be permanently deleted within 30 days. Billing records are retained as required by law (see our Privacy Policy).
• Your app files and credentials on termination: app files produced by a build are short-lived and are not retained for you (section 2b) — retain your own copies before you leave. We recommend you also revoke, in your Apple Developer account, any App Store Connect key you uploaded to us; revocation by you takes effect immediately and does not depend on us.
• Unused build credits on termination: if you close your account, we will refund unused credits you paid for (pack purchases) at the price you paid, on request. Credits you did not pay for — promotional credits, and credits included with a monthly add-on you have already used the benefit of — are not refundable and are not exchangeable for cash. If we terminate without cause, we will refund unused paid credits alongside the pro-rata subscription refund above.
• Sections that by their nature should survive termination will survive, including: Limitation of Liability, Indemnification, Intellectual Property, Governing Law, and Dispute Resolution

14. Export Controls

The Service uses industry-standard encryption which may be subject to export controls. You agree not to use or export the Service in violation of any applicable export control laws or regulations, including UK Export Control Act 2002, EU Dual-Use Regulation, and US Export Administration Regulations (EAR). You represent that you are not located in, or a national of, any country subject to comprehensive trade sanctions.

15. Third-Party Services

• The Service requires the Metro Remote app on iOS (available free from the Apple App Store). Open-source library attributions are available in the iOS app under Settings → Legal → Acknowledgements.
• Metro Remote is not affiliated with, endorsed by, or sponsored by Apple Inc. Apple, Xcode, iOS, and iPhone are trademarks of Apple Inc.
• Metro Remote is not affiliated with Meta Platforms, Inc. or the React Native / Metro bundler projects.
• Cloud builds are performed by a third-party build provider (currently Codemagic) on macOS build machines. Our processors are listed in the Privacy Policy. We remain responsible to you for the Service, but we are not responsible for outages, changes or failures of Apple’s services, our build provider, package registries, or your own dependencies.
• AI assistants are yours, not ours. If you connect an AI coding assistant (such as Claude, Cursor or Codex), you do so under your own account and terms with that provider. What your assistant reads from your app is sent to that provider under their terms and privacy policy. We do not control it and are not a party to it.

16. Dispute Resolution

We encourage you to contact us first at support@metroremote.dev to resolve any disputes informally. Most issues can be resolved quickly by email.

If a dispute cannot be resolved informally within 30 days, either party may pursue formal resolution as described below.

UK/EU consumers: Nothing in these Terms prevents you from bringing a claim in the courts of your country of residence, or from using any applicable alternative dispute resolution (ADR) procedure. UK residents may also refer complaints to the relevant ADR body or small claims court.

Alternative Dispute Resolution (ADR): We are not obliged to use, and do not currently participate in, alternative dispute resolution through a certified ADR provider under the Alternative Dispute Resolution for Consumer Disputes (Competent Authorities and Information) Regulations 2015. You are free to contact any relevant ADR body or use the small claims court. If we join an approved ADR scheme in future, we will update these Terms with the provider details. EU consumers may also use the European Commission's Online Dispute Resolution platform at ec.europa.eu/consumers/odr.

17. Governing Law

These Terms are governed by and construed in accordance with the laws of England and Wales. The courts of England and Wales shall have non-exclusive jurisdiction over any disputes arising from these Terms.

EU/UK consumers: If you are a consumer resident in the UK or EEA, you may also bring proceedings in the courts of your country of residence, and you benefit from any mandatory consumer protection provisions of your local law that cannot be waived by contract.

18. Changes to Terms

We may modify these Terms at any time. We will notify you of material changes via email or a notice on the website at least 14 days before the changes take effect. Your continued use of the Service after changes take effect constitutes acceptance of the revised Terms. If you do not agree with the changes, you may cancel your subscription before the changes take effect.

19. Complaints

If you have a complaint about the Service, contact us at support@metroremote.dev. We aim to acknowledge complaints within 2 business days and resolve them within 14 business days. If you are not satisfied with our resolution, you may refer the matter to the courts or any applicable ADR scheme (see Section 16).

19a. Order of Precedence

Where documents conflict, the following order applies, from highest to lowest: (1) any signed order form or data processing agreement between us; (2) the Beta Terms (during the beta period, and only for the matters they cover); (3) these Terms; (4) the Privacy Policy; (5) plan descriptions, documentation and other material on the website. This order never operates to give you less than another of these documents gives you: where these Terms are more favourable to you than the Beta Terms on the same point, these Terms apply. Nothing in this order of precedence removes any right you have as a consumer that cannot be excluded by law.

20. General

• Entire agreement: These Terms, together with the Privacy Policy, constitute the entire agreement between you and Metro Remote regarding the Service.
• Severability: If any provision of these Terms is found to be unenforceable, the remaining provisions will continue in full force and effect.
• Waiver: Our failure to enforce any provision of these Terms does not constitute a waiver of that provision or any other provision.
• Assignment: You may not assign or transfer your rights under these Terms without our consent. We may assign our rights and obligations (for example, in the event of a business transfer or acquisition) with notice to you.

21. Contact

For questions about these Terms of Service, contact us at support@metroremote.dev.