Proof · Website privacy notice
Website privacy notice
Understand what the public website collects when you browse or contact Proof, which services handle it, and where to ask about your information.
Who this notice covers
This notice describes information handled through the public website at reqproof.com. Proof is founded and operated by Leonid Bugaev. Contact [email protected] about this notice or your website enquiry.
It covers browsing and contacting Proof through the website. Customer source code, hosted project access and assurance-engagement records have separate access, confidentiality and data-handling arrangements. See Trust, access and disclosure and the terms agreed for your engagement.
Website implementation reviewed October 3, 2026.
Information you send through the form
The scoping form requires an email address. You may also submit a message, name, company, component, intended timing and whether the code is public or private. Other submitted form fields can be retained as additional enquiry details. We use that information to receive the enquiry, understand the work and reply.
The intake also records the submission time, the form's source label and a country code supplied by the hosting service. Recent submissions using the same email address may be combined into one enquiry. A hidden field helps reject automated spam.
Enquiry records are stored through Cloudflare's infrastructure. Email services deliver notifications and replies, including to the operator's Google-hosted mailbox. Sending a form therefore involves the hosting and email providers; it is not a private transfer confined to this web page. The form does not require private code, credentials or production data, and you should not include them.
Website analytics and session replay
The public site loads Google Analytics and PostHog to understand page use and interactions. PostHog is configured to use its EU endpoint, record page views and page exits, and enable session replay. Its persistence setting uses cookies and local storage. Analytics can associate browsing activity with browser or session identifiers.
Replay is configured to mask form inputs and textareas. This is a configured protection, not a guarantee that every piece of information visible elsewhere on a page, in a URL or in an error is removed. Avoid putting confidential information in URLs or material you expose through public pages.
The current website scripts load analytics without a site-provided consent or preference dialog. Browser settings and content blockers can restrict cookies, storage and analytics requests; their effect depends on the browser and configuration. Deleting browser storage does not itself delete records already held by a provider.
Provider information: Google's use of information from partner sites and PostHog's privacy information. These provider policies do not replace this description of Proof's website configuration.
Hosting and external destinations
Cloudflare serves the website and processes its requests. Visiting the site sends network and browser information needed to deliver those requests, such as the requesting IP address and request headers, through the hosting service. Read Cloudflare's privacy information for its processing practices.
Links to repositories, the blog, downloadable services and the project portal may lead to other sites or services. Their collection and account settings can differ from this public website. An EU analytics endpoint alone does not establish that every website or enquiry record remains in one jurisdiction.
Retention and requests about your information
The website intake does not configure an automatic deletion period for stored enquiry records. Its 24-hour mechanism for combining submissions is not a 24-hour retention limit: the enquiry and associated email can remain afterward. Analytics and mailbox retention also depend on the corresponding account settings.
To ask about retention, access, correction or deletion of information associated with your enquiry, or to stop follow-up, email [email protected]. Include the address used and the approximate date or subject of the enquiry so the relevant records can be identified. We may need further information to locate a record and establish that the request concerns you.
Deletion terms agreed for customer-engagement working data should not be read as the retention policy for website enquiries or analytics. Ask for the applicable details when arranging an engagement.
Ask about this notice
If a data-handling detail matters to your decision to contact or work with Proof, ask before sharing sensitive information. The contact page provides the direct enquiry route. This notice describes the website's implemented collection paths; it does not assert a certification or a legal-compliance result.