What pages on Convika send

Last updated: November 2, 2026

When you open a page published on Convika, on its own domain or not, your browser sends the information below to the recipients named here. If a page's link brought you to this list, that page is published on Convika. Fluxenic Inc. (株式会社Fluxenic) runs Convika and publishes this list under Article 27-12 of Japan's Telecommunications Business Act.

このページを日本語で読む

1. Visits (every published page)

What is sent: The URL of the page you opened. Only the part before the "?" and the campaign values below are stored. For older records, see How long it's kept.
Where you came from: the referring URL and any campaign values on the link (UTM). From another page of the same site, only the part of its URL before the "?" is stored.
Your browser and device type (User-Agent)
How far you scrolled
How long you stayed, and whether you left right away
For each part of the page: its ID and position, how much of it was on screen and for how long, and whether it was clicked
How fast the page displayed
Whether you started filling in a form (never what you typed)
The links and buttons you clicked (see 2)
The page's ID and version
The day the page was served
Your IP address, and the country Cloudflare estimates from it
If you allowed analytics cookies in the banner: the visitor ID and session ID stored in your browser
Your IP address isn't stored in these records. It's used to work out the ID that counts that day's visitors.
Who handles it: Fluxenic Inc. Cloudflare, Inc. runs the servers that receive it.
Why: To show the page's owner how many people visited and how they read the page
To count page views against the page's plan, which decides when a page stops and what overage is billed
To improve Convika and decide what to build
To decide what Convika's emails to page owners say, and who gets them
To leave bots out of the counts
To choose pages for the gallery on convika.com

2. Clicks (every published page)

What is sent: The words on the link or button you clicked
Where the link goes
Whether it was a link or a button
The path of the page you were on
The referring URL and any campaign values on the link, stored as in 1
The page's ID and version
The day the page was served
When you clicked
Your browser and device type, country, and visitor ID are recorded with each click, as in 1.
Who handles it: Same as 1.
Why: Same as 1.

3. Form entries (pages with a form)

What is sent: What you entered
The form's ID
The value of a hidden field that catches spam
The path of the page
The page's ID and version
The referring URL and any campaign values on the link, stored as in 1
Your IP address, browser and device type (User-Agent), and country
The day the page was served
Apart from what you entered, the fact that you sent an entry is recorded with the same visitor ID as in 1. The form submission's row in Cloudflare Workers Analytics Engine also holds that entry's ID and a site visitor ID computed the same way as the load signal's (4). If you chose Decline analytics cookies on the page's cookie banner, the row holds no site visitor ID: your entry isn't linked to a visit, and its source shows as unknown. An entry from a visitor who hasn't chosen yet is linked. An entry's ID doesn't contain what the entry says. After an entry is deleted, its ID stays in that row. Rows are deleted 3 months after they're written, so it stays for 3 months at most.
Who handles it: Fluxenic Inc., on the same servers as 1. What you entered goes to the recipients the page's owner set.
Why: To deliver what you entered to those recipients
To stop spam and leave bots out of the counts. The IP address and User-Agent stored with the entry are deleted after 90 days, and the record of the request after 7 days.
To show the page's owner where the people who sent it came from
Matched against that day's signals, to let the page's workspace see on the dashboard's overview where the person who answered came from and the first page they opened that day

4. Page load signal (all published pages)

What is sent: The page ID
The path
The URL of the page open before this one (document.referrer)
The utm_source and utm_medium parameters
The day the page was served
Your IP address and User-Agent, which the request carries. They're used to work out the site visitor ID and to leave out bots, and the row holds neither.
When a published page is showing in a browser, its script sends one small request to /_visit on the host name that served the page, once per load. It sets no cookie and stores nothing in the browser, and it is sent whatever you chose in the cookie banner. Convika writes one row to Cloudflare Workers Analytics Engine, which keeps it for 3 months, with the host name of the page's canonical URL (the site it counts under), the host name that served the page, the page ID, the path, a name for where the visit came from, the workspace ID, the time, and a site visitor ID. That name is the referring site's host name or the utm_source value, or else email, direct, or a page on the same site; the URL of the page open before isn't recorded. Whatever you chose in the cookie banner, the site visitor ID is computed without a cookie, from the site's host name, the IP address, and the User-Agent, with a daily key. The same person gets a different ID on each site and on each day, and the same ID ties together every page of one site they open that day. The row holds neither the IP address nor the User-Agent. Nothing is recorded from a browser the page's creator opened the page in from the dashboard (one that has __Host-cvk_owner), from known bots, or from a browser that says a script is driving it.
Who handles it: Fluxenic Inc., on servers run by Cloudflare, Inc.
Why: So the page's workspace can see on the dashboard's overview how many people came to the site (a host name, such as www.example.com). These rows aren't page views, and no plan limit or charge reads them.

5. The check that a person is using order screens and seller information requests

What is sent: Your IP address
Details of your browser's connection (its TLS fingerprint)
Your browser and device type (User-Agent)
The page's domain and the ID of this check (site key)
Who handles it: Cloudflare, Inc. (Cloudflare Turnstile)
Why: To stop prank orders and requests
Cloudflare also uses this to make the check more accurate

6. Fonts, design, and formulas (pages made with Convika's AI or templates, and pages with formulas)

What is sent: Your IP address
Your browser and device type (User-Agent)
The page's URL, up to its domain
Who handles it: Google LLC (Google Fonts), Tailwind Labs Inc. (Tailwind CSS), and, on pages with formulas, Cloudflare, Inc. (cdnjs)
Why: To display the page's fonts, design, and formulas

7. Connection failure reports (pages on convika.page and convika.com; pages on their own domains may send them too)

What is sent: The URL of the page when the connection failed, and the referring URL
The stage and type of the failure, the status code, and the time it took
The request's method and protocol, and the IP address of the server it went to
Your IP address
Who handles it: Cloudflare, Inc.
Why: To find connection failures

8. The dashboard and convika.com

What is sent: The path of the page you opened
The referring site (not the path) and any campaign values on the link
Your device type (worked out from the User-Agent)
Your IP address, and the country Cloudflare estimates from it
If you accepted cookies: the visitor ID stored in your browser
On the sign-up and log-in screens: that a button was pressed, and any errors
On convika.com: that a sign-up or log-in link, the upload box, or a similar button was used, with the page's path; and that the language bar was shown or clicked (no visitor ID)
What you do in the dashboard once logged in (section 1 of the Privacy Policy lists it)
View counts don't store your IP address or User-Agent. Reports from the sign-up and log-in screens go whatever you chose for cookies, with no visitor ID, and are kept with the request's IP address and User-Agent for 7 days.
Who handles it: Fluxenic Inc. Cloudflare, Inc. runs the servers that receive it.
Why: To learn where people come from and which pages they reach, and improve Convika
To find out why signing up or logging in fails

If you decline cookies in the banner

Your browser just doesn't store a visitor ID. Everything in this list is still sent, and visitors are counted with a value that changes every day. No setting stops the sending on published pages. On convika.com and the dashboard, the view counts and the sign-up and log-in reports in 8 aren't sent when your browser's Do Not Track setting is on.

How long it's kept

Records from 1 and 2 are kept at Cloudflare and Tinybird and deleted after 400 days at most. Daily totals with no visitor ID stay for long-term charts. How long what you entered in a form (3) stays is up to the page's owner. The load signal's rows (4), and the entry ID and site visitor ID in a form's row (3), are kept in Cloudflare Workers Analytics Engine for 3 months. Records up to November 2, 2026 can still hold the part of a URL after the "?": the URL of the page you opened, on records of scrolling, time on page, and the like; and the referring URL when you moved from another page of the same site, on page views, clicks, and form entries. Those records are deleted after 400 days at most too, but a referring URL that went into the daily totals stays.

What a page's owner adds

Analytics or ad tags, and images, videos, fonts, or scripts from other sites, that a page's owner adds themselves aren't in this list.

Also sent so a page works

Your choice in the cookie banner goes to Convika's servers. On a page that uses Convika's storage feature, so does what the page's script saves. If you report a page, what you write, the page's path, and your IP address go to Convika.

To find out more

The Privacy Policy lists everything collected, who processes it, and where it's kept. The Cookie Policy covers cookies.

Questions: tomoya.fujita@fluxenic.com