Privacy Policy

The organisation legally responsible for HERE's personal-data processing, its registered address, support email and privacy contact must be supplied and verified before publishing this policy.

Based on the product design, categories include account identifiers from Apple or Google sign-in (such as name and email), venue discovery requests, approximate and—when permission is granted—device location information, optional visibility and presence sessions, and gathering content such as titles, venue names, times and availability.

Device diagnostics, analytics, push-notification tokens and other categories must be added if used in the actual implementation. HERE's intended design does not require profile photos or in-app direct messaging.

Location permissions and sharing presence are separate choices. HERE is designed to avoid showing precise personal coordinates to other users, instead presenting venue-level or approximate context. If the app uses background location, disclose when it is collected, why it is necessary, the controls available, and how to turn it off. Never assume a public invitation is private just because precise GPS coordinates are hidden.

If a host makes a gathering shareable, anyone with the invitation link may be able to see its public title, general venue or area, scheduled time and availability. Other attendees' identities, private presence, precise coordinates and contact information should not be included in a public preview.

Information may be needed to provide sign-in, show relevant places, display user-controlled presence, operate gatherings, prevent abuse, assist support, and secure the service. The relevant GDPR legal basis must be identified for each distinct purpose before launch; consent and legitimate interests are not interchangeable.

Review and list each provider actually used by HERE, such as hosting/database, sign-in, maps or venues, analytics, notifications and support. Explain what data each receives, where it is processed and what safeguards apply to international transfers. Names mentioned during development are not confirmation that those providers are active.

HERE's proposed presence-session design uses short-lived records. Confirm the deployed retention period for each data type, including account information, event invitations, telemetry and backups. Explain deletion, access controls, and what happens to shared invitations after cancellation or expiry. No storage system can guarantee absolute security.

Explain how users can withdraw location/visibility permission, request access, correction, export and deletion, object where applicable, and contact a relevant data-protection authority. A functioning account-deletion process and verified privacy contact must be in place before launch.

HERE is designed for adults aged 18+. Explain age eligibility enforcement and the process for material privacy-notice updates. Add the effective date once this policy is complete.