Skip to content
Open Factura

This translation is provided for convenience. The Spanish version is the legally binding one. Read the Spanish version

Data Processing Agreement

Last updated: November 13, 2026 · Effective from: November 13, 2026

Parties and definitions

This agreement is part of the Terms of Service between you (the “customer”) and Yaya Technologies, Sociedad por Acciones Simplificada de Capital Variable (“Open Factura”, “we”). It applies from the moment you accept the terms and for as long as we process data on your behalf.

  • Customer data: the personal data that you, your users or your integrations put into the service and that we process on your behalf: above all, that of the recipients of your documents and of your customer catalog.
  • Controller: whoever decides what data is processed for and how. Processor: whoever processes it on behalf of the controller. Sub-processor: a provider we engage that processes customer data.
  • Applicable law: El Salvador’s Personal Data Protection Law (Ley para la Protección de Datos Personales) and any other data protection rule that applies to you.

The data of your own account (your name, your email, your plan) is not covered by this agreement: we are the controller of that data, under the Privacy Policy.

Who is who

With respect to customer data, you are the controller and we are the processor. If you in turn process that data on behalf of someone else (for example, you are a platform or a firm that issues for its customers), you are that third party’s processor and we are your sub-processor; in that case you represent that you have their authorization to engage us.

The Ministry of Finance is not a sub-processor of ours: it receives the documents as the tax authority, because the law requires you to transmit them to it.

We process according to your instructions

We will process customer data only to provide the service to you and according to your documented instructions. Your instructions are: the Terms, this agreement, your account’s configuration and each operation that you, your users, your API keys or your integrations run (issue, look up, invalidate, send a webhook, generate a PDF).

We will not use customer data for our own purposes, we will not sell it, we will not combine it with other customers’ data and we will not use it for advertising or to train artificial intelligence models.

If we believe an instruction of yours violates the law, we will tell you and may stop following it while the matter is clarified. If a law requires us to process the data in another way, we will notify you first, unless the law itself prohibits it.

What is up to you

  • Having a legal basis to process your customers’ data and informing them as the law requires.
  • Putting into the service only the data necessary to invoice. Do not upload sensitive data.
  • Configuring your access properly: roles, keys, webhooks and, if you use it, the connection with a platform.
  • Handling your customers’ requests about their data. We help you.
  • Keeping your documents for the legal period.

Confidentiality and staff

Customer data is accessed only by the staff who need it to operate the service, support you or resolve an incident, with the minimum access necessary and under a duty of confidentiality, which remains in force when their relationship with us ends.

Security

We apply the technical and organizational measures described in Annex 2. We may update them, but not significantly reduce the level of protection. It is up to you to assess whether those measures are sufficient for your data and to make good use of the ones that depend on you.

Security breaches

If we confirm a security breach affecting customer data, we will notify you without undue delay and, at the latest, within 72 hours of confirming it, at the email of the organization’s owner. The notice will state, as far as we know at that time: what happened, which data and how many people are affected, what we did to contain it and what we recommend you do. We will complete the information as we obtain it.

We will help you with the notifications you must make to the authority and to those affected; deciding whether to notify and whom is up to you as the controller. Failed attempts that do not compromise data (scans, blocked access attempts) do not count as a breach.

Data subject requests

The dashboard and the API let you look up, correct and delete your customers’ data. If a data subject writes to us directly about data we process on your behalf, we will not resolve their request on our own: we will pass it on to you without delay and tell them to contact you. We will reasonably help you respond, and also with the impact assessments or consultations with the authority that the law requires of you.

Sub-processors

You authorize us to use the providers in the List of Sub-processors. With each one we have a contract with data protection obligations equivalent to those of this agreement, and we answer to you for what they do with customer data.

Before adding a new sub-processor that processes customer data we will update the list and notify you by email at least 15 days in advance. If you have a reasonable data protection objection, write to us within that period: we will look for an alternative and, if there is none, you may stop using the affected feature or cancel the service without penalty, with a pro-rata refund of what you paid in advance. Only in a security or availability emergency may we change providers without prior notice, and we will let you know as soon as possible.

International transfers

You authorize us to process customer data outside El Salvador, in the countries where our sub-processors operate (indicated in the list). We require those providers to give contractual guarantees of security and confidentiality. If the applicable law requires an additional mechanism to transfer the data, we will adopt it with you.

Return and deletion

While you have an account you can export customer data through the dashboard and the API. When you delete your organization, or when the service ends and the export period in the Terms has passed, we erase customer data from the active database; recovery copies disappear through rotation within a maximum of 30 days. We will keep only what a law requires us to keep, and solely for that purpose.

Information and audit

We will give you the information reasonably necessary to demonstrate that we comply with this agreement: answers to security questionnaires and the documentation of our measures. The core of the service is open source and you can review it whenever you want.

If that is not enough and the law requires more of you, you may carry out an audit at most once a year (or when there has been a confirmed breach or an authority orders it), with 30 days’ notice, by remote and documentary means, under confidentiality, with no access to other customers’ data and bearing its costs yourself.

Requests from authorities

If an authority asks us for customer data, we will notify you before handing it over, unless the law prohibits it. We will check that the request is valid, challenge it if there are reasonable grounds and hand over only what is strictly required.

Liability and order of precedence

Each party’s liability under this agreement is subject to the limits in the Terms, except where the law does not allow it to be limited. If there is a contradiction between this agreement and the Terms regarding personal data, this agreement prevails. It is governed by the same law and the same courts as the Terms, and changes to it follow the same notice rule.

Annex 1. Details of the processing

Subject matterProviding the electronic invoicing service: building, signing, transmitting, storing and looking up tax documents.
DurationWhile your organization exists, plus the deletion period.
Data subjectsRecipients of your documents (your customers and, in purchase or withholding documents, your suppliers) and their contact persons.
DataName or legal name, type and number of identity document (NIT, DUI or other), NRC, business activity, address, phone, email and the details of the transaction (what was bought, amounts, taxes, payment method).
Sensitive dataNone expected. The service does not need it.
OperationsReceiving, validating, storing, signing, transmitting to Hacienda, generating the PDF, delivering through the API and webhooks, backing up and deleting.
Sub-processorsThose in the List of Sub-processors.

Annex 2. Technical and organizational measures

AreaMeasure
Encryption in transitHTTPS (TLS) across the whole service, including communication with Hacienda and with providers.
Credential encryptionHacienda credentials encrypted with AES-256-GCM; the master key is stored as a secret, separate from the database; each value is bound to its organization, environment and field. They are never returned by the API.
Encryption at restThe database and its copies are stored encrypted by the infrastructure provider.
Passwords and keysPasswords with salted PBKDF2-SHA256; API keys, codes and single-use links stored only as a hash.
Isolation between customersEvery query is filtered by the organization of the authenticated actor; there are automated isolation tests. In Platform, each key belongs to a single company.
Access controlRoles and permissions per user and per key; test or production mode per key; immediate revocation.
Abuse protectionRequest limits per key and per IP; incoming webhooks verified by signature; idempotency to avoid duplicate issuance.
TraceabilityAudit log of sensitive actions, visible to the customer; request logs for 30 days. Message bodies and full phone numbers are not logged.
DevelopmentOpen, reviewable source code; change review, automated tests and continuous integration before each deployment; a separate staging environment, with no production data.
ContinuityPoint-in-time recovery of the database of up to 30 days.
Internal accessAdministrative access to the infrastructure limited to essential staff.

Known limitations, which we publish so that you can take them into account: there is no external security audit and there are no certifications; the service does not yet offer email verification or two-factor authentication for dashboard users (which is why an invitation link must be shared only with its recipient); and there is not yet an automated process for rotating the master key.