Security

How this site protects what you send it.

How we handle the tender documents you send us, and the controls on this website. If you are evaluating Remo and need detail beyond this, ask — we would rather answer a hard question before a pilot than after one.

Last updated 23 September 2026

Your tender documents

A tender package is the most commercially sensitive thing on a project: your bill of quantities and every contractor's prices, in one place. Five commitments govern how we hold it.

Never used to train models

Your documents are not used as training data. What you send us is used to produce your analysis and nothing else.

Isolated per client

Each client's documents are kept separate. A tender you send us is not reachable from any other client's engagement.

Stored in the UAE

Tender documents are stored within the country. They do not leave the UAE for processing.

Deleted on request

Tell us and we delete your documents. You do not need to give a reason, and there is no charge.

We will sign your NDA

We are happy to sign your non-disclosure agreement before you send anything at all. If your procurement process requires one, that is the normal way to start, not an exception.

This website

The rest of this page covers byremo.ai itself — the site you are reading and the enquiry form on it.

In transit

The site is served over HTTPS only, with HSTS set for two years including subdomains, so browsers refuse to fall back to an unencrypted connection.

A content security policy restricts what the page may load and where it may send data: scripts, styles, fonts and images come from this origin, plus the two named analytics providers and nothing else. Framing is blocked outright, MIME sniffing is disabled, and referrer information is trimmed when you follow a link away from the site.

The enquiry endpoint

The form posts to a single endpoint, which:

• Accepts submissions only from this website's own domains
• Re-validates every field on the server, regardless of what the browser allowed
• Escapes every value before it appears in the notification email
• Rate-limits repeated submissions from the same connection
• Uses a hidden honeypot field and a minimum completion time to reject automated submissions

At rest

Enquiries are stored in managed Postgres, hosted by Neon. Access is limited to the Remo team.

Your IP address is never written down. It is hashed with a secret salt on arrival and only the hash is stored, which is enough to recognise repeat abuse from one connection and not enough to identify you.

There is an export endpoint for moving enquiries into a CRM. It is unusable without a secret token, compared in constant time so the token cannot be guessed by measuring response times, and it is off entirely when no token is configured.

What we deliberately do not do

• We do not store raw IP addresses
• We do not take payment details, and there is nothing on this site to log into
• We do not record the enquiry chat in session replay — it is explicitly masked, so names, emails, phone numbers and notes never reach the recording
• We do not sell or share enquiry data for advertising

Reporting a problem

If you find a vulnerability in this site, email remo@byremo.ai with enough detail to reproduce it. We will confirm receipt and tell you what we are doing about it. Please give us a reasonable chance to fix it before publishing.

What we collect and why is on the privacy page.