CLEAR FROM THE START

Privacy & sharing

A simple guide to how this local version works.

What other people can see

Anyone with a group's results code can see its completed participants' display nicknames and pairwise agreement counts and percentages. Any participant can share that link immediately. Use an alias if you don't want a real name shown. New participants appear on that same page as they complete the quiz.

Your individual answers are not shown to other participants or public visitors. The service stores them to calculate comparisons.

Browser access

An essential first-party browser cookie lets you manage your own participation without an account. A separate essential cookie protects form submissions. Clearing cookies or changing browsers loses management access. Invitations and results codes have different permissions; a results link alone cannot join or manage the group.

This tab temporarily keeps a draft in session storage so you can recover after a failed submission. It is removed when submission succeeds or you close the tab.

Retention and deletion

Sessions stop working 30 days after creation. Cleanup runs every 12 hours to remove expired sessions and answers. Participants can remove themselves; creators can delete the entire session or turn off its shared results link. Removal from the active database is immediate. A hashed browser identifier, form identifier and creation time remain for up to 36 hours to enforce the 24-hour creation limit and prevent deleted submissions being retried. These records contain no answers or nicknames. Downloaded screenshots and social caches cannot be recalled.

Optional sign-in and score history

Funtoolio sign-in is optional and all quizzes remain free. Signed-in and guest participants can play together. We map the verified Funtoolio identity to an account in this app and use an essential secure sign-in cookie lasting up to eight hours. We do not copy your Google profile or email here. Sign-out affects Our Vibes only; the central Funtoolio session and other apps stay signed in.

Your private score history stores quiz titles, dates and agreement counts/percentages. It contains no specific answers, other players' names or shared link codes. Active gameplay still needs private answers for new participants to compare; those answers and their temporary account association expire with the session after 30 days. Saved scores survive normal expiry until you clear them. Whole-session deletion and participant removal remove the affected saved comparisons. Clearing history also detaches your account from active sessions, stopping future scores from those sessions. Account history cannot unlock another browser's private answers or management access.

Just for fun

Scores measure agreement on a specific set of questions. They do not assess relationship quality, personality, or scientific compatibility. This is a free self-service tool; routine individual replies or support are not promised.

Visit tracking

On the configured public website, we use Umami Cloud to count visits to the homepage, quiz catalogue and quiz introduction pages, plus quiz starts. Invitation, answer, management and results pages are excluded. We send fixed public page paths and titles, the website hostname and a quiz type for starts. We do not send your nickname, answers, scores, invitation or result codes, query strings, or referrer URLs. Umami receives ordinary request information such as your IP address and browser headers to process traffic; visitor counts are estimates, not identified people. No analytics cookies, replay or heatmaps are used. This website shares an analytics stream with other Funtoolio products.

Do Not Track is respected. You can turn tracking off in this browser; your choice is stored locally for one year. Changes apply to future visits and do not erase previously collected counts.

JavaScript is needed to save a tracking preference. Local development is untracked.

Local development notice

Localhost visit tracking is disabled. No email service, social account connection or billing is enabled. A public launch requires the operator's verified contact, eligibility and privacy terms, actual hosting and backup retention details. Those production details have not been configured in this local build.