Data linked to the user
- Contact Info: profile name and email from authentication when provided.
- Identifiers: account and provider IDs, device identifier, and push token for notification delivery.
- User Content: interests, profile prompt answers, legacy bio data retained from earlier versions, profile photos, availability, plans, chats, chat photos, voice messages, and safety reports. Date of birth is used for age eligibility; a gender selection is required during onboarding and used for discovery filters.
- Location (Precise): the app requests when-in-use location and reads device GPS to set your city and coordinates and to suggest nearby places for plans. City and coordinates plus place search data are stored.
- Usage Data: requests, connections, plans, meeting confirmations, and notification read states stored to operate the app. Moments is currently disabled.
- Operational records: server request and error logs maintained by our hosting providers. The app has no configured third-party crash or analytics SDK; development console logging is not a production analytics service.
Not collected in current code
- Contacts address book.
- Payment information.
- Advertising ID or cross-app tracking data.
- Third-party advertising or third-party analytics SDK data.
Questions
You can reach WEEKLY for support, privacy questions, or to exercise your data rights at weeklysupport@gmail.com.