Privacy Policy - Adventure Book

Last updated: October 8, 2026

Adventure Book (“the app”) is a mobile app for planning, preparing for, and remembering family activities. You can start saving ideas without an account. Once you create an account, your activities, tasks, gear lists, recaps, and any photos you attach are stored on our server - not only on your device. This page explains what we store, where, who we share it with, and how to get a copy or have it deleted. It also covers what this website collects: anonymous, aggregate page statistics that are not tied to you.

Saving ideas before you have an account

You can save ideas in the app before you create an account. Until you do, those ideas are stored only on your phone - nothing is sent to our server. When you create an account, they are uploaded to it. If you uninstall the app before creating an account, they are deleted along with it, and we can’t get them back.

Signing in

Everything beyond saving ideas on your phone needs an account. You sign in (or create an account) through our authentication provider - your credentials are never seen by any third party. Signing in stores your email address and a display name on our server, tied to your account, so the people you plan with can see who they’re planning with.

What we store on our server

Once you’re signed in, your activities, tasks, gear lists, plan notes, completion recaps, ratings, and any photos you attach are stored on our server - not only on your device - so that everyone in your circle sees the same up-to-date plan. Specifically:

• Activity content (titles, categories, dates, locations, plan notes, tasks, gear, recaps) is stored in a database we run.
• Photos are stored with Cloudflare R2, an object-storage service acting as our data processor. Photos have any embedded location (EXIF GPS) data stripped before upload.
• The database and application server run on hardware we own and operate ourselves - not a third-party cloud provider.

Content is private to your circle - the people you’ve invited to plan or participate in an activity with you. There is no public feed and no discovery; nobody outside your circle can see your content unless you explicitly create a share link for a specific activity or idea (see below).

Inviting someone to your circle

Inviting someone into your circle by email sends them an invitation link through Resend, an email service acting as our data processor. That email contains only the invite link and the display name of the person who sent it. See Resend’s privacy policy for how they handle it on our behalf.

Your household partner

As the account owner, you can make one person your household partner. They can see and change everything in your list - ideas, outings, recaps and photos - and add ideas of their own. They are another user of the same account’s list, not an outside party. People you add to a single outing as guests still see only the outings they’re added to. If you stop sharing everything, your partner keeps access to the ideas they saved themselves.

Sharing an activity

You can generate a link to share a single activity - for example with a relative who isn’t in the app - and choose exactly which fields it exposes (date/time, location, participant names, notes, tasks, gear, recap, specific photos). Anyone with that link can view what you chose to include, without signing in. You can revoke a share link at any time, which immediately stops it from working.

Sending an idea to another family

You can send a single idea to another family as a link. The page it opens shows the idea’s name, category, length and energy level, and the place and your notes only if you choose to include them. It never shows dates, people, photos or how you ranked the idea. Anyone with the link can see it, without signing in, until you remove it.

Finding a day with another family

You can offer another family a few possible days for an idea and share a link. The page it opens shows the idea’s name, your first name, and the days you offered. Whoever opens the link can answer with a name and the days that suit them, without an account or the app. The name is whatever they type, and we use it only to show you who answered.

They can also add an email address. We use it once, to tell them which day was picked, and then delete it. We delete it as soon as the poll closes, whether or not a day was picked. You never see it.

Their answer is stored on our server with the poll, and emailed to you through Resend, the same email service described above. The link stops working one day after the last day you offered, one day after the day you chose, or as soon as you stop asking. We delete the poll and every answer 30 days after that, or sooner if you delete the idea or your account. The day you chose stays on your idea.

Notifications

Reminders (getting ready for an activity the day before, and recapping it afterward) work differently depending on whether you have an account. If you’re signed in, your reminder settings (whether they’re on, the hours you chose, and any activities you turned them off for) and your phone’s time zone are stored on our server with your account. Our server then sends each reminder as a push notification and keeps it in your in-app inbox, so it isn’t lost if you swipe the notification away. Reminder notifications show the activity’s title and how many tasks or items are still open, and go through the same push delivery described below. Without an account, reminders are scheduled locally on your device using your operating system’s notification system, and nothing about them is sent to us or anyone else.

The weekly “free this weekend?” question is always scheduled on your device, with or without an account.

Separately, if you’re signed in and have notifications permission turned on, the app registers a push token with our server so we can send you your reminders and notify you when someone else changes an activity you share with them - for example, if they edit the plan, assign you a task, add or remove you, or mark it done. That push token is tied to your account. Sending the notification itself goes through Expo’s push notification service, which acts as our data processor and hands the message on to Apple’s or Google’s own push delivery service depending on your device - the same kind of processor relationship as Resend for invite emails. We also keep a short in-app history of these notifications (an inbox in the app) for 90 days, then delete it.

You can turn reminders and shared-activity notifications off separately in Settings, and turn reminders off for a single activity. Your push token is deleted right away when you sign out. If Apple or Google tell us a push couldn’t be delivered - most often because the app was uninstalled - we stop sending to that token immediately and delete it within 30 days. Deleting your account deletes any push token tied to it immediately, along with everything else.

Your calendar (Premium)

Premium includes an optional feature that looks at your phone’s calendar to find free time. It is off by default. If you turn it on, the app reads your calendar on your phone only: your calendar events are never uploaded to or stored on our servers. You can turn it off any time in the app’s Settings or in your phone’s own settings.

Subscriptions

Paid subscriptions are handled by RevenueCat, which manages purchase receipts from the App Store or Play Store on our behalf and tells our server whether your account has active access. We never see or store your payment details - those stay between you, Apple/Google, and RevenueCat.

Crash reports

To find and fix bugs, the app sends crash and error reports to Sentry, a third-party error-monitoring service that acts as our data processor. This never includes activity titles, notes, recap text, ratings, or photos - only standard technical diagnostics (device model, OS version, app version) and, once you’re signed in, a random identifier generated on your device so we can tell whether a crash keeps recurring for the same install. See Sentry’s own privacy policy for how they handle data on our behalf.

In-app usage analytics

To understand which parts of the app are actually used - so we spend time on what helps, not what we assumed would help - the app sends anonymous-in-content event counts (e.g. “an activity was created,” “a task was completed,” “the invite screen was viewed”) to PostHog, an analytics service (EU region) that acts as our data processor. This telemetry:

• Never includes activity titles, notes, recap text, ratings, or photos - only event names and coarse counts/buckets (e.g. a length-of-text bucket, not the text itself).
• Is tied to your account (not anonymous) so we can tell whether the same person keeps using the app over time - the one correlation that actually tells us whether the product is working. It’s never sold, shared with advertisers, or used for anything besides understanding and improving the app.
• Before you create an account, the same counts are tied to a random identifier generated on your device instead, and are linked to your account once you create one.

We don’t show a separate consent prompt for this - it runs on the same basis as the crash reporting above, as a normal part of operating and improving the service you’ve signed up for. See PostHog’s own privacy policy for how they handle data on our behalf.

Measuring our ads (Meta) - only if you allow it

We advertise the app on Facebook and Instagram. To see which ads actually bring people to the app, the app includes the Meta SDK. It is switched off by default and sends nothing to Meta until you tap “Allow” on the in-app prompt that asks about it. If you choose “Not now,” it is never switched on and we won’t ask again.

If you allow it, the app tells Meta Platforms Ireland Ltd.:

• That the app was installed and opened, plus standard device information the SDK collects (device model, OS version, app version, language).
• A few milestone events, by name only: that you created an account, created your first activity, or started a subscription.
• Your device’s advertising identifier - on iPhone only if you also allow tracking in the iOS “Allow to track” prompt that follows; on Android, as part of the in-app “Allow.”

It never includes your activities, notes, recaps, photos, names, email address, or anything else you write in the app. Meta can combine this with what it already knows about you if you use Facebook or Instagram, which is how it reports which ad led to an install; Meta acts as an independent controller for that, under Meta’s own privacy policy.

The legal basis is your consent. You can withdraw it at any time in the app under Settings → Privacy → Ad measurement (Meta), which stops anything further from being sent. On iPhone you can also turn off tracking for the app in iOS Settings → Privacy & Security → Tracking; on Android you can reset or delete your advertising ID in the system settings.

Exporting or deleting your data

You can request an export of your circle’s activities, tasks, gear, and recaps as a downloadable file, or request deletion of your circle and its content, from info@adventurebook.app. Deletion requests are honored within 30 days, which gives us a window to confirm the request came from you and to reverse it if it was made by mistake. Deleting your account also removes access for everyone else in your circle.

Analytics on this website

This website sends page views and clicks on the App Store / Google Play buttons to PostHog (EU region), the same analytics service the app uses, so we can see which pages people find useful and whether the site is actually sending people to download the app. This is configured differently from the app’s use of PostHog described above, specifically to avoid needing a consent banner:

• It sets no cookie and writes nothing to your browser’s storage. Each page load gets a fresh, random visitor id that exists only in memory and is gone the moment you close or reload the tab - there is no way for us or PostHog to link one visit to the next, or to your account if you later sign into the app.
• There is no autocapture and no session recording. The only events sent are a page view (URL, referrer, rough geography, and browser/device type) and, when you click one, which app-store button and where on the page.

The legal basis is our legitimate interest in understanding, in aggregate, whether the site works.

What we don’t do

• We don’t sell your data, and we don’t share it with advertisers or data brokers - the only exception is the ad measurement described above, and only if you allow it.
• We don’t show ads in the app, and this website has no ad-tracking or cross-site tracking at all.
• We don’t make your content public. There is no feed, no discovery, and no way for anyone outside your circle to see it unless you send a share link yourself.

Where your data is processed

We (the founder) are based in the EU, and our server runs on hardware we operate ourselves, also in the EU. PostHog is configured to its EU region specifically to keep our usage-data processing there too. Some of the other processors above - Sentry, Cloudflare (R2), Resend, RevenueCat, Expo, and Meta (if you allow ad measurement) - may process or transfer data outside the EU as part of providing their service; each publishes its own data processing and transfer terms, linked above where available.

Children’s privacy

Adventure Book is intended for use by adults planning activities for their family, not for direct use by children. If you enter information about a child (such as a first name in a note), it’s stored under the same handling described above - private to your circle, never sold, and never included in the crash reports, usage analytics, or ad measurement described above.

Changes to this policy

If this policy changes in a meaningful way, we’ll update the date at the top of this page.

Contact

Questions about this policy or your data: info@adventurebook.app