JSTU Connect Beta Privacy Notes

In short

To make JSTU Connect more reliable, Beta builds can send diagnostics about connections, settings, app performance and running time. Nothing is collected until you choose Continue. Reports carry a random installation identifier, so they are not anonymous, but they contain no names, addresses, input or content. They are stored with Apple CloudKit, kept for up to 30 days, and never used for advertising or tracking.

The App Store release and the Windows app do not include these diagnostics; the JSTU Connect Privacy Policy covers them and everything else the app does.

When collection starts and stops

Continue

Collection begins only after you choose Continue on the Beta Testing Privacy Notes screen. Installing a Beta build is not agreement.

Pause Beta Testing…

On Mac in the app menu next to About; on iPhone, iPad and Apple Vision Pro in Settings near About. It stops collection and sending, discards reports not yet sent, and returns to the welcome screen. Your devices, settings and identifier are kept. Collection resumes only if you choose Continue again.

Policy changes

If what is collected or how it is used changes, the app shows the notes again and collects nothing until you choose Continue. Reports gathered under an earlier version are never resent under a new one.

What reports contain

Reports are daily summaries: totals and counts, not a record of what you did and when.

Installation identifier

A random identifier created when the app first opens and shown on the welcome screen. It is not derived from your hardware or account. Reinstalling or restoring the app may create a new one.

Connections

The most paired devices that were online at the same time, overall and separately for direct and Mesh connections, with each device counted once; and the number of saved devices.

Settings

Whether Mesh and Adapter are on; your Shared Insights choice (off, Summary, or Summary & Detailed Readings); and the state of permissions the app already has, such as Local Network or Bluetooth, with a count of stored permission grants but not which devices hold them. The app never asks for a permission or turns on a sensor for diagnostics.

Running time

How long the app was observed in the foreground and while inactive, per day. Time while the system has suspended the app is not counted.

Performance

The app’s own memory and processor use, sampled about once a minute while it runs, as averages and peaks.

Outcomes

Counts of how pairing, connection checks, pointer sessions, compute checks, recovery and Stop turned out, with durations grouped as under 1, 5 or 30 seconds, or longer.

Device context

System and app version, device model, battery and power state, and the kind of network in use (for example Wi-Fi or cellular) and whether it is metered or in Low Data Mode.

Coverage

How much time and how many samples a report is based on, so gaps are not mistaken for no use.

What reports never contain

Your email or Apple Account address; your name or any device name; the identities of paired devices; Wi-Fi network names; IP or MAC addresses; what you type, point at or share; files; pairing or invitation codes; keys; location; raw error messages; or a timeline of events.

Reports are not anonymous. The installation identifier links each day’s report to the others, and is linked to the device model and system version they contain. CloudKit also adds its own record metadata, including a reference to the iCloud account that created each record. We do not use these to find out who you are.

How reports are used

Only to improve connection reliability and app performance, and to decide how fine-grained permissions should be. They are not used for advertising, for tracking across apps, or to study your general device use or social habits. Testers are not a representative sample, and results are read that way.

How reports are sent

Only when the app is quiet: no collaboration, pairing or Stop in progress, a minute without activity in the app, a stable network, normal temperature, enough battery, and neither Low Power Mode nor Low Data Mode. New work cancels a send that has not finished. The app tries at most four times a day, at least six hours apart, with about 16 KB of its own data each time. Cellular data is used if it is not in Low Data Mode.

Until they are sent, reports wait in the app’s private cache, excluded from backups, for at most seven days and 1 MiB. The app writes no files to your Documents, Downloads, Desktop or iCloud Drive. Without iCloud the app works normally and unsent reports expire.

Where reports are stored

In Apple CloudKit, in a container used only for these diagnostics. Apple calls it a public database, but each record can be read and changed only by the iCloud account that created it and by JASON Studio. Apple hosts the data for us. Reports are not sold or shared with anyone for their own purposes.

How long reports are kept

Up to 30 days, counted from the first observation in each daily report. A daily cleanup deletes reports once they are 25 days old. Copies made for analysis are deleted on the same schedule and are never kept in source control.

Leaving and earlier deletion

To leave, choose Pause Beta Testing… and delete the app. Reports already sent are deleted automatically within 30 days; you do not need to ask.

If you would like them deleted sooner, or your email removed from the TestFlight tester group, you can send a deletion request with each installation identifier and the email you applied with. We check it by hand, delete matching reports and analysis copies, remove your email from the tester group, and check again seven days later for late reports. Removing you from TestFlight does not switch off an installed build. If an installation was not paused, we cannot guarantee it will not send another report.

Information you give this website

Applying

Your email, the version of the terms you accepted and the time.

Sending a deletion request

Your email, the identifiers you list and the time.

These are stored with Cloudflare, which hosts this website, and only JASON Studio can view them, after signing in. We use them only to invite you through App Store Connect, which passes your email to Apple to send the TestFlight invitation, and to handle your requests. They are kept while you are a tester and deleted automatically 30 days after a request is finished. To limit abuse, the number of requests from one IP address is briefly counted; the address is not stored with your request. The forms set no cookies.

Form security

The Beta application and deletion forms use Cloudflare Turnstile to prevent automated abuse. A security check runs when you open either form. Cloudflare processes browser and network signals for this check under its Turnstile Privacy Addendum. Turnstile does not read your form entries. We record limited operational diagnostics in Cloudflare Workers Logs: the form type, verification and waiting durations, retry counts, and fixed outcome or failure categories. These diagnostics contain no email address, installation identifier, IP address, browser fingerprint, form contents, verification token or secret. They are retained for up to seven days and do not track you across visits. Diagnostic delivery is best-effort and never waits before sending your form. If the check cannot complete, contact support@jasonstu.cc for help.

Contact

For privacy questions or help with JSTU Connect, email support@jasonstu.cc.