RTTyprivacy / updated 21 August 2026
This policy applies to RTTy for macOS, iPhone, and iPad. RTTy has no account system, advertising, tracking, analytics SDK, or developer-operated measurement backend.
RTTy stores latency, loss, availability, bandwidth counters, route, resolver, interface, VPN and proxy context, permitted Wi-Fi evidence, incidents, configured-target results, and settings locally. Statistics are retained for up to 30 days and events for up to 90 days. Exports occur only when you request them.
The mobile app performs local path and bounded service probes while it is active. It keeps at most 180 aggregate observations and 180 observations per endpoint in protected app storage. Before the first active-session refresh, RTTy idempotently deletes protected public-egress history left by affected earlier versions. It clears any legacy public-egress projection from memory even if file removal fails, reports that failure in Settings, and retries deletion at the next active-session start. The clear-data control removes local observations, endpoint history, and cached Mac snapshots. Pairing credentials are stored separately in Keychain and must be removed with the pairing controls.
RTTy connects directly from your device to displayed, configured, or built-in diagnostic targets. The current mobile default checks www.apple.com:443 about every 15 seconds while the app is active in the foreground. The Mac uses the default gateway and system-provided resolvers rather than fixed public DNS defaults. Destination operators can observe ordinary connection metadata such as your public IP address. RTTy and East Coast Science do not receive a copy of the measurements.
RTTy can detect supported installed apps from their bundle names and identifiers and enable a bounded set of displayed TCP-443 checks. It does not read those apps' documents or user data. macOS may ask for App Management access for this local bundle check; denying it leaves automatic app suggestions unavailable while core network monitoring continues. Eligible hosts are controlplane.tailscale.com, chatgpt.com, claude.ai, www.dropbox.com, drive.google.com, world.tr.teams.microsoft.com, zoom.us, www.webex.com, slack.com, discord.com, github.com, and www.icloud.com. Fresh defaults use a one-second active and five-second idle cadence within the total target budget. Every enabled endpoint is visible; disabling one persists, and observed network domains alone do not enable traffic.
On Mac, RTTy asks for Location authorization only after you choose the Current Wi-Fi Identity action because macOS protects permitted SSID and BSSID access with that permission. RTTy uses the authorization for current Wi-Fi diagnostic context and does not request, store, or transmit geographic coordinates.
Nearby discovery begins only when you choose it. After pairing, RTTy can transfer a bounded, authenticated health snapshot over the local network from a Mac to an iPhone or iPad. A snapshot can include the Mac name, interface and local-address context, VPN state, endpoint results, incidents, and availability evidence. Turning Mac sharing off stops access without changing the valid host-wide group secret. Re-enabling sharing reuses it, including after an app relaunch. Only the explicit Rotate action replaces the secret and revokes every retained copy. A failed rotation remains stopped until replacement completes.
RTTy does not send Cloudflare Speed Test or public-egress metadata requests, and it does not automatically schedule fixed Cloudflare or Google DNS probes. A resolver supplied by the system or chosen by the user can still be operated by either provider. RTTy has no production CloudKit synchronization, advertising, tracking, marketing analytics, third-party analytics SDK, or developer telemetry service.
On iPhone and iPad, Stop Nearby Discovery ends local browsing without deleting pairings; Retry Nearby Discovery starts a new attempt after a denial or error. On Mac, disable Nearby sharing to stop advertising and snapshot sharing. Remove a pairing or rotate the Mac group credential to revoke Nearby access. Mac Erase Settings and Monitoring Data first invalidates, cancels, and awaits in-flight startup, probe, and enrichment work, and drains in-flight archive readers before deleting archives and clearing in-memory evidence, so stale work cannot recreate or repopulate cleared monitoring data. It deliberately preserves device identity, the group pairing credential, and the Bonjour node identifier; those are managed separately through Nearby controls. The mobile clear-data control removes retained measurement history and snapshot caches. Uninstalling removes each app's container.
This site does not use marketing analytics. Its hosting infrastructure may process routine request data needed to deliver and protect the site. Email and attachments you choose to send are used to answer and investigate your request. Remove private hostnames, addresses, and network evidence before sending diagnostics. You may request deletion of support correspondence at the address below.
RTTy is operated by East Coast Science LLC. Privacy questions, consent-withdrawal questions, and support-correspondence deletion requests can be sent to rtty@eastcoastscience.com. This policy was last updated on 21 August 2026.