Data residency
PLANA Business Cloud runs on infrastructure located in Sofia, Bulgaria. This page describes exactly where your data lives.
Headline
Every part of your PLANA Business Cloud tenant — database, filestore, backups, audit logs — is in Exoscale's bg-sof-1 region in Sofia, Bulgaria. EU jurisdiction. No US-cloud exposure for your business records.
Breakdown
| Data | Where | Country |
|---|---|---|
| Your tenant Odoo database | Exoscale SKS cluster, bg-sof-1 | Bulgaria |
| Your tenant filestore (attachments) | Exoscale block storage / NFS, bg-sof-1 | Bulgaria |
| Daily backups (DB + filestore) | Exoscale SOS, bg-sof-1 | Bulgaria |
Your account record + sessions on my.planapulse.ai | Same SKS cluster | Bulgaria |
| Your BOS chat history (Redis, 7–30 days) | Same SKS cluster | Bulgaria |
| Your audit logs (Loki, 90 days) | Same SKS cluster | Bulgaria |
| Authentication data (Authentik) | Same cluster | Bulgaria |
| Your invoices and payment records | Same database; same residency | Bulgaria |
| BOS chat AI inference | Anthropic API | USA (only exception) |
| Stripe payment processing | Stripe Ireland | Ireland (EU) |
| Marketing emails sent from PLANA | Mailu on Hetzner | Germany (EU) |
The single exception to "everything in Bulgaria" is AI inference in BOS chats — when you ask a BOS agent a question, the message and any tool results are sent to Anthropic's API for the model to process. We have a DPA with Anthropic that:
- Prohibits using your data for model training
- Limits retention to ~30 days for operational purposes
- Provides EU contractual clauses (SCCs)
If your policy strictly forbids US-hosted LLM inference, talk to your account manager — Enterprise tier supports configuring a different inference provider.
Why Bulgaria
- Customer alignment — most PLANA customers are Bulgarian SMBs; keeping data in your own country simplifies compliance
- EU jurisdiction — GDPR applies; Bulgarian CPDP supervises
- Latency — your office is ~5 ms from the cluster; the UI feels native
- No US CLOUD Act exposure — Exoscale is Swiss-EU
- Trust — for some customers, "our data is in Bulgaria" is the answer that ends the procurement conversation
What does NOT leave Bulgaria
- Your customer records
- Your vendor records
- Your invoices, bills, payments
- Your stock movements
- Your employees' personal data
- Your bank transactions (PSD2 data)
What may leave Bulgaria (cataloged honestly)
- BOS AI chats — Anthropic in the USA (described above)
- Email PLANA sends to you — Mailu on a Hetzner box in Germany
- Stripe payment processing — your card data goes directly to Stripe Ireland; PLANA never sees the PAN
- DNS lookups — public DNS resolvers don't store your business data, but the DNS query patterns are public infrastructure
What this means for GDPR
PLANA is your processor; you (your company) are the controller for your customers' and employees' personal data. The DPA you signed with PLANA Digital documents this. Sub-processors (Exoscale, Anthropic, Stripe, Hetzner) are listed in the DPA's Annex II.
If your customer or employee exercises a GDPR right (access, rectification, erasure):
- They make the request to you (their controller)
- You use PLANA's tools to fulfil it
- See Activities → Data exports
What this means for cross-border employees
If you have employees outside Bulgaria, their data sits in Bulgaria. Cross-border within the EU is fine (GDPR provides for it). Outside the EU, you need to ensure your own transfer mechanism is in place (SCCs, adequacy decision, or equivalent).
Where to read more
- Backups — backup residency
- Support channel — how to escalate compliance questions
- Platform → Data residency — the policy view in technical depth
- Platform → Compliance — GDPR, DPA, sub-processors