Privacy policy

1. Information we use

With your permission, we use location information such as latitude, longitude, altitude and the time of the location fix to show the direction and distance to a person or destination. During a meetup, you share location, participation status and reactions with the other person. Nearby measurement uses temporary information needed for communication and ranging between supported devices.

Places you share or save include information you enter, such as location, name, description and related links. Maps, place searches and walking routes send search terms and relevant locations to Apple’s map services. The app has no separate account registration, but writing to CloudKit or syncing through iCloud may require you to sign in to your Apple Account.

2. Purposes, advertising and tracking

We use this information to provide the features you choose, including meetups, destination guidance, shared links and QR codes, App Clips, PiP, notifications and syncing saved places.

The current app and App Clip do not use third-party advertising SDKs or access the advertising identifier (IDFA). We do not combine user information with third-party data for advertising or share it with data brokers. Website analytics are described in section 8.

3. Protecting shared data

Current standard meetups and shared destinations encrypt their content on the device using AES-GCM before storing it in Apple CloudKit’s public database. For App Clip meetups, a relay hosted on Cloudflare forwards encrypted content, the record identifier and the sending time to CloudKit. This forwarded data does not include the invitation code or decryption key.

A recipient with the corresponding shared link or other required information can decrypt the content in the public database. Record identifiers, creation and modification times, and user identifiers assigned by CloudKit are not covered by the app’s encryption. Using Apple’s services does not make every communication or record completely anonymous.

Compatibility with older iCloud sharing formats stores information such as coordinates in CloudKit’s private and shared databases, where Apple’s sharing permissions control access. This older format does not apply the same app-level encryption used for standard public sharing.

4. Shared links, QR codes and recipients

Shared links and QR codes contain place information, information needed to join a meetup, or information needed to retrieve and decrypt stored content. People who have a link, including people it has been forwarded to, may be able to view or use its content. Check who you share with and avoid including locations or information you do not want to disclose.

Sending or opening a link involves your chosen messaging service, browser or Apple’s App Clip services. These services also process the link. We cannot erase all information or copies that a recipient has saved.

5. Service providers and notifications

We use Apple services including iCloud / CloudKit, maps, push notifications (APNs) and the App Store, as well as Cloudflare’s web hosting and App Clip relay. These providers may process IP addresses, access times, communication details and errors to deliver requests, maintain security and resolve service issues. Each provider’s processing is subject to its own privacy policy.

Join notifications use CloudKit and APNs. CloudKit manages APNs device tokens; the app does not store or log them. Join notifications do not include coordinates or decryption keys. Nearby-distance notifications are generated by checking the distance on the device.

6. Permissions and background use

Location is used with your permission. The full app may continue using location in the background during an active session to maintain guidance. App Clip location updates run while its screen is open. Ending the session or reaching the sharing time limit stops location acquisition and synchronization. Stopping them does not itself erase information already shared or stored.

You can change location, notification, Bluetooth and nearby-measurement permissions in iOS Settings. You can check participation and distance in the app without allowing notifications. Saving a QR image uses permission to add a photo; the save feature does not read the contents of your photo library.

7. Retention and limits of deletion

In version 1.0.5 and later, standard meetups end location sharing no later than five minutes after both participants have been confirmed. Waiting for the other person and navigating to a fixed destination are separate from this sharing time. Older formats or app versions may behave differently. This limit stops the app’s sharing activity; it does not guarantee automatic deletion of every server record.

When a meetup ends, the app attempts to delete CloudKit records and other session data it manages. Network errors, app suspension or termination, and record permissions may prevent deletion, leaving records stored. Public shared-destination records have no automatic expiry or in-app feature to revoke them all. Creating a new link after changing a place does not remove the record behind its previous link.

Your saved-place list is stored on the device and, when available, synced through iCloud for the same Apple Account. Information needed to resume sharing is stored in the device’s Keychain and other local storage. Removing a place from your saved list does not delete its public shared-destination record. Uninstalling the app does not necessarily remove every public CloudKit record, iCloud-synced item, Keychain item or copy held by a recipient.

8. Public website analytics

Some public website pages use Cloudflare Web Analytics to provide statistics such as page views, referrers and page performance. According to Cloudflare, this analytics service uses neither cookies nor localStorage and does not fingerprint individual visitors. This is separate from advertising tracking inside the app.

Communication information and logs used to deliver and secure the website are handled under Cloudflare’s policies and service settings. Analytics and the processing needed for delivery and security are separate functions.

9. Contact

For questions about how the app handles, stores or deletes data, contact yusukeikeda1.app@gmail.com. We will explain the relevant feature and storage involved. This does not guarantee automatic deletion of every record or revocation of links and copies held by recipients.

10. Changes

We update this page when app features or data practices change. You can check the current policy and its update date here.