Privacy Policy
STEADYWATCH™ — Atomic Clock Multi-Tool
Introduction
STEADYWATCH™ ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use the STEADYWATCH™ app (the "App") on Apple Watch and iPhone.
STEADYWATCH™ captures your biological oscillation frequency via Apple Watch motion sensors, combines it with pre-computed IBM quantum hardware entropy, and generates a cryptographic identity key authorized by Face ID and signed by the Secure Enclave — all on your device.
By using our App, you agree to the collection and use of information in accordance with this policy.
Information We Collect
1. Motion and Biometric Frequency Data
What We Collect:
- Biological oscillation frequency measured from Apple Watch IMU (inertial measurement unit)
- Tremor frequency and amplitude derived from acceleration and gyroscope data
- Atomic clock ratio: your oscillation frequency relative to the Cesium-133 standard (9,192,631,770 Hz)
How We Use It:
- To derive a unique biometric frequency signature specific to you
- To generate a post-quantum biometric identity key seeded by your oscillation ratio
- To produce the quantum circuit confidence score associated with your key capture
Storage: Raw motion sensor data is not stored. Only the derived biometric key (a cryptographic output) is saved locally on your device. No raw IMU data is transmitted or retained.
2. Biometric Key and Cryptographic Identity
What We Generate and Store:
- A biometric identity key (hex string) derived from your oscillation frequency and quantum entropy
- A quantum circuit confidence score (percentage) reflecting capture quality — never modified after generation
- A session identifier, timestamp, and entropy slot reference
- If authorized: a P256 ECDSA signature produced by the Secure Enclave, a reference to the signing public key, and the authorization timestamp
How We Use It:
- To maintain your Biometric Key Vault — a local record of your generated identity keys
- To provide non-repudiable proof that a key was generated by you and authorized by your device at a specific moment
- To optionally sync keys between Apple Watch and iPhone via your local network
Storage: Biometric keys are stored locally on your device. Keys may optionally sync to a local network server you configure (e.g., on your home network). Keys are never transmitted to Quantum V^ LLC servers or any third-party cloud service.
3. Face ID Authorization
What We Use:
- Apple's LocalAuthentication framework to authenticate your identity via Face ID before authorizing a biometric key
What We Do NOT Use:
- ❌ No facial images are accessed or stored by STEADYWATCH™
- ❌ No facial geometry or biometric templates are read by the App
- ❌ Face ID data never leaves the Secure Enclave on your device
How It Works: Face ID is used exclusively as an authorization gate. When you authorize a key, the Secure Enclave's P256 private key signs the biometric key hex string. The signing key never leaves the Secure Enclave chip. The resulting ECDSA signature is what is stored — not any facial data.
4. IBM Quantum Hardware Entropy
What We Use:
- Pre-computed quantum entropy generated on IBM Quantum hardware (ibm_marrakesh), embedded in the App at build time as THE VAULT™ — 81 entropy slots mapped to real hardware job IDs
What We Do NOT Do:
- ❌ The App does not connect to IBM Quantum systems at runtime
- ❌ No user data is transmitted to IBM or any quantum cloud provider
- ❌ The entropy is static, embedded at compile time — it is not fetched dynamically
5. Local Network Communication
What We Use:
- Optional vault synchronization between Apple Watch and iPhone over your local network
- Keys generated on Apple Watch are pushed to your iPhone vault via a local network API (if you have a local server configured)
What We Do NOT Do:
- ❌ No data is sent to external servers operated by Quantum V^ LLC
- ❌ Local network sync is optional and operates only within your own network
- ❌ Default configuration uses localhost — no data leaves your device unless you configure a local server
Your Control: Local network sync is user-configured. If you do not configure a backend URL, all data remains on-device only.
What We Do NOT Collect
We do NOT collect:
- ❌ Personal identification information (name, email, address)
- ❌ Payment information
- ❌ Location data
- ❌ Contacts or address book information
- ❌ Photos, camera images, or video
- ❌ Facial images or facial geometry
- ❌ Raw motion or IMU sensor data (only derived cryptographic output is stored)
- ❌ Health data (HealthKit is not used)
- ❌ Analytics, advertising identifiers, or crash reporting data
- ❌ Any data that identifies you to Quantum V^ LLC
Data Storage and Security
On-Device Storage
All biometric key data is stored locally on your device:
- Biometric keys and vault records: stored in UserDefaults, protected by iOS data protection
- Secure Enclave signing key: stored in the Secure Enclave — never extractable from the chip
- Settings and configuration: stored in UserDefaults
Cryptographic Security
- All signing operations use Apple CryptoKit P256 ECDSA via the Secure Enclave
- Biometric key material is derived using SHA-256
- No proprietary encryption algorithms are used — all cryptographic operations route through Apple CryptoKit and the Secure Enclave
- The App does not use non-exempt encryption — encryption compliance:
ITSAppUsesNonExemptEncryption = false
Local Network Server (Optional)
If you configure a local network backend:
- Biometric keys may be stored on a server you control within your local network
- This server is your responsibility — review its security practices
- Quantum V^ LLC does not operate, monitor, or have access to your local server
Data Sharing and Disclosure
We Do NOT Share Your Data
We do not:
- ❌ Sell your data to third parties
- ❌ Share your data with advertisers
- ❌ Share your data with analytics companies
- ❌ Transmit your data to Quantum V^ LLC servers
- ❌ Access your Secure Enclave signing key or any biometric key material
All biometric key data remains on your device and your local network.
Your Rights and Choices
Access Your Data
- View all generated biometric keys in the Biometric Key Vault within the App
- Inspect key metadata: session ID, confidence score, vault slot, authorization state, and signing timestamp
Delete Your Data
- Delete individual keys from the vault within the App
- Delete all App data by deleting and reinstalling the App
- The Secure Enclave signing key is removed when the App is deleted
Control Data Collection
- Revoke Motion & Fitness permissions in iOS Settings — the App will not be able to capture biometric frequency without this permission
- Disable Face ID for the App in iOS Settings — keys can still be generated but cannot be authorized
- Disable local network access in iOS Settings — vault sync will not function
Third-Party Services
Apple Services Used
- CoreMotion: IMU data for biometric frequency capture on Apple Watch
- LocalAuthentication / Face ID: Authorization gate for Secure Enclave key signing
- CryptoKit / Secure Enclave: P256 ECDSA key generation and signing
- WatchConnectivity: Watch-to-iPhone communication
- UserDefaults: Local data persistence
These services are subject to Apple's Privacy Policy: Apple Privacy Policy
IBM Quantum (Pre-Computed Entropy Only)
THE VAULT™ entropy was generated on IBM Quantum hardware (ibm_marrakesh) in a one-time seed run. This entropy is embedded in the App at build time. The App does not connect to IBM at runtime. IBM's privacy practices are not applicable to App users.
Children's Privacy
Our App is not intended for children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.
Medical Disclaimer
Important: STEADYWATCH™ is for cryptographic identity and informational purposes only. It is not a medical device and is not intended to diagnose, treat, cure, or prevent any disease or medical condition. Always consult qualified healthcare professionals for medical decisions.
Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Changes will be reflected by updating the "Last Updated" date at the top of this page. Significant changes will be noted in the App Store release notes. You are advised to review this policy periodically.
Data Retention
- Biometric keys are retained locally until you delete them
- The Secure Enclave signing key persists until the App is deleted
- No data is held by Quantum V^ LLC — there is nothing to retain on our end
International Users
Data is stored locally on your device in your jurisdiction. We do not transfer data across international borders. Your data is subject to the laws of your jurisdiction.
Contact Us
If you have any questions about this Privacy Policy, please contact us:
Quantum V^ LLC
Email: nate_vazquez@icloud.com
Website: GitHub Repository
Compliance
App Store Requirements:
- ✅ Apple App Store Privacy Requirements
- ✅ iOS/watchOS Data Protection Guidelines
- ✅ Face ID / LocalAuthentication Privacy Guidelines
- ✅ Secure Enclave usage guidelines
Legal Compliance:
- ✅ General Data Protection Regulation (GDPR) — European users
- ✅ California Consumer Privacy Act (CCPA) — California users
Summary
In Simple Terms:
- Your biometric key is generated and stored on your device only
- Face ID is used to authorize keys — no facial data is accessed or stored by STEADYWATCH™
- The Secure Enclave signing key never leaves your device's chip
- IBM quantum entropy is pre-computed and embedded — no runtime connection to IBM
- Local network sync is optional and stays on your network
- We collect no personal information and have no access to your data
Your identity. Your device. Your key.