Privacy Policy
What personal data Krgo collects, what it uses it for, who it shares it with and how to exercise your rights.
Last updated September 16, 2026
1Controller
This policy explains how Krgo collects, uses, keeps and shares the personal data of the people who use the platform, under Law 8968 on the Protection of the Individual with regard to the Processing of their Personal Data and its regulations.
It is written from what the platform does today, not from what it might do. Every category of data, every provider and every cookie named here corresponds to something that exists in the system.
Pending decision
The registered company name, corporate identity number and address of the database controller depend on the company being incorporated.
2Who it applies to
It applies to anybody who visits the platform, creates an account, places an order or subscribes to the newsletter.
It does not apply to the origin marketplaces' own sites, nor to third-party sites the platform may link to, which are governed by their own policies.
3What we collect
The table lists every category of personal data the platform stores today, what it is used for and how long it is kept.
Named under the table are three things the platform does not store: an absence is a disclosure too, and it is the one most people want to read first.
| Data | What it is used for | How long it is kept |
|---|---|---|
| Given name, surnames, email address, hashed password and, when signing in with Google or Facebook, the profile photograph. | Creating the account, identifying the customer and verifying the email address. | For as long as the account exists. |
| The contact phone number on each delivery address. | So the courier can call at the moment of delivery. | While the address is saved. The number used on an order stays with the order. |
| Up to five delivery addresses: the recipient's name, the directions, province, canton, district and delivery zone. | Working out the cost of delivery inside Costa Rica and delivering the parcel. | While the account exists or until the customer deletes the address. The one used on an order is stored with it. |
| The customer's identity number. | Issuing the electronic invoice. | For as long as tax rules require. |
| Carts, orders, products and quantities, the full price breakdown, the measured weights, the tracking, the order's timeline, incidents and the package photographs. | Providing the service, reporting the order's state and handling complaints. | For as long as tax and customs rules require. |
| The payment's and the customer's identifiers at the gateway, the amount, the currency, the state and the date. | Charging for the order, reconciling it and invoicing it. | For as long as tax rules require. |
| The links sent to be read, which marketplace they belong to and the outcome of each request. | Answering the request, applying usage limits and not reading the same listing twice. | For as long as the account exists. |
| The rating, the text, the name the customer chooses to display, any photographs they contribute and the helpfulness votes. | Publishing the review on the product page. | For as long as the review is published. |
| Support requests: the topic, the subject, the messages, the photographs the customer attaches and the order or product they concern. | Answering the request and, when a person at Krgo decides so, opening an incident on the order. | While the account exists. |
| Feedback about the site: the rating, the topic, the comment if one is written and the page it was sent from. | Understanding what to improve on the platform. | While the account exists. |
| The products saved to favorites and when each was saved. | Showing the list so the customer can come back to those products. | Until the customer removes them or deletes the account. |
| The notifications shown in the account and, for each email sent, the address, the subject and whether it was delivered and opened. | Informing the customer and checking that the notices arrive. | For as long as the account exists. |
| The IP address and browser a session is opened with, the visitor's random identifier and the technical error records. | Keeping the session open, protecting the platform from abuse and fixing failures. | Sessions, until they expire or are ended. Error records, for the provider's retention period. |
- The card number, its expiry date and its security code. The payment gateway receives them directly and they never reach Krgo.
- Text messages. The platform sends no SMS, holds no messaging provider and does not verify the phone number.
- Proofs of payment. The only payment method is confirmed automatically against the gateway, so there is nothing to upload and nothing to store.
4Where the data comes from
Data reaches Krgo by four routes and no others:
- From the customer: what they type when registering, when asking for a link to be read, when filling in a delivery address and when paying.
- From Google or Facebook, when the customer chooses to sign in with one of those accounts: name, email address and profile photograph, and nothing else.
- From the payment gateway: the outcome of the charge and the customer's identifier in its system. Never the card details.
- From the use of the platform: the IP address and browser a session is opened with, and the technical records the application produces.
5What we use it for
The data is processed for these purposes only:
- Creating and maintaining the account, and verifying the email address.
- Working out the price of a shipment, issuing the order and charging for it.
- Buying the product at origin, importing it and delivering it to the address given.
- Issuing the electronic invoice and meeting tax and customs obligations.
- Reporting the state of the order and handling enquiries and complaints.
- Protecting the platform from abuse: usage limits, fraud prevention and fixing failures.
- Sending the newsletter, only to those who asked for it.
6On what basis
Processing is carried out with the informed consent of the data subject, given when the account is created and when these documents are accepted, and as far as necessary to perform the service the customer asks for.
Some processing is also carried out to meet legal obligations: electronic invoicing, keeping accounting records and the information importing requires.
Consent may be withdrawn at any time, without retroactive effect. Withdrawing it over data that is necessary to provide the service means Krgo can no longer provide it.
7Payment data
The card charge is processed by ONVO Pay, a payment services provider established in Costa Rica.
The fields the card is typed into are drawn by the provider itself inside the purchase page. The number, the expiry date and the security code travel straight to it: they do not pass through Krgo's servers, they are not written to its logs and they are in none of its tables.
What Krgo stores about a payment is the identifier the provider assigns it, the amount, the currency, the state and the date. That is enough to reconcile the order and to issue its invoice.
8Automated decisions and language models
The platform uses automatic tools on the product's data, not on the customer's: reading the listing from the origin marketplace, translation, tariff classification and weight estimation.
What is sent to those providers is the listing's link and its public content. They are not sent anybody's name, email address, phone number, address or order history.
No decision affecting the customer is taken by automated means alone. Reviewing the seller and reviewing a product before it can be bought are decisions made by a person, and an automatic answer is shown labelled as approximate while nobody has confirmed it.
Use of the platform is not used to build advertising profiles or to make decisions about anybody's credit or solvency.
9Who it is shared with
Krgo shares strictly what is necessary with the origin seller, the carriers, the customs broker and the delivery company, so the parcel can be bought, imported and delivered; and with the authorities where the law requires it.
Krgo also relies on infrastructure and service providers that process data on Krgo's behalf and under its instructions. None of them sells the data or uses it for its own purposes. They are these:
| Provider | What it does | Country | Receives personal data |
|---|---|---|---|
| Vercel | Hosts the application and serves its pages. | United States | Yes |
| Neon | The database where the account, the addresses and the orders live. | United States | Yes |
| Upstash | Short-lived storage for usage limits, quotas and payment idempotency keys. | United States | Yes |
| Trigger.dev | Runs the background tasks: reminders, warnings and payment reconciliation. | United Kingdom | Yes |
| Cloudflare R2 | File storage: the package photographs and the review photographs. | United States | Yes |
| Resend | Sends the transactional email and records its delivery. | United States | Yes |
| ONVO Pay | Processes the card charge. | Costa Rica | Yes |
| Apify | Reads the public content of a listing from its link. It receives no customer data. | Czech Republic | No |
| OpenAI | Translation of the listing, tariff classification and weight estimation. It receives the listing's content, not customer data. | United States | No |
| Sentry | Application error reporting, scrubbed of personal data before it is sent. | United States | Yes |
| Authentication, when the customer chooses to sign in with Google. | United States | Yes | |
| Meta | Authentication, when the customer chooses to sign in with Facebook. | United States | Yes |
Pending decision
The exact registered names of each provider and the data-processing agreements behind them have to be verified by the lawyer. What is named here are products, not companies.
10International transfer
Most of the providers in the table above are outside Costa Rica, mainly in the United States, and provide their services from there. Using the platform involves an international transfer of data to them.
Krgo transfers data only for the purposes described in this policy and requires each provider to apply security measures equivalent to its own.
By accepting this policy the data subject consents to that transfer, under article 14 of Law 8968.
11How long it is kept
Each category states its period in the table in section 3. As a general rule, data tied to an order is kept while the relationship is live and afterwards for as long as tax and customs rules require.
Data not tied to a legal obligation is deleted or anonymised once it is no longer needed for the purpose that justified it.
Pending decision
The exact retention period for accounting and customs information has to be confirmed by the lawyer, along with what must be kept after an account-deletion request.
12Security
Krgo applies technical and organisational measures in proportion to the data it holds:
- Passwords are stored irreversibly hashed and nobody at Krgo can read them.
- Traffic between the browser and the platform is encrypted.
- Files — the package photographs and the review photographs — are stored in a bucket with no public access: they are reached through signed, short-lived links generated on each request.
- Error reports are scrubbed before they leave: they carry no user identity, no cookies, and neither the headers nor the body of the request.
- Internal access is limited by role, and every administration screen demands its own.
- No system is infallible. Krgo will inform the data subject and the competent authorities if it detects a security breach affecting their data.
13Your rights
At any time the data subject may access the data Krgo holds about them, correct it where it is inaccurate, ask for it to be deleted where it is no longer needed, withdraw the consent given, and object to processing that is not indispensable to providing the service.
Requests are handled through the contact channels the platform publishes. Krgo may ask for reasonable identification before answering, precisely so that one person's data is not handed to another.
The data subject may also go to the Agencia de Protección de Datos de los Habitantes (PRODHAB) if they consider their request was not dealt with.
Pending decision
The response time and the formal channel for handling these requests are the lawyer's to settle, together with the procedure for identifying whoever makes one.
14Deleting the account
The data subject may ask for their account to be deleted. Doing so removes what identifies the person and what is no longer necessary: the delivery addresses, the open sessions, the notifications, the history of links sent and the newsletter subscription.
What the law requires to be kept is not deleted: paid orders, their breakdowns and the invoices issued. A paid order is a promise already kept, and its accounting record does not depend on the account continuing to exist.
Reviews already published are withdrawn or depersonalised at the data subject's request.
Pending decision
Today deletion is requested through the contact channels: the platform does not have a screen that carries it out yet. Building one is outstanding.
15Minors
The platform is aimed at adults with the capacity to contract and to pay with a card in their own name. Krgo does not knowingly collect data about minors.
If Krgo finds that it has collected data about a minor without the authorisation of whoever represents them, it will delete it.
16Cookies
The platform uses a small number of cookies, all of them necessary to function or to remember a preference. No advertising or audience-measurement cookies are used.
The detail is in the cookie policy, which forms part of this policy and is linked at the foot of this page.
17Newsletter and marketing messages
The newsletter is sent only to those who expressly asked for it. What is stored about a subscription is the email address and the language it was asked for in, and nothing else.
Every send carries the way to unsubscribe, and unsubscribing takes effect immediately.
An order's operational emails — the confirmation, the reminders and the state notices — are not marketing messages and cannot be switched off while the order is in progress.
18Database registration
Law 8968 requires databases intended for the distribution, dissemination or trading of personal data to be registered with PRODHAB.
Pending decision
Determining whether Krgo's database must be registered and, if so, registering it. It is a legal decision no project document settles.
19Changes to this policy
Krgo may update this policy. The version in force is the one published on this page, with its last-updated date.
Where a change widens the purposes of processing or brings in a new provider that receives personal data, Krgo will say so by email before it takes effect.
20Contact
Enquiries about this policy and the exercise of the rights described are handled through the channels Krgo publishes on the platform.
Pending decision
The controller's email address and the address for notices depend on the company being incorporated.