These terms govern your use of RetroRelay. By creating an account or using the service you agree to them. If you do not agree, please do not use the service.

RetroRelay is operated by Adapanos Ltd (“we”, “us”, “our”), a company registered in England and Wales (company number 17167951), of 483 Green Lanes, London, England, N13 4FG, United Kingdom.

1. The service

RetroRelay lets you pair a 2003–2013 retro phone with a modern cloud account, so the phone can show and manage lightweight, glanceable information: built-in features such as an authenticator, weather, and habit tracking, plus connected services such as your tasks and calendars. Every feature is free for one paired phone; supporters can pair more (see section 7). The service consists of:

A web dashboard for managing your account, paired devices, and integrations.
A J2ME (Java ME) application that runs on supported retro phones.
A backend API that links the two.

Integrations connect RetroRelay to third-party services you already use, such as Todoist, Google Tasks, Microsoft To Do, Google Calendar, and Outlook Calendar. Those services are provided by their respective owners, not by us, and your use of each remains subject to that provider’s own terms and privacy policy. We access a connected service only with the permission you grant, and only to show and manage its items on your paired phone; you can disconnect any integration at any time from your account settings.

2. Eligibility and accounts

You must be at least 13 years old (or the higher age of digital consent in your jurisdiction) to use the service. By creating an account you confirm you meet this requirement.

You may only use RetroRelay if the law allows you to. You confirm that you are not located in a country under UK, EU, or US sanctions or trade embargo, and that you are not on any government list of restricted or sanctioned parties. You also agree not to use the service in breach of any export or sanctions law that applies to you.

You are responsible for the activity that takes place on your account, for the devices you pair to it, and for keeping your sign-in credentials secure. Notify us immediately if you believe your account has been accessed without your permission.

3. Acceptable use

You agree not to:

Use RetroRelay for any unlawful purpose, or to facilitate unlawful activity by others.
Attempt to interfere with the service, gain unauthorised access, or probe for vulnerabilities outside a coordinated disclosure.
Send automated traffic that exceeds reasonable use, beyond the rate limits we apply.
Attempt to extract another user's data or impersonate another user.
Pair devices you do not own or are not authorised to use.
Reverse-engineer the service in order to compete unfairly with it (security research is welcome; see "Security disclosure" below).

We may suspend or terminate accounts that breach these rules, with or without notice depending on the severity.

4. Important risk warnings

4.1 Authenticator codes: loss of access

If you use RetroRelay as the authenticator for external accounts, losing access to your RetroRelay account means losing access to the codes those accounts ask for when you sign in. Examples that can leave you locked out of third-party services:

Deleting your RetroRelay account (even after downloading the Authenticator “Export accounts” export, you must re-register the secrets elsewhere).
Losing or breaking your paired phone with no backup paired phone means your codes cannot be shown on a phone until you pair another one; you can still export your accounts from the web dashboard in the meantime.
Forgetting your sign-in credentials with no recovery method enabled on your sign-in provider.

We strongly recommend you keep authenticator recovery codes issued by the third-party service somewhere safe before relying on RetroRelay as your only second factor. We cannot recover or reset your access to those third-party accounts.

4.2 Legacy network channel: the security trade-off

Communications between paired retro phones and our server use plain HTTP with modern authenticated encryption (ChaCha20-Poly1305, the same cipher TLS 1.3 uses) layered on top, because 2003–2013 phones cannot reliably validate modern TLS certificates. Without this trade-off, the service would not work on the hardware it is designed for.

A passive observer on your phone's network cannot read or modify the request and response contents, and replayed captures of earlier traffic are rejected. The one residual gap is server authentication: there is no equivalent of “this server presented a certificate I trust”, so a network-positioned attacker could in principle impersonate our server to the phone. We therefore consider authenticator codes generated on a paired retro phone to be appropriate for low-risk and medium-risk accounts, and less appropriate for high-value accounts (large financial holdings, administrative access to critical infrastructure, etc.).

The web dashboard runs over modern HTTPS and is not affected by this trade-off. Decisions about which accounts you protect via the paired phone are yours to make.

5. Service availability

We aim to keep RetroRelay available continuously, but we do not guarantee uninterrupted service. Maintenance, third-party outages, network issues, and other factors may cause downtime. We do not offer a service-level agreement during the current phase of the project.

We may update, change, or withdraw features. We only do so for a valid reason, such as:

A third-party provider changes, limits, or ends the access an integration relies on (see below).
A change in the law, or a requirement from a regulator or court.
Keeping the service and your data secure, or stopping abuse.
Keeping the service affordable to run.
Keeping the app working on 2003–2013 phones, including adding or dropping support for particular models.
Fixing problems or improving how a feature works.

A change never costs you anything extra. For changes that materially affect how the service works for existing users, we will give reasonable notice where practical. Section 7.5 covers changes to what supporters get.

Connected integrations depend on the services behind them

Integrations work by talking to third-party services such as Todoist, Google Tasks, Microsoft To Do, Google Calendar, and Outlook Calendar. Those providers control their own systems and the access they give us. If a provider changes its terms, limits or ends the access we rely on, has an outage, or removes a feature, the matching integration may stop working, lose some of what it does, or be withdrawn. This can happen with little or no warning, and it is outside our control.

We will adapt or restore an affected integration where we reasonably can, but we cannot promise that any given integration will keep working, and we are not responsible for a provider’s own decisions, downtime, or changes.

Device compatibility

The J2ME app targets retro phones made between 2003 and 2013. Handsets from that era vary widely in their Java support, memory, and firmware, and we cannot test every model. Some features may behave differently, or the app may not run at all, on a phone we have not tested. Which phones we support can also change over time as we add or drop support for particular models.

We list the devices we have tested in our supported devices guidance. We do not warrant that RetroRelay will work on any specific handset, so please check your phone against that list before you rely on the service.

6. Intellectual property

6.1 Our intellectual property

The RetroRelay name, logo, web app, server software, and J2ME application are owned by us or our licensors. Use of the service does not grant you any rights in our intellectual property beyond the right to use the service as intended.

6.2 Your content

Data you provide to or manage through RetroRelay (authenticator account names and secrets, device names, location, habits, and the tasks and calendar events you view or edit through connected integrations) remains yours. You grant us a limited licence to store, process, and transmit that data only as needed to provide the service to you.

6.3 Third-party names and trademarks

Product, service, company, and network-operator names referred to on our website and in the app are the trademarks of their respective owners. That includes connected-service providers (such as Todoist, Google, and Microsoft) and the mobile network operators named in our connection guides. We use them only to identify those products and services and to help you set up and use your phone. Such use does not imply any affiliation with, sponsorship by, or endorsement from those owners. RetroRelay is an independent service and is not affiliated with any of them.

6.4 Feedback

If you send us ideas, suggestions, or feedback about RetroRelay, we can use them freely to run and improve the service, with no obligation to you and no payment. You do not have to send feedback, and anything you do send is given voluntarily. This does not affect the ownership of your own content described above, or anything covered by our security disclosure process in section 12.

7. Supporter payments

7.1 What a supporter payment is

Every feature of RetroRelay, connected integrations included, is free for one paired phone. A supporter payment is an optional one-off payment of any amount you choose, from £3. It lets your account pair up to 6 phones, for as long as RetroRelay runs. There is no subscription and nothing renews: you are only ever charged when you choose to make a payment. The person paying must be an adult (18 or over in the UK).

The amount you choose is the amount you pay. It includes any VAT or other tax due where you live, which the merchant of record works out and collects (see section 7.2). You can make more than one supporter payment if you wish; each is a separate one-off purchase, and the limit stays at 6 phones. A supporter payment buys the higher phone limit: it is a purchase, not a charitable donation. The current details are on the pricing page.

7.2 Who takes the payment

Payments are handled by Stripe through its affiliate Sold through Link, LLC (branded “Onelink”), which acts as the merchant of record for your payment: it processes the payment, collects any applicable tax, and issues your receipt in its own name. Your card statement will show Onelink’s descriptor rather than our name. Adapanos Ltd remains the seller and provider of the service itself. We never see or store your card details; see section 1.7 of the Privacy Policy for what we do and do not hold.

7.3 Refunds

Our own policy is not to refund supporter payments, apart from the cases in this section and in sections 7.5 and 8. Because your purchase is made through the merchant of record (see section 7.2), Onelink’s own refund policy also applies to your purchase and takes precedence over ours wherever ours is more restrictive. If you are a UK or EU consumer, you also have a statutory 14-day cooling-off right after each supporter payment (in the UK, under the Consumer Contracts Regulations 2013), exercised through the merchant of record. To use it, contact Onelink’s customer support within 14 days of your payment and give “cooling off period” as the basis for your refund request.

If you believe you paid by mistake (for example, you paid twice, or entered the wrong amount), email us at contact@retrorelay.app within 14 days of the payment. We review such requests case by case as a goodwill matter; this is not a contractual right beyond what UK consumer law and the merchant of record’s policy provide.

Nothing in this section affects any statutory rights you have as a consumer, including those under the Consumer Rights Act 2015 and the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, where they apply.

7.4 If your payment is refunded

A supporter payment that is fully refunded, for any reason, no longer counts. Once every supporter payment you have made has been refunded, your account goes back to the free limit of one phone. Phones paired beyond that limit are locked: they stay listed on your dashboard but cannot connect, and the phone you paired first stays unlocked. If you unpair a phone, the next locked one unlocks. Your data stays as it was, and every feature keeps working on your unlocked phone.

7.5 If supporter benefits change, or RetroRelay closes

If we ever reduce what supporters get (for example, by lowering the phone limit), we will email every supporter before the change takes effect. Anyone who made a supporter payment can then ask us for a refund of what they paid, within 30 days of the change.

If we ever decide to close RetroRelay, we will stop taking supporter payments and email every account in advance of the closure.

8. Termination

You can terminate your relationship with us at any time by deleting your account from your Account page. Doing so removes all data we hold about you (subject to the short backup-retention window described in our Privacy Policy). If you are a supporter, deleting your account also ends your supporter status, and deletion does not refund any supporter payment (see section 7.3 for refunds).

We may suspend or terminate your account for breach of these terms, unlawful activity, prolonged inactivity, or if continuing to provide the service to you becomes operationally impossible. For prolonged inactivity we will always email you in advance, with enough time to keep your account by simply signing in; for the other grounds we will notify you first where the circumstances permit it. If you are a supporter and we close your account for a reason that isn’t your fault (for example, because continuing to provide the service has become operationally impossible), we will refund your supporter payments.

9. Disclaimers

The service is provided “as is” and “as available”. To the fullest extent permitted by law, we disclaim all implied warranties, including warranties of merchantability, fitness for a particular purpose, and non-infringement.

Nothing in these terms excludes or limits any rights you have as a consumer that cannot be excluded under applicable law (such as the UK Consumer Rights Act 2015), or our liability for fraud, fraudulent misrepresentation, death or personal injury caused by our negligence, or any other liability that cannot lawfully be excluded.

10. Limitation of liability

To the fullest extent permitted by law, our total aggregate liability to you for any claim arising out of or in connection with the service is limited to £100, or, if greater, the total amount you have paid for the service (whether to us or through the merchant of record) in the twelve months preceding the event giving rise to the claim.

We are not liable for indirect, incidental, special, consequential, or punitive damages, including loss of profits, loss of data, or business interruption, even if we have been advised of the possibility of such damages.

11. Indemnification

You agree to indemnify and hold us harmless from any third-party claim, loss, or expense (including reasonable legal fees) arising out of your misuse of the service, your breach of these terms, or your violation of any law or third-party right.

12. Security disclosure

If you discover a security vulnerability in RetroRelay, please report it to contact@retrorelay.app rather than disclosing it publicly. We will acknowledge your report promptly and work with you on a coordinated disclosure timeline. Good-faith security research conducted against your own account is welcomed and will not be treated as a breach of these terms.

13. Changes to these terms

We may update these terms from time to time. The date at the top shows when they were last changed. For material changes we will notify signed-in users by email or in-app notice before the change takes effect. Continued use of the service after a change means you accept the updated terms.

14. General

14.1 The agreement between us

These terms, together with our Privacy Policy, are the full agreement between you and us for your use of RetroRelay. They take the place of anything said or written before on the same subject. This does not limit any responsibility we have for something we told you dishonestly.

14.2 If part of these terms cannot be enforced

If a court finds any part of these terms invalid or impossible to enforce, the rest stays in effect. Where it can, that part is narrowed just enough to make it valid rather than dropped completely.

14.3 Transferring these terms

We may transfer our rights and duties under these terms to someone else, for example if the business is sold or reorganised, provided this does not weaken your rights. Because your account is personal to you, you cannot transfer yours without our written agreement.

14.4 If we do not enforce a term right away

If we do not enforce a right under these terms, or we are slow to, that does not mean we have given it up. We can still enforce it later.

14.5 Other people cannot enforce these terms

These terms are an agreement between you and us. No one else can enforce any part of them under the Contracts (Rights of Third Parties) Act 1999.

14.6 Events outside our control

We are not responsible for failing to do what these terms require when the cause is beyond our reasonable control. That includes power or network failures, outages at our hosting or at a third-party provider, strikes, fires, floods, and government action.

15. Governing law and jurisdiction

These terms are governed by the laws of England and Wales. Any dispute arising out of or in connection with these terms or the service is subject to the exclusive jurisdiction of the courts of England and Wales, except where you are a consumer resident in another part of the United Kingdom, in which case the courts of your country of residence will also have jurisdiction.

16. Contact

Questions about these terms? Email us at contact@retrorelay.app or write to us at Adapanos Ltd, 483 Green Lanes, London, England, N13 4FG, United Kingdom.

Complaints. If something about the service has gone wrong and you want to complain, use either contact route above and say that it is a complaint. We will acknowledge it promptly and tell you the outcome without undue delay. Complaining to us is free, and it does not affect any statutory right you have as a consumer.

For technical details on how this data is protected, encryption algorithms, key derivation, and threat model, see how it works.

Terms of Service