WristviaEffective 2 November 2026. This policy covers the Wristvia Android and Apple Watch prototype, run by Tomas Norkus. Email tomasnorkuss@gmail.com for privacy questions. Email signup has a separate notice.
The service and your choices
Wristvia links its phone and watch apps separately from Apple’s existing iPhone pairing. The prototype does not offer a public customer account or production purchase system. Optional Android subscription testing is described below. Nearby features use Bluetooth; Internet Backup needs separate approval on both devices. Health sync, Media, Find phone, notification actions and Wi-Fi sharing have their own controls or approvals.
We use the information described below to provide the features you choose, maintain the link, report delivery state and protect the service. We do not sell personal or health data or use health data for advertising. The app does not include advertising trackers.
Notifications, app choices and actions
Android notification access allows Wristvia to receive posted notifications. On the phone, it uses app/package and channel information to apply your forwarding choices and may list installed launchable apps and observed notification sources with their labels and icons. Eligible selected notifications can provide sender/title, message preview, source icon, timestamps and supported action labels to the watch, subject to privacy settings.
Preview content is encrypted on the sending device. The watch decrypts it to present an alert or short-lived inbox entry. If you separately enable replies/actions, the watch encrypts your reply or selected command for the phone, which checks the live source notification before invoking the source app. The source app and any recipient handle the resulting communication under their own policies.
Phone delivery history and watch receipts retain limited status information. Turning off preview text does not necessarily remove routing metadata or already saved copies. Use the relevant data controls.
HealthKit and Health Connect
Health sync is optional. With watch authorization, Wristvia reads permitted watch records such as sleep stages, heart rate and variability, breathing and oxygen measurements, wrist temperature, steps, energy, distances, floors, wheelchair pushes, fitness estimates, exercise/stand/move minutes, daylight, noise exposure, mindfulness, workouts and workout routes when available. Routes can include location coordinates. Not all watches provide all types.
Encrypted batches travel over nearby Bluetooth or the approved internet relay to the linked phone. Health permission and the Health sync choice are required independently of the selected route. Wristvia stores received records in its local health archive, derives views such as sleep summaries and an estimated sleep score, and writes supported types to Health Connect with your permission. Some types stay in Wristvia because Health Connect has no faithful equivalent. Android Health Connect access in the current implementation is write-only; it does not read other apps’ records.
Other health apps receive data only through permissions you grant them in Health Connect. We do not send health records to advertising or marketing services. The optional development Health Connect check writes small synthetic hydration entries and attempts to delete them; it is separate from real watch sync. Health features are for personal wellness, not medical diagnosis.
Media, device status, Wi-Fi and camera
Media controls use the phone’s active session, supported commands and, when enabled, track/artist/album and cover art. Commands are encrypted for the linked phone. Device-status features exchange battery, model, connection and alarm-time information; Find phone sends a ring/stop request.
If you choose Wi-Fi sharing, Wristvia handles the network name, security type and password you enter or scan and encrypts them for the watch, which asks for approval. A shared Wi-Fi image is decoded locally to fill the form; it is not automatically sent. Camera access scans link or Wi-Fi codes. The scan is not a photo-upload feature.
Opening Apple Find Devices takes you to Apple’s service; Wristvia does not receive your Apple sign-in or Apple account password.
Optional subscription testing
Opening the Android Wristvia Pro screen initializes RevenueCat to retrieve development offers and test subscription status. It uses an anonymous SDK-generated app user identifier and processes offer, test purchase, entitlement and restore information, with technical and network information needed to provide the service. Wristvia does not set email, link credentials, notification content or health records as subscriber attributes.
Current transactions use RevenueCat Test Store and do not charge real money. This is separate from the nearby device link. RevenueCat explains its processing and retention; a privacy request can identify subscription records separately from relay or health data. Final production subscription flows and store disclosures remain pending.
Internet processing and service providers
When Internet Backup is approved, the Wristvia service hosted on Cloudflare receives encrypted feature payloads together with operational information such as opaque device/link/event identifiers, credential digests, push tokens, timestamps, expiry, payload size and delivery/receipt status. Encryption does not conceal all service metadata.
Apple Push Notification service processes watch push addressing and delivery when that route is used. Apple operates HealthKit on its platform; Google operates Android and Health Connect. Cloudflare provides relay/database hosting and network protection. Hosting providers can process IP addresses, request information and service logs under their own policies.
The website is hosted through ChatGPT Sites. Support email uses the owner’s Gmail inbox. Service and email providers may process data in countries other than yours. Read Cloudflare privacy, Apple privacy, Google privacy and OpenAI privacy for their practices.
Storage and retention
Link credentials and keys are stored in protected device storage. Received content is readable on the receiving device, so device locking and preview settings matter. The relay is designed to carry encrypted feature content without the devices’ decryption keys. Independent security review remains pending.
| Notification payloads | Relay alert envelopes expire within 10 minutes and are cleared on saved receipt or cleanup. Limited attempt/receipt metadata can remain for about a day after expiry; cleanup is asynchronous. Watch previews are short-lived too. |
|---|---|
| Health transfer | Relay health batches expire within 72 hours; encrypted health receipts within 7 days. Expired items become unavailable and scheduled/request-driven cleanup removes them. These are not promises of instantaneous physical erasure. |
| Media, status and Wi-Fi | Media/command/state messages have short validity windows. Latest encrypted artwork, source icons and status may be stored separately; do not assume every icon or operational record shares the notification expiry. |
| Phone health history | The phone archive is retained until you delete it or clear app storage. Health Connect records have a separate deletion control and platform retention. |
| Device links and logs | Link records, protected retry state and content-free diagnostics may remain until expiry, unlink cleanup or local data removal. Unlinking is not the same as clearing every data store. |
| Support email | Support and privacy correspondence remains in the owner’s Gmail inbox until manually removed. Request removal by email; identity may need to be checked. |
Provider-managed infrastructure logs or backups can have separate retention; this prototype does not promise immediate erasure from every provider copy. Ask for clarification about a specific record or store before relying on a deletion outcome.
Access, deletion and contact
You can stop forwarding, revoke Android notification/camera/Bluetooth permissions, disable optional features, revoke HealthKit or Health Connect access and unlink the Wristvia apps. Revocation stops future access but does not automatically erase existing history or destination copies.
Use Delete data for local history, Health Connect and service requests. Write to tomasnorkuss@gmail.com to request access, correction or deletion of information the project holds. We handle requests manually and may ask for a minimal, safe way to identify the relevant record; never email keys, QR codes, health values or passwords.
We will update this policy as the prototype’s processing changes. Store privacy declarations must be checked against the final distributed build; this page does not establish store approval or production readiness.