Decide what the app truly needs
An attendance tracker may need planned days and check-ins but not heart rate, location, Contacts, or a social profile. Match each permission to a visible feature. Decline access that is unrelated to the way you intend to use the app.
Understand local storage and backups
No account can reduce identity linkage, but local data may still be included in device backups or lost with the phone. Check whether the app offers export, iCloud sync, or a clear recovery story and whether those features are optional.
Review analytics and notifications
Read the App Store privacy details and policy for analytics, crash reports, identifiers, third-party SDKs, and purchases. Consider what a Lock Screen notification reveals about your schedule or membership.
Understand Went’s focus
Went is designed without a Went account or workout uploads. Your schedule, membership price, check-ins, and settings stay on the iPhone; review the current privacy policy and App Store disclosure when the app launches.
Common questions
Does no account mean no data collection?
Not necessarily. Check analytics, crash reporting, identifiers, purchases, and the privacy policy. Account creation is only one part of the data flow.
Does a gym tracker need location access?
Attendance can be recorded manually without continuous location. A location feature should be optional and clearly explained.
Can local-only data be recovered?
Only if the app supports export, device backup, or another recovery method. Privacy and recoverability involve different tradeoffs.