Terms of Service

1. Scope

This policy forms part of the Terms of Service and applies to everyone who uses Agripino, whether account holder or user invited to an organisation.

The list is deliberately short. We do not try to anticipate every conceivable misuse, but to describe clearly what we will not tolerate.

2. Prohibited uses

You may not use Agripino to:

• Unlawful activity. Any purpose contrary to Costa Rican law or to the law of the country where you operate, including falsifying sanitary, traceability or payroll records.
• Impersonation. Passing yourself off as another person or entity, or falsely stating your connection to a farm or organisation.
• Unauthorised access. Attempting to reach another organisation's data, circumventing authentication or row-level security controls, or probing the infrastructure without written authorisation.
• Degrading the service. Generating disproportionate automated load, running stress tests without prior coordination, or interfering with other people's legitimate use.
• Harmful code. Uploading files containing malicious programs, or using the platform to distribute them.
• Third-party content without rights. Uploading material you have no rights to, or personal data of third parties you are not entitled to process.
• Unauthorised resale. Reselling, sublicensing or providing the service to third parties outside your organisation without a written agreement with us.
• Harassment. Using free-text fields, record names or platform messages to harass, threaten or defame anyone, including our support staff.

3. Your staff data

Agripino includes payroll and time-tracking modules. When you record data about your workers, you are the data controller and you assume the obligations of Law 8968.

In concrete terms, it falls to you to:

• Inform your staff that their data is recorded in Agripino, for what purpose and who may consult it.
• Obtain their express consent where the law requires it, separately from the employment contract.
• Handle the access, rectification and suppression requests your workers put to you.
• Record only the data necessary for employment management, and not sensitive data you do not need.

We act as processor and give you the tools to comply. The relationship is governed by the Data Processing Agreement, incorporated into the Terms as an annex.

4. Accounts and credentials

• Each user must have their own account. Sharing credentials makes it impossible to know who did what and compromises the traceability of records.
• You are responsible for keeping your password confidential and for telling us immediately if you suspect unauthorised use.
• When someone leaves your organisation, it is for you to deactivate their access on the platform.

5. What we do about a breach

We would rather talk than suspend. Unless there is immediate risk to other users or to the integrity of the service, we proceed as follows:

• Notice. We tell you in writing which conduct we consider contrary to this policy and give you a reasonable period, no less than 10 business days, to correct it.
• Suspension. If the breach persists after notice, we may suspend the account. Suspension is limited to what is necessary and is lifted once the cause is remedied.
• Termination. For a serious, unremedied breach we may terminate the contract. In that case we refund the pro-rata unused portion of the current cycle and keep your data available for export for 30 calendar days.

Immediate suspension without prior notice is reserved for manifest unlawful activity, attacks on the infrastructure, or a real risk to third-party data. Even then we tell you the reason within the following 24 hours.

6. How to report abuse

If you observe a use of Agripino that contravenes this policy, write to [email protected] with whatever detail you can provide. We review every report.

1. Availability commitment

We commit to keeping Agripino available 99.5 % of the time in each calendar month, measured as set out in section 3.

A monthly 99.5 % allows roughly 3 hours and 39 minutes of downtime per month. We would rather commit to a figure we can sustain with the infrastructure we actually have than announce a 99.99 % we would not be in a position to guarantee.

2. Definitions

• Downtime. A period during which the application does not respond to valid sign-in or data read requests, or returns server errors continuously for more than five consecutive minutes.
• Scheduled maintenance. Work announced at least 48 hours in advance by email, carried out preferably between 22:00 and 05:00 Costa Rica time.
• Total time in the month. The number of minutes in the relevant calendar month.

3. How it is measured

Monthly availability is calculated by taking the total time in the month, subtracting recorded downtime, and dividing the result by the total time in the month.

The following do not count as downtime:

• Scheduled maintenance, up to a maximum of 4 hours per month.
• Interruptions caused by the customer's network, internet provider or equipment.
• Interruptions arising from use contrary to the Acceptable Use Policy.
• Force majeure events, as understood under article 830 of the Commercial Code and article 702 of the Civil Code.

If you disagree with our measurement, you may submit your own records and we will review them in good faith.

4. Credits for shortfall

If in any calendar month we fail to meet the commitment, you are entitled to a credit against that month's fee:

To claim the credit, write to [email protected] within 30 calendar days of the end of the affected month. The credit is applied to the next invoice or, if the contract has ended, refunded by the same payment method used.

5. Prolonged outages

If the service remains continuously unavailable for more than 72 hours, you may terminate the contract immediately by written notice, with a pro-rata refund of the unused portion of the current cycle and without any penalty.

6. Support response times

Independently of availability, we commit to the following first-response times on Costa Rican business days:

The support channel is [email protected]. The formal complaints channel, free of charge under article 195 of the Regulation to Law 7472, is [email protected].

1. How to cancel

You will find the cancellation option in your organisation settings. Cancellation takes effect at the end of the current billing cycle, so you keep access for the time you already paid for.

If you prefer to do it in writing, you can write to [email protected] and we will process it. It is not required, simply another route.

2. Right of withdrawal

Under article 40 of Law 7472 and article 72 of its Regulation, you have eight business days from the conclusion of the contract to withdraw, without needing to justify your decision and without penalty.

Withdrawal is exercised through the same medium you used to give consent, and the refund is made by the same payment method.

Example: if you take a monthly plan and withdraw on the fifth business day having used the service for five days, we refund the proportion corresponding to the remaining days of the cycle.

3. Other refunds

Besides withdrawal, we refund in the following cases:

• Billing error. If we charge you an amount that was not due, we return it in full as soon as we verify it.
• Prolonged outage. If the service is unavailable for more than 72 continuous hours, you may terminate with a pro-rata refund, under the Service Level Agreement.
• Objected subprocessor change. If you reasonably object to a new subprocessor and we cannot offer an alternative, you may terminate with a pro-rata refund.
• Termination by us. If we terminate the contract without any breach on your part, we refund the pro-rata unused portion.

Outside these cases, and outside withdrawal, monthly fees already consumed are not refunded. Plans are month to month with no minimum term, so you can cancel whenever you like to avoid being billed for the next cycle.

4. What happens to your data

On cancellation:

• You keep access until the end of the paid cycle, including the ability to export all your information.
• After that date, we keep your data available for export for a further 30 calendar days in read-only mode.
• Once that period elapses, we delete your data from active systems. Encrypted backups retain it for up to 90 further days while they rotate.

You may request immediate deletion at any time by writing to [email protected]. We will handle it within the 5 business days set by article 7 of Law 8968.

5. Price changes

If we change the price of your plan we will tell you at least 30 calendar days in advance. The new price will apply only from the following billing cycle.

6. Taxes

Published prices include the 13 % Value Added Tax applicable in Costa Rica and are shown with a breakdown, under article 187 of the Regulation to Law 7472. Refunds are calculated on the amount actually paid, tax included.

1. Parties and subject matter

This agreement is entered into between the natural or legal person holding the account, hereinafter the Controller, and PENDIENTE DE COMPLETAR (razón social registrada), hereinafter the Processor.

This agreement forms an integral part of the Terms of Service and is incorporated into them as an annex, so that its content is presented alongside the main contract rather than by reference to an external document.

2. Definitions

Personal data

Any data relating to an identified or identifiable natural person, under article 3 of Law 8968.

Processing

Any operation on personal data: collection, recording, storage, consultation, modification, transfer or deletion.

Data subject

The natural person the data refers to: a farm worker, a supplier, a client.

Subprocessor

A third party engaged by the Processor that processes personal data on behalf of the Controller.

3. Scope of processing

The Processor processes the following data on behalf of the Controller:

Processing is carried out by automated means, for the term of the service contract and for the retention periods set out in section 9.

4. Processor obligations

The Processor undertakes to:

• Process data only on instructions. It will not use the data for its own purposes, nor to build profiles, nor to train models, nor for any purpose other than delivering the contracted service.
• Not sell or assign the data. Under no circumstances will it commercialise, disseminate or distribute the data to third parties.
• Maintain confidentiality. The duty of secrecy survives the end of the contractual relationship, under article 11 of Law 8968.
• Apply security measures. Those described in the Security Overview, which forms part of this agreement.
• Assist the Controller. It will provide the technical means to handle access, rectification and suppression requests received from data subjects.
• Notify incidents. It will report without undue delay any security breach affecting data processed on behalf of the Controller, with the information needed for the Controller to meet its own obligations.
• Return or delete. On termination it will proceed as set out in section 9.

5. Controller obligations

The Controller represents and undertakes to:

• Have informed data subjects, under article 5.1 of Law 8968, of the existence of the database, its purposes, who may consult it and how to exercise their rights.
• Have obtained express consent where the law requires it, independently of any other document, and to retain proof of having done so.
• Record only the data necessary for the stated purposes, refraining from entering sensitive data it does not need for farm management.
• Handle, in its capacity as controller, requests from data subjects within the 5 business days set by article 7 of Law 8968.
• Keep the list of users with access to its organisation up to date and revoke access for those who leave.

6. Subprocessors

The Controller gives the Processor general authorisation to engage subprocessors, subject to the following conditions:

• The current list is published in the Subprocessor List and forms part of this agreement.
• The Processor will impose on each subprocessor, in writing, data protection obligations no less demanding than those in this agreement.
• Any addition or replacement will be notified at least 10 business days in advance.
• The Controller may object in writing within 30 calendar days of the notification.
• If the objection is reasonable and no viable alternative exists, the Controller may terminate the contract without penalty, with a pro-rata refund of the unused portion.

The Processor is liable to the Controller for the acts and omissions of its subprocessors as if they were its own.

7. International transfers

The main database remains hosted in Costa Rica. File storage and network routing involve transfer to Cloudflare infrastructure outside the country.

Under Chapter III of Law 8968, those transfers rest on the informed consent of data subjects, which the Controller undertakes to obtain, and on contractual confidentiality and security commitments with the subprocessor.

8. Verification

The Controller may request, once a year and with 30 calendar days' notice, reasonable information to verify compliance with this agreement. The Processor will respond in writing and may satisfy the request with documentation of its security measures.

If the Controller requires an on-site audit, its scope, date and cost must be agreed in advance, and it may not compromise the confidentiality of other customers' data.

9. Return and deletion

On termination of the service contract:

• The Controller retains read-only access and export capability for 30 calendar days.
• After that period the Processor deletes the data from active systems.
• Encrypted backups retain copies for up to a further 90 calendar days while they rotate, without being accessible for ordinary use.

After deletion the Processor retains, for the sole purpose of evidencing compliance with its legal obligations, the record of acceptance of the contractual documents. That record contains no farm or staff data.

10. Liability

Each party is liable for breach of the obligations this agreement places on it.

11. Term and applicable law

This agreement takes effect on acceptance of the Terms of Service and remains in force for as long as the Processor processes data on behalf of the Controller.

It is governed by the laws of the Republic of Costa Rica, in particular Law 8968 and its Regulation, and submits to the jurisdiction of the Costa Rican courts.

For any communication relating to this agreement: [email protected].

1. Purpose of this list

When a customer uses Agripino, we process personal data on their behalf: that of their staff, their suppliers and their clients. In that relationship the customer is the data controller and Agripino is the processor. To deliver the service we rely on a small number of third parties, which act as subprocessors.

This list forms part of the Data Processing Agreement and is kept current. Any change is communicated at least 10 business days in advance, as described in section 5.

2. Our own infrastructure

This means your farm data, staff records and financial movements are stored in Costa Rica, on equipment we administer directly. There is no external cloud provider with access to that database.

We use PostgreSQL with Supabase in self-hosted mode. Supabase is open-source software that we run ourselves; Supabase Inc. plays no part in the processing and has no access to the data.

3. Current subprocessors

The following third parties take part in the processing. None is authorised to use the data for its own purposes.

4. International transfers

File storage and network transit involve transferring data outside Costa Rica. Pursuant to Chapter III of Law 8968, those transfers rest on the informed consent of the data subject and on contractual confidentiality and security commitments with the subprocessor.

The main database, which holds most of the farm, staff and financial information, remains in Costa Rica and is not transferred.

5. Changes to this list

Before adding a new subprocessor:

• We publish the change on this page and notify the customer by email at least 10 business days in advance.
• The customer has 30 calendar days to object in writing.
• If the objection is reasonable and we cannot offer an alternative, the customer may terminate the contract without penalty and with a pro-rata refund of the unused portion of the current cycle.

To receive these notifications or to consult the change history, write to [email protected].

6. What we do not use

For the avoidance of doubt, and because their absence matters as much as their presence, we record that Agripino does not use:

• Web analytics or behavioural tracking tools.
• Advertising networks or third-party pixels.
• Payment processors with access to platform data.
• Third-party SMS or mapping services.
• Third-party artificial intelligence services that receive user data.

If any of these are introduced in future, this list will be updated under the procedure in section 5 before they go into operation.

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.

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.