Privacy Policy
Last updated: 8 October 2026
1. About this policy
This Privacy Policy applies when you visit our website beyzer.com, request a demo or contact us through a form, visit portal.beyzer.com, create or use a BEYZER account, or connect an external service to a BEYZER workspace. BEYZER is the controller for website, marketing, account, support, and platform-administration data described here.
Customers may add business content that contains personal data about their own staff, customers, authors, or other people. For that data, the customer normally determines why it is processed and BEYZER acts as its processor. Customers remain responsible for having a valid basis to provide that information to BEYZER.
2. Personal data we collect
Depending on how you use BEYZER, we may process:
Form data: when you book a demo or contact us, we receive your name, business email address, phone number, company or website, the plan you selected (if any), your message, and the page and language from which you sent the form.
Website usage data (with your consent): pages visited, clicks and scroll behaviour, form interactions, referral source and campaign, approximate location, device and browser information, pseudonymous cookie and device identifiers, and, for session recordings, a replay of your interaction with our pages. Session recordings are configured to mask the content of form fields.
Company identification data (with your consent): your IP address may be used to identify the company network you visit from. We use this to recognise business visitors, not to identify you as a private individual.
Account data: name, business email address, company, role, account status, accepted policy versions, and authentication identifiers.
Workspace data: websites, keywords, notes, brand story, product or service descriptions, brand colours, image instructions, excluded terms, focus country and language, source URLs, and generated drafts or images.
Integration data: selected Search Console property, Google account email, encrypted authorization tokens, public Google Drive folder details, and performance or keyword metrics returned by connected services.
Security and usage data: login and audit events, administrator support access, timestamps, error information, IP address, browser or device information, and technical request logs.
Communications: information you include in support requests, emails, demonstrations, or other conversations with us.
We receive most information directly from you or your organisation. We also receive data from services you deliberately connect, from public folders or websites you provide, and from normal security and server logging.
3. Why we use personal data
We process personal data for the following purposes and legal bases:
Handling demo and contact requests: responding to your request, scheduling a demonstration, and following up. This is necessary to take steps at your request before entering into an agreement and is based on our legitimate interest in responding to business enquiries.
Website analytics and improvement: understanding how visitors use beyzer.com so we can improve our content and usability, using Google Analytics, Microsoft Clarity, and Leadinfo. These tools are only loaded after you consent to the Analytics category in our cookie banner.
Advertising and conversion measurement: measuring the results of our advertising on Meta (Facebook and Instagram) and showing relevant ads to people who visited our website, using the Meta Pixel. This only happens after you consent to the Advertisement category in our cookie banner.
Spam and abuse prevention: protecting our website forms with Google reCAPTCHA, based on our legitimate interest in preventing automated misuse.
Providing the service: creating accounts, keeping workspaces separated, storing setup information, retrieving chosen metrics, and generating content. This is necessary to perform our agreement with the customer.
Security and reliability: authenticating users, preventing misuse, recording administrator actions, diagnosing errors, and maintaining backups. We rely on our legitimate interests in operating a secure and dependable service.
Support and communication: answering questions, handling requests, and sending essential service notices. This is based on the agreement and our legitimate interests.
Optional integrations: accessing a Google service only after an authorised user connects it or supplies a public folder. Where consent is the applicable basis, it can be withdrawn by disconnecting the integration.
Legal obligations: keeping information required for tax, accounting, compliance, dispute resolution, or lawful authority requests.
You can change or withdraw your cookie consent at any time via the cookie icon at the bottom left of every page. We do not use customer workspace data to create content for another customer. We do not make decisions that produce legal or similarly significant effects about people solely through automated processing.
4. Connected services and AI processing
BEYZER sends only the information needed for the feature you choose:
Google Search Console: after you authorise a Google account and select a property, BEYZER retrieves and stores search-performance data for that customer workspace. Authorization tokens are encrypted before storage.
Google Drive: BEYZER reads image files and folder metadata only from the public folder URL a customer supplies. A Google Drive sign-in is not stored for this integration.
SE Ranking: the platform may send an exact focus keyword and focus country to retrieve monthly search-volume and estimated average-CPC data. For GEO visibility, it may send the customer’s public website domain, focus country and registered company name or optional AI tracking brand name to retrieve monthly sampled brand mentions, domain citations and average position across supported AI engines. The saved focus language remains BEYZER context but is not sent as a language filter because these endpoints are country-based. Customers do not connect an advertising account.
OpenAI API: BEYZER may send the selected keyword, relevant setup instructions, approved source material, and selected reference images to generate an article draft or image. OpenAI states that API data is not used to train its models by default unless the API customer opts in. Standard API abuse-monitoring retention may be up to 30 days.
BEYZER’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
5. Who receives personal data
We do not sell or rent personal data. We share data only when needed to provide the service, protect legitimate interests, comply with law, or follow your instructions. Current categories of recipients include:
Supabase: authentication, PostgreSQL database, and private generated-image storage.
Vercel: application hosting, delivery, and operational request logs.
OpenAI: text and image generation through the business API.
Google: Search Console, Drive, OAuth, and central Ads keyword-research functionality selected by the customer or operated by BEYZER; on our website also Google Tag Manager, Google Analytics 4 (with consent), and reCAPTCHA. Without consent, Google only receives limited, cookieless signals through Google Consent Mode.
Microsoft: Microsoft Clarity heatmaps and session recordings on our website (with consent).
Leadinfo B.V. (the Netherlands): identification of companies visiting our website and visit analytics (with consent).
Meta Platforms Ireland Ltd.: the Meta Pixel for advertising measurement and audiences (with consent). For the collection and transfer of this data, Meta and BEYZER can act as joint controllers; Meta is responsible for its further processing under its own privacy policy.
CookieYes: our consent-management platform, which stores your cookie choices and keeps a consent log.
Email and hosting providers: hosting of our website and form submissions, and reliable delivery of account, verification, support, and service messages.
Professional advisers and authorities: only where reasonably necessary for legal advice, compliance, security, a transaction, or a binding legal request.
Service providers may use approved subprocessors. We assess the role of each provider and use contractual and technical safeguards appropriate to the processing.
6. International data transfers
Some providers or their subprocessors, including Google, Microsoft, and Meta, may process data outside the European Economic Area, in particular in the United States. Where a provider is certified under the EU-U.S. Data Privacy Framework, we rely on the European Commission’s adequacy decision. Where the destination is not covered by an adequacy decision, we rely on an appropriate transfer mechanism such as the European Commission’s Standard Contractual Clauses and apply supplementary safeguards where required.
7. How long we keep data
We keep personal data only for as long as needed for the purpose for which it was collected. Account and workspace information is generally kept while the customer account is active. After termination or a valid deletion request, we delete or anonymise data unless it must be retained for security, legal claims, accounting, or another legal obligation.
Technical logs, audit records, support correspondence, and backups can follow separate retention cycles. Deleted information may remain temporarily in protected rolling backups until those backups expire. Connected providers may also retain limited copies under their own documented retention schedules.
For our website specifically: demo and contact requests are kept as long as needed to handle the request and any follow-up, and deleted after no more than 24 months if no customer relationship follows. Google Analytics user- and event-level data is kept for 14 months. Microsoft Clarity keeps session recordings for up to 30 days and aggregated heatmap data for up to 13 months. Leadinfo and Meta keep data according to their own retention settings and policies. Your cookie choice is stored for 12 months, after which we ask again.
8. How we protect data
We use technical and organisational safeguards designed for the sensitivity of the data and the risks involved. These include encrypted network connections, encrypted integration credentials, server-side authorization, tenant-scoped database access, restricted administrator functions, audit logging, managed secrets, and provider access controls. Passwords are handled by Supabase Auth and are not stored in the BEYZER application database.
No online service can guarantee absolute security. If we identify a personal-data breach, we will investigate it and notify affected parties and regulators when the law requires us to do so.
9. Cookies and similar technologies
We use cookies and comparable browser storage on beyzer.com and portal.beyzer.com. When you first visit our website, a cookie banner lets you accept, reject, or customise your choices per category. Non-essential cookies are only placed after you consent.
Necessary: required for the website and platform to work, such as secure sign-in, session continuity, request protection, language preference, and storing your cookie choice (CookieYes). These cannot be switched off.
Analytics: Google Analytics (for example _ga and _ga_*), Microsoft Clarity (for example _clck and _clsk), and Leadinfo (for example _li_id and _li_ses). They help us understand how visitors use our website.
Advertisement: the Meta Pixel (for example _fbp and _fbc). It measures the results of our Meta advertising and enables relevant ads.
We use Google Consent Mode v2: if you do not consent, Google tags do not place analytics or advertising cookies and only send limited, cookieless signals. You can change or withdraw your consent at any time via the cookie icon at the bottom left of the page. You can also remove or block cookies in your browser, but essential cookies are required to sign in and use protected parts of the platform. The current list of cookies, with their duration and purpose, is available in the cookie banner under Customise.
10. Your privacy rights
Subject to the conditions in applicable law, you may ask us to:
confirm whether we process your personal data and provide access to it;
correct incomplete or inaccurate personal data;
delete personal data that is no longer required or was processed unlawfully;
restrict processing in certain circumstances;
provide data you supplied in a structured, machine-readable format;
stop processing based on legitimate interests when your rights outweigh those interests;
withdraw consent at any time, without affecting earlier lawful processing; and
object at any time to direct marketing.
We may ask for information needed to verify your identity. We normally respond within one month. Some rights are not absolute; if an exception applies, we will explain it.
11. Children and automated decisions
BEYZER is a business service and is not directed to children. We do not knowingly create accounts for, or collect personal data directly from, anyone under 18.
AI-generated articles, images, keyword metrics, and suggestions are working materials for business users. They do not make legal or similarly significant decisions about individuals, and customers remain responsible for reviewing generated output before using or publishing it.
12. Third-party websites
BEYZER may contain links to external websites or customer-provided sources. We do not control those websites and are not responsible for their privacy practices. Review the relevant privacy information before providing personal data to another organisation.
13. Changes to this policy
We may update this policy when BEYZER, our providers, or legal requirements change. We will publish the revised version here and update the date at the top. If a change materially affects how we use personal data, we will provide an additional notice where appropriate.
14. Contact and complaints
To ask a privacy question or exercise a right, contact:
BEYZER
Haaksbergerstraat 67
7554 PA Hengelo
The Netherlands
Chamber of Commerce: 90674049
Email: hi@beyzer.com
You also have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens, or with the data-protection authority in your country. We would appreciate the opportunity to address your concern first.
For the contractual rules that apply to the platform, see our Terms.