ScryStat Privacy Policy

1. Overview

ScryStat is a privacy-focused analytics tool designed to let developers view limited application activity data while minimizing the amount of information handled.

ScryStat Viewer is an iPhone companion app for viewing ScryStat metrics. When enabled and actively open, it may also process application signals through the configured CloudKit environment.

The Viewer does not allow users to edit the Mac application’s counter definitions.

ScryStat does not use advertising SDKs, does not use IDFA, and does not use third-party analytics SDKs.

2. Information ScryStat Handles

Depending on how ScryStat is configured, the system may process limited application signals such as:

• observed device events
• daily active events
• developer-defined custom counter events
• event identifiers used to prevent duplicate processing
• installation-derived hashes, which are scoped identifiers rather than a guarantee of anonymity
• ScryStat Home, Application, and Counter routing identifiers

These signals are intended for aggregate application measurement.

ScryStat does not require application users to provide a name, email address, phone number, postal address, contacts, photos, videos, advertising identifier, or browsing history for analytics operation.

Processing by the apps is different from receipt by Roy App Works. Signal destinations and the party controlling them are described in Section 3. A developer integrating a sender in another app is responsible for that app’s own privacy notices and declarations.

3. CloudKit and Signal Storage

3.1 Current ScryStat Setups

Current ScryStat setups use a developer-owned Apple CloudKit Public database as the signal inbox for that developer's application.

Signals generated by the developer's application are sent directly to the CloudKit container configured by that developer.

ScryStat does not operate a custom analytics relay server for this current BYOC workflow.

In the BYOC workflow, the container and its access credentials are controlled by the developer who configures it. The standard BYOC collection path does not send a separate copy of those signals to Roy App Works. Access through CloudKit is governed by the developer’s database security settings; a Public Database is not a private store merely because it is developer-owned. Apple operates the CloudKit infrastructure.

ScryStat uses private iCloud / CloudKit storage for synchronization between the user's ScryStat Mac application and ScryStat Viewer.

Personal CloudKit synchronization is separate from the BYOC Public signal inbox. It uses the signed-in user’s Private database for workspace and counter data and, when signal access is shared with the iPhone, a collector credential whose token is written to CloudKit encrypted fields. This policy does not claim that local PIN protection alone encrypts cloud data.

3.2 Legacy Compatibility

Older ScryStat configurations may retain a legacy compatibility path that uses a ScryStat-managed CloudKit Public database.

This legacy path is maintained for backward compatibility and is not the default path for new ScryStat setups.

The legacy path is limited to the same types of analytics signals described in this policy and is not used to build advertising profiles or to combine data across unrelated developers.

This compatibility path remains available in current Release code for retained existing configurations; it is not merely historical text. Signals in that ScryStat-managed Public database may be accessible to Roy App Works as the container operator and to other parties permitted by the database’s security settings. Routing identifiers are used for selection and do not by themselves make Public records private. This does not mean that Roy App Works has inspected particular users’ records.

4. Local Device Storage

ScryStat and ScryStat Viewer store configuration and operational data locally as needed for functions such as:

• connection state
• pairing information
• synchronization checkpoints
• local event state
• PIN verification data

Sensitive credentials are stored using Apple Keychain where applicable.

The Viewer PIN is not stored as plaintext.

The configured BYOC API token is stored in Keychain on the Mac and, when shared and retrieved by the paired iPhone, in the iPhone Keychain. Event state and synchronization checkpoints are stored locally; processed events and definitions may also be synchronized to the user’s Private CloudKit database. These storage locations are distinct from Public signal records.

5. Camera Access

ScryStat Viewer uses camera access only when the user chooses to scan a ScryStat pairing QR code.

Camera access is not required until the user initiates QR scanning.

ScryStat does not use the camera for advertising, profiling, or unrelated analytics.

6. Local Network and Legacy Functionality

ScryStat may use local network services for optional iPhone pairing, Viewer discovery, and authorized snapshot access. Certain legacy local-development workflows may also use a loopback receiver.

These services are separate from CloudKit synchronization, which may allow the iPhone companion to retrieve previously synchronized, available data while the Mac is offline. LAN snapshot access requires a reachable Mac. This policy does not describe all local-network functionality as inactive.

7. Tracking and Advertising

ScryStat does not:

• use App Tracking Transparency for cross-app tracking
• use IDFA
• include advertising SDKs
• sell analytics data to advertisers
• use third-party behavioral analytics SDKs

ScryStat is not designed to track users across applications or websites owned by other companies.

8. Data Retention and Deletion

Retention depends on the type of information and the CloudKit environment in which it is stored.

Developer-owned CloudKit data remains subject to the developer's CloudKit configuration and Apple iCloud infrastructure.

Private synchronization data may remain in the user’s iCloud storage until an applicable owner-authorized cloud deletion or workspace reset is completed. Changing an account or resetting a local connection does not by itself guarantee deletion of remote records.

Local connection data may be removed through features such as disconnecting, resetting a connection, or using the applicable reset or forgot-PIN workflow.

Disconnecting or resetting Viewer connections primarily removes local connection and authorization state; it does not erase all owner CloudKit data. BYOC Public signal deletion is managed by the container owner and applicable CloudKit permissions. The app does not promise that a reset deletes legacy Public signals or that a fixed retention period applies to every store. Keychain data should not be assumed to be removed solely by uninstalling the app.

9. Security

ScryStat uses Apple platform security features including CloudKit, Keychain, HTTPS, and cryptographic functions provided through Apple platform APIs.

ScryStat is designed to minimize unnecessary data collection and to separate developer signal storage from ScryStat's private synchronization data.

No system can guarantee absolute security, and this policy does not make such a guarantee.

10. Children's Privacy

ScryStat is a developer analytics and companion utility and is not designed as a service directed specifically to children.

ScryStat does not intentionally include advertising or behavioral tracking features directed at children.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

Changes will be posted on this page with an updated effective date.

12. Contact