Skip to content

Security

Your data, kept apart and kept safe

Every store gets its own database. Every staff sign-in needs a second step. Card details never reach our servers. This page explains how Elara One protects your business and your customers, in plain terms.

Report a vulnerability

Isolation

One store, one database

Stores on Elara One do not share tables with a store ID column to tell them apart. Each store gets its own database, and everything around it is separated too.

  • Its own database

    Each store’s customers, orders, CRM records and consent records live in a database of their own.

  • Its own search index

    Product search runs on a separate index per store, so one shop’s catalogue can never surface in another’s results.

  • Separate cache and media

    Cached data carries a per-store prefix, and uploaded media is kept under per-store paths.

Access

Every sign-in takes two steps

Most account takeovers start with a reused password. So two-step sign-in is required for every member of staff, on every store, with no way to switch it off.

  • Two-step sign-in, required

    An authenticator code or a passkey on every account, with recovery codes for a lost phone.

  • Remembered devices, on your terms

    Staff can skip the second step on a trusted device for up to 30 days. Your store sets the limit, or turns it off.

  • New-device emails

    A sign-in from a new browser sends the staff member an email, with a “This wasn’t me” button if it was not them.

  • Roles and permissions

    Give each person the access their job needs, and see everyone’s two-step status in one list.

  • Activity log, kept 730 days

    Staff actions and the order timeline are recorded and kept for two years, past card chargeback windows.

  • Limited support access

    Our support team works with limited access. It cannot switch on email tracking for you.

Payments

Card data never touches us

Shoppers pay through your own Stripe or PayPal account. Card details go from their browser straight to the payment provider. We only ever see the result.

  • Your own payment accounts

    Money goes to your Stripe or PayPal account. We take no fee on your sales.

  • No overselling

    Stock is locked as each order is placed, so two shoppers can never buy the last one.

API lock

Your keys only work from your sites

A store’s public API key is useless on its own. Browser calls are accepted only from the websites you register, and calls from servers must carry your secret.

  • Registered websites

    List your storefront addresses. Browsers on any other site are refused, and cross-origin access is set per store, never open to all.

  • Server secret

    Server-to-server calls carry a secret that never reaches the browser. Our starters refuse to start without it.

  • Report first, then enforce

    A new store watches for 14 days and reports what would be refused, then locks automatically.

  • Rotate without downtime

    Rotate your public key whenever you like. The old key keeps working for seven days while you deploy.

Encryption and backups

Backups we encrypt before they leave

Every store’s database is backed up every night. Each backup is encrypted on our own servers, with a key that never leaves them, before it is copied anywhere.

  • Encrypted before upload

    The storage provider holds the backups but cannot read them.

  • Kept for 14 days

    Each nightly backup is deleted after 14 days, so erased data does not linger.

  • A point-in-time copy too

    A separate encrypted copy, kept in UK storage, lets us restore to a moment rather than a night.

  • Encrypted in transit

    Every connection to the admin and the API uses HTTPS. Passwords are stored only as one-way hashes.

Data and hosting

Where your data lives

Your store runs in London, on UK servers. Encrypted backups are kept in the EU, which the UK recognises as giving adequate protection.

  • Regional hosting is on the roadmap

    Regional servers are planned, so stores can run closer to their customers. Until then, every store runs in London.

Privacy by default

Private unless you choose otherwise

The defaults protect your customers. Anything that shares more is a choice you make, and most of it waits for the shopper’s consent.

  • No third-party tracking pixels

    We add no ad pixels or tracking scripts. Tools like Google Analytics are your choice, and wait for the shopper’s consent.

  • Email tracking off by default

    Open and click tracking stays off until you confirm a lawful basis. Every marketing email has a one-click unsubscribe.

  • Consent you can prove

    Each shopper’s choices are recorded with the banner and notice versions they saw, and when.

  • Erasure that survives restores

    If a store is ever restored from a backup, every erasure, unsubscribe and withdrawn consent since is replayed before it reopens.

Compliance

Papers your team will ask for

We would rather show you what is true today than a wall of badges. Here is where things stand.

  • Available

    UK GDPR

    We act as your processor under a data processing agreement.

    Read the DPA
  • Available

    Sub-processors

    Every company that processes data for us, what it does and where.

    See the list
  • Planned

    Cyber Essentials

    The UK government-backed scheme. Planned; not certified yet.

Responsible disclosure

Reporting a vulnerability

If you think you have found a security problem in Elara One, please tell us privately at [email protected]. We will acknowledge your report within 3 working days and keep you updated until it is fixed.

[email protected]security.txt

If you follow these rules and act in good faith, we will not take legal action against you, and we will thank you publicly if you want us to. We do not run a paid bug bounty yet.

What to include

  • What you found and where: the address, endpoint or screen.
  • Steps to reproduce it, and what an attacker could do with it.
  • Your name or handle if you would like credit.

Please keep to these rules

  • Test only against your own store or our demo store. Never access, change or delete data that is not yours.
  • Do not run denial-of-service tests, spam, social engineering or physical attacks.
  • Give us reasonable time to fix the problem before you share it.

Questions from your security team?

Book a demo and we will walk your team through how Elara One handles your data, and answer your security questionnaire.

Get startedBook a demo