Privacy Policy for jourwe

Privacy Policy for Jourwe

Last updated: May 6, 2026

This Privacy Policy describes how jourwe (“we”, “us”, or “our”) handles information when you use the Jourwe mobile application (the “App”) on Apple devices. It is aligned with the App Privacy labels we publish in App Store Connect for the App.

By using the App, you agree to this Privacy Policy. If you do not agree, please do not use the App.


1. Summary

  • No user account is required; we do not offer sign-up or login inside the App.
  • In App Store Connect, we disclose two data types collected from the App: Purchase History and Other User Content. See Section 3 and Section 11.
  • Trip planning input you type may be sent to our servers to run AI itinerary generation; we treat this as Other User Content and disclose it as not linked to your identity in App Store Connect.
  • Subscriptions use Apple In-App Purchase; we do not receive your payment card number. Subscription-related data is disclosed as Purchase History, used for App functionality, and linked to your identity as described in Apple’s developer reporting (see §3.2).
  • Maps use Apple MapKit on device; Apple’s processing is covered by Apple’s privacy policy.
  • We do not sell your personal information for money.

2. Who we are

Data controller: jourwe (the publisher of the App).

Country: China

Contact (privacy questions): [email protected]


3. Information we collect (matches App Store Connect)

This section mirrors what we declare under App Privacy → Data Collection for Jourwe.

3.1 Purchase History — linked to you; used for App functionality

We process information about your purchases and subscriptions in the App (for example, whether you have an active Basic or Premium subscription, as provided through Apple’s In-App Purchase).

  • Purpose: App functionality — to unlock or limit features (such as AI generation allowances) according to your plan.
  • Linked to identity: Yes, in the sense required for Apple’s subscription / purchase history reporting: this information is associated with your Apple ID / App Store account for the purpose of delivering the purchased entitlement. We do not receive your full payment card details.

Apple’s own privacy policy applies to how Apple processes payment data:
https://www.apple.com/legal/privacy/en-ww/

3.2 Other User Content — not linked to you; used for App functionality

When you create a trip plan, you may submit user-generated content such as:

  • Country / region and city
  • Trip length, start date, notes about companions
  • Budget hints, “must-see” ideas, style or theme, and other free-text preferences

This content is used only to generate and display itineraries (including when it is sent to servers we control and processed with AI / model providers acting on our instructions).

  • Purpose: App functionality — to produce the travel plan you asked for.
  • Linked to identity: No — we do not combine this planning text with a jourwe account (there is none) for profiling, and we report this category in App Store Connect as not linked to your identity. Processing is tied to delivering that request, not to building a long-term identifiable customer dossier inside Jourwe.

Saved trips or bookmarks you keep in the App are stored on your device unless we state otherwise in a future update.

3.3 Preferences on your device

Language, display options, notification cadence, and similar settings may be stored locally on your device to run the App. These items are not listed as separate data types in our current App Store Connect Data Collection disclosure unless we add them in a future version.

3.4 Maps (Apple MapKit)

The App uses Apple MapKit for place search and maps. That processing is subject to Apple’s policies, not this Policy alone.


4. AI processing

Your Other User Content (§3.2) may be transmitted over HTTPS to our backend and AI services we use to return an itinerary. We use such content only to provide App functionality (your plan). We do not use it for cross-app advertising or sale of personal information.

We minimize retention on servers to what is reasonable for operation, security, and legal compliance, and we delete or aggregate data when no longer needed, subject to legal holds.


5. Legal bases (EEA / UK)

If the GDPR applies, we may rely on performance of a contract / pre-contract (providing the App and paid features), legitimate interests (security, fraud prevention, where proportionate), consent where required, and legal obligation where applicable.


6. Sharing

We may share data with:

  • Apple (In-App Purchase, MapKit) under Apple’s terms.
  • Service providers (e.g. hosting, AI inference) under contract for App functionality only.
  • Authorities when required by law.

We do not sell personal information. Subscriptions in the App are through Apple; we do not use PayPal or Alipay inside the App for those digital purchases unless we add them and update this Policy.


7. International transfers

Data may be processed in China or other countries where we or processors operate. Where EU/UK law requires safeguards (e.g. Standard Contractual Clauses), we will apply them when applicable.


8. Retention

  • Purchase / subscription records: as needed to validate entitlements with Apple and meet tax / legal obligations where they apply to us.
  • Other User Content on servers: kept only as long as needed for the stated purposes and then deleted or de-identified where feasible, unless law requires longer retention.

9. Security

We use reasonable technical and organizational measures. No system is 100% secure.


10. Your rights

You may have rights to access, rectification, erasure, restriction, objection, portability, or withdraw consent depending on your region.

Because there is no jourwe login, we may need reasonable proof of identity when you email us.

Contact: see Section 2.


11. California (CCPA/CPRA) — aligned with App Store Connect

This section is written to match our App Store Connect disclosure that we collect only these types from the App:

| Apple label (Data types) | Purposes (as filed) | Linked to identity (as filed) |

| Purchase History | App functionality | Yes (linked) | | Other User Content | App functionality | No (not linked) |

What this means in practice

  1. Purchase History (linked)
    We use purchase/subscription status obtained via Apple to provide paid features. CCPA Category D (commercial information) may apply to this information. It is linked to the consumer as that term is used in Apple’s App Privacy for this data type.

  2. Other User Content (not linked)
    We use the trip-planning text and choices you enter to generate itineraries (including via our servers and AI). Under our App Privacy filing, this category is not linked to your identity for our reporting. CCPA categories that may overlap include aspects of user-generated content; we do not use this content for cross-context behavioral advertising as described in the CPRA.

  3. No sale
    We do not knowingly “sell” personal information of minors under 16, and we do not sell personal information in the ordinary sense of trading data for money.

  4. Your rights
    California residents may request access, deletion, correction, and may have opt-out rights for certain sharing as defined by law. Submit requests using the email in Section 2. We will verify your request as required by law.

If we add new data types in App Store Connect, we will update this Policy and the labels together.


12. Children’s privacy

The App is not directed at children under 13. We do not knowingly collect personal information from children under 13. Contact us if you believe we have.


13. Third-party links

The App may link to Apple (e.g. Privacy or Terms of Use). Third-party sites have their own policies.


14. Changes

We may update this Policy. We will change the “Last updated” date and post the new version. Material changes will be described as required by law or by app store rules.


15. Contact

Email: [email protected]


This Policy is intended to match Jourwe’s current configuration: Purchase History and Other User Content as the only data types declared in App Store Connect, with the linkage fields described above. You are responsible for keeping labels and this document aligned if your practices change.