Privacy policy.

Private tools and optional dating-log storage

The tools under Free tools run in your browser. They do not send birth dates, date entries, profile inputs, or profile drafts to our server or custom analytics events. Analytics can record page visits and tool completion, without these inputs.

The dating tracker stores entries only when you choose Save on this browser. The saved log contains dates, how you met, date types, and your costs. It uses the local storage key pool-report-private-dates-v1. Storage has no automatic expiry. It remains until you delete it or your browser removes it.

Local storage is not encrypted or protected by an account password. Anyone using the same browser profile could read the saved log. Avoid saving on shared devices. Save again after edits or deletions to update the saved copy. Delete all tracker data removes the local saved log and current entries. It does not remove files you exported.

Exports can contain sensitive personal history. Keep them private. The site does not provide account backups or cross-device sync. Profile drafts and birth dates are not saved in browser storage or added to result URLs.

Where this policy applies

The calculator works without an account. It also works if you say no to analytics.

We do not ask for your name, email, phone, app login, payment details, exact location, or contacts.

This Privacy Policy applies to The Pool Report at datingpoolreport.com, including its calculators, state reports, and research pages. It describes the current implementation and does not cover third-party websites linked from the service.

Privacy questions and applicable rights requests may be sent to privacy@datingpoolreport.com.

Calculator inputs

The calculators do not require an account. They do not ask for your name, email address, phone number, dating-app login, payment information, precise location, or contacts. Calculations run in your browser. The site no longer accepts study responses.

Selected filters can appear in a shareable result URL. Anyone who receives that URL can see those inputs. Do not share it if you do not want the selections visible to recipients, browser history, or services that process the link.

Former expectations study

The 2026 dating expectations study has ended. New responses are not accepted. Closing the study does not delete previously stored records. Each stored response is deidentified. This means it does not include direct identifiers.

What the study stored

The study stored broad answers about age, gender, partner group, filters, relationship goals, values, and expected dating spending. It also stored the study version, submission date, broad completion-time band, completed-step count, and interaction count for quality review.

The full record includes a broad age range, gender category, intended partner pool, and calculator filter snapshot. It also includes relationship goals, preferences about children, education, smoking, drinking, and shared religion, optional dealbreakers, monthly dating-spend band, payment expectation, and self-rating.

If the visit used campaign tags, the record can also include sanitized source, medium, and campaign labels. This helps us check recruitment channels. Fine-grained content and creator labels are not copied into the record.

What we do not store

The research record does not include a name, email, phone number, free-text answer, exact birth date, specific religious affiliation, exact submission time, IP address, user agent, generated headcount, or advertising identifier.

What could still identify you

A detailed combination of structured answers can still make a person easier to recognize. For that reason, we do not describe the record as anonymous. Cloudflare may also process ordinary request information in hosting and security logs separately from the stored research object.

Raw records are kept in private U.S.-region object storage and are not published. The public study pages and downloads have been removed.

Hosting and security

Cloudflare hosts the site and provides security services. It may process request information needed to deliver and protect it. This can include IP address, timestamps, requested URLs, user-agent or device information, referral headers, bot-detection signals, and security or diagnostic logs. Web servers must receive requests to return a page.

We use this information to operate, secure, debug, and prevent abuse of the service.

Cookieless page counts

We count visits with PostHog in cookieless mode. It sets no cookies and saves nothing in your browser. It does not collect your name, email, or account details, and it does not build a profile of you. Visitors are counted with a hash that changes every day.

It records the page path without the query string, campaign tags such as utm_source, the referring site, device and browser type, and a few actions: a tool showing a result, a share or copy, and a click to an outside product page. It does not record calculator inputs or result values. Like any web service, PostHog receives your IP address with each request. It uses the address only to make the daily count. It does not store the address or a location based on it. PostHog processes this data in the United States.

If a script on the page breaks, PostHog also gets an error report. It holds the error message, where in our code the error happened, the page path, and the same device and browser details as a page count. Web addresses in the report lose their query strings.

Counting stops if your browser sends Do Not Track or Global Privacy Control, or if you choose No thanks in the analytics choice.

Google Analytics

Google Analytics loads only after you accept optional analytics. It may then process page views, page URLs and titles, approximate geography, device and browser information, referral information, sessions, and interaction events.

Custom events can include selected state code, age range, height and income thresholds, active filters, result ratios, preset use, calculation details open, and monthly or annual spend bands. We do not intentionally send names, email addresses, phone numbers, or account identifiers to Google Analytics. Use Cookie settings in the footer to change your choice.

Cookies and local storage

Your analytics choice is stored in browser local storage. Google Analytics uses first-party cookies to distinguish users and sessions only after you accept. The site does not store calculator settings in cookies or browser local storage. Shareable settings can appear in a result URL.

Sanitized campaign and creator labels can stay in session storage for the current browser tab. This lets attribution survive navigation.

A cookie from past study participation can remain for up to one year after submission. The site no longer sets or uses it. It contains no research answers.

See the Cookie Policy for cookie names, purposes, default durations, and controls.

How information is used

We use information to deliver and secure pages, reproduce selected calculator settings, understand site use, diagnose errors, and improve content and usability. We also use it to enforce the Terms and comply with legal obligations.

Research answers help us review group patterns in partner filters, self-rated fit with stated goals, and dating-spend expectations. We do not use them to create dating profiles, contact respondents, or identify people represented in source datasets. We also do not use them for eligibility, credit, housing, insurance, employment, or healthcare decisions.

Who may process or receive data

Information may be processed by Cloudflare for hosting and security, by PostHog for cookieless page counts, and by Google for Analytics. It may also be disclosed when reasonably necessary to comply with law, respond to valid legal process, protect rights or safety, investigate abuse, or complete a business reorganization subject to appropriate protections.

Public Census microdata and CDC distributions used by the models are disclosure-protected or aggregated source data. The site cannot identify the people represented and does not attempt to do so.

Sale, sharing, and advertising

The current site does not sell personal information, use personal information for targeted advertising, or integrate an advertising network. Google receives measurement data for Analytics as described above.

This policy must be updated before advertising, personalization, email capture, user accounts, payments, or additional analytics vendors are enabled.

Retention and security

Hosting logs and analytics data are retained under the configured settings and legitimate operational needs of the relevant service providers. Research records are retained through analysis and publication review, then reassessed at least annually for deletion, de-identification, or continued research need. We avoid promising a shorter period than the systems can verify.

Reasonable technical and organizational safeguards are used, including HTTPS, private research storage, and restricted platform access, but no internet service can guarantee absolute security.

Your privacy choices and rights

You can decline optional analytics in the site’s privacy control, block or clear cookies in browser settings, avoid sharing result URLs, and use browser privacy controls. The calculator works without analytics consent.

Because a research submission intentionally contains no account, name, email, or response identifier returned to the browser, we may be unable to reliably locate one deidentified record later without collecting additional identifying information. Depending on where you live and whether a law applies to the operator, you may still have rights to request access, correction, deletion, portability, or information about disclosures, and to appeal or avoid discrimination for exercising a right. Submit a request to privacy@datingpoolreport.com.

Children, international use, and changes

The site is not directed to children under 13 and does not knowingly request information from them. If you believe a child submitted personal information, contact us.

The site is operated from the United States, and service providers may process information in the United States or other countries. We may update this policy as the product, vendors, or law changes; the effective date will identify the latest version.