Legal documents

Security Overview

Version:
1.0
Effective from:
17 August 2026

This is a courtesy translation. The Spanish version is the only binding one and prevails in case of any discrepancy.

Read the Spanish version

How we protect the information you keep in Agripino, which measures are actually in place, and which are not yet.

1. Our commitment

You trust us with your farm data: your animals, your staff, your costs and your income. That information describes your business rather precisely, and we treat it accordingly.

This document describes what we do today, not what we aspire to do. Section 7 expressly lists the measures we have not yet implemented.

2. Where your data lives

Agripino runs on our own infrastructure located in Costa Rica. The database, the authentication service and the application run on equipment under our direct control, not on a third-party managed cloud.

  • No exposed ports. The server accepts no direct inbound connections from the internet. All traffic enters through a Cloudflare tunnel, so the origin IP address is never exposed.
  • Minimal surface. The API gateway publishes only the authentication and data routes the application needs. Administration, schema editing, GraphQL, realtime and edge function services are disabled on public access.
  • Admin console off the internet. The database administration tool is reachable only through an SSH tunnel from the internal network.

3. Isolation between organisations

Agripino is a multi-tenant platform: several farms share the same database. Separation does not depend on application code but on the database itself.

  • Row Level Security. Every table has row-level security policies restricting each query to the authenticated person's organisation. Even if an application query were written incorrectly, the database would return no rows belonging to another organisation.
  • Automatic verification. An event trigger enables Row Level Security on every new table at creation time, so a table cannot be left unprotected by oversight.
  • Roles. Within an organisation, read and write permissions are controlled by role, and read-only users cannot modify records.

4. Encryption

  • In transit. All traffic between your browser and Agripino travels encrypted with TLS. We do not serve the application over unencrypted HTTP.
  • At rest. The volumes holding the database and its backups are encrypted. Files you upload are stored encrypted at rest at the object storage provider.
  • Passwords. Passwords are never stored in plain text. They are kept as salted cryptographic digests, and we can neither recover nor read them.

5. Staff access

Access to production systems is limited to those who need it to operate the service. In practice, and given the stage of the company, that group is very small.

  • Administrative server access uses SSH keys, not passwords.
  • We do not look at your farm data unless you expressly ask us to in order to resolve a support issue, or unless it is indispensable to restore service.
  • We do not sell, assign or share your data with third parties for their own purposes. The full list of third parties involved is in the Subprocessor List.

6. Backups and continuity

We take periodic backups of the database and keep them encrypted. Backups allow us to restore service after a hardware failure or an accidental deletion.

If you delete your account, your data disappears from active systems immediately and from backups as those rotate, within a maximum of 90 days.

7. What we do not yet have

We would rather say it before you ask. As at the date of this document we do not have:

  • SOC 2, ISO 27001 or equivalent certification.
  • Penetration testing by an independent third party.
  • Two-factor authentication for users.
  • A customer-visible audit log.
  • Round-the-clock security monitoring with an on-call rota.

These measures are on our roadmap. We will update this document when each one goes live, and not before.

8. Vulnerability reporting

If you discover a vulnerability in Agripino, please report it privately to [email protected] before disclosing it publicly.

We commit to acknowledging receipt within 3 business days, keeping you informed of progress, and taking no legal action against anyone researching in good faith, without accessing third-party data, without degrading the service and without exfiltrating information.

9. Security incidents

If an incident occurs affecting the security of your personal data, we will notify you without undue delay by email, describing what happened, which data were affected, what we did about it and what we recommend you do.

Provider identification

Razón social
PENDIENTE DE COMPLETAR (razón social registrada)
Nombre comercial
Agripino
Cédula jurídica
PENDIENTE DE COMPLETAR (3-101-XXXXXX)
Domicilio social
PENDIENTE DE COMPLETAR (dirección exacta), PENDIENTE DE COMPLETAR, PENDIENTE DE COMPLETAR, PENDIENTE DE COMPLETAR, Costa Rica
Teléfono
PENDIENTE DE COMPLETAR (teléfono de contacto)
Correo electrónico
[email protected]
Sitio web
agripino.io
Registrador del dominio
PENDIENTE DE COMPLETAR
Fecha de registro del dominio
PENDIENTE DE COMPLETAR
Alojamiento
Infraestructura propia ubicada en Costa Rica, con Cloudflare como proveedor de red y de almacenamiento de objetos.

License and attribution

Adapted from the Basecamp open-source policies, available under the Creative Commons Attribution 4.0 International licence. Text modified by Agripino to reflect its own infrastructure.

Basecamp open-source policies37signals LLC · CC-BY-4.0