Velin is a running journal that only reads health data. There is no account, no advertising, no third-party analytics, and no developer-hosted server that receives your workouts. This policy explains when, why, and which data the app processes.
On device
Workout caches, memory photos, and preferences stay in Velin's container on your iPhone.
Health data is read-only
Velin reads from Health and never writes to or modifies anything there.
No tracking
No ads, third-party analytics, crash SDKs, cross-app tracking, or developer telemetry.
1. Scope and controller
This policy applies to the Velin iOS app distributed through the App Store, together with the home screen widgets installed alongside it. The data controller is One Nexus Design, the developer identified on Velin's App Store product page (“we,” “us”).
Velin does not require an account and offers no sign-in. When you use Health, location, Apple Weather, Maps, or Photos, Apple separately processes the related data under its own policies.
2. How data is handled
“Process” includes reading, storing, organizing, displaying, and deleting data on your device, and transmitting only what a feature you requested requires. The items below follow the app's actual features.
Health and fitness data (read-only)
Once you grant access in Health, Velin reads the following to show your training history and condition analysis: workouts (running, walking, hiking, cycling, and similar), workout routes, heart rate and resting heart rate, step count, walking/running distance, cycling distance, active and resting energy, body mass, running speed, running power, vertical oscillation, ground contact time, stride length, and date of birth (used only to derive age-based heart rate zones).
Velin requests read-only authorization. It never writes to or modifies anything in Health, and it never sends this data to our servers — we do not operate any.
What it reads is cached locally for offline browsing, chart calculations, and widgets. You can adjust each type, or revoke everything, in Settings → Privacy & Security → Health → Velin.
Workout routes and maps
Outdoor routes come from route samples already stored in Health, not from location recording performed by Velin. Velin does not track your location in the background.
Route coordinates are used on device to draw route thumbnails and to compute elevation and pace distribution, and are cached in the app container. Drawing a map uses Apple Maps (MapKit), so Apple may receive the requests needed to render that area.
Velin does not upload your routes to us or to any third party. When you share a workout card, you decide before sharing whether it includes the route.
Location and weather
Velin requests your location only when you view weather on the home screen and grant the iOS permission. The coordinates go to Apple Weather, through WeatherKit, to retrieve current conditions and a short forecast, and to Apple's geocoding service to produce a city name for display.
Apple states that WeatherKit uses location information only to provide weather, does not associate it with personally identifiable information, and does not track it between requests. Weather results are shown for that session; we hold no dataset as a result.
You can refuse or later revoke location access. Workout history, charts, and the rest of the app continue to work.
Photos, avatar, and workout memories
When you attach a memory photo to a run or set a profile avatar, Velin reads the images you explicitly select through the system photo picker. iOS presents the picker; Velin does not gain access to your whole photo library.
Selected images are copied into the app container (the avatar is stored in app preferences) and used only for display inside Velin. They are not uploaded. You can delete them in the app at any time.
Nickname, goals, and preferences
Your nickname, yearly/quarterly/monthly/weekly goals, appearance mode, language, and chart and unit preferences are stored in app preferences on your device.
So home screen widgets can show current numbers, a small summary — such as the latest run's distance and time and your progress for the period — is written to the App Group container shared by the app and its widgets, which also lives on your device.
Sharing and external links
When you share a workout card, the system share sheet hands the image to the app you choose. Velin takes no part in what happens next.
The rating entry in Settings uses Apple's App Store review interface, and links such as Weibo or X open those sites. Your activity there is governed by their own policies.
Diagnostics and support
Velin integrates no third-party analytics, crash reporting, or advertising SDK, and has no feature that uploads usage data automatically.
If you contact us by email or through App Store support, we use the address, description, and screenshots you choose to provide to answer that request.
Never for advertising or profiling: the data above is not used for third-party ads, developer marketing, data brokerage, cross-app tracking, or user profiles. We do not sell or share your personal information.
3. External services
Velin uses only Apple's system services. They may record requests, IP addresses, or account activity under their own policies, and Apple is responsible for those retention periods and rights-request channels.
Apple Health (HealthKit)
Data stays on your device and is provided to Velin by the system according to the permissions you grant.
Apple Weather (WeatherKit)
Receives coordinates and request time, returns current conditions and forecast.
Apple Maps (MapKit)
Renders the map area behind route thumbnails and detail maps.
App Store and Photos
Handle distribution, the rating prompt, and photo selection through iOS and the App Store.
Velin includes no third-party advertising, analytics, or crash-reporting SDK, and no developer-hosted backend.
4. Storage, security, and retention
Local data
Caches, memory photos, and preferences live in the app sandbox and are removed when you delete Velin. The health cache refreshes as the source data in Health changes; when the schema changes in an update, the old cache is discarded and rebuilt on the next sync rather than migrated.
Backups
If you use iCloud Backup or an encrypted computer backup, the contents of the app container may be included in that backup. Those backups are controlled by Apple and your backup settings, and we cannot read them.
Security measures
The app runs in the iOS sandbox, health access is controlled type-by-type by the system, and outbound requests happen only inside system frameworks such as Weather and Maps over HTTPS. No technical measure guarantees absolute security, so protect your iPhone and Apple Account as well.
5. Your choices and rights
- Health data: toggle each type, or turn everything off, in Settings → Privacy & Security → Health → Velin.
- Location: revoke access in Settings → Privacy & Security → Location Services → Velin.
- Photos: adjust the system photo permission; delete memory photos or your avatar inside the app.
- Local data: delete a workout's notes and photos, or delete Velin to remove all local data.
- Access, correction, deletion, or complaints: contact us using the details below about support communications or other information we actually hold.
Because Velin has no accounts and no server holding your workout data, we generally cannot locate, export, or delete data on your device by email. Those actions need to be completed on the device itself.
6. Children
Velin is a general-purpose running journal and is not directed specifically to children. We do not serve age-based advertising and do not knowingly collect children's personal information through a developer-hosted service. Minors should use features involving health data and location with a guardian's guidance.
7. International processing
Velin itself transfers no data abroad. When you use weather or maps, Apple provides those services according to your account and service region and may process requests across its global infrastructure.
Review Apple's policies before using the related features. Any separate consent, notice, or transfer mechanism required by applicable law depends on the actual publishing entity, service deployment, and storefront at release.