Privacy
This page describes what the Relationship Closeness Inventory website collects when you use the test and browse these pages. We keep practices straightforward: no accounts, no marketing emails from this site.
Information you enter in the test
You provide two first names (yours and the other person’s), each limited to 25 characters. Those names appear on your results page and in share previews if you distribute the link.
Your answers to the questionnaire are held in a temporary server session while you move through the five steps. When you submit the final step, the site calculates a closeness score and stores:
- the numeric score;
- the date and time of submission;
- the two names you entered.
Stored results are tied to a unique URL (for example results.php?id=…). Anyone with that URL can view the score and names. There is no password protection on result links.
Information collected automatically
Like many websites, we use Google Analytics (Universal Analytics) to collect aggregated usage data such as pages viewed, approximate geography, browser type, and referral source. Google’s policies govern how they process that data.
Advertising
Google-served display ads are not currently shown on this site. If that changes in the future, we will update this page and comply with applicable consent and labeling requirements.
Cookies and sessions
The test relies on a session cookie so your progress is not lost between steps. Analytics may set its own cookies. You can control cookies through your browser settings.
Retention and deletion
Result records remain in the database so shared links keep working. We do not offer a self-service deletion tool. If you need a specific result removed, contact the site operator through the channel listed on the live site (if any). Otherwise, avoid sharing result URLs you want to keep private.
Children
The inventory is intended for adults and older teens who can consent to sharing names and relationship details. We do not knowingly collect data from young children.
Changes
We may update this policy when practices change. The current version is always on this page.
Last updated: October 2026