Legal

Privacy Policy

Last updated: August 12, 2026

Rincer is operated by Showr LLC (“Rincer,” “we,” “us,” or “our”). This Privacy Policy explains how we collect, use, store, and protect information when you use the Rincer research and survey website.

Rincer is in development. Today this website exists mainly to run consumer research: a short survey plus an optional early-access email signup.

Showr LLC is the entity that determines how and why information collected through this website is handled, and is the controller of that information. You can reach us about any privacy matter at admin@rincer.io.

Survey Information

We collect the answers you voluntarily submit through the Rincer consumer survey. The survey does not ask for your name, address, or payment information.

We use survey responses for:

  • product research
  • understanding consumer needs
  • aggregate market analysis
  • improving Rincer

Early Access Email

After completing the survey you may optionally provide an email address to join the early-access list. Providing an email is completely optional and is not required to complete the survey. You are only added to the list after you intentionally submit your email.

We are not sending email at this time. Rincer currently stores early-access addresses only. We have not built an email sending system, and no marketing, launch, or newsletter email has been sent to any address collected through this site.

If we begin sending early-access or promotional email in the future, those messages will identify us, will include a working unsubscribe mechanism, and will comply with applicable email law. Until then, if you want your address removed, email admin@rincer.io and we will delete it — see “Your Choices and Requests” below.

Cookies and Pseudonymous Identifiers

To operate the survey we use limited first-party pseudonymous identifiers and technical signals. A pseudonymous identifier does not directly reveal your real-world identity, but it may be used to recognize repeat participation in the survey. Because these identifiers may still be considered personal information under applicable privacy laws, we do not describe them as anonymous.

We may use:

  • a first-party cookie or browser identifier
  • a randomly generated session or respondent ID
  • a privacy-preserving hash derived from technical information such as an IP address
  • device and browser information
  • approximate geographic information derived from an IP address

These are used to:

  • detect duplicate survey submissions
  • prevent automated or fraudulent responses
  • maintain survey integrity
  • measure aggregate survey and site usage
  • diagnose security or technical issues

These pseudonymous identifiers are used by Rincer for operation of the survey, survey integrity, and duplicate-response detection. They are not used for cross-site advertising or behavioral advertising, and they are not used to build advertising profiles or track you across unrelated websites. This site does not run third-party advertising pixels or third-party tracking SDKs.

IP Addresses and Approximate Location

We may temporarily process the IP address associated with your request for security, fraud prevention, duplicate-response detection, and approximate geographic validation.

Where we convert an IP address into a one-way hash using a private server-side key, that transformation is intended to reduce direct identifiability and the raw address is not stored, is not sent to the browser, and is never displayed in the Rincer admin dashboard. A hashed IP address is treated as a pseudonymous identifier, not as anonymous information. A matching hash on its own is never treated as proof that two responses come from the same person, and we do not reject a response solely because more than one respondent shares a network. IP-derived information is used only for survey integrity, security, duplicate detection, and approximate location — never for advertising or profiling.

Any location information derived from network information is approximate and limited to coarse signals such as country, state/region, and city.

Rincer does not request or collect precise GPS location through this survey website.

We do not use invasive browser fingerprinting techniques, and we do not use these signals for third-party advertising.

Technical Information

When you visit the site, we may automatically receive limited technical information associated with the request, such as:

  • device category (for example mobile, tablet, desktop)
  • browser type and operating-system family
  • the referring page or referring website that sent you to Rincer, where your browser provides it
  • UTM campaign parameters (such as source, medium, campaign, content, and term) when they are present in the URL you arrive on
  • approximate network location

We use referrer and UTM information to understand how respondents reached the survey, measure the effectiveness of our own outreach, and analyze aggregate survey traffic.

This attribution information is not used for third-party behavioral advertising and is not used to build cross-site advertising profiles.

How We Use Information

  • survey research
  • product development
  • survey integrity
  • duplicate detection
  • aggregate analytics
  • acquisition and source analysis
  • communication with users who voluntarily join early access

Data Sharing

Rincer does not sell personal information. We do not use survey information for third-party behavioral advertising, and we do not allow advertising companies to use this survey to track respondents across unrelated websites.

We may disclose information where required by law.

Service Providers

We currently use service providers for these functions:

  • website hosting and content delivery
  • database infrastructure and account authentication
  • bot and abuse protection
  • application deployment and error reporting

These providers may process information only as needed to provide services to Rincer, subject to applicable contractual or legal protections.

We do not currently use an email delivery provider, an analytics provider, or an advertising provider. If that changes, we will update this policy before the change takes effect.

Data Retention

We want to be precise here rather than vague. Rincer is a research project, and the research value of a response does not expire on a schedule, so most information is retained for as long as it remains useful for the purpose it was collected for, rather than being deleted automatically after a fixed period.

  • Survey responses — retained for as long as reasonably necessary to analyze research results, validate findings, and support the development of Rincer. There is no automatic deletion schedule.
  • Survey-integrity identifiers — respondent IDs and the hashed network value are stored alongside the response they relate to, and are retained for as long as that response is retained. They are not deleted on a separate schedule.
  • Approximate location — the country, region, and city values derived from network information are stored with the response and retained for as long as that response is retained.
  • Abuse-prevention counters — the short-lived counters used for rate limiting are deleted automatically after approximately seven days.
  • Early-access email addresses — retained until you ask us to remove your address, or until we no longer have a reason to keep it.
  • Administrative records — records of administrative access to respondent data are retained so we can review who accessed what, which is part of protecting your information.
  • Technical and security logs — held by our hosting and database providers under their retention settings rather than ours.

Browser storage — the cookie and local values described above — stays on your device until it expires or you clear it. You can delete it at any time through your browser.

Information may also be retained longer where required by law, to resolve disputes, or to enforce agreements. If we later adopt a fixed deletion schedule, we will update this section to describe it.

Minors’ Privacy

Rincer and this survey are intended for a general adult audience and are not directed to children. The survey does not ask for your age or date of birth, and we do not knowingly seek to collect personal information from minors.

If we become aware that a respondent is under 13 — for example because they say so in a written answer — we delete that response and any email address submitted with it, and we record that the deletion happened without keeping a copy of what was written. Parents or guardians who believe a minor has provided information can contact admin@rincer.io and we will review and delete the information.

Security

We use reasonable technical and organizational safeguards to protect the information we collect. Survey responses and early-access emails are stored in access-controlled databases readable only by authorized Rincer administrators, enforced by database-level access rules rather than by the website alone. Our service providers can also access the systems they operate for us, as described above.

Administrative access to respondent data is recorded — including when responses or email addresses are exported or deleted — so that we can review who accessed what. Those records identify the administrator and the action, not the contents of your response.

No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

Your Choices and Requests

For privacy questions or requests, including access, correction, or deletion, contact admin@rincer.io. We will respond where we can reasonably verify the requester and identify the relevant information.

If you gave us an email address, we can find it and delete it, along with the survey response it was submitted with. That is the most reliable way for us to act on a request.

If you completed the survey without giving an email address, your response is stored with pseudonymous identifiers and no name or contact information. In that case there is usually no reliable way for us to determine which response is yours, so we may not be able to locate or delete a specific response. We would rather say this plainly than imply a capability we do not have.

You can clear the cookie and browser storage described above at any time using your browser settings.