What Stays on the Device. What Never Crosses.
VECTAC does not operate a centralized private health or workout-history repository. Private fitness data stays on the user's phone or transfers directly to Apple Health / Health Connect after explicit permission. Signing in does not upload workouts.
Device-Only Storage
Hardware-Key EncryptedStored in device-local encrypted JSON with iOS Keychain (AES-GCM) or Android Keystore. Excluded from cloud backups.
-
Goals & Active Adaptive Training Plans -
Full Private Workout & Practice History -
BCA Circumference Tape Inputs -
Perceived Effort (RPE) & Check-In Logs -
On-Device AI Planning Rationale Cache
Memory-Only (RAM)
Wiped After Active SetProcessed in volatile device RAM during live computer vision capture. Never written to flash disk and never transmitted across network links.
-
Raw 640×480 Front Camera Video Frames -
TrueDepth Disparity & Metric Depth Maps -
Vision Face Bounding Boxes & Landmarks -
High-Frequency GPS Coordinates -
Ephemeral Session Sensor Buffers
Prohibited & Never Stored
Strict Product InvariantVECTAC architecture strictly prohibits advertising trackers, behavioral profiling, and cloud sync of unreviewed health metrics.
-
Centralized Cloud Workout Database -
Biometric Identity / Facial Templates -
Public Location Coordinates or Heatmaps -
Health Data Sharing with Third-Party SDKs -
User Data Sales or Behavioral Profiling
Health Platform Integration Contract
Integration with Apple HealthKit or Android Health Connect is completely optional and strictly scoped. VECTAC requests write permissions just-in-time only after a local workout is completed and reviewed. Health sync failure never rolls back or cancels a successful local save.
Workouts are written only after you confirm local device persistence. VECTAC servers never read or touch this data.
Health platform samples are processed entirely on-device and never relayed to remote AI endpoints.