Cookie Policy

Last reviewed on April 24, 2026

1. What Cookies Are

Cookies are small text files that a website places on your device — usually in your browser — when you visit. They let a site remember things between pages and between visits, such as whether you've dismissed a banner, which language you prefer, or whether you're logged in. This Cookie Policy explains what cookies BirthPlan.net uses, why we use them, and how you can control them. It supplements our Privacy Policy.

When we say "cookies" on this page, we also mean similar browser storage technologies — local storage, session storage, and tracking pixels — that serve the same general purpose.

2. How BirthPlan.net Uses Cookies

BirthPlan.net is a static informational site. We don't run user accounts, shopping carts, or personalized feeds, so our first-party cookie usage is minimal. Most cookies you'll encounter on the site come from two third-party services: Google Analytics (to measure traffic) and Google AdSense (to display ads that keep the site free). We also store small pieces of data in your browser's local storage so that interactive tools like the birth plan generator and hospital bag checklist can remember your entries while you're using them.

3. Categories of Cookies We Use

3.1 Strictly Necessary

These are required for the site to function correctly. They remember that you've accepted our cookie notice so the banner stays dismissed, and they preserve the state of interactive tools while you're using them. They cannot be turned off from inside the site, but you can block them through your browser settings — with the understanding that some features will stop working.

3.2 Analytics

We use Google Analytics (GA4, measurement ID G-DS0WPWM0NY) to understand how people find the site and which pages they read. Analytics cookies record things like the page you're on, how long you stayed, what you clicked, your approximate geographic region, and the device and browser you're using. They do not record your name, email, or other personal details. For Google's description of the cookies used by Google Analytics and what each one stores, see Google Analytics cookie usage.

3.3 Advertising

BirthPlan.net displays ads through Google AdSense. Google and its advertising partners may set cookies on your device to serve and measure ads, limit how often you see the same ad, and — if ad personalization is enabled — show ads that are relevant to your interests based on your past activity across Google's partner sites. Advertising cookies used by Google may include identifiers such as IDE, ANID, DSID, NID, and test_cookie. Google also supports a consent framework for users in regions that require it. Full details are in Google's Advertising & Privacy policy.

3.4 Preference

Interactive tools on the site save what you've typed or selected to your browser's local storage so your progress isn't lost if you navigate away. This data stays on your device and is not transmitted to us. You can clear it at any time using your browser's "clear site data" or "clear local storage" option for birthplan.net.

4. Third-Party Services That Set Cookies

The following third parties may set cookies or similar identifiers when you use BirthPlan.net:

We do not control cookies set by third parties directly. If their policies change, the most accurate information will always be on their own sites, which is why we link to them rather than reproducing them here.

5. How to Control or Opt Out of Cookies

5.1 In-Browser Controls

All major browsers let you view, delete, and block cookies. The exact steps differ by browser, but the option is usually found under "Privacy," "Security," or "Site settings":

You can also browse in private or incognito mode, which starts each session with no cookies and deletes them when you close the window.

5.2 Opting Out of Google Ad Personalization

You can turn off personalized advertising across Google products and partner sites — including the ads shown on BirthPlan.net — at Google Ad Settings. Turning off personalization doesn't stop ads from appearing; it stops them from being tailored to your inferred interests.

5.3 Industry-Wide Opt-Outs

Several industry tools let you opt out of interest-based advertising from many advertising networks at once:

5.4 Opting Out of Google Analytics

Google offers a browser add-on that prevents Google Analytics from receiving data from your browser on any site: Google Analytics Opt-out Browser Add-on.

6. Do Not Track

Some browsers send a "Do Not Track" (DNT) signal. There is no industry consensus on how sites should respond to DNT, and many analytics and advertising services, including Google's, do not act on it. BirthPlan.net does not currently change its behavior based on DNT. If you want to limit tracking, the most effective options are the browser settings and opt-out tools listed in Section 5.

7. Consent

Where required by law — for example, in the European Economic Area and the United Kingdom — we rely on your consent before setting non-essential cookies. The cookie banner on the site is how that consent is collected. You can change your mind at any time by clearing your browser's cookies for birthplan.net, which will cause the banner to reappear and let you make a different choice.

8. Children

BirthPlan.net is intended for adults preparing for childbirth. We do not knowingly direct advertising to children under 13 (or the equivalent minimum age in your jurisdiction). See our Privacy Policy for the full children's privacy statement.

9. Changes to This Cookie Policy

We may update this Cookie Policy from time to time to reflect changes to the services we use or the law in relevant jurisdictions. When we update it, we'll update the "Last reviewed" date at the top. Material changes will be accompanied by a visible notice on the site.

10. Contact

Questions about this Cookie Policy or how BirthPlan.net uses cookies can be sent to [email protected]. General questions go to [email protected], and you can also reach us through the Contact page.

11. Governing Law

This Cookie Policy is governed by the laws of [Jurisdiction], without regard to conflict-of-laws principles. Where local data protection law (for example, GDPR in the EEA or CCPA/CPRA in California) provides stronger rights, those rights apply regardless.