Skip to content
VOWR
AboutPrivacySupportPrivate beta

Privacy Policy

Private choices deserve careful handling.

This policy describes the current VOWR private-beta architecture in readable terms.

Last updated: 29 August 2026

Private beta: VOWR is still being developed. This policy will be reviewed before public launch and whenever the service or its providers materially change.

1. Who is responsible

VOWR Ltd, United Kingdom, is responsible for VOWR. Privacy questions can be sent to support@vowrapp.com.

2. Information used by the app

VOW and lifecycle information

The app stores the commitments you create, including type, duration or schedule, selected consequence amount, lifecycle status, completion history and intervention outcomes. Much of this information is stored locally so the app can work and recover state.

Device identity and protection state

VOWR uses pseudonymous installation and device-group identifiers to coordinate eligible devices, policy versions and protection readiness. Backend records can include VOW identifiers, timestamps, policy status, integrity events and idempotency records. They are designed not to contain readable app-selection names or browsing activity.

Screen Time selections

Apple’s Family Controls picker gives VOWR opaque application, category and website tokens. The current app stores these selections locally and in its private App Group so its Screen Time extensions can apply protection. VOWR does not receive a normal readable list from Apple’s token values and does not send those tokens through the VOWR web API.

Private recordings

If you record a future-self message, the recording and its VOW-specific reference are stored on the device. It is not included in VOW Together progress data.

Interventions and personalisation

VOWR stores limited local records about intervention choices and outcomes so it can avoid repetition and learn which pauses may be useful. The current analytics and founder-intelligence structures are local/internal foundations; this public website does not add a behavioural analytics service.

3. VOW Together

Invitation tokens are opaque, expiring and stored by the backend as secure hashes where applicable. Linked participants receive deliberately limited progress information such as lifecycle status, percentage complete and time remaining. Blocked targets, private reasons, recordings and stake details are not part of the linked-progress response.

4. Memberships and financial consequences

Apple processes App Store membership purchases and provides transaction information used to verify membership. Apple’s own privacy terms apply to that processing.

In supported test environments, Stripe processes payment-method authorisation for a possible later consequence. Stripe receives payment information directly through its iOS components; VOWR’s backend receives identifiers and authorisation status needed to manage the test workflow. VOWR does not place Stripe secret keys in the app. Live financial consequences are not enabled while the operating and charitable arrangements remain under review.

5. Notifications

If allowed, VOWR schedules reminders and lifecycle notifications. Permission is controlled in iOS Settings. Notification content is designed not to reveal private app-selection tokens.

6. Location

Location is optional and used when you ask VOWR to discover nearby sunrise, sunset or walking ideas. The current feature requests an approximate current location and uses MapKit searches in memory; it does not intentionally store a precise route history in VOWR persistence. You can instead search by town.

7. This website

This static website does not include advertising pixels, Google Analytics, Meta Pixel or behavioural cookies. The hosting provider may process ordinary request information such as IP address, user agent, requested page and security logs to deliver and protect the site.

8. Providers and disclosures

Depending on the feature and build, VOWR relies on Apple services, Stripe test services, a VOWR backend and the website hosting provider. Information may also be disclosed where required by law or to protect the security and integrity of the service.

9. Retention and deletion

Local records remain until removed by the app, reset during testing or deleted with the app, subject to device backup behaviour. Backend records are retained only as needed for private-beta operation, security, audit integrity and legal obligations. Some immutable security or financial audit records cannot be casually edited. Contact VOWR to request access, correction or deletion; the response will explain any data that must lawfully or technically be retained.

10. Your rights

Depending on where you live, you may have rights to access, correct, erase, restrict or object to certain processing, and to complain to a data-protection authority. VOWR may need to verify a request without asking for more information than reasonably necessary.

11. Children

The financial-consequence journey is intended only for adults whose eligibility can be confirmed through supported platform controls. VOWR does not treat possession of an Apple Account or payment method as proof of age.

12. Changes and contact

Material changes will be reflected by updating this page and its date. Contact support@vowrapp.com with privacy questions.

VOWR

VOWR Ltd

United Kingdom

AboutPrivacyTermsSupport
© 2026 VOWR Ltd.