Journey Weaver privacy notice

Services, diagnostics and external links

The current app has no advertising or analytics SDK and no configured remote crash-reporting service. Development tooling and the operating system can produce local diagnostics; they are not a Journey Weaver cloud backup.

Sunimod accounts and service connections

Older internal previews may still connect through https://collaboration.sunimod.com, a compatibility address for the same Sunimod-operated service. Current development builds use the Journey Weaver address below.

Accounts, collaboration routes, notification queues and outgoing email run on Sunimod-operated infrastructure at ns1.rankthe.net. HTTPS email-code login, local sign-in mail receipt and session rotation/revocation have been checked. Successful shared-trip synchronization, presence and live updates still need validation with an entitled trip. Native passkeys and real-device push also remain unverified.

The separate billing service is designed for application-scoped subscription verification and currently remains disabled pending store-provider readiness. Each app needs its own allowed package, store products and entitlement mapping; a purchase for one app does not automatically unlock another. The service is not presented as a universal verifier for every purchase type.

Account and shared-planning controls use HTTPS requests to collaboration.journeyweaver.app. Requesting an email sign-in code sends the email address you enter, an app identifier and an app-generated device identifier. Starting passkey sign-in sends the app and device identifiers to request a challenge. These requests can reach Sunimod even when sign-in fails; they do not upload your vault or personal trip library. A successful email-code sign-in creates or uses a server-held account, including the entered email address, account and device identifiers, and session/security state. Account records are separate from device-only trip and document storage.

The client also implements code redemption, session refresh, account and email changes, device and passkey management, invitations and shared-trip requests. When an authenticated session is present, account-dependent requests can include session credentials, account/device/passkey identifiers, email changes, invitation tokens and the trip or family text selected for that action. Passkey responses contain public credential information and cryptographic proofs, not your biometric data or private passkey. Account details, entitlements and permitted shared metadata may refresh when you open or resume the app or relevant screens.

The development client can attempt billing requests to billingverification.sunimod.com for account-bound purchase context, subscription entitlement checks and purchase verification. That host currently exposes health checks only; billing and store webhook routes remain closed, and store-provider verification is disabled. When verification is enabled, a request can send an Apple transaction identifier or Google Play purchase token with the authenticated session. Native billing components also initialize when the app starts and may contact Apple or Google even if you do not start a new purchase. No successful real purchase, renewal, refund or entitled shared-trip synchronization is claimed.

Notifications and online presence

The server notification capability is configured, but real-device push and successful presence/live updates for an entitled trip remain unverified. Native reminder controls are still in development. In a development build with these features enabled and an authenticated session, optional shared-activity push and email notifications are disabled by default. Notification settings can store your push/email choices, quiet hours and time zone, and trip mute choices on Sunimod. Turning off optional activity email does not stop a sign-in code you request or necessary account-security messages.

Enabling push also requires the device's notification permission. The app registers an Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) delivery token with Sunimod, alongside the app, account, device and session scope, provider, permission state and registration time. The server implementation encrypts the token at rest. Apple or Google receives the delivery token and technical delivery information needed to route a notification. Push messages contain a generic shared-activity hint and an opaque notification identifier, not trip names, itinerary text, reservation details or documents. The app must authenticate and synchronize to retrieve permitted details. A notification may appear on a lock screen according to your device settings.

Apple APNs and Google FCM are used only as optional push transports. Sunimod does not use Firebase database, authentication, storage, hosting, functions or analytics for Journey Weaver; Firebase billing stays disabled. The account, sync, billing and notification system does not depend on a paid external backend service. Delivery can be delayed or unavailable, and the implementation queues and backs off rather than enabling a paid plan to bypass limits.

Requested sign-in and account-security emails, and optional generic collaboration emails, use Sunimod's own SMTP service. Sunimod holds the recipient address, the queued purpose and delivery-attempt state; your email provider receives the message and ordinary delivery information. Collaboration emails contain no trip details or imported content. They tell you to open the app for permitted updates. Local sign-in email receipt and code redemption have passed service checks. A generic test was accepted by Gmail's mail server, but inbox or spam-folder placement was not observed. Device push and collaboration-email delivery for an entitled trip remain unverified, and server configuration does not establish availability in the internal preview. The local bounce handler processes only correlated delivery-status metadata and discards returned message content; it does not import or parse your travel emails.

When a shared trip is actively open in the foreground, the development client can send app/account/device/session and trip identifiers to show an online indicator to authorized trip members. Editing indicators also identify the record and field group being edited. Online presence expires after two minutes without renewal and is advisory, not a lock or proof that someone read a change. Updates stop when the app is in the background or the trip is inactive. This does not collect GPS location or continuously track activity in the background.

In builds where notification controls are available, you can disable optional push or activity email, set quiet hours, mute a trip and manage the device's notification permission. Disabling delivery does not erase a notification or email already delivered. Provider records and mailbox copies remain separate from Sunimod records. Contact us about server-held notification information through the privacy route below.

Sunimod hosts receive technical connection information, such as IP address, request time, method, path and response status. Technical request logs may be retained for operation, security and troubleshooting, including failed requests. Sending a request is not proof that an account was created or its contents were saved as an account record. The active service access log excludes query strings and request bodies, rotates daily and retains 14 compressed generations. Service diagnostics have separate system-managed retention; the application security-audit policy retains rows for 90 days. These are separate records and do not imply that all connection information is automatically erased after a failed sign-in. Contact us using the privacy route below.

Apple, Google, your device provider and distribution services may independently process installation, security, diagnostics and device information under their own policies and your platform settings. This notice does not set their retention periods or claim that removing Journey Weaver erases their records.

If you open a provider or support destination outside Journey Weaver, that service receives the information needed to handle the visit or message, such as connection details and content you choose to submit. Visiting sunimod.com is covered separately by the Sunimod website privacy section, including its technical request information and browser storage.

Document boundaries remain separate

The client separates trip-shared text, family-private reservation text and device-only documents. Imported files and images, passport identifiers and images, thumbnails, raw imported email content and raw OCR are never uploaded to Sunimod. An email address entered for sign-in is distinct from imported email content. Paying for or organizing a trip does not grant access to another family's private information. Metadata synchronization is not described as end-to-end encrypted.

The active account service and configured collaboration/notification routes are separate from complete app readiness. We will update this notice as billing activation, shared-trip validation, device delivery and user controls change. An endpoint response alone does not establish that the complete app workflow works.

Support and privacy requests

Email support@journeyweaver.app and identify Journey Weaver for privacy questions or requests about connection attempts, technical logs or other information you have sent to Sunimod. If a support message is delivered, we receive your sender details, message and any attachments you choose to provide and use them to respond. Do not send passports, ticket barcodes, reservation codes, passwords, payment details or unnecessary personal travel records.

Support correspondence follows the Sunimod policy's retention and choices provisions. You can ask for access, correction or deletion of information you sent us; verification and applicable retention needs are described there. This support route does not remotely erase your local app container.

Audience

Journey Weaver is being designed as an adult-managed travel-planning tool. It is not intended for children to submit information to Sunimod. Adults should handle sign-in attempts, support and privacy requests. No store age rating or public availability is claimed by this notice.

Updates

We will update this notice as Journey Weaver's implemented behavior changes. The development status and scope are shown on the Journey Weaver product page.

Journey Weaver help & support · Sunimod website & app privacy · All Sunimod apps