SAKURAKO AYABE, an individual business operator ("we," "us," or "our"), handles user information in simrip (the "App") in accordance with this Policy. Our current business address will be disclosed without delay upon request.
1. Information stored on the device
Trip names, destinations, dates, plans, packing items, booking and contact information, URLs, amounts, notes, settings, images, and PDFs are generally stored on the device. We do not transmit this content for AI processing, advertising, or analytics unless the user selects it for Edit together, sharing, or a contact request.
2. Usage analytics
The App uses Firebase Analytics and the official website uses Google Analytics 4. Information about feature usage, item counts, the app, OS, device or browser, viewed pages, and predefined interactions is sent to Google to understand usage and improve the service. The implementation is not designed to send trip names, booking numbers, phone numbers, notes, contact messages, images, or PDF contents as analytics events.
3. Operational error information
When a serious error occurs, the error type, content, location, frequency and time; app, OS, device, language and screen information; and an installation identifier may be sent to Firebase Crashlytics provided by Google LLC and the simrip API to investigate causes, prevent recurrence, and improve reliability. We do not intentionally include trip content and take measures to limit information that directly identifies an individual. Error information sent to the simrip API is generally retained by Cloudflare for 90 days and may be sent to a private Slack workspace when needed. Information handled by Firebase Crashlytics is governed by Google’s terms and settings.
4. Advertising and consent
The App uses Google AdMob and User Messaging Platform. Google may process IP address, device and app information, approximate location, ad interactions, diagnostics, and consent status for ad delivery, measurement, fraud prevention, and consent management. Ad requests are non-personalized, and publisher first-party ID is disabled. The App does not request App Tracking Transparency authorization and does not use IDFA. Where required, a choice screen is shown before ads are requested. New ad requests stop after an ad-removal purchase is confirmed.
5. In-app purchases
In-app purchases use Apple’s App Store and StoreKit. We do not obtain credit card numbers. Product, transaction, entitlement, trip, and processing-status information is processed by Apple and the simrip API to verify purchases, provide and restore features, and prevent duplicate or fraudulent use.
6. Edit together
When Edit together is used, trip content, selected attachments, participant names, identifiers and permissions, synchronization, change and connection information, and purchase-verification information are processed by Cloudflare to provide editing and sharing, manage permissions, prevent misuse, and respond to errors. Share invite links only with intended participants.
7. Contact requests and abuse prevention
For in-app support, Cloudflare stores and processes your messages, selected images, support-specific identifier, app version and build, OS version, device model, display language and the screen from which support was opened to respond, investigate and prevent abuse. Trip content is not sent automatically. Replies can be read in the app. Slack receives only the inquiry number and an administration link; chat messages, images and device details are not forwarded. Conversations and images become inaccessible 180 days after the last message and are then deleted through scheduled processing, with retries on failure. Backups may retain data during the provider's recovery retention period. Deleting the app or local trips does not delete support data on the server. History transfer after changing devices or reinstalling is not guaranteed. To request deletion, contact us in the relevant conversation. The existing web form continues to operate separately; submitted information, including a reply email address and attachments, may be forwarded to Slack as needed to handle the inquiry.
Cloudflare Turnstile may process IP address, browser and device information, and verification information for bot prevention.
8. Export, sharing, and backups
When images, PDFs, text, or backups are exported or shared, information is sent to the app, service, or destination selected by the user and is governed by that provider’s terms. The user is responsible for files after they are created.
9. Retention and deletion
- On-device trip data and attachments: until the user deletes them or removes the App.
- Edit together trips, participants, permissions, and attachments: generally within 37 days after Edit together ends or the owner deletes it. Copies on participants’ devices are excluded.
- Records needed to prevent duplicate entitlement use: up to seven years after free use or purchase.
- In-app conversations and images: inaccessible 180 days after the last message, then deleted through scheduled processing. Web-form contact information and attachments: generally 180 days on Cloudflare. Copies from the web form in Slack are generally deleted within one year after collection.
- Error information: generally 90 days on Cloudflare. Slack notifications are generally deleted within one year after collection.
- Information independently held by providers: under their terms and user settings.
Deleting the App does not immediately delete server-side Edit together information. Earlier deletion may be requested through the privacy rights form.
10. Providers and international processing
We do not sell or rent user-entered information. The principal providers are Cloudflare (API, Edit together, contact requests, storage, bot prevention and security), Slack (contact support and error notifications), Google (analytics, error diagnostics, advertising, measurement and consent management), and Apple (purchases, payments and purchase management). They may process information outside Japan. We supervise processors and provide information as required by applicable law.
11. User requests
Subject to applicable law, users may request access, correction, deletion, restriction of use, or restriction of third-party provision. Use the privacy rights form with the requested action, a reference number, or information sufficient to identify the data. A reply email address is required. We verify identity or authority using only reasonably necessary information.
12. Minors
Minors should obtain guardian consent where required. Anyone entering or sharing another person’s information or photos, particularly a child’s, must obtain the required permission.
13. Security and incident response
We take reasonable safeguards appropriate to the information, including access controls and protection of communications. Incidents requiring reporting or notification will be handled under applicable law.
14. Changes and contact
If this Policy changes, we will state the change, revision date, and effective date on this page or in the App. Where individual consent is required, we will act under applicable law.