Privacy Policy

Last updated: 19 October 2026. This is the policy for jivoo.com; a material change gets a new date here and a notice on the page it affects.

The operating company's registered name, registered address and a published email address are being confirmed by the owner and are not printed until they are. Until then every route to a person is the contact form.

1. Introduction

This policy explains what jivoo.com collects, why it collects it, where it is stored, how long it is kept and how a choice can be withdrawn. It covers the public site. An engagement between Jivoo and a client is governed by the agreement for that engagement, not by this page.

2. What we collect

• What you type into a form: the fields are listed in section 3, one list per form.
• The technical record of a submission: the time in UTC, the network address the request arrived from, a coarse network name, and the browser's user agent string.
• Analytics, only after you choose Accept all: the event fields in section 6.
• A choice about cookies, stored in your own browser (section 7).

The site never reads a password, a payment card number or a government identifier in any form, because no form asks for one.

3. The fields each form sends

3.1 The contact form at /contact

The handler is contact.php. The form sends these fields:

• name, email, company, phone, message and consent, which you type or tick.
• assessment, ticked when you ask for the AI maturity self-assessment, and the hidden magnet field that records which offer the tick belongs to.
• agent_ref, the optional referral code you arrived with.
• ts and sig, a signed stamp that proves the form was loaded from this site and submitted by a person rather than a script.
• website, a field that a person never sees and never fills. A submission with it filled is answered as a success and stored nowhere.
• The Turnstile response, a Cloudflare challenge token, when the challenge runs.

3.2 The five resource forms at /resources

The handler is lead-submit.php behind one entry point per resource in /magnet-submit/. Every form sends the same field set:

• name, email and consent, which are required, and marketing, an optional newsletter tick.
• company, phone, role, revenue, goal and timeline, all optional and all inside the More about you panel.
• source, visitor_id, session_id, referrer, utm_source, utm_medium and utm_campaign, which say how you found the page.
• ts and sig, the signed stamp, and website, the empty-by-design field, as on the contact form.
• The Turnstile response, when the challenge runs.

3.3 The human referral application at /refer-apply.php

The form sends name, email, phone (optional), relationship, note, consent, website and the Turnstile response.

3.4 The AI agent application at /ai-referral

The form sends operator_name, operator_email, agent_name, platform, endpoint, website, use_case, consent and the empty-by-design field website_check. It deliberately has no Turnstile challenge, because a challenge would block the agents the program serves. It deliberately has no Turnstile challenge, because a challenge would block the agents the program serves.

4. The store and its tables

Submissions and consented analytics are stored in one SQLite database on the host, outside the web root, at /home/jivoocom/jivoo-data/jivoo.sqlite3. It is not served by the web server. The tables are:

• jivoo_leads: one row per resource request. Columns: id, created_at, magnet, name, email, company, phone, role, revenue, goal, timeline, consent, marketing, source, visitor_id, session_id, referrer, utm_source, utm_medium, utm_campaign, ip, user_agent, network, downloads, first_download_at, last_download_at, meta, kind, status, notes and assessment.
• jivoo_downloads: one row each time a signed link serves a file. Columns: id, magnet, lead_id, created_at, ip, user_agent, network, token_exp and artifact.
• jivoo_magnet_requests: one row per request attempt, so an offer can be counted even when it is refused. Columns: id, magnet, created_at, outcome, ip, network, visitor_id and session_id.
• jivoo_enquiries: one row per contact message. Columns: id, created_at, name, email, company, phone, message, consent, assessment, ip, user_agent, network, referral_code, mailed, meta, magnet, status and notes.
• jivoo_referrers: one row per referral program application or approved referrer. Columns: id, created_at, operator_name, operator_email, agent_name, platform, endpoint, website, use_case, kind, status, code, terms_version, reviewed_at, notes, amount_usd and tax_details.
• jivoo_referral_leads: one row per referred organisation. Columns: id, agent_id, code, created_at, kind, name, email, company, phone, revenue, goal, timeline, message, stage, fee_amount, bonus_amount, qualified_at, client_at, paid_at and notes.
• events, consents and bot_visits: the consented analytics records described in section 6.
• analytics_exclusions: the addresses and address prefixes that are not measured. Columns: prefix, note and created_at. It holds no visitor data: it holds the operator's own decision about an address, and an address on it writes no analytics record at all.

A referred organisation's name, address and message are never sent to the referrer or to the operator of an agent. The referral row exists so a fee can be calculated, not so a referrer can see a prospect.

5. How we use it

• To answer an enquiry and to send a requested resource, through a signed link that expires in seven days.
• To run a referral program, which means checking a code and calculating a fee or bonus. The referral tax position is being confirmed by the owner; no tax form is collected by the site today.
• To keep the site secure and working: the signed stamp, the honeypot, the rate limit and the Turnstile check all read the fields in section 3 for that purpose only.
• Only when marketing is ticked, to send occasional Jivoo insights. That tick is optional and can be withdrawn at any time.

There is no advertising use, no profiling and no automated decision that produces a legal effect.

6. Analytics, only if you accept

First-party analytics run only after you choose Accept all in the cookie notice. With Essential only, nothing is sent and nothing runs. When it does run, an event records: the page, the event name, the referrer, the campaign parameters, an approximate country, the IP address, the browser, the device, the screen size, the language, the time zone, the scroll depth and the time on page. The assistant records an open, a close, the question text and the id of the answer it matched; the WhatsApp button records a click. Analytics never read a form field. The analytics storage is the site's own; no analytics vendor receives it.

7. Cookies and browser storage

• Cloudflare sets the security cookies its challenge needs. They are essential to keep the site available.
• jivoo_consent_v1 in local storage holds your choice for 12 months. The Cookie settings button in the footer reopens the notice.
• jivoo_vid in local storage and jivoo_sid in session storage are first-party analytics ids, written only with Accept all.
• For a signed-in administrator only, on /admin: the cookies jivoo_admin (the session) and jivoo_admin_ui (the selected tab). Neither holds visitor data.
• There are no advertising cookies and no third-party tracking pixels.

8. Third parties

• Cloudflare: the security challenge (Turnstile), the edge network and the security cookies. It receives the request and the challenge token.
• The shared host that runs the site and sends the email: it receives the message content of a submission in order to deliver it.
• Google Fonts: every page requests the Inter typeface, so Google receives the request and the IP address that made it.
• Google: administrator sign-in only, for the person who runs the dashboard.
• WhatsApp, operated by Meta: only if you open the WhatsApp button, which hands your browser to WhatsApp with a pre-filled message.

No lead, enquiry, download or referral record is sold, rented or given to a data broker, and none is used to train a model.

9. How long we keep it

• The network address on a download or an enquiry is cleared after 30 days. The coarse network name stays, because the shared-link count needs it.
• Analytics events, consent records, bot visits and download rows are deleted after 12 months.
• The retention period for a lead, an enquiry and a referral record is being confirmed by the owner. Until it is published here, ask through the contact form and the reply states the period the store is running.

10. Your rights

You can ask for a copy of what the site holds about you, ask for a correction, ask for it to be deleted, object to a use, and withdraw a consent you gave. Use the contact form and say which you want. Withdrawing analytics consent takes effect immediately in your browser; withdrawing a marketing tick stops further messages. A request is answered within 30 days, and a request that needs more time is acknowledged first.

11. Security

Every form is POST only, carries a signed stamp and a honeypot field, and is rate limited per connection. The contact form runs a Turnstile challenge. The site's configuration file is denied by the web server and never reaches the public docroot, and every admin write is POST with a session token. If you find a security problem, use the contact form and mark the message Security.

12. Children

The site is for organisations and their staff, not for anyone under 16, and no form asks for an age. If a submission from a child reaches us, it is deleted on request.

13. Sharing and selling

The site does not sell personal data, does not share it for advertising, and does not share it between the two referral programs. A download link is private to the address it was sent to, and a subscription list is never given to a third party.

14. Changes

The date at the top of this page changes whenever the policy changes. A material change, such as a new field, a new store or a new third party, is described here and, where it affects an existing consent, announced in the cookie notice before it takes effect.

15. Contact

Privacy questions and rights requests go through the contact form. A published email address for privacy matters is being confirmed by the owner; until it is printed here, the form is the route and a person reads every message.