Security
Your data, kept apart and locked.
PerformHub holds a copy of your point-of-sale and online-store data to give you sales, stock and customer reports. This page says, plainly, how that copy is protected.
State as of 24 October 2026. We update this page when something changes.
Layers around your data
- A database of your ownwith its own database login
- An encrypted vaultevery database file and backup, AES-XTS 512-bit
- Encrypted contact detailsnames, phones and e-mails, AES-256-GCM
- Hourly off-site copiesEU data centre, locked against early deletion
- Two-step sign-inwith an authenticator app
At a glance
The short version, for IT teams.
- Company separation
- A separate database for each company, with its own database login that can reach no other database.
- In place
- Encryption at rest
- Database files and backups in an encrypted volume (LUKS2, AES-XTS, 512-bit key). The unlock key is not kept on the server.
- In place
- Customer contact details
- Encrypted inside the database (AES-256-GCM); the key is kept outside the database.
- In place
- Encryption in transit
- HTTPS only, TLS 1.2 or 1.3, with HSTS. The link to Retail Pro requires AES-256.
- In place
- Backups
- Full every night, changes every hour, checked when written; full restore tested every Sunday.
- In place
- Off-site copy
- Encrypted on our server, then copied every hour to an EU data centre. Locked against early deletion: daily copies 30 days, monthly 12 months. Restore tested.
- In place
- Hosting
- One dedicated server, rented from Contabo GmbH, in the European Union. Databases accept connections from the server itself only.
- In place
- Access control
- Roles, store-limited access, and separate rights to download and to e-mail.
- In place
- Support access
- Staff open your company's data only after your administrator approves a support request: read-only, time-limited, ended by you at any time.
- In place
- Sign-in
- Two-step sign-in required for owners; your company can require it for everyone. Owners and admins sign in again every 12 hours, others every 7 days.
- In place
- AI
- Your own provider key (Anthropic or OpenAI). Customer contact details are masked before anything is sent.
- In place
- Monitoring
- Independent outside check every 5 minutes, a heartbeat alert if the server goes silent, health checks every 2 minutes.
- In place
Staff still see what running the account needs: users, store names, sync health and billing.
The details
- Where your data lives
- Your company is kept apart
- Who can see what
- Sign-in
- Encryption
- Backups
- How long we keep data
- AI and Joe
- Audit trail
- When something goes wrong
Where your data lives
- On one dedicated virtual server rented from Contabo GmbH in the European Union. Your data, uploaded files and exports are stored there.
- Databases run on Microsoft SQL Server on the same server and accept connections only from the server itself, never from the internet.
- The firewall allows only secure web traffic and administrator sign-in with keys. Administrator password sign-in is switched off.
Your company is kept apart
- Each company has its own database. No two companies share one.
- Each company's database has its own database login, which can reach only that database. If the application ever sent a request to the wrong database, the database server itself would refuse it.
- A security review in October 2026 tested this on test workspaces: every attempt to reach another company's data was refused.
Who can see what
- Roles. Your administrators decide which parts of PerformHub each person can open, and what they can do there.
- Store-limited access. A person limited to some stores sees only those stores' figures, in every page, report and export.
- Download and e-mail are separate rights. Seeing a report does not allow downloading or e-mailing it. Every change to someone's rights is recorded.
- Customer contact details are hidden unless a person holds that right. Every view is logged.
- Support access needs your approval. PerformHub staff cannot open your company's data — sales, customers, products, reports or AI chats — unless your administrator approves a support request. Approved access is read-only, time-limited and can be ended by you at any time, and you can see every page it opened. Emergency access by the platform owner is logged and notifies your administrators immediately.
Sign-in
- Two-step sign-in with an authenticator app is required for company owners and PerformHub staff. Your company can require it for administrators or for everyone.
- Passwords need at least 12 characters, are checked against a long list of common passwords, and are stored only as strong one-way hashes.
- Repeated wrong passwords slow down and lock sign-in. An unusual spike in failed sign-ins alerts us.
- Session limits. Owners and administrators sign in again every 12 hours; other users after at most 7 days. Signing out, changing a password or suspending an account ends the session on every device.
- A sign-in from a new device sends the person an e-mail.
Encryption
- In transit: HTTPS only, with TLS 1.2 or 1.3, and HSTS so browsers refuse unencrypted connections. The link to your Retail Pro database requires encryption (AES-256).
- Database vault: database files are stored in an encrypted volume (LUKS2, AES-XTS with a 512-bit key) — all of your data, including sales, stock and every business figure, and all backups. The unlock key is not stored on the server; after a restart the databases stay locked until we unlock them.
- Customer contact details copied from your point of sale and online store are also encrypted inside the database (AES-256-GCM), with the key kept outside the database. Search by phone or e-mail still works through one-way keyed indexes.
- Connection secrets (Shopify, AI, Retail Pro and others) are encrypted with AES-256-GCM, with keys kept outside the database.
- Every backup is encrypted (AES-256-GCM), on the server and off-site.
- The app runs under a strict Content Security Policy, so the browser refuses scripts from anywhere else.
Backups
- Every database is backed up in full every night, and each live database's changes every hour.
- Every backup is checked when written. Every Sunday a full restore is tested and checked for integrity.
- Backups are kept for 14 days on the server, encrypted.
- Off-site copy: every backup is also sent, encrypted before it leaves our server, to a second location in an EU data centre, every hour. Copies are locked so nobody can delete them early: daily copies for 30 days, monthly copies for 12 months. A full restore from the off-site copy has been tested and checked for integrity.
How long we keep data
- Customer purchase history is kept for as long as your company uses PerformHub, so opening a customer always shows their full history. It is never anonymised or trimmed on a timer.
- Customer export files expire after 24 hours.
- When a company leaves and its workspace is deleted, its database and its backups are deleted.
- Working data is cleaned up automatically: AI chats nobody has opened for 12 months are deleted; failed sign-in records are kept 90 days, used sign-in links 30 days, unused devices and e-mail logs 12 months.
AI and Joe
- Your AI runs on your own provider account. Each company's AI features, including the analyst Joe, use a key held for that company alone (Anthropic or OpenAI). Requests and costs are never mixed with another company's.
- Customer contact details are masked before anything goes to the AI provider. For Joe's queries this is enforced in the database, not only in the application.
- Joe sees only what the person asking may see: the same stores, modules and customer-detail rights.
- Joe never sends e-mail or changes data by himself. He drafts, the person confirms, and the server checks the confirmation again.
- Spending caps per person and per company stop AI work when a monthly limit is reached.
Audit trail
- Administrator changes (users, roles, rights, stores), PerformHub staff actions, views of customer contact details and failed sign-ins are recorded with who, when and from where.
- The application can add to these records but cannot change or delete them.
When something goes wrong
- Outside monitoring: an independent service checks the application and this website from outside every 5 minutes. A second heartbeat check alerts us within minutes if the server itself goes silent.
- Detection: health checks every 2 minutes restart the application if it stops answering. We are alerted to unusual sign-in failures, expiring certificates and stale data.
- Response: a written incident procedure covers keeping evidence, signing out every session, stopping a connection, suspending a workspace and replacing keys.
- Telling you: if your data may have been seen or changed by someone who should not, we tell your company owner what happened, which data, when and what we did, the same day where possible. We follow the reporting duties that apply: Egypt's personal data protection law and, for people in the EU, the GDPR.
Need more for your IT team?
We can go through any point on this page with your IT team. Ask for:
- Our written security overview
- The current status of penetration testing
- Answers to your security questionnaire
Ask a security questionOr write to info@performhub.ai