A GDPR compliant website builder: EU-hosted, in a database of your own, and yours to export
Three plain questions deserve plain answers. Where does it live — the EU. Who can see it — your team, exactly as far as you allow, plus support in a read-only mode when you ask for help. Can you get it out — yes, and not through a support ticket: real exports you run yourself.
The short version
Run from the EU
A database of your own
Access you control
Exports you trigger yourself
Not a row in a shared table
A lot of "multi-tenant SaaS" means your data sits in the same tables as every other customer's, distinguished only by an ID column and the hope that every query remembered to filter on it. Olmira doesn't work that way: every account is provisioned with its own database, with its own generated credentials — a real, separate MySQL database, not a partition, and one application can't read another's without holding that account's own credentials. That's already true for every plan, from the trial up. Pro+ accounts are provisioned on Olmira's isolated tier, which gets its own separate database and its own connection endpoint rather than sharing the one the lower tiers use — the strongest data-separation tier Olmira offers today. The application and its databases run in an EU region.
Access is a setting, not a mystery
Inside your account, you decide who sees what. Team members start at a role — Viewer, Editor, Admin — and you can go finer than that: grant or revoke individual capabilities per person, build a named role like "Store manager" with exactly the permissions that job needs, or hand a contractor access to one workspace only, scoped to the one module they're working on. That last one needs a second seat, so it starts on Starter; the trial is a single seat. Nobody inherits more than you gave them. On Olmira's side, our support team can look at your account only in a read-only mode, only when you're getting help, time-limited and individually revocable — writes are blocked at the gate regardless of who's looking, and every session like that is logged. Nobody at Olmira can quietly edit your business on your behalf.
Two exports, because two kinds of data deserve two answers
"Can I get my data out" has two answers, because personal data and business records aren't the same request. Your own account — profile, any orders or support conversations tied to you personally, your sessions, your consent history — downloads as a single JSON file the moment you click Download my data in Account settings. No wait, no ticket, no operator in the loop. Your business's records — the catalogue, the order book, invoices, tax summaries — export from the screens that already show them, as CSV, XLSX or PDF, whenever you want them, not bundled behind one all-or-nothing archive. That split is deliberate: it's faster than a single mega-export would be, and it means you're never stuck waiting on anyone to hand your own data back to you. If you ever want to close the account entirely, that's also self-serve, with a password re-confirmation — the exact retention window afterwards is in the privacy policy, not restated here as a number that could drift out of sync with it.
Getting your data, right now
1
Your personal data
2
Your catalogue
3
Your orders and invoices
4
Everything, if you ever leave
The rest of how Olmira is run
White-label
Import your data
No. Every account gets its own database, with its own credentials, from the start — not a shared table distinguished by an ID column. Pro+ accounts are provisioned on the isolated tier, with a separate database and connection endpoint from the one lower tiers share.
Only in a read-only mode, only when you're being helped, time-limited and revocable, with every session logged. Writes are blocked at the gate — nobody at Olmira edits your account on your behalf.
The application and the databases behind it run in an EU region. Uploaded files are served from a global object store and CDN so images load quickly wherever your visitors are — that is a separate question from where your business records are kept, so if the storage location of uploaded media matters to your compliance position, ask us before you commit.
Two ways, both self-serve: your personal account data downloads as JSON instantly from Account → Privacy; your business records — catalogue, orders, invoices — export as CSV, XLSX or PDF from the screens that hold them, whenever you want, for as long as the account is open.
Not today — data comes out per record type (catalogue, orders, invoices, your personal account) rather than as one combined archive. In practice that's usually faster: you export what you need instead of waiting on one large bundle.
Yes, at a fine grain — role, individual capability, and a scoped grant limited to one workspace and one set of modules. Seats are what set the floor: the trial has one, so there's nobody to scope; Starter has two, Pro ten, Pro+ twenty-five. Nobody on your team automatically sees more than you gave them.