1. Data Controller
The data controller for the personal data processed through the Yabrix website and services (the “Service”) is CAHAMS INTERNET S.L., with registered office at Calle General Díaz Porlier, 48, 1A, 28001 Madrid, Spain, Tax ID ESB85084317, registered with the Commercial Registry of Madrid, Volume 24,243, Page 157, Section 8, Sheet M-435744.
For any questions regarding this Privacy Policy or the processing of personal data, you may contact us at:
📧 info@yabrix.com
2. Categories of Personal Data Processed
Yabrix processes only identification and technical data. Under no circumstances does Yabrix intentionally process special categories of personal data as defined under Article 9 of the GDPR, nor data relating to criminal convictions or offences.
Depending on the interaction with the Service, the following categories of data may be processed:
- Account data: name, email address, login credentials
- Billing data: billing address, payment status (payments are processed by third-party providers)
- Technical and usage data: IP address, timestamps, user agent, page URLs, referrer information
- IP addresses are processed only for technical and security purposes and are anonymized before being stored. Yabrix does not store IP addresses in identifiable form and does not use them to identify individual users.
- Configuration and preference data related to the Service
Mandatory fields indicated in registration or contact forms are required to provide the requested service.
3. Data Subjects and Responsibility
Depending on the context, Yabrix may process data relating to:
- Customers (organizations or individuals with a Yabrix account)
- Authorized users acting on behalf of a customer
- Website visitors whose data is processed through the analytics Service on customer websites
Customers are responsible for ensuring that their use of the Service complies with applicable data protection laws, including obtaining any required user consent.
By providing personal data, you confirm that you are legally authorized to do so and that the information provided is accurate, complete, and up to date.
In the context of the analytics Service, customers act as data controllers and Yabrix acts as a data processor.
4. Purpose and Legal Basis of Processing
Yabrix processes personal data for the following purposes and legal bases:
4.1. Provision of the Service
To create and manage user accounts, provide analytics, dashboards, and related features.
Legal basis: Performance of a contract (Article 6.1.b GDPR).
4.2. Communications and Support
To respond to inquiries, provide technical support, and communicate service-related information.
Legal basis: Legitimate interest (Article 6.1.f GDPR) and/or performance of a contract.
4.3. Commercial Communications
To send product updates or commercial communications when explicit consent has been granted.
Legal basis: Consent (Article 6.1.a GDPR).
You may withdraw consent at any time.
4.4. Analytics and Measurement
Yabrix provides analytics without cookies or invasive tracking techniques by default.
Where required by law or explicitly enabled by the customer through a valid consent mechanism, Yabrix may use cookies or a persistent identifier (such as a user_uuid) to enhance accuracy or functionality.
4.5. Google Analytics and Google Search Console Integrations
Yabrix may allow users to connect their Google accounts in order to import reporting and search-performance data from Google Analytics and Google Search Console into the Yabrix platform.
These integrations are available only when a user explicitly authorizes access through Google OAuth.
Depending on the features enabled, Yabrix may access the following categories of Google user data:
- Google account identifiers and basic account metadata required to complete and maintain the OAuth connection
- Google Analytics property and reporting data made available to Yabrix through the Google Analytics Data API
- Google Search Console site and performance data made available to Yabrix through the Search Console API
- Technical authentication data such as access tokens, refresh tokens, token expiry timestamps, and connection status metadata
Yabrix uses this data only for the following purposes:
- to authenticate the user and establish the requested Google integration
- to retrieve analytics and search-performance data requested by the user
- to display dashboards, reports, summaries, comparisons, alerts, or other user-facing product features inside Yabrix
- to maintain, secure, troubleshoot, and improve the specific integration features requested by the user
Yabrix does not use Google user data obtained through these integrations for advertising, profiling for advertising purposes, resale, or data brokerage.
Yabrix does not use Google user data obtained through these integrations for any purpose that is not clearly disclosed in this Privacy Policy and, where applicable, in the product interface presented to the user at the time of connection.
Legal basis: performance of a contract (Article 6.1.b GDPR), and where required, consent (Article 6.1.a GDPR).
4.6. Limited Use of Google User Data
Where Yabrix accesses Google user data through Google APIs, Yabrix will use that data in accordance with the Google API Services User Data Policy, including the Limited Use requirements where applicable.
Google user data obtained through Google APIs will only be used to provide or improve user-facing functionality that is visible and relevant to the user in the Yabrix application.
Yabrix does not sell Google user data.
Yabrix does not transfer Google user data to third parties except:
- as necessary to provide or secure the requested service through subprocessors acting on Yabrix’s behalf and under contractual confidentiality and data-protection obligations
- where required by law
- where necessary to investigate abuse, fraud, or security incidents
- in connection with a merger, acquisition, or sale of assets, subject to applicable legal requirements
Yabrix does not allow humans to read Google user data except:
- where necessary to provide support requested by the user
- where necessary for security, fraud prevention, or debugging
- where required by law
- where the data has been aggregated or sufficiently de-identified for internal operational purposes, where permitted by law
Y además añade esto dentro de 5. Data Retention:
For Google integrations specifically:
- OAuth tokens and connection metadata are retained for as long as the integration remains active, unless earlier deletion is requested
- imported Google Analytics and Google Search Console data is retained for as long as necessary to provide the related reporting and analytics features to the customer, subject to the customer’s subscription settings, deletion requests, legal obligations, and legitimate backup requirements
- when a user disconnects a Google integration, Yabrix will stop new data collection from that Google account and will delete or anonymize related credentials within a reasonable period, unless retention is legally required
Backup copies may persist temporarily for security and disaster-recovery purposes and are deleted according to Yabrix’s backup retention cycle.
Y esto dentro de 8. Data Subject Rights:
Users who connect Google integrations may, subject to applicable law and technical limitations:
- request information about the Google user data processed by Yabrix
- request deletion of imported data associated with their account
- disconnect Google Analytics or Google Search Console integrations from within the Yabrix product or by contacting Yabrix support
- revoke Yabrix’s access from their Google account permissions settings
Legal basis: Legitimate interest or consent, as applicable.
5. Data Retention
Yabrix applies privacy-by-design principles.
IP addresses are anonymized prior to storage and are never retained in a form that allows the identification of an individual user.
By default, Yabrix provides analytics without the use of cookies or invasive tracking techniques. Where explicitly enabled by the customer and only where valid consent has been obtained from end users, Yabrix may use cookies or a persistent technical identifier (such as a visitor UUID) to enhance functionality, improve accuracy, or enable optional features.
6. Data Recipients and Processors
Personal data will not be disclosed to third parties except:
- When required by law
- When necessary to provide the Service through trusted processors
Yabrix works with third-party service providers acting as data processors, including but not limited to:
- Hosting and infrastructure providers
- Payment processors (e.g. Stripe Payments Europe Ltd.)
- Email and notification services
All such providers operate under data processing agreements compliant with GDPR requirements.
Customers may enter into a Data Processing Agreement (DPA) with Yabrix in accordance with Article 28 GDPR.
7. International Data Transfers
Where personal data is transferred outside the European Economic Area, Yabrix ensures appropriate safeguards are in place, such as Standard Contractual Clauses or equivalent legal mechanisms.
8. Data Subject Rights
You have the right to:
- Access your personal data
- Request rectification of inaccurate data
- Request erasure of your data when no longer necessary
- Request restriction of processing in certain circumstances
- Object to processing based on legitimate interests
- Request data portability where applicable
Requests may be made by email or postal mail, provided that proof of identity is supplied where necessary.
You also have the right to lodge a complaint with the Spanish Data Protection Authority (AEPD):
https://www.aepd.es/
9. Security Measures
Yabrix implements appropriate technical and organizational security measures to protect personal data against unauthorized access, alteration, loss, or disclosure.
While no system can guarantee absolute security, Yabrix continuously reviews and improves its safeguards.
10. Confidentiality
All personal data is treated as confidential and accessed only by authorized personnel and service providers acting under Yabrix’s instructions.
11. Changes to this Privacy Policy
Yabrix may update this Privacy Policy from time to time. Material changes will be communicated through the Service or by other reasonable means.
Yabrix does not provide user-level identification and does not offer personally identifiable tracking capabilities.
Continued use of the Service after an update constitutes acceptance of the revised Privacy Policy.
12. Contact
For any questions regarding this Privacy Policy or data protection matters: Contact