Privacy notice · Rev. 05 — August 2026

How we handle your inquiry

This notice explains, in plain terms, what Reativei receives when you submit the contact form, why, and how to ask us to delete it.

What the contact form collects

When you submit the "Show us the manual step" form, we receive the information you enter:

The Quick Fix page has its own version of the same form. It collects your name, email address and company, a description of what your team does manually today, and — optionally — the systems or tools involved and how often the workflow happens. It also marks the inquiry as a Quick Fix inquiry so it can be handled accordingly.

Alongside these, the form automatically includes a small amount of technical context: UTM parameters (utm_source,utm_medium,utm_campaign,utm_content) when present in the link that brought you here, the first page of the site you landed on, the page where you submitted the form, the referring page when your browser provides it, and, when you view a demo during the session, which one — the public interactive example, or a personalized demo page identified by an opaque tracking id rather than a company name. While you browse, this UTM, landing and demo context is kept in your browser's session storage, which lasts only for the current browsing session. If you submit the contact form, the relevant attribution fields are included with your inquiry, so the inquiry we receive — and keep in order to respond to you — may retain that context after your browsing session ends. A hidden field labelled "phone" is a spam honeypot: humans never see it, and a legitimate submission leaves it empty. Before the form sends, it also runs a Cloudflare Turnstile security check to help confirm the submission comes from a person rather than an automated bot.

Why this information is collected

It is collected solely to understand your inquiry and respond to it — specifically, to assess whether the workflow you describe is a good candidate for a small software build, and to reply to you.

How the information is used

The information is used only to respond to your inquiry (a transactional message). It is not used for cold outbound prospecting or automated marketing.

Analytics

We use Cloudflare Web Analytics to understand aggregate, non-identifying traffic — page views and visits — without cookies.

Separately, the site records a small number of first-party, non-identifying events to measure how visitors move through the site: when the public interactive example is viewed, started, completed or skipped, when its call-to-action is clicked, when a personalized demo page is viewed, when its call-to-action is clicked, when certain links on the homepage are clicked, and when the contact form is started and successfully submitted. Each event logs only campaign attribution — UTM values, the first page you landed on, and, when you viewed a demo, an opaque identifier (never a company name) — plus a timestamp. Where a call-to-action is involved, the event also records a fixed, non-personal location label — which section the click came from (for example the header, the hero, pricing, the contact section, the public example, or a personalized demo) — so we can tell where a lead's conversion started, without logging the text of the button you clicked. These logs never include your name, email, company, website, workflow description, IP address, full page URL, or the referring page. They exist solely to measure which outreach campaigns lead to conversations.

Infrastructure and providers

Requesting deletion or contacting us

To request deletion of a submission, or with any privacy question, emailvinicius@reativei.com.

Operator

Reativei is operated by Vinicius Bernardini Goncales Consultoria em Tecnologia da Informação Ltda.

Rua Pais Leme 215, Conj. 1713, Pinheiros, São Paulo, SP, 05424-150, Brazil

Compliance

This notice describes Reativei's current data-handling practices. It is not a certification or a legal compliance statement.