Notice on independently operated relays

Effective date: November 1, 2026

1. What this notice covers

This notice explains how a relay operated by someone other than us differs from the official JunoFleet service. It grants no licence or permission. Protocol descriptions and test vectors do not make our proprietary software open source or grant rights beyond their applicable licences. Rights that the law gives you are unaffected; the client licence covers our software.

2. What the official service includes

The official subscription pays for the operated JunoFleet service, including its relay and supported account, device-directory and notification features. An independently operated relay is not that service and does not receive our availability commitments, operation, updates or support.

A self-hosted relay gets no JunoFleet push delivery and no official store app for connecting to it. Official Apple and Google store apps connect to the official relay. JunoFleet push delivery through APNs and FCM, is provided only through that relay. This statement concerns JunoFleet's push facilities; it does not claim that another operator cannot build its own notification system.

This notice does not promise that a current official binary supports changing its relay address, or that we distribute a ready-to-install relay package.

3. Keep the services separate

A modified or independently made compatible client must not connect to the official relay. Running another relay does not authorise access to someone else's JunoFleet account, devices or sessions, use of our push credentials, or bypassing payment or access controls. Mandatory legal rights remain unaffected.

You must not describe an independent relay as operated, endorsed or supported by JunoFleet. Redistribution or modification of our proprietary binaries needs permission unless a separate component licence or applicable law allows it.

4. The operator's responsibilities

The independent operator manages its hosting, security, authentication, updates, backups, retention and legal obligations. Protocol compatibility alone does not establish that its security matches the official service. End-to-end encryption still depends on trustworthy endpoints and correct key handling.

Our Privacy Policy covers our processing for the official service; it does not describe an independent operator's processing. Ask that operator which data it receives, where it keeps it, and how to exercise privacy rights. Your chosen AI provider's terms and charges still apply.

Questions about the official service or its licence: [email protected].