Security

Questions: hola@estibra.com · Legal notices and vulnerability reports: legal@estibra.com

1. What this page is

You are letting a robot into the software your business runs on. This page says exactly how much of it the robot can reach, what we store, who can see it, and how you take the access back. Everything below describes how Estibra works today. If something changes, this page changes with it and the date at the top moves.

Estibra is a service, not a box. There are two parts:

• The cloud robot, which runs on Estibra’s servers and logs into your courier software the same way one of your employees would.
• A 5 MB local agent, which you install on the PC next to the printer. It prints and it talks to your dimensioner. Nothing else.

2. How your credentials are stored

1. You type the robot user’s password once, yourself, inside your own panel at yourcompany.estibra.com. It is never typed into WhatsApp, into email, or into any form on this website.
2. It is encrypted at rest, with a separate key for each customer.
3. We cannot read it back out. The panel can use it to log in; it cannot display it.
4. It is changed automatically every day.
5. It is used for one purpose only: logging into your own account, to do the work you turned on. It is never used to reach any other account, at your company or anywhere else.
6. If you would rather not store a password with us at all, disable the robot user in your own system and the stored password stops being worth anything the moment you do.

3. The robot user is not your user

The robot never logs in as a person.

• You create the user, inside your own courier software, and you name it. We suggest Estibra Robot so it is obvious in your logs.
• Give it data-entry permissions only. It should be able to enter packages and waybills, and nothing else — no admin, no deleting, no rates, no prices, no user management.
• Every action shows up under that name, with a timestamp, inside your own system. Your audit trail stays honest and you can read it without asking us for anything.
• If only your software provider can create users, ask them. It is a phone call.

We will not ask you for an owner’s login or a person’s login, and you should refuse if anyone ever does.

4. What the robot can do, and what it cannot

It can:

• Log into your own account, on your own screens, and type what a data-entry employee would type.
• Read the pre-alert emails you forward to your Estibra address, to pull out tracking data.
• Read the label photos your team uploads.
• Take weight and dimensions from your dimensioner and enter them.
• Print labels and documents on the printers and trays you chose.
• Keep a log of every action it took, which you can read in your panel.

It cannot:

• Open your courier software from your own PC. That happens on Estibra’s servers, not on your machine.
• Read files, folders, or the screen of the PC where the agent is installed.
• Accept an inbound connection. The agent calls out; nothing calls in, and no port is opened.
• Reach any account other than yours.
• Delete records, change rates or prices, or open admin screens — the robot user has no permission for any of it.
• Read email you did not forward.
• Bulk-export your courier software’s database.
• Install a camera or watch your warehouse. Estibra has none.

5. What Estibra can see

• The screens the robot user can reach — the same ones a data-entry employee sees.
• The pre-alert emails you forward, and only those.
• The label photos your team uploads.
• Weight and dimensions from your dimensioner.
• The action log the robot writes.
• Your account details: company name, the people you gave panel logins to, and billing records.

What Estibra cannot see:

• Any email you did not forward.
• Your bank accounts, your card processing, or your customers’ payments.
• Admin screens, rates, or anything the robot user has no permission for.
• Files on your warehouse PC.
• Another customer’s data. Every warehouse is kept separate.

We do not sell your data, we do not use it for advertising, and we do not use it to train AI models.

6. Who can look at your data, and when

• Access is least-privilege and logged.
• No person at Estibra reads your forwarded email or your operational records except to fix a specific failure you reported, and that access is written to a log.
• Everyone with access is under a confidentiality obligation.
• If you ask us to stop looking, we stop, and the robot keeps running or pauses — your call.

7. Audits, rotation, and monitoring

• Two security audits so far. If you want the detail of who ran them and what was in scope, ask on a call. That answer belongs in a conversation, not on a public page.
• The robot password rotates every day, automatically.
• A guardian agent watches the robot 24 hours a day and raises an alert the moment the robot stops, gets stuck, or does something it was not asked to do.
• What Estibra is not: we have no SOC 2 report and no ISO 27001 certificate. Not yet. We would rather say so than let you assume otherwise.

8. Who else touches your data

A small number of vendors sit behind the service — hosting, email delivery, and payments. The current list, with what each one does and where it runs, is kept with our data processing terms. Ask at hola@estibra.com and we send it the same day.

If we add a new vendor that touches your operational data, we tell you before it starts, and you can cancel that month if you do not want it. Everything is month-to-month, so saying no costs you nothing.

9. If something goes wrong

Our incident steps, in order:

1. Stop the bleeding. Pause the affected robot, cut off the access being misused, or take the affected part of the service down.
2. Tell you. See the notice commitment below.
3. Say what we know. What happened, when, which of your data was involved, what we have done, and what you should do on your side.
4. Fix it and write it down. You get a written follow-up once the cause is closed out.

Breach notice: within 72 hours. If we determine that a security breach involved your data, we notify you within 72 hours of that determination, by email to the contacts on your account, and by phone or WhatsApp if the situation is urgent. Florida law gives a company in our position up to 10 days to tell you. 72 hours is the tighter promise we make on purpose, and it is written into our data processing terms as well as this page.

A robot that stops is an outage, not a breach. Outages are covered on the service level and cancellation page.

10. How to revoke access in one minute

Three ways. All three are yours, none of them needs our permission, and each takes under a minute.

1. Press Pause robot in your panel. It stops mid-task, immediately.
2. Disable the robot user inside your own courier software. You do this in your own system, without telling us first. The robot is locked out in seconds.
3. Delete the forwarding rule and uninstall the agent. Then no mail arrives and nothing prints.

Doing any of these does not cancel your account and does not delete anything. To cancel and have your data deleted, see the service level and cancellation page.

11. Reporting a vulnerability

If you found a weakness in Estibra, please tell us before you tell anyone else.

Write to legal@estibra.com. A person reads that inbox. If you have not heard back in 3 business days, write to hola@estibra.com.

Please include: what you found, the steps to reproduce it, and what an attacker could do with it. Screenshots help. Please do not include any real customer data in your report.

What we promise you:

• A first response within 3 business days, from a human, in English or Spanish.
• We will tell you what we found and when we expect to fix it.
• If you reported in good faith and followed the rules below, we will not pursue legal action against you, and we will not ask your employer or your hosting provider to.
• Credit on this page if you want it, and no credit if you would rather stay anonymous.
• No bounty money at this stage. We would rather say that up front than waste your time.

The rules, so the safe harbor holds:

• Only test against your own account or an account you were given for testing.
• Do not access, download, or modify another customer’s data. If you stumble into it, stop and tell us.
• Do not destroy, degrade, or disrupt the service. No denial-of-service, no load testing, no spam, no social engineering of our people or our customers, and nothing physical.
• Give us a reasonable time to fix it — 90 days is the norm — before publishing.

Out of scope: findings from an automated scanner with no working proof, missing best-practice headers with no exploitable impact, and anything that requires an already-compromised device.

12. Independent product

Estibra is not affiliated with, sponsored by, or endorsed by CargoTrack or any other courier-software vendor. Estibra operates your own licensed account, using a user you create, with your authorization.

13. Changes to this page

If we change something material on this page, we email the contacts on your account at least 30 days before it takes effect, and we move the date at the top. Security questions go to hola@estibra.com. Vulnerability reports and legal questions go to legal@estibra.com. Written notice by mail goes to Estibra LLC, Miami, Florida.