Privacy Policy

Wicked Funnels (ABN 18 616 868 350) (“we”, “our”, or “us”) operates the Limbo travel planning app and the website at getlimbo.app (together, the “Services”). This policy explains what information we collect, why we collect it, and the choices you have. It applies whenever you use the Services.

• Account information. Your name, email address, and password (stored as a one-way hash), or the basic profile we receive if you sign in with Google or Apple. You can also add an optional avatar photo.
• Trip and communications content. The trips, plans, bookings, checklists, budgets, expenses, settlement records, votes, comments, chat messages and polls, notes, search queries, photos, attachments, readiness actions, and AI requests you create or submit, and the crew members you invite to your trips.
• Purchase and subscription information. When you buy or restore Limbo Pro, we receive information about the store product, transaction or receipt identifier, purchase or restore outcome, subscription status and expiry, and refunds or chargebacks. We may retain older Trip Pass or Planner Pass transaction records for account history and reconciliation. Apple, Google, and their payment providers process your payment credentials; Limbo does not receive your full card number.
• Forwarded booking emails. If you forward a confirmation email to addthis@getlimbo.app, we receive that email and any attachments so we can turn it into a plan for you. See “How forwarded emails are handled” below.
• Device, usage, analytics, and diagnostic information. App and website activity such as app opens, screen views, taps, feature and purchase-flow events, website page views and referrals, and interface labels or text associated with an interaction. We also collect device and browser type, operating system, app version, locale and time zone, push notification tokens, IP address and approximate location derived from it, crash reports, stack traces, recent diagnostic context, and performance information. App analytics and crash reports may be associated with your Limbo account ID, name, or email address. Diagnostic context may incidentally contain information entered or displayed in the app. When Google Mobile Ads is eligible to run, Google may also process advertising, app-set, or other device and account identifiers, ad interactions, and SDK diagnostics as allowed by your platform and consent settings.
• Communications preferences and engagement. If you are subscribed to Limbo product updates, we record your subscription preference and information about delivery, opens, clicks, and unsubscribes so we can operate and measure those communications.
• Sponsored, partner, and creator-guide activity. The sponsored or partner item shown, placement, impression and click identifiers, creator or guide attribution, reports and blocks, copied-guide records, and provider-reported booking, refund, and paid-commission status. We do not put your raw trip, email address, or invite data into sponsor click identifiers.

• To provide the Services: storing your trips, syncing them across your devices, and sharing them with crew members you invite.
• To send you flight status alerts, trip updates, and invitations you have asked for.
• To turn forwarded booking emails into draft plans for your review.
• To provide optional AI-powered trip ideas, commands, and checklist features.
• To process and restore annual Limbo Pro, honour an existing legacy entitlement until its recorded expiry, preserve historical purchase records, and apply the resulting ad-free status.
• To send service emails such as verification, password resets, and important account notices.
• To send product updates if you are subscribed. Every update email includes an unsubscribe link.
• To provide support, keep the Services secure, understand how they are used, diagnose problems, and improve them.
• To display and measure sponsored or partner content, prevent repeated impressions and advertising fraud, secure ad delivery, attribute completed bookings, moderate creator guides, and calculate creator revenue shares.

We do not sell your personal information.

Email import is built to be private by default:

• Forwarded emails are stored encrypted (AES-256) on our infrastructure while they are processed.
• AI extracts the booking details (dates, venues, confirmation numbers) and creates a pending plan. Nothing is added to your trip until you review and confirm it in the app.
• Attachments are saved with your trip only if you opt in when confirming the plan.
• Raw emails are automatically deleted within 30 days of processing.
• Pending plans you never confirm expire and are removed after 90 days.
• Email authenticity is verified (DKIM/SPF), and personal identifiers are kept out of the extracted data wherever possible.

Trip content is shared with the crew members you invite, according to the permissions you give them. Beyond that, we share data only with the service providers that make Limbo work:

• Google Maps Platform & Places: in Limbo 2.4.01, every in-app basemap, plus destination and location search, place matching, selected place identifiers, coordinates, and current place names and addresses. Depending on the feature and platform, Google may receive relevant search terms, selected place identifiers and coordinates, IP addresses, device and request metadata, a Maps SDK-specific pseudonymous identifier, and map interactions such as panning or zooming. Limbo keeps the Google Maps branding and data-provider attribution supplied on maps and place-search results visible. Google processes this information under the Google Privacy Policy.
• Mapbox: older app versions may continue to request Mapbox basemap tiles and styles while version 2.4.01 rolls out. Mapbox receives ordinary network and request information needed to serve the map. Limbo disables Mapbox SDK telemetry in those builds.
• Wikimedia Foundation: optional Wikipedia place summaries. The selected place name and ordinary connection information are sent when Limbo requests a summary.
• AirLabs: live flight data for flight tracking.
• Unsplash: destination photos.
• OpenAI: extracting booking details and providing optional AI-powered trip, inspiration, command, and checklist features.
• PostHog: identified product analytics and feature-use measurement.
• Sentry: app and server error reporting and performance monitoring.
• RevenueCat, Apple, and Google: in-app purchases, subscription administration, restoration, refunds, and entitlement status.
• Google Mobile Ads: native ad delivery, regional consent choices, advertising measurement, analytics, and fraud prevention. Depending on platform and consent settings, Google may collect and share IP-derived approximate location, ad and product interactions, diagnostic information, and device or account identifiers. On Android, these identifiers can include the Advertising ID and App Set ID. This release requests non-personalized ads and does not request permission to track you across other companies' apps and websites. Google processes this information under the Google Privacy Policy.
• Travel and advertising partners: the specific booking fields shown in a just-in-time confirmation, or a server-approved sponsored destination and an opaque click identifier for attribution.
• Vercel: website hosting and aggregated, cookie-free website analytics.
• SendGrid: service and subscribed product-update emails, including delivery, open, click, and unsubscribe events.
• Amazon Web Services: file storage and secure booking-email receiving and processing.
• Expo: delivering push notifications.
• Slack: restricted internal operational, security, and diagnostic alerts.

These companies process information for the purposes described above under their own terms and privacy commitments. We may also disclose information if required by law.

Some of these providers store or process data outside Australia, including in the United States. When data is transferred overseas, we take reasonable steps to ensure it is handled consistently with this policy.

Limbo may show optional links to travel partners. Before current in-trip booking context is placed into an outbound partner link, we show a confirmation that names the partner and every trip field to be sent. Depending on the offer, those fields may be a coarse destination, relevant travel dates, or an exact selected public place that came from structured place data. The displayed booking context is not sent through the link unless you choose Continue; cancelling sends no click.

We do not send exact coordinates, inferred crew size, private notes, arbitrary free text, or raw account, trip, plan, email, invite, or roster identifiers in a partner URL. We record the offer selected and may associate that event internally with your account, trip, or plan for security, attribution, and reporting. Once the partner page opens, the partner and its affiliate network receive ordinary browser or device information and may use cookies or similar technologies under their own privacy policies. We may earn a commission if you obtain a quote or make a purchase through one of these links.

Free accounts may receive server-selected sponsored cards at a small set of placements. A placement may contain a directly managed sponsor card or a Google native ad. For directly managed cards, we record an impression only when the card is viewable and use a random event identifier to make retries idempotent. Before requesting a Google ad, Limbo checks whether Google requires a consent choice in your region; available choices can be reopened from the app’s profile settings.

Public creator guides show the creator profile and submitted guide content. Reports and blocks are associated with your account so we can enforce your choice and moderate the service. When a provider confirms attributable commission, we retain the provider transaction identifier, status, currency, and net commission needed for accounting and a creator revenue share.

We keep your account data while your account is active. The in-app Delete account action immediately disables access, anonymises your account, removes private trip and planner material, removes or anonymises your contributions to shared trips, and starts deletion requests with relevant processors. You do not need to email us to complete the in-app deletion request.

Shared-trip records may retain anonymised information needed for crew continuity, resolved ballots, transactions, fraud prevention, legal obligations, security, and backups. Accounting identifiers may be retained where legally required. If Apple or another processor is temporarily unavailable, local deletion continues and the external request is retried. Store billing records remain subject to Apple or Google’s retention rules, and deleting Limbo does not itself cancel a store subscription. See our account deletion page for instructions.

Google Place IDs may remain with the related trip or plan so Limbo can request current details later. For new records handled by version 2.4.01, Google-derived coordinates expire no more than 30 days after they are fetched and are then refreshed or removed. Other Google-supplied place display data returned for a live request is not written into new durable trip, plan, or place records or durable response caches. Limbo is moving older Google-linked records to these rules in stages. During that transition, older place text, display fields, or coordinates may remain with an existing trip until Limbo can safely classify, refresh, or remove them without deleting text that you entered, asked Limbo to generate, or imported from your own booking. That user, generated, or imported trip content follows the account and trip retention rules above.

Data is encrypted in transit, passwords are hashed, forwarded emails are encrypted at rest, and access to production systems is restricted. No service can promise perfect security, but we treat your travel plans as private by default.

You can correct or delete much of your personal information directly in the app. To request access, an export, or anything else, email us and we will help. If you are in a region with specific privacy rights (such as Australia, the EU/UK, or California), we honour the rights that apply to you.

Limbo is not directed at children under 13, and we do not knowingly collect personal information from them. Trip organisers may add children to a trip (a name and age) so families can plan together; that information is provided by the adult who manages the trip.

We may update this policy from time to time. The latest version will always be at getlimbo.app/privacy-policy, and we will note the date it was last updated above. If a change is material, we will let you know in the app or by email.

Questions about privacy? Email support@getlimbo.app.

If you have a privacy complaint, email us and we will look into it promptly. If you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.