Last updated: 8 October 2026
Application: TripReady: Packing Planner
Application ID: com.tripready.packing
Responsible publisher: Marie Tømrer ApS
Privacy contact: vyngo20042008@gmail.com
Scope
This policy applies to the Android application identified above, including its translated and regional store names. It explains local trip-planning records, online functions and attribution services. Version 1.1 uses an Internet connection and includes AppsFlyer and Meta/Facebook SDKs. It is intended for adults aged 18 and over.
Trip-planning records stored on your device
Trip names, destinations entered as text, travel dates, traveller names and types, packing lists, quantities, notes, bag details, preparation tasks, templates and drafts are stored in the app's private Android storage. Appearance, units, onboarding and reminder settings are also stored locally. These planner records are not attached to the app's attribution or online-service requests. The planner does not read your contacts, calendar or GPS location. Only enter information about other people that you are entitled to use.
Information transmitted automatically
AppsFlyer and Meta/Facebook process installation and app-launch/session events, available advertising identifiers, SDK/app-instance identifiers, device and operating-system information, app version, timestamps, install-referrer and campaign/deep-link information. Online requests expose an IP address, which can be used to infer approximate region or city; the app does not request precise location permission. Technical processing includes diagnostics and app-performance information. Meta SDK instrumentation can also transmit SDK-related crash, error and application-not-responding reports when its reporting features are enabled.
The app sends its AppsFlyer identifier and available campaign and deep-link parameters to service providers supporting its online functions. These providers receive the requests and associated network metadata. Automatically collected attribution and diagnostic data is not treated as transient, in-memory-only processing. The current app does not provide an in-app switch to disable initialization of these SDKs.
Why information is processed and who receives it
Online and SDK information is used for app and deep-link functionality, installation attribution, analytics, advertising campaign measurement and fraud prevention. It is transmitted to AppsFlyer, Meta/Facebook and service providers supporting the app’s online functions. AppsFlyer processes attribution data as a service provider; Meta processes app events and identifiers for attribution and advertising measurement under its applicable terms. Advertising integrations may exchange attribution information with the networks involved in a campaign. The app does not include the contents of your local packing database in these exchanges.
Provider privacy information:
AppsFlyer: https://www.appsflyer.com/legal/privacy-policy/
Meta: https://www.facebook.com/privacy/policy/
Online functions and information you choose to provide
Online services receive connection metadata such as IP address and device/software information. They can use cookies and local storage to support their functions. This processing is separate from the local planner database. Third-party cookies are disabled.
If a function asks you to select a file or take a photo, only the content you choose is made available to that function and its service provider. The app does not silently upload your photo library or backups. You can decline to provide files or photos.
Local backups, sharing and reminders
Backups are exported as ZIP files only at your request through Android's document picker. You select the file provider and destination. Shared trip summaries are sent only to the receiving app you choose; notes and traveller names are optional and excluded by default. Cloud-backed file providers and receiving apps process the information you give them under their own terms. Exported ZIP files are not password-protected or encrypted by this app. Protect copies containing personal information. The app disables automatic Android cloud backup of its private records.
Optional departure and task reminders are scheduled locally. Notification content may be visible on your lock screen according to Android settings. You can disable reminders or their notification permission.
Retention, deletion and controls
Planner records remain on the device until you delete or replace them, clear app storage or uninstall. Archiving is not deletion. Settings, Data & backup, Delete all local data removes trip records, templates and drafts and cancels reminders; theme and onboarding preferences remain. A confirmed restore replaces the relevant local records. Exported files and shared copies must be deleted separately.
Clearing local planner data or uninstalling does not delete information already transmitted to an online service or SDK provider. Attribution, event and technical records are retained for their processing purposes and applicable legal requirements under the relevant service's retention rules. Device advertising-ID controls can limit available advertising identifiers but do not stop all network requests or remove past records. For questions about your information or the relevant privacy rights, contact vyngo20042008@gmail.com. Do not send passwords, payment details or a complete backup with an enquiry. Correspondence you send provides your email address and the content of your message for handling that enquiry.
Security
The app’s SDK and online-service requests use HTTPS, and cleartext traffic and mixed HTTP content are disabled. Local storage uses Android's application sandbox. The app does not provide a separate database password or encryption feature. Protect your device and exported files. No method of storage or transmission guarantees absolute security. External services may process data in countries other than your own under their applicable privacy terms.
Children and changes
The application is not directed at children. Contact the publisher if you believe a child has provided information through it. This policy will be updated when information-handling practices change; the date above identifies this revision.