Privacy Policy

1. Data we collect

We only collect what the features you use need.

• Account: email address, username, display name, password (stored only as a bcrypt hash, never as text), language and time-zone offset for reminders. If you sign in with Google: your Google account ID and its email.
• Profile (optional): profile photo, bio, city, gender, birth year, weight and height, maximum heart rate, units. Used for heart-rate zones, calories and training plans.
• Activities: type, title, description, time, duration, distance, elevation, speed, cadence, calories, perceived effort, splits and laps, the GPS track (location points with time and altitude), heart rate (from a Bluetooth sensor or Health Connect), photos you upload, gear (shoes, bikes) and the privacy setting of each activity.
• Training: goals, training plans, races you join, and fitness estimates computed from your activities.
• Social and safety: accounts you follow and your followers, cheers (kudos) and reactions, comments, posts (text and photos), 24-hour stories (photos or activity cards, and who viewed and reacted), direct messages, @mentions, club membership and posts, challenges, event RSVPs, block and mute lists, moderation reports, safety contacts, and the live beacon (your position while a beacon is active, only for the contacts you choose).
• Device and technical: the device push-notification token and notification preferences; server logs with IP address, user ID, endpoint, status and size of requests (no request bodies, no tokens).
• Error reports: when the app hits an unhandled error it sends a technical report (error type, message, stack trace, app and Android version, account ID when signed in). When you tap "Report" on an error's detail screen the report also carries the note you write. No location or activity content; kept 90 days and deleted with the account.

2. Location

Arviy asks for location permission to record activities. While recording, a foreground service (with an ongoing notification) keeps GPS running with the screen off. Arviy does not request background location permission and does not track you outside recording and beacons.

Your position is sent to our server only when you save or upload an activity, use map features (route suggestions, place search, nearby segments), or start a live beacon. You can revoke the permission any time in Android settings.

3. Optional data from other services

• Health Connect (Android): only after you grant permission in Settings → Connections & sync. Arviy reads exercise sessions, routes, heart rate, distance and calories to import workouts from your watch or other apps, and writes your Arviy activities (exercise, distance, calories, route) when you choose to. Health Connect data is not sold, not used for advertising and not shared except as described here. You can revoke access in the Health Connect app.
• Strava: if you link your account we store the Strava access token (encrypted) and the IDs of uploaded activities, and upload activities to Strava at your request. Strava data is not shown to other users.
• Google: if you choose to sign in with Google or link it.

4. How we use data

• To run the service: account, recording and storing activities, statistics, training plans, segments, leaderboards, clubs and challenges.
• Social features according to your privacy settings (section 5), in-app and push notifications, and training reminders.
• Security and abuse prevention: rate limiting, token-theft detection, moderation of reports.
• Aggregate heatmaps: only from activities set to "Everyone", trimmed by privacy zones and hidden start/end, and only shown where at least 3 different athletes passed. You can opt out of the heatmap in settings.
• AI summaries (optional, section 6) and fixing technical problems.

We do not sell personal data, do not use it for advertising or ad profiling, and the app contains no third-party advertising or analytics SDKs.

5. Who can see your data

• Other users: each activity is "Everyone", "Followers" or "Only me". Your display name, username, photo, bio and city are visible to other users. Kudos and comments are visible to anyone who can see the activity. Posts have the same privacy choices. Stories are visible to your followers only, for 24 hours, then deleted. Direct messages are visible only to you and the other person; deleting a conversation removes it on your side only. Segment, club and challenge leaderboards show names and results from activities that are visible.
• Privacy zones and "hide start/end" cut GPS data for others; you always see your full data. Activity photos are served through signed, expiring URLs; profile photos are public.
• Your safety contacts: the live beacon position while the beacon is active (it stops after 30 minutes without updates or 24 hours).
• Service providers (section 7) only receive the data their function needs.
• Authorities, when required by law or to protect rights and safety.

6. AI summaries

When the server enables it, opening the detail of your own activity may generate a text summary through the Claude API (Anthropic). Only derived, non-identifying numbers are sent: activity type, distance, duration, pace, per-km splits, elevation, that activity's average/maximum heart rate, time in zones, personal records and a comparison with the previous 6 weeks. Never sent: GPS coordinates, titles, descriptions, comments, segment names, other users, email, name, or heart-rate settings/age/weight. The summary is stored with the activity and visible to anyone who can see that activity.

7. Third-party services

• Google (Firebase Cloud Messaging) delivers push notifications: device token and notification text. Google Sign-In if you use it.
• Anthropic: AI summaries (section 6).
• Strava: only if you link it.
• Google AdMob (ads): when the server enables it, the feed shows native ads marked as ads. The Google Mobile Ads SDK collects the device advertising ID, IP address and device information to serve and measure ads, under Google's privacy policy. Arviy never sends your health, location, activity or profile data to the ad network. You can reset or delete the advertising ID in Android settings.
• Open-Meteo: the app requests temperature and dew point to adjust pace targets in hot weather. Coordinates are rounded to 3 decimals (about 100 m) and Open-Meteo sees the device's IP address.
• OpenStreetMap (map tiles from tile.openstreetmap.org and the bike-lane overlay): the app downloads tiles directly from their servers, so they receive your IP address and the map area you view.
• Nominatim and Overpass (OpenStreetMap): place and point-of-interest searches are relayed by our server; they receive the search text or area, not your identity.
• Our server hosting provider stores data under our control.

8. Retention and deletion

Data is kept while your account is active. You can delete your account in the app (You → Settings → Session → Delete account) or by email; the steps are on the Delete Account page. In short:

• Deleted: profile, profile photo, all activities with their GPS tracks, heart rate, photos and AI summaries, your kudos and comments, your posts, stories and direct messages, followers and following, goals and training plans, gear, privacy zones, safety contacts, push tokens, Strava link, block and mute lists, and login sessions.
• Kept without your name: segments, challenges, club events and races you created remain without a link to you; moderation reports you filed stay without the reporter's identity. Clubs you own pass to the longest-standing member (deleted if there is nobody else).
• Daily server backups are deleted automatically within 14 days; server logs rotate automatically and only keep the most recent period. Heatmaps are recomputed without your activities.
• Deleting your account does not revoke access at Strava or Google; revoke it in those services if needed. Data you already exported, or that sits in Health Connect, Strava or on your device, is not deleted.

You can also delete only part of your data: delete specific activities or photos, delete privacy zones, disconnect Strava, or revoke Health Connect access, without deleting the account.

9. Security

All app-to-server traffic uses HTTPS. Passwords are stored as bcrypt hashes; access tokens last 2 hours and single-use refresh tokens are rotated, with reuse detection. The session token on the device is kept in Android's secure storage (Keystore) and is excluded from Android backups. Strava tokens are encrypted on the server. Photos are served through signed URLs. No system is perfectly secure; use a strong, unique password.

10. Children

Arviy is not directed at children under 13 and we do not knowingly collect their data. If you know a child under that age has an account, contact support@sigarda.com and we will delete it. Where local law sets a higher age of digital consent, that age applies.

11. Your rights

Under applicable law, including Indonesia's Personal Data Protection Law (Law No. 27 of 2022), you may access, correct, delete and port your data, withdraw consent and object to processing.

• Access and correction: view and edit your profile and activities in the app.
• Export: activities can be exported as GPX or TCX; for a full copy email support@sigarda.com from your account's email address.
• Delete: see section 8 and the Delete Account page.
• Withdraw consent: revoke location, notification, Health Connect, Strava or Google access at any time.

We answer requests within 30 days.

12. International transfers

Our server and the providers in section 7 may be located outside Indonesia. Your data may be processed in those countries with protection we aim to keep equivalent to this policy.

13. Changes

Material changes are announced on this page with a new update date, and in the app if they affect the data we collect.

14. Contact

Sigarda · support@sigarda.com. See also the Terms of Service.