01
Data Controller
KARYENDA acts as the data controller for personal data collected through karyenda.com, beatsignals.com, BEAT™ workspaces, contact forms, outbound pre-assessments, and related communication channels.
- Company name
- KARYENDA srl
- VAT number
- BE 0673 535 237
- Registered address
- Chaussée de Waterloo 702, 1180 Uccle, Belgium
- Contact
- contact@karyenda.com
02
Information We Collect
We collect information that you voluntarily provide, information generated through your use of KARYENDA services, and business-related signals obtained from publicly available or third-party B2B sources where legally permitted.
- Contact form submissions — first name, email address, company name, website URL, and any context you choose to share
- BEAT™ account and workspace information — name, work email, company, website URL, role, organization, workspace memberships, team invitations, and workspace-related settings
- BEAT™ Business Context submissions — business priorities, growth objectives, constraints, strategic context, website URL, and declared priorities
- BEAT™ briefing data — public signals, contextual signals, generated briefings, signal clusters, and analytical output history
- Competitive benchmarking inputs — competitor URLs you choose to track and the publicly observable signals collected for those domains
- Connected intelligence data— data from the analytics and advertising accounts you explicitly authorize, accessed read-only: Google Analytics 4, Google Search Console, and Google Ads through Google’s OAuth consent flow (see the Google User Datasection below), and Meta advertising (Meta Ads) and organic social data — Facebook Pages and Instagram — through Meta’s login (see the Meta Platform Data section below)
- Outbound pre-assessment information — company-level growth signals, public website observations, positioning signals, and business context used before outreach
- Business context — company details, growth signals, conversion challenges, CRM usage, revenue visibility constraints, acquisition context, and stated priorities
- Website and platform usage information — pages visited, session duration, referral sources, login activity, workspace interactions, and general interaction patterns
- Technical data — browser type, device type, approximate geographic region, IP-derived technical signals, and basic system information
- Business-related information voluntarily submitted through any KARYENDA service, form, briefing request, workspace, or communication
We do not intentionally collect sensitive personal data. We do not collect payment card information directly — transactional data is handled by our payment infrastructure provider, Stripe.
03
Why We Collect It
Information is collected and used for the following purposes:
- Operate BEAT™ workspaces and related platform functionality
- Deliver BEAT™ Growth Intelligence and generate analytical intelligence briefings
- Capture business context and improve the relevance of signal interpretation
- Provide Connected Intelligence features — validating signal hypotheses against the connected data you choose to connect: Google Analytics 4, Search Console, and Google Ads, and Meta advertising and organic social (Facebook Pages, Instagram)
- Respond to contact, inquiry, collaboration, and follow-up requests
- Deepen analysis of signals uncovered through BEAT™ or outbound pre-assessments
- Improve the relevance, quality, and accuracy of KARYENDA analytical systems
- Understand website and platform usage patterns to improve user experience, content structure, and conversion clarity
- Conduct business signal research to develop future analytical systems, benchmarks, methodologies, and signal libraries
- Support outbound B2B communication where a legitimate business interest has been identified
- Maintain, secure, debug, and improve KARYENDA infrastructure
04
Legal Basis for Processing
Depending on the context, KARYENDA may process personal data under one or more GDPR legal bases.
- Consent: when you voluntarily submit a form, opt in to receive communication, connect a Google account or other data source, or accept non-essential cookies
- Contract or pre-contractual steps: when processing is necessary to respond to your request, operate a BEAT™ workspace, deliver a briefing, or explore a potential engagement
- Legitimate interest: when processing is necessary for B2B signal analysis, outbound pre-assessment, prospect qualification, service improvement, fraud prevention, or system security, provided those interests are not overridden by your rights and freedoms
- Legal obligation: when processing is required to comply with applicable law, accounting, tax, or regulatory requirements
Where KARYENDA relies on legitimate interest, it seeks to limit processing to professional or company-related information, minimize privacy impact, and provide a clear right to object.
05
Business Signal Intelligence & Data Enrichment
As part of its business signal intelligence methodology, KARYENDA may enrich business-related information using publicly available professional and company data sources. This enrichment is used to improve analytical accuracy, signal interpretation, outbound pre-assessment quality, and the relevance of intelligence outputs.
Business signal enrichment may include:
- Company-level information derived from public business registries, professional databases, company websites, and public digital properties
- Publicly available business indicators — website structure, positioning, technology stack signals, hiring signals, market context, and organizational indicators
- Website content and publicly observable funnel, messaging, conversion, trust, visibility, and positioning signals
- Publicly observable signals of companies you choose to track as competitors within your workspace
- Company-level enrichment sourced from legitimate B2B intelligence providers
- Declared form inputs submitted voluntarily by users
- Information submitted through the BEAT™ platform and workspace
- Publicly available information required to contextualize growth, conversion, CRM, acquisition, and revenue visibility signals
This enrichment is primarily performed at the company level. Where professional contact data is processed, KARYENDA does so under an appropriate legal basis, including legitimate interest where applicable, in the context of B2B analysis, prospect qualification, outbound pre-assessment, and business signal intelligence.
Individuals who wish to object to the processing of their professional information in the context of business intelligence activities may do so by contacting contact@karyenda.com.
06
Automated Analysis & AI-Assisted Interpretation
KARYENDA systems may use automated analysis, AI-assisted interpretation, signal interpretation logic, or workflow automation to process declared, public, enriched, connected, or observed business signals.
These systems are used to generate probabilistic intelligence outputs, detect signal patterns, structure analytical briefings, and support business interpretation. They are not designed to produce legally binding decisions about individuals.
- BEAT™ outputs are probabilistic and signal-based
- Outputs may include inferred growth constraints, signal clusters, strategic friction points, and revenue leakage hypotheses
- Automated outputs are informational and should not be interpreted as confirmed factual diagnoses
- KARYENDA may review, improve, or adjust its analytical logic over time based on quality control and observed signal patterns
KARYENDA does not use automated analysis to make decisions producing legal effects concerning individuals. The objective is business signal interpretation, not individual profiling for legal, financial, employment, or credit decisions.
07
Third-Party Services
KARYENDA uses a limited set of third-party service providers (subprocessors) to operate its website, platform, workflows, enrichment, email delivery, analytics, and analytical infrastructure. Each provider receives only the data necessary to perform its function:
- Vercel — hosting and content delivery for beatsignals.com; processes request data required to serve the platform
- Supabase — authentication and database infrastructure; stores account, workspace, signal, briefing, and connected intelligence data
- Anthropic— AI analytical infrastructure; receives the signal, context, and connected data needed to generate the briefings, analyses, and chat responses you request. This data is not used to train Anthropic’s models
- n8n — workflow automation and orchestration of scanning and briefing pipelines; routes data between the services above
- Stripe — payment infrastructure; processes subscription and billing data
- Brevo — transactional email delivery; receives the email address and message content of operational communication
- Google APIs — performance measurement (PageSpeed), public review aggregation (Places), and — only where you connect them — Analytics, Search Console, and Google Ads data access
- Meta APIs — only where you connect them, read-only access to Meta Ads reporting and Facebook Page / Instagram organic insights for the accounts you select
- Apollo.io — B2B firmographic enrichment; receives company domains for company-level enrichment
- Jina AI — public website content extraction; receives public URLs to be parsed
- ScreenshotOne — homepage screenshot capture; receives public URLs to be captured
These providers act only as our processors: they receive data solely to perform the function described above, process it only on our instructions, and never for their own purposes. Disclosing data to a processor that operates part of the service is not the same as sharing it with an independent third party for that party’s own use — which KARYENDA does not do. KARYENDA does not sell, rent, or trade data to third parties.
08
Google User Data
BEAT™ offers optional Connected Intelligence features that let you connect your Google Analytics 4 property and Google Search Console account through Google’s OAuth consent flow. This section describes how Google user data obtained through Google APIs is accessed, used, stored, shared, and deleted.
What we access. With your explicit authorization, BEAT™ accesses — read-only — analytics data from the Google Analytics 4 property you select (traffic, engagement, and conversion metrics) and search performance data from the Search Console site you select (queries, impressions, clicks, and positions). We never modify data in your Google account.
How we use it. Google user data is used solely to provide user-facing Connected Intelligence features in your workspace: validating, contradicting, or extending the signal hypotheses in your briefings, Lens analyses, and BEAT Chat answers. It is not used for advertising, profiling unrelated to these features, or any purpose beyond providing and improving the features you have requested.
With whom it is shared, transferred, or disclosed. We do not sell Google user data, and we do not share it with advertisers, data brokers, or any other third party for their own purposes. It is processed only by the subprocessors strictly necessary to operate the service, acting on our instructions under contractual data protection obligations:
- Supabase — stores connected data snapshots and OAuth tokens in our database
- Vercel — hosts the application infrastructure that processes the data in transit
- Anthropic— receives the portions of connected data needed to generate the specific analysis you request; this data is not used to train Anthropic’s models
Beyond these providers, Google user data is disclosed only if required by applicable law or valid legal process, with your explicit consent, or — with prior notice to you — as part of a merger, acquisition, or sale of assets where the recipient remains bound by this policy.
In line with those Limited Use requirements:
- Google user data is only used to provide or improve the user-facing features described above
- It is never used to develop, improve, or train generalized artificial intelligence or machine learning models
- It is never transferred for advertising purposes or sold to data brokers
- Humans do not read this data, except with your explicit consent, where necessary for security or abuse investigation, to comply with applicable law, or where the data has been aggregated and anonymized for internal operations
- It is excluded from the cross-customer aggregation and benchmarking activities described elsewhere in this policy
Storage and security. OAuth tokens and connected data snapshots are stored encrypted at rest and transmitted over encrypted connections (TLS). Access is restricted to your workspace.
Deletion and revocation.You can disconnect Google Analytics or Search Console at any time from your workspace settings. Upon disconnection, the associated OAuth tokens are invalidated and the stored Google user data for that connection is deleted from our systems within 30 days. Deleting your workspace or account has the same effect. You can also revoke BEAT’s access directly from your Google account security settings, or request deletion at any time by contacting contact@karyenda.com.
09
Meta Platform Data
BEAT™ offers optional Connected Intelligence features that let you connect your Meta assets through Meta’s Facebook Login: your Meta advertising accounts (Meta Ads) and your owned organic social channels — the Facebook Pages you administer and the Instagram professional accounts linked to them. This section describes how Meta Platform Data obtained through the Meta APIs is accessed, used, stored, shared, and deleted.
What we access. With your explicit authorization, BEAT™ accesses — read-only — advertising reporting data from the Meta ad accounts you select (spend, impressions, clicks, conversions, and campaign metadata) and organic analytics from the Facebook Page and Instagram account you select (audience and follower metrics, reach and impressions, engagement, and post-level performance). We never create or edit campaigns, publish or schedule content, manage messages, or modify any setting in your Meta accounts, and we never access private messages or direct messages.
How we use it. Meta Platform Data is used solely to provide user-facing Connected Intelligence features in your workspace: validating, contradicting, or extending the signal hypotheses in your briefings, Lens analyses, and BEAT Chat answers. It is not used for advertising, profiling unrelated to these features, or any purpose beyond providing and improving the features you have requested.
With whom it is shared, transferred, or disclosed. We do not sell Meta Platform Data, and we do not share it with advertisers, data brokers, or any other third party for their own purposes. It is processed only by the subprocessors strictly necessary to operate the service, acting on our instructions under contractual data protection obligations:
- Supabase — stores connected data snapshots and OAuth tokens in our database
- Vercel — hosts the application infrastructure that processes the data in transit
- Anthropic— receives the portions of connected data needed to generate the specific analysis you request; this data is not used to train Anthropic’s models
Beyond these providers, Meta Platform Data is disclosed only if required by applicable law or valid legal process, with your explicit consent, or — with prior notice to you — as part of a merger, acquisition, or sale of assets where the recipient remains bound by this policy.
In line with those requirements:
- Meta Platform Data is only used to provide or improve the user-facing features described above
- It is never used to develop, improve, or train generalized artificial intelligence or machine learning models
- It is never transferred for advertising purposes or sold to data brokers
- Humans do not read this data, except with your explicit consent, where necessary for security or abuse investigation, to comply with applicable law, or where the data has been aggregated and anonymized for internal operations
- It is excluded from the cross-customer aggregation and benchmarking activities described elsewhere in this policy
Storage and security. OAuth tokens and connected data snapshots are stored encrypted at rest and transmitted over encrypted connections (TLS). Access is restricted to your workspace.
Deletion and revocation.You can disconnect any Meta connector at any time from your workspace settings. Upon disconnection, the associated access tokens are invalidated and the stored Meta Platform Data for that connection is deleted from our systems within 30 days. Deleting your workspace or account has the same effect. You can also revoke BEAT’s access directly from your Meta Business Integrations settings, request deletion at any time by contacting contact@karyenda.com, or follow the Data Deletion Policy.
11
Data Retention
Information is retained only as long as operationally necessary or legally required.
- BEAT™ workspace and Growth Intelligence data may be retained to generate outputs, operate the platform, improve analytical system quality, and support follow-up communication
- Connected Google user data is retained only while the corresponding connection is active — it is deleted within 30 days when you disconnect the data source, delete your workspace, or delete your account
- Outbound pre-assessment data may be retained where relevant to B2B signal intelligence, prospect qualification, or business communication
- Assessment, context, signal, and briefing data may be retained in anonymized or aggregated form for long-term pattern analysis, benchmarking, and signal library development
- Contact information is retained for as long as necessary to respond to inquiries, manage the relationship, or maintain relevant B2B context
- Website and platform analytics data is retained in accordance with the retention policies of the analytics provider
- Data subject to legal obligations is retained for the period required by applicable law
You may request deletion of your personal data at any time by contacting contact@karyenda.com. Some anonymized, aggregated, or legally required records may be retained where permitted by law.
12
Aggregation, Anonymization & Benchmarking
KARYENDA may use anonymized or aggregated information to identify recurring growth patterns, build benchmark intelligence, improve signal interpretation, and develop future analytical systems.
Aggregated or anonymized data may be used to:
- Identify recurring growth leakage patterns
- Improve BEAT™ signal interpretation and intelligence logic
- Develop benchmark intelligence by sector, maturity, growth stage, or signal family
- Produce Signal Studies based on composite patterns
- Improve business signal intelligence systems over time
Connected Google user data is excluded from these cross-customer aggregation and benchmarking activities, consistent with the Limited Use requirements described in the Google User Data section.
Where data is anonymized, KARYENDA takes reasonable steps to prevent the identification of specific individuals from the resulting analytical patterns.
13
Your Rights
Under the General Data Protection Regulation (GDPR) and applicable Belgian data protection law, you have the following rights regarding your personal data:
- Access
- Request a copy of the data we hold about you
- Correction
- Request correction of inaccurate or incomplete data
- Deletion
- Request erasure of your personal data
- Objection
- Object to processing based on legitimate interest
- Portability
- Receive your data in a structured, machine-readable format
- Restriction
- Request restriction of processing in certain circumstances
To exercise any of these rights, contact contact@karyenda.com. We will respond within the legally required timeframe. You also have the right to lodge a complaint with the Belgian Data Protection Authority.
14
International Transfers
Some third-party providers used by KARYENDA may process or store data outside Belgium or the European Economic Area. Where this occurs, KARYENDA seeks to rely on appropriate safeguards, such as adequacy decisions, contractual protections, or other mechanisms recognized under applicable data protection law.
15
Security
KARYENDA takes reasonable technical and organizational measures to protect personal data against unauthorized access, misuse, loss, alteration, or disclosure. Data is encrypted in transit, stored with access controls scoped to your workspace, and OAuth credentials for connected data sources are stored encrypted.
No digital system can be guaranteed to be completely secure. Users are encouraged not to submit highly confidential, sensitive, or regulated information through general website forms or BEAT™ workspaces unless specifically requested under an appropriate engagement framework.
16
Contact
For any privacy-related inquiry, data subject request, objection, or question regarding this policy: