What MaiCation keeps, and who sees it.

Last updated 5 September 2026 · Applies to holiday.maisoftware.app

MaiCation is a travel planner for families, made by Mai Software, an independent studio in Australia. This page says plainly what the app stores, what it sends to other companies to do its job, and how to get your data back or have it deleted. If anything here is unclear, write to support@maisoftware.app.

What we store

• Your account — name, email address and a salted hash of your password. Never the password itself.
• Your household and trips — the people travelling, the places, the bookings, ideas, budget lines, notes and decisions you enter or approve, and the conversation with the assistant.
• The vault — passports, visas, insurance and emergency contacts you choose to store, encrypted at rest with AES-256-GCM. Opening it needs a separate passphrase on top of your login; it locks after ten minutes; every access is logged for you to see.
• Mailbox connection — if you connect a mailbox, the revocable app password you provide, stored encrypted. The scanner lists only sender, subject and date; reads a body only when the envelope already looks travel-related; stores only travel emails; and keeps nothing but an anonymous fingerprint of everything else so it is not looked at twice.
• Passes — each Trip Pass you buy: when it runs, how many questions it includes, and Stripe's identifiers for the payment and your customer record. Never card details.
• Usage counts — how many assistant questions the household has asked, to count them against the free allowance and any pass.
• A referral label — the Booking.com and Expedia links the app fills in for you carry a short code derived from your household, so a commission those sites pay can be matched back to you and your pass refunded. It names nobody and contains nothing about you; it is the only thing about you that travels in those links. The Booking.com link passes through CJ (Commission Junction), the network that runs Booking.com's programme, which records the click and sets a cookie in your browser so the booking can be attributed; CJ's own privacy policy covers that cookie.

Who processes it for us

• Supabase — hosts the database, in Sydney.
• Vercel — runs the app, with its functions in Sydney.
• Anthropic — runs the assistant (Claude). It receives the trip you're asking about, the question, and any document or screenshot you hand it. Vault contents are sent only for the one scan you request, and the result is shown to you before anything is saved. We do not use your data to train models, and Anthropic's API terms prohibit them from doing so.
• Stripe — takes payment on its own hosted page and emails the receipt, and pays a refund back to the same card. We never see your card.
• Booking.com (through CJ) and Expedia affiliate programmes — when you follow one of the app's links and book, they tell us the referral label, the date and the commission. They do not tell us who you are, and we do not tell them.
• Google Maps Platform — place search and street-level photos when you search for a hotel or restaurant; it receives the search text and the area, never your name.
• Open-Meteo, Nager.Date, travel-advisory.info — the forecast, public holidays and travel advice for the evening memo. They receive a place name or country, nothing else.
• OpenStreetMap Nominatim and OSRM — the "leave by" estimate in the memo. This is the one feature that sends a booking's street address to a third party: two addresses, the bed and the first stop, with no name, reference or date attached. It can be switched off per trip under Settings & tools.
• AviationStack — flight status for booked flights: a flight number and a date.
• Your own mail server — the evening memo is sent over SMTP with the app password you already provided, from your own address, or over a relay you configure.

What we don't do

• No advertising, no analytics trackers, no selling or sharing of data with anyone not listed above.
• A commission never changes which links you are shown, or the order of the prices. Every tagged link says it is one, beside the link.
• Shared pages and exports are built from a redacted view with no booking references, loyalty numbers, full names or contact details.
• Nothing inside a document, an email or a web page is treated as an instruction to the assistant.

Your choices

• Export — any trip can be exported as a standalone page at any time.
• Delete a trip — from Settings & tools; everything on it goes with it.
• Disconnect a mailbox — from Set up; the stored app password is removed at once, and you can revoke it with your mail provider too.
• Delete your account — email support@maisoftware.app from the address on the account and we will remove the account, its household and everything in it within 14 days, and confirm when it is done.
• Passes — a pass is one payment; there is nothing to cancel and nothing renews. Book a stay through one of the app's links and we refund it when the commission reaches us, which is six to eight weeks after the stay; we check the reports monthly. Any other refund: email us within 14 days of buying.
• Connect your own assistant — Claude.ai or ChatGPT can read and propose to your trip through the connector under Set up → Connected apps, and you can revoke that there at any time. What you say to that assistant is between you and its provider.

Cookies

One session cookie to keep you signed in (30 days if you ask to be remembered, otherwise until the browser closes), one short-lived cookie while the vault is unlocked, and nothing else. No third-party cookies.

Changes

If this policy changes in a way that matters, the date above changes and the app says so on the Set up screen.