Beta Terms

1. Scope

These Beta Terms apply to founding members and other private-beta users of Metro Remote ("the Service"), operated by Metro Remote ("we", "us", "our"). They supplement (do not replace) the standard Terms of Service and our Privacy Policy.

In case of conflict between these Beta Terms and the standard Terms during the beta period, these Beta Terms prevail. When the beta period ends, founding members automatically transition to the standard Terms (see Section 8).

2. Service state (private beta)

Metro Remote is currently in a paid private beta since May 2026. Some components are still in active development and deployment:

• CLI (@metroremote/cli) — preparing for npm publication. You will receive an email with installation instructions when it is available.
• iOS app — TestFlight invites for founding members are sent manually after activation. Public App Store listing is pending Apple Developer organisation verification.
• Backend tunnel infrastructure — fully operational (production relay live).
• AI MCP integration — operational.
• OTA deploy and tester-invite features (marketed as "Beta" on the Pro plan) — subject to the as-is and discontinuation provisions of Sections 5 and 5a.

By becoming a founding member, you acknowledge that full access to the CLI and iOS app may not be available at the moment of payment. We are working to deliver these components as soon as practical, with a current target of July 2026 (Q3 at the latest). This is a best-effort estimate, not a guarantee, and may be longer due to factors outside our reasonable control (including Apple Developer organisation verification, App Store / TestFlight review timelines, and npm package publication).

For specific provisions covering the possibility that the Service does not reach full launch, see Section 5a (Discontinuation risk) below.

3. Founding member pricing — locked-in for life

Cohort cap (anchors the "limited founder spots" claim): Founding membership is limited to a fixed, finite number of spots that was set before the program opened. The cap is enforced atomically by our API — there is no overselling and no replenishment from cancellations (once a spot is taken, it counts against the cap whether or not the subscription stays active, per the permanent forfeiture clause below). The exact number is undisclosed to preserve commercial flexibility (we may raise or lower the cap, or close the program at any time, without changing public-facing copy). Anyone may request written confirmation of the current cap by emailing support@metroremote.dev.

By paying as a founding member you agree:

• $99 is charged today via Stripe for your first year of Pro access.
• Your subscription auto-renews at $99/year — locked in at this rate for the lifetime of your continuous, uninterrupted subscription.
• This locked-in $99/year price is not subject to standard Pro pricing increases, so long as your subscription remains continuously active and Metro Remote continues to operate the Service in substantially its current form.
• You may cancel at any time via the Stripe billing portal (run metro-remote billing once CLI is installed, or use the customer portal link emailed to you).
• If you cancel, your locked-in pricing terminates. Re-subscribing later means whatever standard pricing applies at that time.

Permanent forfeiture clause (v1.5): If you cancel your founding subscription — voluntarily via the dashboard, by failing to maintain a valid payment method (Stripe dunning auto-cancellation), or by upgrading/changing plans — your founding member benefit is permanently forfeited. Subsequent re-subscriptions at the same email address, with a new email address on the same Metro account, or via any other path will not restore the locked-in $99/year founding price. Such re-subscriptions will be auto-refunded and the new subscription cancelled. To use Metro Remote after forfeiture, you must subscribe to a standard Pro plan ($708/year, see /pricing).

This clause codifies an existing rule (the "continuous, uninterrupted subscription" language in §3 since v1.0) — not a new restriction.

Recurring-payment authorisation: By proceeding to payment, you authorise Metro Remote to charge $99 to the payment method on file each year, on or shortly after the anniversary of your founding payment, until you cancel. We will send a renewal reminder email at least 7 days before each annual renewal charge.

All amounts are exclusive of sales tax. Stripe applies any applicable sales tax / VAT at checkout based on your billing address.

3a. Grandfather clause for pre-v1.4 founders

Founders who paid before 22 May 2026 under Beta Terms v1.3 retain their original locked-in pricing of $12/year (or £12/year for GBP-grandfathered accounts) after their first year, for the lifetime of their continuous, uninterrupted subscription. Beta Terms v1.3 remain available on request to support@metroremote.dev.

4. Express consent to immediate digital delivery

Under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 ("CCR 2013"), UK and EU consumers ordinarily have a 14-day right to cancel a consumer contract for digital content.

By ticking the consent checkbox on the pricing page and proceeding to payment as a founding member, you expressly consent to receive the digital content (your founding member account and access entitlement) immediately upon payment. You acknowledge that:

• Performance of the contract begins immediately upon payment (provisioning of your founding member account and locked-in pricing entitlement).
• Immediate digital delivery extinguishes your 14-day cooling-off period under CCR 2013 Regulation 36(1)(a) and (b).
• You will not receive a refund of the $99 payment after activation, except as required by your statutory rights (see Section 6 below).
• You have read and understood this waiver and agree to it knowingly and explicitly.

Stripe will email you a payment receipt as a durable record of the transaction. The version of these Beta Terms in effect at the moment of your payment (currently the version dated 22 June 2026 (v1.7)) is preserved at metroremote.dev/beta-terms and is the version that applies to your consent. If we revise these Beta Terms, prior versions remain available on request to support@metroremote.dev. A copy of your subscription details and confirmation of your founding member status is also sent to your registered email address.

4a. Confidentiality of technical implementation

By accessing the Service during the beta period under v1.6 or later, you agree to the following confidentiality terms. These obligations protect Metro Stack Limited's proprietary technical implementation and preserve pending and future intellectual property rights, including patent novelty under UK Patents Act 1977 s.2 and corresponding EPO/US provisions.

(a) What you may publicly share: that you use Metro Remote; your subjective experience using the Service; the outcomes you achieve; screenshots of the user-facing interface; the publicly-documented feature set described at metroremote.dev; quotes, reviews, and word-of-mouth endorsements; comparisons of Metro Remote to other tools at the outcome level.

(b) What you must keep confidential: any non-public technical details of the Service's internal architecture, proprietary algorithms, server-side code and runtime-served code templates, protocol details, API request and response payload shapes beyond what is documented at /docs, internal data structures, network-level transport mechanisms, isolation and tenancy mechanisms, and any other implementation technique that you reasonably understand to be non-public information through your use of the Service or through analysis of network traffic, application binaries, log output, or other artifacts. 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.

(c) No public speculation about internals: you will not publish, blog, tweet, post, present, broadcast, or otherwise publicly disclose accurate or speculative descriptions of the Service's internal technical implementation without our prior written consent. This includes social media, technical blogs, conference talks, podcast appearances, code repository READMEs, comments in public forums (Hacker News, Reddit, Stack Overflow, Discord, dev.to), and academic publications.

(d) No reverse engineering (restates and reinforces standard Terms §6): you will not attempt to reverse engineer, decompile, disassemble, intercept, or otherwise analyse the Service's internal implementation. Where such activity occurs incidentally (e.g., normal network-tab use during your own React Native development), the confidentiality obligations in (b) and (c) apply to whatever you observe.

(e) Survival and sunset: these confidentiality obligations survive termination of your beta access 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 4a. Public disclosure of any particular detail by Metro Stack Limited (e.g., a granted patent publishing, or a marketing blog describing a previously-confidential technique) extinguishes the obligation as to that specific detail immediately. A reasonable five-year sunset ensures the obligation is proportionate to the consideration paid.

(f) Statutory exceptions preserved: nothing in this Section 4a 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); (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 (see Section 6); or (vi) any other non-waivable statutory right. Nothing in this Section 4a expands PIDA 1998 to disclosures otherwise unprotected under that Act.

(g) Breach remedies: where breach of this confidentiality clause results in loss of patent rights in jurisdictions with absolute novelty requirements (such as the UK and the European Patent Convention contracting states), 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. Breach does not affect your right to a refund or cancellation under Sections 5a, 6, or 7.

(g-bis) US-resident users: where the user is resident in the United States, publication of non-public technical implementation details described in (b) 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.

(h) Existing public disclosures excluded: this Section does not apply to technical details that were already public at the time you accepted these Beta 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). The intent is to protect what is genuinely non-public, not to retrofit confidentiality onto already-disclosed material.

5. Beta service — provided "as-is"

You acknowledge that during the beta period, the Service may:

• Experience bugs, errors, or unexpected behaviour
• Have temporary downtime or degraded performance
• Lack features that will be added later
• Change in significant ways as we iterate

The Service is provided "as-is" and "as-available" during the beta period. Subject to your statutory rights under the Consumer Rights Act 2015 (see Section 6), we do not warrant that:

• The Service will be uninterrupted or error-free
• All features described on the marketing site will be available immediately upon payment
• Specific issues will be resolved within a specific timeframe

5a. Discontinuation risk — beta software disclosure

Metro Remote is in active development. While we are committed in good faith to launching the Service publicly with all features described in our marketing materials, and are targeting July 2026 (Q3 at the latest), you expressly acknowledge that:

• Software development and new-product launches carry inherent commercial and technical risk.
• We cannot guarantee that the Service will reach general availability, that any specific feature described in marketing materials will be delivered, or that delivery will occur within any specific timeframe.
• Launch timelines and feature timelines stated anywhere on this site or in marketing materials are best-effort estimates only, and may slip due to factors outside our reasonable control — including but not limited to: Apple Developer organisation verification, App Store / TestFlight review timelines, npm package publication, third-party dependencies, regulatory changes, or commercial circumstances.
• We reserve the right to discontinue, suspend, or substantially change the Service at any time during or after the beta period, in our sole discretion.

If we discontinue the Service before delivering it to you in a substantially complete form, or before the end of your prepaid first year, the following protections apply:

• We will give you at least 30 days' written notice by email before discontinuation takes effect.
• We will issue a pro-rata refund of the $99 first-year payment, calculated by reference to the number of days of access you have received (or zero days, if you have not yet received access to the CLI or iOS app). Refunds are paid via the original payment method within 14 days of discontinuation.
• If we discontinue before you have received any meaningful access to the Service (i.e., CLI or iOS app never delivered), we will refund the full $99.
• Your statutory rights under CRA 2015 ss.34-46 are unaffected — if you believe the Service materially fails to meet what was described, you may exercise statutory remedies (see Section 6) regardless of this clause.

This clause is intended to give you full transparency about beta-software risk. It does not exclude or limit any liability that cannot be excluded or limited under UK consumer protection law (CRA 2015, CCR 2013, CPUTR 2008, or any other applicable law).

6. Beta refund policy — statutory rights preserved

Founding members agree that:

• No general refund will be issued after activation, given that immediate digital delivery has been expressly consented to (Section 4).

This does not affect your statutory rights, which are preserved in full:

• Consumer Rights Act 2015 (CRA 2015) — digital content must be of satisfactory quality (s.34), fit for a particular purpose (s.35), and as described (s.36). If it materially is not, you retain rights to repair / replacement / price reduction / refund under CRA 2015 ss.43-44.
• Section 75 Consumer Credit Act 1974 — if you paid by credit card and the contract has been breached, you may be entitled to claim from your card issuer.
• Chargeback — you retain your right to chargeback through your bank at any time.
• GDPR / UK Data Protection Act 2018 — your data rights (access, erasure, rectification, portability) are unaffected by these Beta Terms.
• Unfair Contract Terms — nothing in these Beta Terms attempts to override the unfair terms protections in CRA 2015 Part 2 or the Unfair Contract Terms Act 1977.

To exercise a statutory right, email support@metroremote.dev. We aim to acknowledge requests within 2 business days and resolve them within 14 business days.

7. Cancellation during beta

You may cancel your founding member subscription at any time via:

• The Stripe billing portal — link emailed to you after activation, or by running metro-remote billing once CLI is installed
• Emailing support@metroremote.dev with your account email

Cancellation takes effect at the end of your current billing period. You retain access until then.

No prorated refund of the $99 first-year payment is provided after the immediate-delivery consent (Section 4), except where required by your statutory rights (Section 6).

8. Beta period end — transition to standard Terms or discontinuation

These Beta Terms apply until the earlier of: (a) the general release of the Service to the public ("General Availability" or "GA"), or (b) discontinuation of the Service under Section 5a.

On General Availability, founding members automatically transition to the standard Terms of Service while:

• Retaining their locked-in $99/year founder pricing for the lifetime of their active subscription (or $12/year for pre-cutover founders per §3a grandfather clause)
• Retaining all features included in the base Pro subscription at the time of purchase, on their then-current pricing terms (subscription features bundled; usage-metered add-ons priced separately — see §8b)
• Being notified at least 30 days before the transition with a copy of any changes

These Beta Terms remain in effect until the beta period is formally announced as ended. The transition does not require any further action from you — your locked-in price continues automatically.

8b. Add-ons and metered services — outside lock-in scope

Metro Remote may offer usage-metered services as optional add-ons separate from the base Pro subscription. As of v1.7, this includes:

• Cloud builds — no-Mac iOS native builds executed on dedicated cloud Mac compute (Apple licensing requires native Mac hardware). Priced as a Pro+ paid add-on from $2 per build, sold either via a monthly add-on subscription or as pay-as-you-go credit packs at the prices disclosed on /pricing at the time of add-on purchase.

Add-ons offered under this §8b:

• Are NOT included in the base subscription "features included at the time of purchase" under §8.
• Are billed separately on a per-use, per-pack, or per-add-on-subscription basis as disclosed at the time of add-on purchase.
• May change in price, availability, or composition. We will give existing add-on subscribers at least 30 days' written email notice before any add-on price change or discontinuation takes effect.
• Cancellation of an add-on does not affect your base Pro subscription or your locked-in $99/year founder pricing. You may cancel an add-on at any time from your dashboard before any noticed price change takes effect.
• Pay-as-you-go credits already purchased remain valid for use until expiry (5 years from purchase) or 30 days after written notice of any pricing change or discontinuation, whichever is later, subject to the continued availability of the underlying compute capacity.
• No monthly build credits or other add-on consumables are bundled with the $99/year founder rate. Founder lock-in covers the base Pro subscription only.

This §8b clarifies — but does not narrow — the base Pro entitlement under §8. The following remain part of the locked-in Pro plan and are NOT add-ons: unlimited AI tool calls (subject to fair usage), OTA deploy, encrypted tunnel, Model Context Protocol (MCP) integration, device allotment, and invite-testers-via-link. For the avoidance of doubt, references to "the Service" in §3 and §5a mean the base Pro subscription as defined in §8, and exclude metered add-ons offered under this §8b.

9. Severability

If any clause of these Beta Terms is held unenforceable by a court of competent jurisdiction, the remainder remains in full force and effect. Statutory rights (CRA 2015, CCR 2013, Section 75 CCA 1974, UK GDPR) are never overridden by these Beta Terms and survive any unenforceable clause.

10. Governing law

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

UK/EU 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.

11. Contact

For questions about these Beta Terms, or to exercise a statutory right, contact us at support@metroremote.dev. We aim to respond within 2 business days.