Privacy notice for site visits and inquiries.

This notice explains how Relpop processes public-site analytics and information submitted through the contact form, including purpose, service providers, retention, and your rights.

Applies to visits to relpop.com and inquiries submitted through the site. Last updated July 12, 2026.

Who handles the inquiry
Relpop handles the submitted inquiry. For privacy questions or requests, email .
Fields collected
  • Name and email.
  • Target Company B type and specific scenario.
  • Optional organization, known context, and expected output when you choose to provide them.
  • Technical anti-abuse and request metadata needed to secure and operate the form.
Purpose
Relpop uses the information to assess, reply to, and manage a potential collaboration. It is not used to build advertising profiles and is not sold.
Storage and notification
The inquiry record is stored in Cloudflare D1. Resend is used to deliver an operational notification to Relpop so the inquiry can be reviewed; Resend is not the system of record.
Cloudflare Web Analytics

Relpop uses Cloudflare Web Analytics to understand page views and page performance and to improve the public site. Typical reporting can include visited pages, performance measures, browser, operating system, and device type, plus a coarse geographic area. Cloudflare processes this analytics data as the analytics service provider.

This setup does not add a Relpop-managed analytics cookie and Relpop does not use it to create cross-site advertising profiles. This is a boundary of Relpop's implementation, not a claim that every analytics record is absolutely anonymous.

Under the documented dashboard baseline, the most recent 7 days retain unsampled beacon data; older data is retained in aggregated form at approximately 10%, and the longest accessible window is 6 months. Dashboard and GraphQL results may also be adaptively sampled according to query size, so analytics is not treated as an event-level audit log.

For questions or an analytics-related request, email . You can also use browser or content-blocking settings to limit analytics requests. Core content remains readable, although blocking scripts may affect Cloudflare verification or the inquiry form.

Retention
The retention threshold for inquiry records in Cloudflare D1 is 365 days. Cleanup is triggered when a new inquiry is successfully accepted and can also be run by operations staff. Records that reach the threshold are deleted during the next cleanup, so physical deletion may occur after day 365. A valid request can lead to earlier deletion, subject to security, dispute, or legal exceptions.
Your rights
You may ask to access, correct, or delete your inquiry by emailing from the address used to submit it. Relpop may ask for enough information to verify the request.
Do not submit sensitive information
Do not submit business secrets, identity documents, financial account details, passwords, health information, or other sensitive personal or company data through the public form. Arrange an appropriate private channel before sharing restricted material.

Send only what is needed for an initial fit review.

The required fields are designed to describe the question without requesting documents or confidential operating data.

Open contact form