Your plans.
Your boundaries.

Information on your device

Journey Weaver stores personal trip names and details, destinations, itinerary entries and drafts, transport plans, packing and task states, expense entries and imported vault files on your device. Entries may include dates, locations, notes, provider links and other information you choose to enter. Use only information you are entitled to hold.

Encryption and device authentication

Stored record content and imported vault files are encrypted with AES-GCM. Device keys use the platform’s Keychain or Keystore. Biometric and device-credential checks are handled by the operating system; Sunimod does not receive your face, fingerprint, device PIN or device password.

The app uses app-switcher redaction and Android screen-capture protection for sensitive views. These controls do not guarantee that a person with access to an unlocked device cannot view or copy information.

Selected files and permissions

When you import a file, the app receives the selected file through platform interfaces and stores an encrypted local copy. The original file and its source metadata remain separate. Keep your originals for re-import; the app must not be your only copy of important travel documents.

Journey Weaver has no advertising or analytics SDK and no configured remote crash-reporting service. The operating system and local tools can produce diagnostics; those are not a backup of your travel documents.

Trip-shared text and family-private information

The app separates trip-shared planning text, family-private reservation text and device-only files. A shared action sends the text selected for that action to the service and to people authorized to see it. Family-private text has separate permissions from trip membership.

Organizing or paying for a trip does not grant access to another family’s private information. Shared metadata uses HTTPS in transit and encryption at rest on Sunimod’s server. It is not end-to-end encrypted; do not treat the service as a way to store passport identifiers, raw travel emails or imported files.

Accounts and service connections

Sunimod operates the account, collaboration, notification queue and email services on its own infrastructure. Journey Weaver account and shared-planning requests use collaboration.journeyweaver.app. Older app versions may use collaboration.sunimod.com, a compatibility address for the same service.

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 app and device identifiers to obtain a challenge. Requests can reach Sunimod even when sign-in fails; they do not upload your vault or your personal trip library.

A successful sign-in creates or uses a server-held account with your email address, account and device identifiers, and session/security state. Account controls may send code redemption, session refresh, email-change, device-management and passkey-management requests. Invitations and shared actions can send invitation tokens and selected trip or family text with authenticated session credentials.

Passkey responses contain public credential information and cryptographic proofs, not your private passkey or biometric data. Account details, entitlements and permitted shared metadata may refresh when you open or resume the app or relevant screens. Network access and account authorization are separate from access to locally available documents.

Technical request information

Sunimod hosts receive IP addresses, request times, methods, paths and response status to operate and secure the service. Service access logs exclude query strings and request bodies, rotate daily and retain fourteen compressed generations. System diagnostics have separate system-managed retention; application security audit records follow a 90-day policy. Failed requests can still produce technical records.

Apple, Google, your device provider and distribution services may independently process installation, security, diagnostic and device information under their own policies and your platform settings. Removing Journey Weaver does not erase their records.

Store and billing connections

The shared Sunimod verification address is billingverification.sunimod.com. Account-bound billing actions, where enabled, can send an Apple transaction identifier or Google Play purchase token with the authenticated session for subscription verification and entitlement checks. The app does not receive your full payment-card details.

Native store components may contact Apple or Google when the app starts, even if you do not begin a new purchase. Store processing follows the provider’s own terms and privacy policy. Verification is scoped to the relevant app, store products and entitlement mapping; a purchase for one Sunimod app does not automatically unlock another.

Notifications, email and online presence

Optional shared-activity push and email notifications are off by default. When you choose them, Sunimod can store your push/email choices, quiet hours, time zone and trip mute settings. Turning off optional activity email does not stop a sign-in code you request or necessary account-security messages.

Push also requires your device’s notification permission. The app registers an Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) delivery token with Sunimod, together with its app, account, device and session scope, provider, permission state and registration time. Sunimod encrypts the delivery token at rest.

Apple or Google receives the token and technical delivery information needed to route a notification. Messages contain a generic 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. Device settings control whether a notification appears on your lock screen; delivery can be delayed or unavailable.

APNs and FCM are optional delivery transports. Journey Weaver does not use Firebase database, authentication, storage, hosting, functions or analytics; Firebase billing stays disabled. Accounts, sync, billing, notification queues and SMTP remain on Sunimod infrastructure.

Requested sign-in and account-security emails, and optional generic collaboration emails, use Sunimod’s SMTP service. Sunimod holds the recipient address, queued purpose and delivery-attempt state; your email provider receives the message and ordinary delivery information. Activity emails tell you to open the app for permitted updates and contain no trip details or imported content. Bounce handling uses correlated delivery-status metadata and discards returned message content; it does not import or parse travel emails.

When a shared trip is actively open in the foreground, the app can send app/account/device/session and trip identifiers for an online indicator visible to authorized trip members. Editing indicators also identify the record and field group being edited. Presence expires after two minutes without renewal. It is advisory, not a lock or proof that somebody 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.

You can change optional notification choices and your device’s permission settings. Turning off delivery does not erase messages already delivered or copies held by providers and mailboxes.

Reports and copies you choose to share

Selected PDF, JSON, CSV and ICS reports are generated on your device. Review the privacy scopes before creating a report. Family-private codes and notes require explicit inclusion, and raw imports and original document files are not automatically attached.

These reports are unencrypted copies outside the app’s control. The destination you choose can retain or share them under its own rules. Reports are not a complete vault backup and cannot recover a lost device-only encryption key.

If you open a provider link, map destination or support destination outside Journey Weaver, that service receives the information needed to handle the visit or message. Sunimod cannot recall information you deliberately export, send, photograph or share.

Visiting journeyweaver.app

This static site provides product information, real app screenshots, support details and privacy disclosures. It has no advertising, analytics scripts, third-party fonts, account forms or document-upload controls. Its page code does not set cookies or use browser storage. Screenshots and the app icon are served from this domain.

The hosting server receives your IP address, request time, requested path and response status to deliver and secure the site. Website access and error logs rotate weekly with five rotated generations. Website records are separate from app service records.

Following a link to another website brings that website’s privacy practices into scope. Visiting sunimod.com is covered by Sunimod’s website privacy notice. Opening an email link uses your chosen email application and does not automatically send a message.

Retention, deletion and your choices

Local information remains in the app’s container until it is removed or replaced. Archiving a trip keeps its records and documents; it is not deletion. A failed sign-in, sign-out, loss of connectivity or subscription downgrade does not delete saved personal trips or block locally available documents.

To remove the local app container, use the operating system’s app-data controls. On iPhone, Delete App removes app data while Offload App retains documents and data. On Android, clearing app storage or uninstalling removes local app data. Platform key storage can persist separately, so app removal is not proof that every key or provider-held record has been erased.

The app requests exclusion of its data from automatic app cloud backup and device transfer. Platform and device-provider behavior can vary; this is not a recovery guarantee. Manage any existing backups through the provider holding them.

An account cannot recover or remotely erase information that remains only on your device. Losing the device or its encryption key can make saved files inaccessible. Keep your own originals. Server-synced text, locally generated reports and device-only documents have different recovery boundaries.

For account information, shared records, notification information or technical logs held by Sunimod, contact us to request access, correction or deletion. Removing the app does not delete server-held information. Requests may require identity verification and are subject to applicable retention needs.

Encrypted server backups contain server-held information, never your imported documents. Recovery copies are retained until they can safely be retired; they do not automatically disappear when a record or account is deleted. Security investigations, legal obligations and recovery requirements may require retention beyond ordinary operational windows.

Deleting or removing Journey Weaver does not erase originals elsewhere on your device, exported reports, copies you shared, support emails, platform diagnostics or records independently held by another provider. Manage those copies with their respective service or location.

Contact and privacy requests

Email support@journeyweaver.app and identify Journey Weaver for a privacy question or request. If a message is delivered, we receive the sender details, message and attachments you choose to provide and use them to respond.

Do not send passports, ticket barcodes, reservation codes, passwords, sign-in codes, payment information or unnecessary travel details. Support correspondence follows the Sunimod retention and choices policy. Support cannot remotely erase your local app container.

Audience and notice updates

Journey Weaver is an adult-managed travel-planning tool. Children should not submit information to Sunimod; adults should manage sign-in, support and privacy requests. We update this notice when the app’s information handling changes. The date above identifies this version.