The public site should explain data handling simply, without pretending to be a product policy for flows that do not exist here.

This notice applies to the public Cursivo marketing site and related public content pages such as the product page, blog, changelog, and legal routes.

It does not describe private product workspaces, customer operations data, or future account flows that are not available on this site today.

The site itself is primarily static. Cursivo may receive information only when a visitor sends an email, follows a direct contact link, or shares information voluntarily in a conversation.

That information may include a name, company, email address, and the contents of the message needed to continue the discussion.

Contact details and message content are used to reply to inbound questions, discuss pilots or partnerships, and understand whether the product is relevant for the team making the request.

Cursivo does not position this public site as a consumer advertising surface, and the intention is to keep outreach direct rather than turn messages into broad mailing activity.

Like most public sites, the hosting provider or delivery layer may process basic technical request data such as IP address, browser details, and log timestamps in order to serve pages and maintain reliability.

If lightweight analytics is enabled later for this public site, it should remain privacy-conscious, limited to aggregate page-level measurement, and should not introduce invasive tracking as a condition of using the site.

When visitors use external destinations such as email clients or public repository links, those services operate under their own terms and privacy practices.

Direct contact records are kept only as long as they are useful for the conversation, relationship, or reasonable business follow-up around the request.

This notice should be updated whenever the marketing surface changes materially, especially if forms, analytics, user accounts, or customer data workflows are added later.