Remeet1. Introduction
This policy explains how the operator (Tomokichi) handles user information for the iOS app “Remeet” and this website (together, the “Service”). This website is the authoritative version; the app refers back to it. When offline, a bundled reference copy may be shown in the app.
2. Operator
The Service is developed and operated by an individual, Tomokichi. Contact support@tmkch.io or the shared support form.
3. Scope
This policy applies to use of the app and browsing of this website.
4. Basic policy
The app does not require a proprietary account. Reunion plans, photos, and notes are stored on your device. If you are signed into iCloud with the same Apple Account, personal records may also sync to your private iCloud database. A shared reunion syncs with the one partner you invite through Apple iCloud and CloudKit. The operator does not run a proprietary server that collects or views those records. Google Mobile Ads is used for advertising, but your in-app records are not sent to advertising partners.
5. Information stored on your device
The app stores the following in an on-device database (Core Data) and an App Group container. If you are signed into iCloud with the same Apple Account, personal records may also sync to your private iCloud database. For a shared reunion, the relevant information is shared with the invited partner:
・Reunion plan names, dates, and notes
・Place names, coordinates, and time zones
・Wish-list items and completion state
・Photos, dates, notes, impressions, and ratings
・Sharing state, Share Pass transaction ID, pass state, and reunion ID
・App settings such as notification preferences
Some on-device information is shared within the developer’s App Group for widgets.
6. Information sent externally
The app communicates externally in these cases:
(1) iCloud sharing and the Share Pass ledger: shared reunion content, first-free-sharing state, and the Share Pass ledger are sent to Apple iCloud / CloudKit. The partner who accepts your invitation can view and edit that reunion.
(2) In-app purchase: Apple StoreKit is used to buy and verify Share Pass transactions and synchronize purchase information.
(3) Weather: saved coordinates are sent to Open-Meteo; names are not sent.
(4) Place search / geocoding: search terms or coordinates are sent to Apple.
(5) Ads and consent: Google Mobile Ads and User Messaging Platform may send IP address, device or advertising identifiers, technical information, and consent status. Reunion content is not sent.
(6) Legal documents: the latest copy is loaded from this website.
(7) Support: only when you submit the form, your entries and related app, OS, language, time, and enquiry identifiers are sent to the support API and email provider. Records are not attached automatically.
7. Device permissions
With your permission, the app uses:
・Camera — photos of waiting days and reunions
・Photo library — photos you choose
・Location — only when you tap “Use current location”, to resolve a place name and time zone; never continuous tracking
・Calendar — write a reunion when you choose; existing events are not read
・Notifications — reunion reminders on device
・Tracking — only if allowed, for personalized ads using cross-app / cross-website data. Every feature remains available without tracking permission.
8. Advertising
The app uses the Google Mobile Ads SDK and the User Messaging Platform (UMP) for consent.
・Information such as IP address, device details, advertising identifiers, ad interaction / diagnostics and consent status may be processed by Google and advertising partners for delivery, measurement and fraud prevention
・Use of advertising identifiers follows your permission and regional consent
・Personalized or non-personalized ads may be shown depending on consent
・Refusing App Tracking Transparency (ATT) does not limit core app features
・You may be able to change consent via the consent form and iOS Settings
In-app records such as plans, photos and notes are not sent to advertising partners. See Google’s privacy policy and ads documentation for more detail about Google’s processing.
9. Service providers and disclosure
The operator does not sell or lend your in-app records. The Service uses Apple (iCloud / CloudKit, StoreKit, and system features), Google (ads and consent), Open-Meteo (weather), Cloudflare Workers (support API), and Resend (support email). Information is not otherwise disclosed to unrelated third parties except where required by law.
10. Retention and deletion
On-device and iCloud information is kept until you delete it. Delete individual records on their screens, or all data from Settings → Delete all data. Deleting a shared reunion also removes access for its participant. Uninstalling removes on-device data, but sharing state and the Share Pass ledger in iCloud may remain as needed for synchronization after reinstalling.
11. Security
The app has no proprietary account and does not handle passwords. On-device data is protected by iOS security mechanisms; shared data is protected through Apple iCloud / CloudKit.
12. Information obtained from reports
Content created through sharing (text and photos) is not sent to the operator during ordinary use. It stays between the device and iCloud.
Only when you tap Report on a partner’s content does the operator receive, for review:
・The reported text
・Any image attached to that content
・The reason and an optional explanation you type
・Report id, content id, reunion id, and device identifiers for the author and the reporter
・App version, build number, OS version, and language
The purpose is responding to misuse, keeping people safe, and handling support.
Reported images are stored in private storage (Cloudflare R2) for review and are deleted automatically within 30 days in principle.
Report records and related information may be kept as needed for misuse response, safety, disputes, and similar purposes.
13. Minors
If a minor uses the app, please do so with a parent or guardian’s consent.
14. Changes
This policy may change with law or product updates. Material changes will be announced in the app or on this website and take effect when published.
15. Contact
Questions about this policy: shared Tomokichi support form or support@tmkch.io. Support information is not sent unless you submit the form.