BEVIZIO

Privacy Policy

Last updated: November 4, 2026

This policy explains what personal data Bevizio (“we”, “us”) collects through bevizio.com and the Bevizio application, why, and the choices you have about it. Bevizio is run by Daniel Kloss, a sole trader trading as Bevizio, 61 Bridge Street, Kington, HR5 3DJ, United Kingdom. He is the data controller and can be reached at hello@bevizio.com.

1. What we collect

  • Sign-in data: your name (or your Google profile name and photo if you use “Continue with Google”), your email address, and a securely hashed password if you set one. Each time you sign in, our sign-in service records the date, your IP address and your browser type, so we can keep your account secure.
  • Account data: the product name and website you track, other spellings of your product name, the questions you enter or that we write for you, the competitors you choose to track, and dated notes (written by you or, if you allow it, by an assistant). For a local business account: the business name, the services you offer, the towns you serve and your country, and, only if you give them, your website, phone number and address (we use these to tell your business apart from another with a similar name). They stay until you delete the account.
  • Your settings: which recap emails you want and how often, and your answer to the product-news question — with the exact wording we showed you and when you answered.
  • Assistant connection (optional): you can let an AI assistant read your Bevizio results in two ways. For each we keep only what is needed to run and secure the connection.
    • Signing in from your assistant (you press Allow on a Bevizio page). We keep the name the assistant gives itself; its identifier (for most assistants, the web address where it publishes its details); the address it sends you back to; which product and which login it is connected to; what it may do (read your results and, only if you allow it in Settings, make the changes you chose); and when it was connected, last used, when its access ends and, if you disconnect it, when. Its access passes are stored only in a scrambled form that cannot be turned back into them.
    • While you decide. When your assistant starts a connection, we keep a short record of the request: which assistant, where it will send you back, a value the assistant chose, and a scrambled copy of a value held in a cookie in your browser, so the request can only be completed in the browser that started it. It does not say who you are, and it works for ten minutes.
    • After you press Allow. Your assistant receives a one-time code and must exchange it within 60 seconds. We keep the code only in scrambled form, with the product and login it is for.
    • What assistants publish about themselves. We keep a copy of an assistant’s published name and the addresses it sends people back to, so we do not fetch them on every sign-in. These describe the assistant, not you.
    • A connection key (created in Settings). We keep the name you gave it, its first few characters (so you can tell your keys apart), and when it was created, last used, due to expire and, if you revoke it, revoked. We store only a scrambled version of the key, never the key itself.
    • Either way. Each time your assistant asks for your results we record which tool it used, whether it worked, how long it took, and which connection or key and product it was for. We also count how often each connection, key and product connects, so we can enforce limits. We do not record what you asked your assistant or what it received back, except the changes it makes for you, which we keep in the record of changes described below. Our sign-in pages also count requests from each internet address to stop floods; for that we keep only a scrambled form of the address, never the address itself. Our hosting provider handles addresses as it does for every visit to our site.
    • Changes through an assistant (optional, off unless you turn it on). If you let an assistant make changes, we keep a record of the permission: which connection, what you allowed, when, until when (30 days) and, if you took it away, when. For each connection we keep only the current or last permission, and why it ended. We also keep a record of every change that goes through: when, which assistant (its name and identifier), your login, the connection and request it came from, the permission level, and what changed, including the text of a question, competitor, alternative spelling, area, service or note before and after and, for a note, a page of your own site if one was given. You can see your latest 20 changes in Settings, and ask for a copy of the whole record at hello@bevizio.com. We use the record to show you what was changed, so the assistant can undo a change for 7 days, to keep your account secure, to enforce limits and to answer a question about what happened. The changes themselves are part of your account data like any you add yourself. Any assistant you have allowed to make changes can read this record, including changes made by your other assistants, so that text goes to its provider. Every assistant you have connected can read your notes and see which questions an assistant added. We keep the record of changes for 90 days, a deleted note for 30 days after it was deleted, and the record of a permission for 30 days after it ends. A deleted note disappears at once and its text is also removed from the record of changes. You can ask us to delete your record of changes earlier at hello@bevizio.com; we reply within one month, and if a request is complex we tell you within that month that we need up to two more, and why. Deleting the record early also ends the undo. When your account is permanently erased, the record and the permissions are erased too. This record sits in our database in the US like the rest of your account data.
  • Research tools and usage (optional). If your plan includes the Bevizio Agent’s research tools, your assistant can ask Bevizio to look up search data (for example keyword ideas, who ranks for a phrase, or a site’s search overview). The phrase, web address or site it asks about is sent to our data provider DataForSEO to get the answer; we do not store it. For each call we record only the tool, the time, which connection made it, and what it cost, so we can enforce your monthly allowance and daily limits.
  • Google Search Console data (optional). If you connect Search Console, we read your site’s search numbers (pages, clicks, impressions and average position) through Google’s read-only permission; we cannot change anything in your Search Console. We keep the site you chose, the permission level Google gave your account, the connection’s status and times, and Google’s long-lived key that lets us keep reading (stored encrypted). We keep weekly counts per page while you stay connected, for up to 16 months, to show you trends and to compare periods around your changes. We use the data only for these features. We do not sell it, use it for advertising, or combine it with other customers’ data. By default no assistant sees any of it: in Settings you can tick “Show these numbers in my AI assistant” for each assistant company (Anthropic for Claude, OpenAI for ChatGPT, the company behind Cursor). Only then can that assistant read your Search Console numbers, and results calculated from them, when it asks; they go to that company, which handles them under its own terms. Search queries can occasionally contain personal names; if that concerns you, don’t tick a box. We keep your ticks, and you can change them at any time.
  • Site log (optional). A dated record of changes to your own website. You, or an AI assistant you have connected, can add an entry when something on your site changes. For each entry we store the kind of change, the pages it affected (only pages on your own site), a short description and an optional short reason, the day it took effect, when it was recorded, and who wrote it (you, or the name of the assistant). We also store the name of your site and your choice about whether assistants may add entries. The log holds what you or your assistant recorded and, only if you switch on the page watcher described below, changes Bevizio noticed on your pages. Any assistant you connect can read the log when it asks, so the entries go to the company behind that assistant, under its own terms; please don’t put anything personal or confidential in them. An assistant can add entries, or mark its own mistakes as retracted, only while you leave that switched on in Settings; it can never edit or delete an entry and cannot change your site. You can add, retract or delete entries yourself, and delete the whole log in one click. If you have also ticked an assistant’s company for Search Console, your weekly clicks and impressions can appear beside the log when that assistant asks for the timeline.
  • Page watcher (only if you switch it on). If you use the site log, Bevizio can also visit the pages of your own website to notice changes for you, such as a changed title, a page that now returns an error, or a changed robots.txt file. It is off until you turn it on in Settings, and it needs Search Console to be connected. It only visits pages that belong to the site you connected in Search Console. It starts from your home page and your sitemaps, and, only if you have ticked an assistant’s company under Search Console in Settings, also from the page addresses Search Console shows us. It does so politely: it identifies itself as BevizioBot (our page about it is at bevizio.com/bot), reads and follows your robots.txt first, makes one request at a time, and slows down or stops if your site asks it to or blocks it. For each page we store a small set of facts: its address and status, its title and description, its headings, its canonical address, its robots settings, and fingerprints of its main text, structured data and internal links. We do not store the page itself, but the title, description and headings are stored as they appear on your pages, so if your pages name people, those names can be in them. When a later visit confirms a difference, we add an entry to your site log saying what changed and when we first saw it; one-off differences are not logged, and a change that is only to numbers on a page is not noticed. The entries the watcher adds can be read by any assistant you connect, so they go to the company behind that assistant, as with the rest of your log. You can switch the watcher off in Settings and it stops. Deleting your site log deletes what it stored.
  • Your website: when you sign up or try the free check, we read the public text of the site you give us so we can write relevant questions.
  • Local free check: the business name, trade, town and country you type in, and the answers the AI systems give, which name other businesses. Those names are public information taken from search results.
  • Answer results: the answers third-party AI systems (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews and, for local business accounts, Google AI Mode) give when we ask your questions, including the sources and competitor names they mention, and when each answer was collected. You can read the full text of each answer in your dashboard. For local accounts this includes the names, addresses, ratings and review counts of other businesses that the answers show; those are public information from search results.
  • Billing data: handled by our payment provider, Paddle.com, as merchant of record. We never receive or store your card details. Paddle shares limited data with us (such as subscription status, plan and renewal date) to run your account.
  • Usage data: pages visited and basic interaction data via Vercel Web Analytics (cookieless) and, only if you accept analytics cookies, Google Analytics (GA4).
  • Abuse prevention: we use your IP address to stop bots and repeated free checks. We store it only as a one-way scrambled code, which for the free check changes every day.
  • Free check: the product and website you enter and the result. If you ask for a copy by email, we use your address only to send it and don’t keep it. If you also tick the product-news box, we keep your address as a pending request and email you a button to confirm; if you don’t confirm within 14 days we delete it, and if you do, we keep your address and that choice until you unsubscribe.
  • Feedback: if you use “Send feedback” in the app, your message, the type you picked, the page you were on, your email address, product and plan are emailed to us so we can reply. It isn’t stored in the Bevizio database.
  • Waitlist: if you joined our pre-launch waitlist, your email address.
  • Skills waiting list: if you joined the waiting list for a planned weekly SEO service, on bevizio.com or earlier on the old SEOO site (seoo.tools), we hold your email address, when and where you joined (the page, the website you came from and your country), what you signed up for (the description shown beside the form), and the exact consent wording you saw, with its version. For the old SEOO site the list was kept at a different provider in Ireland; it now sits, with new sign-ups, on Bevizio’s own database.
  • Free skills download: when you download the free SEO skills we record the date and time, the version, where you came from (a short label such as the referring website), your country as given by our host, and whether the visit looks like a bot. We do not record your IP address or browser details, and you need no email or account to download.

2. How we use it, and on what basis

We use your data to:

  • run the service — ask your questions, store the answers, and work out real changes over time;
  • send service emails: billing and account notices, a security notice when an assistant is connected to your account by signing in, when you allow an assistant to make changes (with a link to switch it back to read only), and when you create an assistant connection key, when one is about to expire, and when you revoke one (these are security messages, so they cannot be switched off while the connection is available to you), alerts when how often you’re named really changes, recaps of your own numbers, tips during your trial, and a short note if you haven’t signed in for two weeks. Some of these depend on how you use Bevizio — for example whether you’ve edited your questions, or when you last signed in;
  • take payment and manage your subscription;
  • run the assistant connection if you switch it on, keep it secure, and enforce its limits;
  • run the Bevizio Agent features if you switch them on: research tools, the Search Console connection and the site log;
  • if you are on the skills waiting list, email you once if the weekly SEO service you signed up for is released. We use that list for nothing else: no Bevizio marketing, no newsletter, no sharing, and it is never merged with any other list;
  • count free skills downloads, so we can show a real total on the skills page;
  • prevent abuse; and
  • understand how the site is used so we can improve it.

The legal bases we rely on:

  • running the service, service emails and billing — our contract with you; the one or two reminder emails about setting up an account you created are part of that, and our legitimate interest in helping you finish;
  • the assistant connection (the connection and key records, access checks, limits, the record of changes and the security notices) — our contract with you, and our interest in keeping accounts secure;
  • the Bevizio Agent features you switch on (research tools and their usage record, the Search Console connection, the site log) — our contract with you; sending your Search Console numbers to an assistant’s company — your consent, given by ticking that company in Settings, which you can withdraw by unticking it;
  • the short-lived records kept to keep it secure (sign-in requests in progress, used one-time codes, scrambled internet addresses used for limits, and the record of each request) — our legitimate interest in keeping Bevizio and your account secure and stopping misuse. These short-lived records hold no questions or answers; the record of changes is separate and does hold the text of what was changed;
  • abuse prevention, cookieless analytics and the download count — our legitimate interests;
  • the skills waiting list — your consent, given with the wording shown beside the sign-up form (on bevizio.com or the old SEOO site), which we keep with your entry;
  • Google Analytics cookies — your consent;
  • product news, tips and “come back” emails after you cancel — your consent, only if you ticked the box at sign-up, on the free check, or turned it on in Settings;
  • keeping billing and consent records — our legal obligations.

You can change or turn off recap emails, and your product-news choice, in Settings. Every product-news email also has a one-click unsubscribe link. Billing and account emails always go out while you have an account.

We don’t make automated decisions about you that have legal or similarly significant effects.

3. Who we share it with

We use a small number of providers to run Bevizio:

  • Paddle.com — our merchant of record. Paddle acts as a separate controller for payment data; see Paddle’s privacy notice.
  • DataForSEO — also answers the research lookups your assistant asks for (see “Research tools and usage” above). It asks your questions on ChatGPT, Claude, Gemini, Perplexity and Google on our behalf (passing them to OpenAI, Anthropic, Google and Perplexity to get the answers), writes the starter questions from your site, and identifies competitor names in the sources those answers cite.
  • Neon — hosts our database, and Neon Auth runs sign-in and sessions.
  • Google — “Continue with Google” sign-in, if you use it, and, if you connect Search Console, the read-only access that lets us read your Search Console numbers. Bevizio’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
  • Have I Been Pwned (a free breach-lookup service) — when you choose a new password, your browser checks it against known data breaches by sending only the first five characters of a scrambled (SHA-1) copy of it. Your password and the rest of that copy never leave your browser.
  • GitLab — holds our code and the weekly encrypted copy of our database that we keep outside Neon in case of disaster.
  • Cloudflare Turnstile — bot checks on sign-up and the free check; it receives your IP address and browser signals.
  • Vercel — hosts the application, provides cookieless analytics, and keeps short-lived server logs of requests.
  • The AI assistant you choose to connect (for example Claude, ChatGPT or Cursor). This is a provider you choose and direct, not one we use. We do not choose, instruct or pay it, and it is not our processor: it handles your results as its own controller or on your behalf, under your agreement with it. It can read your results only after you sign in and press Allow on a Bevizio page, or after you put a connection key into it yourself. It can then read the results stored for your one product: the product name, website and other spellings, your questions and the competitors you track, how often each AI engine named you, which companies and web pages the answers cited, the recent answers in full, read in short pieces (with the full text for the last 12 months; this can include the names of other businesses and, for local businesses, their public addresses and ratings), the searches an engine ran, changes we detected, your local areas and services, your dated notes and, if you allowed changes, the record of changes, and your plan and trial status. It cannot read your email address, your password, your billing details, other customers’ data or the raw data our provider returns. We never send your results to an assistant ourselves: the assistant asks for them. Whatever it reads, whatever you ask it, anything you ask it to change and the text it writes into your account go to that assistant’s provider. That provider’s own privacy terms then apply, and it may process your results outside the UK or EU under your agreement with them, not ours. Disconnecting stops it reading anything new, but it does not recall what it has already read. If you are named in an answer and want it removed, email hello@bevizio.com. You can disconnect any assistant, or revoke any key, in Settings at any time. If you paste a key somewhere it should not be (a chat, an email, a document), revoke it and make a new one.
  • Resend — delivers all our emails, including results, alerts and (if you opted in) product news.
  • Google Analytics (GA4) — site usage analytics, only with your consent.
  • Sentry — tells us when something on the site breaks, so we can fix it. It’s configured to collect only what’s needed to debug an error (data hosted in the EU) — never cookies, passwords, page content, or the contents of any request.

We do not sell your personal data. We only share what each provider needs to do its job.

4. International transfers

Several of these providers are based in, or process data in, the United States, and our database is hosted in the United States (AWS, us-east-1). Where UK or EU personal data leaves those areas, we rely on the UK–US Data Bridge, the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses, as each provider offers.

5. How long we keep it

  • Active, free and cancelled accounts: kept until you delete your account, so your history is there if you come back — every answer, who was named and what was cited. The full text of each answer, and the raw technical data our provider returns with it (which also contains that text), are deleted after 12 months. The first 2,000 characters of each answer, who was named and what was cited stay.
  • Deleted accounts: inaccessible immediately (Settings → Delete my account) and permanently erased after 30 days (once any subscription is cancelled) — your questions, answers, notes, the record of changes and change permissions, connection keys and their records, email preferences and product-news choice. Your sign-in record is removed within 7 days after that. The 30 days are a grace period in case you change your mind. Erased data leaves our backups within 8 days.
  • Assistant connection:
    • An assistant connected by signing in gets access that lasts one hour. If it asks to stay connected, the access renews automatically for up to 30 days without use and 90 days in total, after which you press Allow again. A key works for 90 days. Either stops working for any new request as soon as you disconnect it or revoke it in Settings, or when your subscription ends.
    • The record of each access pass and each key (its name, scrambled version and the times above) is deleted about 30 days after it expired or was cancelled.
    • Permission to make changes lasts 30 days unless you renew it, and its record is deleted 30 days after it ends. The record of changes is deleted after 90 days, and a deleted note 30 days after it was deleted. (This is separate from the access pass, which lasts one hour, and the connection’s own renewal, described above.)
    • Sign-in requests in progress are deleted within two days of expiring. One-time codes are deleted about 30 days after they expire: we keep them that long so that if a code is ever used twice, we recognise it and cancel the connection it made. Our copy of an assistant’s published details is deleted 90 days after anyone last signed in with it.
    • The short record of each request (tool, outcome, connection or key, and product) is kept by our hosting provider only as long as its plan keeps logs, currently up to a day. The provider’s logs also contain the page address and the internet address of each visit.
    • The counters we use for limits, including the scrambled internet addresses, are deleted within about two days of the last request.
    • If you delete your account, every connection and key stops working immediately, and their records are erased with the rest of your data after the 30-day grace period.
  • Bevizio Agent features:
    • Search Console: the weekly counts are kept while you stay connected, for up to 16 months. When you press “Disconnect Search Console” in Settings we delete the numbers, your ticks and the connection record straight away and ask Google to cancel our access. If you delete your account they are erased in the 30-day purge.
    • Site log: kept until you delete it (one click in Settings) or delete your account, when it is erased in the 30-day purge. Disconnecting Search Console does not delete the log.
    • Page watcher: the facts stored about your pages are kept until you delete your site log or your account (erased in the 30-day purge). Switching the watcher off stops the visits but does not delete what was stored, and neither does disconnecting Search Console: page addresses the watcher already stored (including any it first learned from Search Console) stay until you delete your site log or your account. A counts-only record of each visit (how many pages were visited and how many changes were logged) is kept for 30 days.
    • Research usage record (tool, time, connection, cost): kept while your account exists and erased in the 30-day purge. The phrases and addresses your assistant asked about are not stored by us.
    • Copies of any of this in our backups are overwritten within 8 days of erasure.
  • Billing records: kept by Paddle as the law requires.
  • Test copies: when we test new features we sometimes use a temporary copy of the database; it is used only for that test and deleted within 24 hours of the test finishing.
  • Free check (including the local free check): deleted after 7 days, including the answers and any corrected name you give. A short progress note kept only while a check runs (the question and a verdict for each engine, with no name or address of yours) is deleted within a day.
  • Feedback and emails you send us: kept in our email inbox only while useful for replying and improving Bevizio; ask and we’ll delete them.
  • Scrambled IP codes used for rate limits: within about two days of the last request.
  • Waitlist: we email everyone on it once to say Bevizio has launched, then delete the list 30 days later.
  • Skills waiting list: kept until the weekly service is released or we decide not to build it, and in any case reviewed by October 18, 2027: on that date the list is deleted unless the service has by then been decided and is being built. If the service is released we email you once; if it is not, the list is deleted. You can be removed at any time by emailing hello@bevizio.com (the old route, a message to @danielkbuilds on X, also works), and we delete your row.
  • Free skills download records: kept without an expiry because they hold no information that identifies a person (no address, no browser details).

6. Your rights

You can ask to access, correct, delete, restrict or port your data, object to how we use it, and withdraw consent at any time. Several of these you can do yourself: Settings has account deletion, your email choices and the product-news switch, and the dashboard can export your answers as a CSV file. For anything else, email hello@bevizio.com — we’ll reply within one month. If you’re not satisfied, you can complain to the UK Information Commissioner’s Office at ico.org.uk, or your local data protection authority if you’re in the EU.

7. Cookies and browser storage

Strictly necessary (no consent needed): the sign-in cookies that keep you logged in (a session cookie, a short-lived copy of your session details so pages load quickly, and a one-time cookie used only while a Google sign-in is being finished); a plain flag cookie (bv_in, 7 days, no personal data) that lets our public pages show “Dashboard” instead of “Log in” once you are signed in; two short plain cookies, set when you press a plan button or run the free check, that carry what you just chose from one page to the next for about an hour (bv_plan, the plan you picked on the pricing page, and bv_checked, only the website address you ran the free check for, so the plan screen can refer to it); a cookie (bv_door, 24 hours) that remembers you arrived through the local-business sign-up so the plan screen describes the right product; the email you typed on the sign-in screen, kept in that tab only until you sign in or close it; and a few settings saved in your browser — your cookie choice, whether the sidebar is collapsed, and whether you’ve seen the product tour. Cloudflare’s bot check may read browser signals when you submit a form. When you connect an assistant by signing in, we also set a short security cookie (__Host-bvz_oauth) that makes sure the request is finished in the browser that started it. It lasts ten minutes and is removed once you choose Allow or Cancel.

Analytics (only with your consent): Google Analytics sets _ga and _ga_<id> cookies, which last up to 2 years. Vercel Web Analytics is cookieless. You can change your choice at any time with “Cookie settings” at the bottom of the home page and your dashboard, or here: .

8. Changes to this policy

We may update this policy from time to time; the “Last updated” date above shows the latest revision.

9. Contact, children and reminder emails

Questions or requests about your data can be sent to hello@bevizio.com or +44 7418 384943. By post: Daniel Kloss (Bevizio), 61 Bridge Street, Kington, HR5 3DJ, United Kingdom.

If you create an account and don’t finish setting up, we send one reminder email about it (and one more if you start a trial but your first check hasn’t run). They are part of the service you began, each is sent once, and if you reply asking us to stop, you won’t get another.

Bevizio is a business tool, not meant for anyone under 16, and we don’t knowingly collect children’s data. If you think a child has given us data, tell us at hello@bevizio.com and we’ll delete it.