Privacy Policy

This English version is provided for convenience. If there is any discrepancy, the Spanish version prevails.

Last updated: September 5, 2026

ERPLEXIA respects the privacy of everyone who visits this site. This policy explains what data we collect, for what purpose, and what rights you have, in accordance with Costa Rica's Ley N.º 8968 de Protección de la Persona frente al Tratamiento de sus Datos Personales (Law No. 8968 on the Protection of Individuals with Regard to the Processing of Their Personal Data).

Data controller

ERPLEXIA, Cartago, Costa Rica. Contact email: leo@erplexia.com.

What data we collect

Cookies

This site does not use advertising cookies or cross-site tracking cookies. Cloudflare Web Analytics measures visits without cookies and without building individual profiles. The form uses the browser's session storage solely to keep the campaign source for the duration of your visit; it is deleted when you close the tab.

How we use your data

We do not sell, rent or transfer your data to third parties for commercial purposes.

Data processors

To operate the site and manage contacts, we use providers that act on our behalf: Cloudflare (hosting, security and analytics), Odoo (customer relationship management), Resend (delivery of contact notifications) and Google Workspace (email and calendar). Each one processes the data solely in accordance with our instructions.

How long we keep your data

Business contact data is kept for as long as there is a legitimate interest in the relationship and for no more than five years from the last contact, unless you request its deletion sooner.

Your rights

You may at any time request access to, rectification or deletion of your data, or withdraw your consent, by writing to leo@erplexia.com. We handle your request within the following five business days. You may also file a complaint with Costa Rica's Agencia de Protección de Datos de los Habitantes (PRODHAB), the national data protection authority.

Security

The site is served exclusively over HTTPS, enforces a strict content security policy and protects the form with anti-bot verification. Integration credentials are stored encrypted and are never exposed in the browser.

Changes

If we change this policy, we will publish the updated version at this same address, stating the date of the change.

← Back to home