Cookie & Tracking Policy
Version: 1.2
Effective Date: 29th July 2026
This page explains the cookies we use on the indi website and the tracking technologies we use in the indi app, what each one is for, and how you can stay in control. We've kept it plain and short on purpose. For the full picture of how we handle your information, see our Privacy Policy.
Two places, two different needs
Our website and our app collect information for different reasons, so we've split this page to match:
- On our websitewe use cookies to understand how the site is used and, when our ads are running, to measure whether they reach the right families. You choose whether we do either, and until you choose, we don't. A handful of pages also embed something from another company, like a video player or a booking calendar, which is the point of the page it sits on. Those are listed under Functional below.
- In the appwe use tools that keep you signed in, fix crashes, keep things fast, manage your subscription, and help us understand how features are used. Because you're signed in, some of this is linked to your account.
Cookies are small text files a website stores on your device. In the app we mostly use similar technologies built into the tools below (sometimes called SDKs) rather than cookies. We don't sell or rent your data.
On our website (projectindi.com)
Strictly necessary
The indi website itself doesn't need any strictly necessary cookies to show you our pages. Signing in to your indi account happens in the app, not here. When you make a choice in our cookie banner we store one small cookie to remember it, so we don't have to ask every time.
| Cookie | Set by | What it does | Lasts for | Type |
|---|---|---|---|---|
| indi_consent | indi | Remembers the choice you made about analytics and marketing cookies, so we don't ask you again on every page. It holds your choice and nothing else about you. | 1 year | First-party |
Functional
A few pages embed something that comes from another company, and each one is the point of the page it sits on, so we treat it as part of the page rather than something to switch on. This is the full list. Two of them wait: the enquiry form on our allied health page loads when you scroll down to it, and the booking calendar there only after you've sent the form. The video player and the design-with-us calendar load with their page, so those can set cookies before you've answered our banner. If you'd rather not use any of them, email us instead and we'll pick it up from there.
| Cookie | Set by | What it does | Lasts for | Type |
|---|---|---|---|---|
| hubspotutk, __hstc, __hssc, __hssrc | HubSpot | Runs the enquiry form on our allied health page and links your submission to it, so we can follow up. The form is the reason that page exists, so it loads when you scroll down to it, whether or not you accept the cookies below. | Up to 6 months | Third-party |
| Calendly session cookies | Calendly | Shows the booking calendar so you can pick a time for a call. It only loads after you've sent the enquiry form, never before. The calendar runs in Calendly's own frame, and Calendly asks its own cookie question there before storing anything that outlasts your visit. | Until you close your browser, unless you accept more in Calendly's banner | Third-party |
| Loom player cookies | Loom | Plays the welcome videos on our get started and welcome pages. The player is a Loom frame and it loads with the page, so Loom may set cookies there as soon as you arrive, before you've made a choice with us. If you'd rather it didn't, your browser settings can block third-party cookies. | Set by Loom | Third-party |
| Cal.com booking cookies | Cal.com | Shows the booking calendar on our design with us page so you can pick a time. It loads with that page, and only that page. | Set by Cal.com | Third-party |
Analytics
These help us understand how people use the site so we can make it clearer and more helpful. They don't use your name, and we only set them if you accept analytics cookies.
| Cookie | Set by | What it does | Lasts for | Type |
|---|---|---|---|---|
| indi_anon_did | indi (PostHog) | A random id given to your browser so we can understand how people use the site (which pages help, where things get confusing) and make indi better. It isn't your name, but it is a unique identifier, so we treat it as personal information rather than calling it anonymous. | 1 year | First-party |
| indi_attribution — referring site | indi | Remembers which site first sent you to indi — a search engine, an AI assistant, another website — so we can tell which channels help families find us. It holds that site's web address, not your name or anything you did there. We only write it from this website if you accept analytics cookies; the app writes the same cookie under its own notice. | 90 days | First-party |
Marketing
These measure how well our ads work. We only set them if you accept marketing cookies.
| Cookie | Set by | What it does | Lasts for | Type |
|---|---|---|---|---|
| _fbp, _fbc | Meta (Facebook) | Measures whether our ads bring families to indi, so we can reach more parents who would benefit. We set these once you've accepted marketing cookies. | Up to 90 days | Third-party |
| indi_attribution — campaign details | indi | Records the campaign details from the ad or link that first brought you to indi (like which ad you clicked), so we can tell which campaigns help families find us. It holds those details, not your name. We only write it from this website if you accept marketing cookies; the app writes the same cookie under its own notice. | 90 days | First-party |
Your cookie choices
This is the choice you made in our banner, and you can change it here whenever you like, for each category. It applies to this website. Strictly necessary and functional cookies aren't listed here: the consent cookie is how we remember this choice, and each functional embed is the point of the page it appears on.
In the indi app (app.projectindi.com and our mobile apps)
When you sign in and use indi, we rely on a few tools to keep the service running, fix problems, manage your subscription, and understand how features are used so we can keep improving them. Because you're signed in, some of this activity is linked to your account. We use it to run and improve indi.
| Tool | Set by | What it does | Linked to your account | Type |
|---|---|---|---|---|
| Sign-in & app storage | indi (Supabase) | Keeps you securely signed in and remembers your preferences on your device. The app can't work without it. | Yes | First-party |
| indi_consent | indi | Remembers the cookie choice you make in the app, which is separate from the choice you make on this website. When you're signed in, your choice is also saved to your account so it follows you between devices. | Yes, when you're signed in | First-party |
| Product analytics | indi (PostHog) | Shows us which features help families and where the app gets confusing, so we can keep improving it. On our mobile app this can include session replay, a recording of how you move through screens; we hide anything you type into text fields. We use this to run and improve indi, not to advertise to you. | Yes, when you're signed in | First-party |
| Crash & performance | Sentry | Reports crashes and slow screens so we can fix them and keep indi reliable. If something goes wrong, we may capture a replay of that session to help us debug it. | Yes, when you're signed in | Third-party |
| Subscriptions | RevenueCat | Manages your subscription and purchases in our mobile apps so we can give you the right access. | Yes | Third-party |
| Ad attribution | AppsFlyer | On our mobile app, measures which ad or link brought you to indi (for example when you sign up or start a subscription) so we can reach more families who would benefit. You can control this through your device's tracking settings. | Yes | Third-party |
How to stay in control
You're in control. Here are the ways to manage this:
- On the website:our banner asks before we set any analytics or marketing cookies, and you can change your answer any time under “Your cookie choices” above. Turning a category off stops us using it from that moment, but it doesn't reach back and delete a cookie already on your device: those sit there unused until they expire, and your browser settings will clear them sooner if you'd like them gone now.
- For Meta's marketing cookies: you can manage ad preferences in your Facebook or Instagram account settings.
- In the mobile app:you can manage ad tracking (which is what AppsFlyer uses) through your device's tracking settings.
- Some tools can't be switched off: sign-in, crash reporting, and subscription management are needed to run the service and keep it secure and reliable. On the website, the same goes for the functional embeds listed above, and you can email us instead of using them.
Questions
If you have any questions about how we use cookies or other tracking technologies, reach out and we'll be glad to help.
Email: privacy@projectindi.com
Updates to this policy
We may update this policy as our site, our app, and the tools we use change. When we do, we'll update the version and effective date at the top of this page.