Security and data

In Chile, Law No. 21,719 governs personal data protection. We apply it where relevant when Edvance processes third-party data in a project.

Information a client provides to evaluate or execute work is used only for that purpose. We don't sell it or share it with commercial third parties.

When an infrastructure provider is needed to run the system (hosting, database, email), that provider may process data on our behalf. Only who the project needs gets access.

For contact form data on edvance.cl, also see the privacy policy.

This site (edvance.cl) and client projects are hosted on Vercel.

If the scope calls for another provider, we tell you before signing: where your system will live and what data will pass through there.

Backups are made according to each client's needs.

When the project includes maintenance with Edvance, backups are included in that price.

Without maintenance, we hand over what your team needs to configure them.

Before you share internal documentation, processes, or your clients' data, we can sign an NDA.

It's not required for a first conversation, but it's available if your legal team asks.

Email us at operaciones@edvance.cl and we'll work it out case by case.

Code is versioned on GitHub. Every change is logged: who made it, when, and with what message.

Before production, work goes through a test or preview environment when the project allows. We don't push straight to what your users rely on without a prior pass.

Deliveries happen in agreed increments: visible progress, not a surprise package at the end.

We don't grant repository access unless it is agreed and priced separately.

• Private repository per project on GitHub.
• Protected main branch: changes go in through review, not blind merges.
• Sensitive variables (API keys, passwords) stay out of code, in environment variables.
• Minimum documentation on delivery: how to run the project and where credentials live.