Security

This page describes the security measures BetterMap runs today. It is written from our live configuration, and it lists only what we actually do.

If you are reviewing BetterMap for your organisation and need something this page does not answer, email support@bettermap.com.

Where Your Data Is Hosted

  • The BetterMap website, our API, the AI service that reads floor plans, our database, the files you upload, our database backups and our analytics server all run in Amazon Web Services (AWS), in the London region (eu-west-2), in the United Kingdom.
  • Our database is MongoDB, which we run ourselves on an AWS server in London. It is not a third-party database service.
  • Requests to bettermap.com and our API pass through Cloudflare, which protects the site and delivers it quickly.
  • Our analytics software, PostHog, runs on our own server in the same AWS London region. See our Cookie Policy for what it collects.

The other companies that process data for us are listed, with what each one does, in our Data Processing Addendum.

Encryption

In transit. bettermap.com and our API are served over HTTPS only. Requests made over plain HTTP are redirected to HTTPS, and our servers send a Strict-Transport-Security (HSTS) header that tells browsers to connect to them over HTTPS only.

At rest.

  • The files you upload, such as floor plans and images, are stored in Amazon S3 with default server-side encryption (AES-256).
  • The disks of our database server are encrypted.
  • Database backups are stored in Amazon S3 in London with server-side encryption (AES-256).

Signing In

  • Sign-in is provided by Google Firebase Authentication. You can sign in with an email address and password, with Google, or with Facebook.
  • Passwords are handled by Firebase. Our own database does not store them.
  • Our API checks every Firebase sign-in with Firebase before it opens a BetterMap session.

Who Can See and Change a Map

  • Every map has an owner. The owner can invite team members and give each one a role: Map Manager, Store Manager, Content Manager or Viewer. Each role is a set of individual permissions, such as editing the map layout, editing store details or managing team members, and the owner can adjust them.
  • A Store Manager can be limited to specific stores on the map.
  • Our API enforces these permissions on the server for each request that reads or changes a map. Hiding a button in the app is never the only protection.
  • BetterMap administrators can access any map in order to provide support and operate the service. Where your account was supplied by an authorised BetterMap partner, that partner can also access the maps it manages for you.

Payments

Card details are entered into payment fields provided by Stripe and go directly to Stripe. They do not pass through our servers, and we do not store card numbers.

Our Own Access

  • Administrative access to our AWS account requires multi-factor authentication, and so does the account's root user.
  • Errors in the website, the API and the AI service are reported to Sentry, our error monitoring service, in its EU (Germany) region, so that we can find and fix problems quickly.

Backups and Retention

Our database is backed up every day to encrypted storage in AWS London. As our Privacy Policy states:

"Backups: Backup systems may retain data for up to 90 days after deletion from primary systems."

How long we keep personal data in other cases is set out in the Data Retention section of the Privacy Policy.

If Something Goes Wrong

As our Privacy Policy states, in the event of a personal data breach:

"We will notify the Office of the Commissioner for Personal Data Protection of Cyprus within 72 hours of becoming aware of a breach that is likely to result in a risk to the rights and freedoms of individuals"

and we will notify affected individuals without undue delay if the breach is likely to result in a high risk to their rights and freedoms. Where we process data for a customer, we notify that customer as set out in our Data Processing Addendum.

Reporting a Vulnerability

If you think you have found a security problem in BetterMap, please email security@bettermap.com. We reply within 24 hours on working days.

To help us act quickly, please include:

  • what you found and where (the page or API address)
  • the steps to reproduce it
  • what an attacker could do with it

While you investigate, please:

  • use only your own account and your own maps, and do not access, change or delete anyone else's data
  • do not run denial-of-service tests, spam or social engineering against our staff or customers
  • give us a reasonable time to fix the problem before you tell anyone else about it

We will keep you informed while we fix it.

Contact

Security questions: support@bettermap.com
Privacy and data protection: privacy@bettermap.com

BetterMap Ltd, Christaki Kranou 58, Yermasoyia, 4042 Limassol, Cyprus. Registration number HE 395187.


This page was last updated on October 3, 2026.