Privacy Policy — Scry

Scry is Bravely Studios LLC’s remote desktop product for your own computers and invited support sessions. This Privacy Policy covers the Scry browser app at scry.bravely.dev, the marketing hub at bravely.dev/scry, and the native host and client apps for macOS, Windows, iPhone, iPad, and Android.

When you sign in to Scry, we store the account details needed to identify you and secure access to your devices. This can include your Bravely Account identifier, email address, sign-in method, and the display name returned by that sign-in method. We do not store your password in plain text; credential handling is delegated to our authentication system and the sign-in method you use.

To make remote access work, Scry stores the devices attached to your account and the metadata needed to establish sessions between them. This includes device names, platform type, online/offline state, ownership and sharing state, session identifiers, timestamps, and connection diagnostics such as connection-allocation details and coarse network errors. When direct peer-to-peer connection is unavailable, some active session traffic may pass through Bravely-managed relay systems so the session can stay connected.

We use Scry data only to operate the product: • authenticate you and protect access to your devices • show your device list and current availability • establish, route, and troubleshoot active remote sessions • enforce preview and paid-feature access rules • answer support requests and investigate abuse or fraud We do not sell your information or use it for advertising.

Scry uses product analytics to understand aggregate product usage, feature adoption, and coarse failure states. Events may include app version, platform, anonymous device identifiers, account-linked identifiers where needed for Pro access troubleshooting, and high-level session lifecycle events. Where a client exposes an analytics toggle, you can opt out there. We do not use Scry analytics to record the contents of your desktop, your files, or the text you type into another app.

Scry has a paid Pro tier. We store your Bravely Account identifier, contact email, Pro access status, platform customer identifiers, and transaction identifiers so we can unlock the correct features on your account across supported platforms. Payment card details are handled by the platform that billed you, not by Bravely Studios LLC.

Native Scry builds may request system permissions such as screen capture, accessibility/input control, microphone access, notifications, or file access when those capabilities are part of the feature you are actively enabling. Granting a permission does not by itself publish your data to other users; the permission is used so the app can perform the remote access or support action you requested on your own device.

We share Scry data only in these limited cases: • with service providers that run parts of the service on our behalf, including authentication, hosting, analytics, Pro access, billing, and app-store providers • with another person you explicitly authorize once support-session or trusted-sharing features are enabled in your build • when required by law, legal process, or to protect the safety and integrity of the service We do not sell or rent your data to advertisers or data brokers.

We secure Scry using authenticated accounts, transport encryption, and device/session authorization checks. We are not marketing Scry as end-to-end encrypted at this time, and we do not make privacy or security claims beyond what we have shipped and documented publicly. If stronger guarantees are shipped later, this policy and the product materials will be updated to match that proven contract.

We retain account, device, session, and Pro access records only as long as reasonably necessary to operate Scry, investigate abuse, comply with legal obligations, and support customer requests. To request account deletion, email jeff@bravely.dev. During preview, account deletion requests are handled manually.

We may update this Privacy Policy from time to time. The effective date at the top of this page will be updated accordingly. Continued use of Scry after changes constitutes acceptance of the revised policy.