Show your visitors a consent banner where accepting and rejecting are equally easy, choices are made per category, and a decision can be changed later. Every decision goes into a tamper-evident record. Install with a one-line snippet — no code required.
Consentivo is currently under development. Public sign-up isn't open yet.
Do you accept cookies?
We use cookies to improve your experience.
1
line of code to install
4
consent categories
$0
during the controlled beta
TR · EN
dashboard languages
Live preview
Change the layout, position and color — the preview updates instantly. This is a design preview: there is no screen yet for saving these settings, so a live banner runs on the defaults.
Do you accept cookies?
We use cookies to improve your experience, analyze traffic and personalize content.
Layout
Position
Accent color
Title
From the banner to category choices, from withdrawing consent to a tamper-evident record.
"Accept all" and "Reject all" sit side by side at the same size, always visible. The reject option cannot be configured away.
Necessary, analytics, marketing and functional are chosen separately. Optional categories start unticked — nothing is pre-consented.
A persistent "Cookie settings" control stays on the page, so a visitor can reopen their preferences, change them, or withdraw consent.
Every decision is stored with a timestamp, region, a pseudonymous id and an integrity signature. Records are append-only at the database level.
You add a single <script> tag to your site's <head>. No build step, no package to install, no code changes.
Mark a <script> with a category and it will not run until that category is allowed. You do the marking — this is not automatic, universal blocking.
Install, mark, let visitors choose, and it is recorded.
Paste the one-line snippet into your site's <head>. The banner is live for your visitors from that moment.
Add a category marker to the <script> tags you want held back. They will not run until that category is allowed.
Accept, reject, or choose per category. The decision can be changed later from the "Cookie settings" control.
Every decision is written to an append-only ledger with a timestamp, region, pseudonymous id and integrity signature.
What GDPR, KVKK and CCPA expect from a consent banner — and which part of that Consentivo covers.
GDPR
European Union & UK
GDPR requires clear, freely-given opt-in consent before any non-essential cookie loads, and requires withdrawing consent to be as easy as giving it. Consentivo makes rejecting as easy as accepting, lets a decision be reversed later, and holds back the scripts you have marked until the category is allowed.
KVKK
Türkiye
KVKK requires informing the visitor and obtaining explicit consent for non-essential cookies. You write the banner copy in your own disclosure language; Consentivo runs the explicit opt-in flow and records the decision that was made.
CCPA
California (US)
CCPA/CPRA gives visitors the right to opt out of the sale/sharing of personal data. Consentivo reads the browser's Global Privacy Control (GPC) signal and writes it into each consent record, so it appears in your evidence. The banner does not act on the signal automatically — acting on it is yours as the controller.
Consentivo is a compliance tool, not legal advice. Do your own legal review before going live.
For every team that uses cookies and wants to get it right.
Collect consent for analytics and ad pixels without losing conversions.
Sort your third-party trackers into categories and hold each one until consent arrives.
Drop the one-line snippet onto every client site and follow them all from one account.
Collect visitor consent from day one and keep a record that shows what was chosen.
Install
A one-line snippet, no build step, and a plain convention for marking your own scripts.
<!-- Paste into your site's <head> -->
<script
src="https://cdn.consentivo.com/banner.js"
data-site="cs_live_8f3c91d2"
data-region="auto"
defer
></script>
<!-- → Consentivo scans, shows the banner,
and logs every consent for you. -->One snippet, an endpoint that records the consent, and the database the ledger lives in.
banner.js
One-line <script> snippet
Consent Endpoint
Consent recording endpoint
Supabase
Consent ledger & auth
No banner, a generic banner, and Consentivo — side by side.
| No banner | Generic banner | Consentivo | |
|---|---|---|---|
| "Reject all" as easy as accepting | Varies | ||
| Category-level choices | Varies | ||
| Withdraw consent later | Varies | ||
| Hold marked scripts | Varies | ||
| Tamper-evident consent record | Partial | ||
| Setup time | — | Hours | 5 minutes |
We collect no more than recording the consent requires.
We store consents against a pseudonymous id; we keep no IP address, only a country code derived from it — and no user-agent at all. These records may still constitute personal data.
Each consent is written to a timestamped, append-only ledger with an integrity signature.
Every sub-processor we use, and where it is located, is named in the DPA.
The standard data processing agreement forms part of the Terms of Service — no separate signature needed.
Everything is free during the beta.
For small teams and businesses.
For growing businesses.
For agencies & enterprises.
Every plan includes the GDPR, KVKK and CCPA banner.
Can't find an answer? Reach our team.
You paste a one-line <script> snippet into your site's <head> — no coding required. As soon as it loads, the consent banner is live for your visitors.
No. The automatic cookie scanner is switched off for the controlled beta and does not run on any account today. The banner does not need it: you define your categories yourself and mark the relevant <script> tags with a category.
Consentivo does not make you compliant on its own and does not promise to. What it gives you is concrete: explicit opt-in, a reject that is as easy as accepting, category-level control, the ability to withdraw consent later, and a tamper-evident record of what was chosen. Configuring it correctly for your own site and assessing your own legal obligations remains yours — we recommend an independent legal review for your situation.
Records are held on infrastructure operated by Filova — not in a database of your own. Every consent is stored with a timestamp, region, a pseudonymous id and an integrity signature. Records are append-only: they cannot be modified, and no ordinary application path can delete one. We do not store the IP address — only a country code derived from it — and we do not store the browser's user-agent in any form. That does not mean the records are not personal data: pseudonymous consent evidence may still constitute personal data. See our Privacy Policy for retention, deletion and your rights.
Partly. The banner reads layout, position, color and copy settings, and you can try them live in the preview on the home page — but there is no screen yet for saving those settings from the dashboard, so a live banner currently runs on the defaults. Do not count brand customization as an available feature.
Today the product features are the same on Free and Pro. No domain/site limit is enforced during the controlled beta. Pro also cannot be purchased right now — the controlled beta is free and billing is off. Exact post-beta limits and pricing have not been finalized.
Consentivo is in a controlled beta right now: billing is not live, we do not ask for card details, and nothing is charged — so there is no subscription to cancel. The paid plans are a non-binding preview; binding payment, renewal, cancellation and refund terms will be published before billing is enabled, and your acceptance will be asked for before they take effect.
We aim to respond within 24-48 hours, Monday-Friday during business hours (excluding weekends).
There is no one-click migration tool, and we cannot import your historical consent records. Switching means removing the old tool's snippet, adding ours, and carrying your category markers over to your own <script> tags.
One line of script, category-level consent, and a tamper-evident record.