ADVIXY.COM PRIVACY POLICY
1. Controller and scope
Advixy, S.L., tax ID B05495445, with its main contact address at Av. Santa Cruz 76, 38500 Santa Cruz de Tenerife, is the controller for the processing described here. This policy applies specifically to the institutional website advixy.com, its forms, content, contact tools and booking services. Privacy contact: info@advixy.com.
2. Data we process
We may process identification and contact data, professional or business information, the content of enquiries and forms, language and communication preferences, booking and payment data when that service is initiated, and technical data relating to browsing, security, consent and use. Do not send passwords, recovery phrases, full payment-card data or sensitive documents through free-text fields.
3. Purposes and legal bases
- Answering enquiries, preparing quotations and taking requested pre-contractual steps.
- Managing bookings, payments and contracted services on the basis of the contract and applicable legal duties.
- Protecting the site, forms and communications, preventing abuse and keeping evidence on the basis of legal duties and legitimate interests.
- Measuring public-page use in accordance with the cookie choice and the information in the Cookie Policy.
- Sending marketing communications only where separate, optional and withdrawable consent has been given.
4. Forms, bookings and assistants
Forms may be provided through WordPress and WPForms. Bookings may open Calendly services and, where applicable, a secure payment handled by Stripe. The AI assistant and interfaces for external assistants process only the information that the user chooses to provide or authorise for an enquiry or booking. Each service identifies actions that require confirmation.
5. Analytics, language and accessibility
The site uses WPML for language, OneTap for accessibility preferences and Google Analytics on public pages. Before Analytics is accepted, Google Consent Mode keeps analytics storage denied: Analytics cookies are not created, although cookieless measurement signals containing the public URL, page title and technical parameters may be sent. Form answers are not sent to Analytics.
6. Recipients and processors
Advixy does not sell personal data. Access may be given, under the appropriate safeguards, to providers of web hosting, forms, business email and communications, contact management, security, analytics, accessibility, bookings, payments and support. Data may also be disclosed to public authorities or professional collaborators where required by law or necessary to provide the requested service.
7. International transfers
Where a provider processes data outside the European Economic Area, Advixy will rely on an adequacy decision, approved contractual clauses or another mechanism permitted by data-protection law, together with any supplementary safeguards required for the risk.
8. Retention
Enquiries and requests are kept for the time needed to respond and, if no professional relationship begins, are erased or restricted when no longer necessary. Customer, booking, billing and service data is kept throughout the relationship and the subsequent legal, accounting and defence periods. Marketing data is kept until consent is withdrawn. Security and consent evidence is retained only for the period needed to demonstrate the relevant operation.
9. Rights
You may request access, rectification, erasure, objection, restriction and portability, and withdraw consent without affecting prior lawful processing, by writing to info@advixy.com. Advixy may request additional information only where needed to verify identity. You may also lodge a complaint with the Spanish Data Protection Agency.
10. Third-party data and children
If you provide another person’s data, you must be authorised and give that person the relevant information. The site’s services are aimed at professionals and businesses and are not designed for minors to submit data without their legal representative.
11. Security
We use access, encryption in transit, backup, traceability and minimisation measures appropriate to the risk. No system is entirely invulnerable; incidents are assessed, contained and notified in accordance with the applicable requirements.
12. Cookies and updates
Cookies and similar technologies on this domain are explained in the Advixy Cookie Policy. Material changes to this policy will be published here with the applicable version date.
13. Internal page-view counts
Advixy uses limited internal counts to evaluate its Mexico, Argentina and Colombia pages. When enabled, the record contains only totals by day, page and general access source: LinkedIn, Facebook or unknown. Days follow Canary Islands time (Atlantic/Canary), and aggregates are retained for 90 days. Recovery backups may retain older aggregates under their recovery retention, but reports exclude them after the reporting period.
The counter adds no visitor cookies or identifiers. Source classification uses the current navigation; full URLs, full referrers, campaign identifiers and questionnaire answers are not included in the aggregate record. Counts remain separate from commercial requests and the consented questionnaire analysis, and are available only to authorized Advixy staff.
Global Privacy Control (GPC), explicit Analytics refusal and invalid or ambiguous preferences exclude the signal. This limited internal measurement may run when no choice is recorded. You can review your preferences through the site’s privacy controls. A later choice affects future signals; an earlier aggregate cannot identify an individual page load for removal.
Results describe detected visible page loads, rather than unique people or verified advertising clicks. Reloads, bots, blockers, refusals, failures and technical limits affect coverage. The counts do not reconstruct individual journeys or support a cohort conversion rate with questionnaire totals. Network transport handles necessary connection metadata transiently; this design does not imply zero technical processing across all infrastructure layers. Use the privacy contact given in this policy for questions.
Version updated on 14 October 2026.
