Privacy Policy

Calculator inputs and pregnancy information

You may enter a last menstrual period, due date, expected period, usual cycle length, ovulation date, current DPO, most recent relevant sex or contraception-failure date, documented fertilization date, embryo transfer date, reference date, dated pregnancy weeks, height, pre-pregnancy weight, current weight, pregnancy type, or current gestational age. If you use Pregnancy Tracker, you may also enter appointment dates and details, plain-text personal notes, symptom and mood check-ins, personal and suggested-task status, movement and contraction timing sessions, hospital-bag items, birth-plan preferences, and an optional birth date when closing a record. Client-side code in the browser processes those values. Default calculations do not save inputs, have no calculation API, and do not create an account, profile, or saved pregnancy record unless the user explicitly starts Pregnancy Record and separately turns on browser storage.

Not storing default calculator inputs in a project database does not mean that ordinary technical requests never occur. This policy makes no claim about health-data regulatory coverage.

Optional local Pregnancy Record

Pregnancy Record and Pregnancy Tracker begin in ephemeral browser memory. They are written to localStorage only after the user chooses “Save this Pregnancy Record in this browser.” The versioned snapshot can contain dating-record types and entered dates, controlled source labels, derived EDDs and pregnancy-calendar starts, the user-selected current timeline basis, a separately marked current clinical EDD, basis history, audit metadata, optional dated weights, appointments, notes, symptom and mood check-ins, task status, movement and contraction timing sessions, hospital-bag items, birth-plan preferences, and optional closeout or birth date.

Pregnancy Metrics does not send these values to an application server, account, analytics platform, advertising request, URL, cookie, or sessionStorage. Anyone with access to the browser profile may be able to read local data. Clearing browser site data or using the page’s explicit clear action removes it. Choosing to install the site or use its offline shell does not automatically save a Pregnancy Record.

The current Pregnancy Record storage key is pregnancy-metrics:pregnancy-record:v3. A valid opted-in v1 or v2 record is migrated locally to v3, verified after a write-and-read-back check, and only then is the corresponding legacy key removed. New v3 fields begin empty; migration does not invent historical symptoms, tasks, sessions, plans, or checklist activity. The older weight-only tracker uses a separate key. Legacy weight migration is optional and does not invent measurement dates for gestational-age-only entries.

Offline shell and user-created files

The installable web app uses a service worker to cache the Pregnancy Tracker shell and selected same-origin static assets so the shell can reopen after it has been loaded. The cache contains published application files, not the contents of a Pregnancy Record. External medical-source pages are not cached by Pregnancy Metrics.

JSON and readable-text exports can contain the Pregnancy Record sections the user has entered. A calendar file contains the selected appointment title, date or local time, location, and notes. Print or “Save as PDF” creates the readable summary through the browser. These files and printouts are created only after a user action, remain outside project-controlled server storage, and may be copied, shared, backed up, or retained by the user’s device or chosen software. Users are responsible for deciding where to keep or share them.

Optional local weight-gain tracker

The weight-gain calculator does not write data to localStorage until you explicitly choose “Keep this tracker on this device.” After that action, the browser may store a versioned tracker snapshot containing canonical metric height, pre-pregnancy weight, pregnancy type, the estimated-baseline flag, and weight points identified only by gestational age in days and weight in kilograms.

It does not store a calendar date, name, email, account identifier, due date, last menstrual period, IP address, or free-text medical note. Stored only in this browser on this device. Pregnancy Metrics does not send tracker values to a calculation server or project-controlled database. Clearing the tracker removes the saved local tracker; browser site-data controls can also remove it.

Routine hosting and infrastructure data

The site is hosted on Vercel and its domain uses Cloudflare DNS. Ordinary requests may include an IP address, an IP-inferred approximate location, request time, request URL, browser, device, operating system, system configuration, and information used for errors, security, performance, or abuse prevention. These are different from calculator values.

Providers may process this information under their policies to operate, secure, measure performance, and prevent abuse. Pregnancy Metrics does not use routine hosting logs to reconstruct calculator inputs, and does not promise that third-party providers never retain logs. Read the Vercel Privacy Notice and Cloudflare Privacy Policy.

Support emails

If you email us, the sender address, subject, content, time, and ordinary email headers may be processed. Cloudflare Email Routing forwards mail to a verified destination address, and the destination email provider also processes and stores the message. This support flow is separate from browser calculator inputs.

Please do not send pregnancy records, symptoms, ultrasound images, identification, or unnecessary health information. The support address is not a patient portal, diagnostic service, or emergency channel, and does not promise an immediate response. Messages may be retained as needed to address website issues, keep necessary records, prevent abuse, or resolve disputes. See Cloudflare Email Routing documentation.

Cookies, analytics, and advertising status

The current site does not load Google Analytics, Google AdSense, or another ad-serving script, and it has no consent-management platform. Current application code does not intentionally set a project cookie for an account, session, or calculator result. Default calculations do not save inputs; Pregnancy Record and the optional weight-gain tracker use localStorage only after the user chooses to keep the relevant data on that device.

The root layout's AdSense account meta tag and ads.txt are for publisher account recognition, authorization statements, or audit preparation. On their own, they do not show ads, read calculator inputs, or set advertising cookies. An ads.txt file does not mean advertising is currently running.

If Google advertising is activated later, third-party vendors, including Google, may use cookies, local storage, web beacons, IP addresses, or other permitted identifiers to serve ads, control frequency, measure performance, produce reporting, and prevent fraud and abuse. Google advertising may include ads influenced by a user's prior visits or previous interactions where the relevant Google product and settings permit. Users can manage applicable personalization in Google Ads Settings. The exact data flow would depend on the configuration, consent requirements, and applicable Google settings in effect at that time.

Calculator inputs, pregnancy weight, BMI, pregnancy type, gestational age, tracker history, expected period, last menstrual period, cycle information, ovulation date, DPO, recent sex or contraception-failure date, and pregnancy-test timing calculations or results must not be intentionally inserted into ad requests, personalized advertising audience lists, analytics or ad fields, page URLs, or advertising identifiers sent to advertising providers.

Pregnancy Metrics must not intentionally use visits to these reproductive-health pages or calculator activity to build user-based interest or demographic advertising profiles. Before Google AdSense for Content is activated on Pregnancy Metrics, the applicable user-based advertising control in the publisher's AdSense ad-serving settings must be opted out. Google's AdSense for Content user-based advertising opt-out prevents eligible advertising platforms from using visitation information from the publisher site to help infer interests and demographics. This is an AdSense for Content publisher/account ad-serving control; it is not a claim that every Google privacy or ad-serving setting is site-specific. The AdSense user-based ads opt-out does not prevent ads based on a user's previous interactions with an advertiser, which Google describes as remarketing. This is not a claim that Google never processes identifiers or that every future ad configuration would be non-personalized.

If advertising is enabled, users can manage ad personalization in Google Ads Settings. Google describes its data use on partner sites. If a non-Google third-party advertising vendor or network is enabled later, this policy must identify its relevant data use and provide applicable privacy or opt-out information before that vendor is activated. No other advertising vendor is currently enabled.

Before Google ads are enabled for users in the EEA, the UK, or Switzerland, the site must implement the disclosures and consent controls required for the region and intended ad configuration. Where Google requires a certified CMP integrated with the IAB Transparency and Consent Framework, that setup must be active before eligible personalized advertising is served. A privacy policy alone does not collect consent. The current site has no consent-management platform, and these advertising data flows are not active now. See Google's required content guidance and publisher privacy disclosures.

Sharing, sale, and retention

Pregnancy Metrics does not sell calculator inputs or support-email content. Hosting, DNS, email-routing, and destination-email providers may process relevant data to operate their services. Necessary information may be disclosed for legal requirements, security, preventing abuse, or protecting legitimate rights.

This project does not retain default calculator inputs. Infrastructure logs are retained by their providers under their policies, and support messages are retained for actual website-operating needs. We do not promise a fixed retention period or that information is never shared.

Your privacy choices

You can choose not to send support email and can control cookies, cached content, and site data through your browser. If Google advertising is enabled later, Google Ads Settings may offer choices about personalization. You can ask us to find, correct, or delete a support message you sent; enough information may be needed to identify the sender and locate the message. Regional rights depend on applicable law, and third-party infrastructure logs may not be directly controlled by Pregnancy Metrics.

Security

The production site is served over HTTPS and uses reasonable measures suited to a static website and email flow. No internet transmission or storage method can guarantee absolute security.

Policy changes and privacy questions

Before advertising, Analytics, accounts, a database, server-side calculation, a new provider, or another material data flow is enabled, the public policy and necessary controls must be updated first.

This policy is reviewed when a material data flow, provider, storage practice, advertising configuration, or applicable disclosure requirement changes. If a provider, feature, storage, retention, sharing, legal, or Google policy change makes a disclosure inaccurate, the policy must be reviewed again. Minor formatting changes are not presented as a substantive privacy review.

Pregnancy Metrics is independently maintained by an individual developer, who is responsible for keeping this public Privacy Policy aligned with the current site data flows. For website privacy and data-processing questions, email support@pregnancymetrics.com. This is not a channel for medical diagnosis, patient records, or emergency help. You can also read our About, Editorial and Methodology Review, Medical Disclaimer, and Terms of Use.