The provider of simrip (the "App," "we," "us," or "our") handles user information in accordance with this Policy, based on a principle of not collecting more information than necessary so users can create trip plans with confidence.
Summary
The App can be used without registration, and information entered by users, such as itineraries, packing items, and booking notes, is generally stored on the device. We do not send this entered information to external servers for AI processing, advertising delivery, or behavioral analytics. Only when a user starts or joins collaboration, the trip data needed for syncing is sent to the simrip collaboration API. For some features, such as advertising and in-app purchases, Google or Apple may handle information.
1. Basic app structure
The App can be used without account registration. It does not require login, email registration, or social network linking. Information entered by users, including itineraries, packing items, and reservation notes, is generally stored on the device being used.
2. Information stored on the device
Trip names, dates, plans, packing items, reservation numbers, phone numbers, URLs, amounts, notes, images, settings, and similar information are stored on the device to provide the App's features. We do not send this information to external servers for AI processing, advertising delivery, or behavioral analytics. If collaboration is not used, trip data is intended to remain on-device.
3. Information externally transmitted for advertising
The App uses Google AdMob provided by Google LLC to maintain free availability. For ad delivery, measurement, analytics, and fraud prevention, information such as IP address, device and app information, advertising identifiers and other identifiers, approximate location, ad display and interaction data, and diagnostic information may be automatically sent to Google. For details about the information transmitted and how it is handled, please see the Google Privacy Policy.
We do not send itineraries, reservation numbers, phone numbers, notes, images, or similar information entered by users in the App to Google for advertising delivery.
4. Advertising consent and choices
In regions where consent is required by law or regulation, a consent screen is shown before requesting ads. If "Ad privacy settings" is shown in the settings screen, users can review or change their consent there. If ad removal has been purchased, ads are not displayed and new ad requests are not made.
5. In-app purchases
Purchases of ad removal and Collaboration are handled through the App Store and StoreKit provided by Apple Inc. Ad removal can be restored with the same Apple Account. Collaboration is a per-trip product and becomes available by completing setup for the selected trip after purchase rather than through the ad-removal restore function.
Purchase processing, payment information, and purchase history are handled by Apple, and we do not obtain credit card information. The App stores the purchased status needed to provide ad removal on the device. For Collaboration, the App stores the product ID, App Store transaction ID, local identifier of the selected trip, and purchase-processing state, and sends necessary information to the collaboration API for purchase verification, fulfillment, duplicate-use prevention, fraud prevention, and recovery from errors. For details, please see Apple's Privacy Policy.
6. Sharing, Collaboration, contact, and other external transmissions
When a user saves or shares images, PDFs, text, or backup data, information may be sent through iOS sharing features to the app, service, or storage destination selected by the user. Sharing is performed only through an explicit user action, and information after sharing is handled according to the terms and privacy policy of the selected destination.
When a user starts Collaboration or joins an invite, the collaboration API receives and stores the selected trip's name, destination, dates, plans, packing items, booking notes, reservation numbers, phone numbers, URLs, amounts, notes, cover image, images and PDFs selected for sharing and related file name, type, and size information, participant nicknames, identifiers, participation status and roles, each participant's packing checks, synchronization operations, change history and connection state, hashed invite and authentication tokens, identifiers used to identify a device or participant, and the purchase-verification information described above. We use this information to provide collaboration, synchronization, permission and attachment management, purchase verification, security, fraud prevention, incident response, and data consistency.
Invite links contain a token required to join. Because a person who knows the link may be able to complete the joining process, share it only with intended participants. Participants may view or change shared data according to their assigned roles. During attachment uploads, the IP address is processed temporarily for access control and abuse prevention, and a device or participant identifier is stored with the upload record.
Collaboration data is stored and processed using Workers, Durable Objects, D1, and R2 provided by Cloudflare, Inc. Access and diagnostic information associated with network transmission and server operation may also be processed by Cloudflare.
When a user submits the contact form, we collect the selected category, message, images or video the user chooses to attach, an email address when a reply is requested, submission source, app version, build number, iOS version, device type, language, the screen from which the form was opened, submission time, and reference number. We use this information to investigate issues, respond, improve the service, and prevent abuse. Itineraries, reservation notes, packing items, Collaboration content, and other on-device data are not included automatically. Contact data is stored and processed using Workers, D1, and R2 provided by Cloudflare, Inc. We may also send the message, reply address, and attachments to our private Slack workspace to notify the operator and handle the request.
7. Images, PDFs, and backups
When exporting images, PDFs, or backup data, files may be created on the device. When outputting a PDF, temporary data is stored on the device to display the print screen and is deleted after processing. Saving, deleting, and sharing files after creation are controlled by the user's own actions and the mechanisms of the selected destination.
8. Retention period and data deletion
Data on the device is retained until the user deletes it or deletes the App. Users can delete trips, plans, packing items, reservation notes, and other data stored on the device from "Delete all data" in the settings screen. Deleted data cannot be restored. If the App is deleted, saved data in the App is also deleted. Please make a backup before deleting data if needed.
Deleting on-device data or deleting the App alone does not immediately delete server-side Collaboration data needed to synchronize with other participants. When the owner ends or deletes Collaboration, or when a participant leaves or is removed, the last content saved on a device may remain in read-only form, or shared data and attachments may be deleted from that device.
9. Server retention and deletion
Collaboration trip data, participant and permission information, and purchase transaction records are retained for as long as needed to support post-termination viewing, prevent duplicate purchase use, investigate abuse, respond to incidents, and maintain data consistency. Operational records such as ordinary change events and completed upload records are generally deleted on a rolling basis 30 days after termination or completion. Expired temporary connection tokens are generally deleted on a rolling basis after one day.
Shared cover images, images, and PDF files are generally deleted on a rolling basis after a 30-day retention period following the trip's end date plus a seven-day deletion grace period. If a user deletes a shared file, deletion processing begins promptly. Actual deletion may be delayed by failures or retries.
Contact data is generally retained for 180 days after submission and then deleted or anonymized on a rolling basis. We may retain information longer where necessary for legal compliance, dispute handling, abuse investigation, or security.
Advertising consent can be changed from "Ad privacy settings" in the App. To request deletion of data held by the collaboration API or contact form, contact us through the Contact page with information allowing us to verify that you are the data subject or an authorized person, and include the reference number when available. Retention, deletion, cross-border handling, and similar matters for information independently obtained or processed by Google, Apple, Cloudflare, or Slack are governed by each company's privacy policy and applicable laws.
10. Third-party provision and information protection
We do not sell or rent user-entered information. Except where required by law, where the user selects a sharing destination, or where necessary to use the external services described in this Policy, we do not provide user information to third parties. Information handled by the third-party services we use is processed according to each provider's privacy policy and applicable laws.
11. Notes on storage
On shared devices, other people using the same device may be able to view saved content. Please pay attention to how the device is managed when entering reservation numbers, phone numbers, or other important information. Saved data may be lost due to device failure, loss, initialization, or deletion of the App.
12. Device features and notifications
The App uses standard iOS features according to user actions in order to provide functions such as file selection and sharing. The App currently does not provide notifications. If future features require access to photos, camera, location, contacts, notifications, or similar device features, we will state the purpose and obtain user permission within the necessary scope.
13. Contact
For inquiries about this Policy, the App's handling of data, consent, or deletion, please contact us by email at pairrun0214@gmail.com or through the method listed on the Contact page.
14. Changes to this Policy
We may revise this Policy in response to changes in laws, external services we use, or App features. If there are important changes, we will provide notice on this page or in the App.