Skip to content

ES · Español

dev@burgo.dev

Legal · Burgo

← All documents

Sub-processors and data location

List of the providers involved in Burgo’s services, what they do, what data they see and which country they are in.

Version
1.0
In force since
Applies to
burgo.dev · Account · Cancha · Pique · Brío · Cuadre · Sobre · Cabal
Language
Leer en español
Draft v1.0 pending legal review

This text is not legal advice or a final commitment. Points marked with ⚖️ need a lawyer’s review before monetising or offering the service to third parties.

What this list is for

Burgo uses external providers to host the services, send email or connect to other services. Listed here are those that exist today, what they do, what data they can see and which country they are in. When Burgo acts as a business’s processor (Cabal), this is the list of sub-processors that business authorises; see the Cabal data processing agreement.

Controller: Burgo, operated by José Burgos (natural person). Contact: dev@burgo.dev.

Current providers

  • Contabo (VPS). Hosting of the applications, databases, files and logs. Where the data is: United States. What data: All data of the services described in the privacy policy. Scope: burgo.dev, Account, Cancha, Pique, Brío, Cuadre, Sobre and Cabal.
  • Cloudflare. DNS for the burgo.dev domain and inbound email forwarding (from dev@burgo.dev to José’s mailbox). Where the data is: Provider’s global network. What data: DNS queries and the content and metadata of emails sent to dev@burgo.dev. Scope: Domain and contact email of all sites.
  • Google (Gmail). Mailbox where José receives the email forwarded from dev@burgo.dev. Where the data is: According to Google’s infrastructure. What data: Emails you send us (inquiries, rights requests, reports). Scope: Only handling of those who write to us.
  • Postfix propio. Our own outbound mail server (application notices and messages), with no sending intermediary. Where the data is: On the same VPS (United States). What data: The recipient’s email address and the message content. Scope: Account, Cabal and notices of the applications that send email.
  • Telegram. Sobre alert bot, only if the user links it. Where the data is: According to Telegram’s infrastructure. What data: Telegram identifier and the text of the alerts sent. Scope: Sobre only.
  • Square. Card payments in client projects that use it. Not used on burgo.dev or in Burgo’s apps. Where the data is: United States (per the provider). What data: Payment data that the end customer enters into the Square flow; Square handles it as the client business’s provider. Scope: Only client projects that contract it.
  • GitHub. Source code hosting. No user data is uploaded. Where the data is: According to GitHub’s infrastructure. What data: Code and its history; no users’ personal data. Scope: Development of all projects.

Where the data is

The applications and databases are hosted on a Contabo virtual server (VPS) in the United States. This means data of users from Venezuela and other countries is stored outside their country. There are no servers of our own in Venezuela.

⚖️ Pending lawyer review. International transfer clauses, and whether an agreement with each provider is needed or their standard terms suffice. The exact location of each provider, which today is stated according to their infrastructure.

What does not exist

We use no advertising providers, third-party analytics, embedded social networks or third-party maps on these sites. Square is only involved in client projects that contract it, never in Burgo’s apps.

Changes to the list

If we add or change a provider that sees personal data, we will update this list and give notice of material changes at least 15 days ahead, and to Cabal businesses at their email. Version 1.0, in force since November 2, 2026.