Why Security Matters More Than You Think
Most small business owners think of data security as a concern for banks and hospitals — not a repair shop. This underestimates what repair shops actually hold.
Your RepairCoreX account contains: every customer in your database, their contact information, complete repair histories, invoice and payment records, staff information, inventory values, and business financial data. If this were all lost or accessed by an unauthorized party, the impact on your business — and your customers — would be severe.
Here's exactly how RepairCoreX protects it.
Tenant Isolation: Your Data Is Yours Alone
RepairCoreX is a multi-tenant SaaS platform — many repair shops use it simultaneously. But each shop's data is completely isolated from all others.
Every record in the database carries a tenant identifier. At the database query level, it is architecturally impossible for one shop's data to appear in another shop's requests. A bug in one tenant's workflow cannot expose another tenant's records.
This is different from weaker separation models where isolation relies entirely on application-layer logic. RepairCoreX's isolation is enforced at the data layer.
Encryption at Rest and in Transit
At rest: All data stored in RepairCoreX databases is encrypted using AES-256 — the same standard used by financial institutions and government systems. Even if a storage medium were physically compromised, the data would be unreadable without the encryption keys. In transit: All communication between your browser (or mobile device) and RepairCoreX servers travels over TLS 1.3 — the current gold standard for transport security. The padlock in your browser's address bar confirms this is active. Sensitive fields: Particularly sensitive fields — device passcodes, certain customer personal details — use an additional layer of field-level encryption. They are stored encrypted in the database and decrypted only at the moment of display to an authorized user.Role-Based Access Control
As described in our permissions guide, not every staff member can access every piece of data. Role-based access control ensures:
Access control failures are one of the most common sources of internal data incidents. RBAC eliminates the majority of this risk by default.
The Audit Log
Every action taken in RepairCoreX — viewing a record, editing a ticket, generating an invoice, changing a password — is logged with:
The audit log cannot be modified or deleted by any user (including owners). If an incident occurs, the log provides a complete forensic trail.
This also acts as a deterrent: staff who know their actions are logged behave accordingly.
Secure Authentication
RepairCoreX accounts use:
Backups and Disaster Recovery
Your data is backed up continuously:
A hardware failure, a data center incident, or even an accidental mass deletion is recoverable. Your data does not exist in only one place.
What You Should Do on Your End
Security is a shared responsibility. RepairCoreX provides the infrastructure security. You provide the operational security:
1. Enable 2FA on your owner account. Do this today if you haven't already. 2. Use strong, unique passwords. Don't reuse your email password for RepairCoreX. 3. Disable accounts immediately when staff leave. 4. Don't share accounts. Each staff member should have their own login. 5. Lock your workstation when stepping away from the counter.
The combination of platform security and operational discipline makes your repair shop data as secure as it can reasonably be.