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.

[COMPLETE: anything more specific to commit to on retention, deletion, or third-party access]

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

Each project may use a different provider depending on scope. There isn't one datacenter for everything.

This site (edvance.cl) is deployed on [COMPLETE: actual provider — e.g. Vercel, AWS, Chilean hosting].

Client projects are hosted on [COMPLETE: actual provider(s) in use today — can be a short list].

Before signing, we tell you where your system will live and what data will pass through there.

Backups depend on the project and the agreed maintenance plan.

[COMPLETE: actual backup frequency — e.g. daily, weekly, what's included and how long backups are kept]

If the project includes maintenance with Edvance, backup scope is written in the proposal. 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 in Git. 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.

[COMPLETE: whether you use GitHub, GitLab, or other; if there's CI; whether the client gets repo access on delivery]

• Private repository per project.
• 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.