
Security, Hosting and Recovery — Procurement Reference
Customer summary · Version 1.6 · 17 November 2026 · v5ultimate.com/security#procurement
V5 Ultimate hosted services (Cloud and Private Cloud). On-Premises and customer-managed cloud deployments are operated by the customer; see the On-Premises specification. How to read this document. Where a signed Order or customer-specific agreement exists, it governs. Otherwise the current S.G. Systems SLA and the applicable commercial terms set the commitments; Orders that accepted MSA V1.24 keep its terms. This page describes how the service currently operates; it does not change, add to or replace any contract term.
Where V5 Ultimate runs
Layer | Provider | Location |
|---|---|---|
Application | Google Cloud Run | London, United Kingdom for United Kingdom and European customers; Oregon (United States) for other customers |
Database, sign-in and file storage | Supabase, running on Amazon Web Services | London, United Kingdom for United Kingdom and European customers; United States — Oregon for other customers; confirmed for your deployment |
Independent backup and archive copies | Google Cloud Storage | London, United Kingdom for United Kingdom and European customers; United States multi-region for other customers; confirmed for your deployment |
Source code, review and release approval | GitHub | Not a store of Customer Data |
Service Levels and Support
1. Is there an uptime SLA, and how does it differ from a 2-hour response?
They are different measures. Uptime measures how much of the month a hosted service is available. A response target measures how quickly a person at S.G. Systems starts working on your issue. For critical (Severity 1) issues that is 2 hours, 24/7/365. It is not uptime, automated recovery or a guaranteed fix time.
- Uptime, backups, RPO/RTO and service credits apply only to V5 Ultimate Cloud and Private Cloud, under the S.G. Systems SLA (§5 and §6).
- Severity 1 (critical): a person from S.G. Systems responds within 2 hours, 24/7/365, for every supported deployment, including V5 Classic and on-premises. Hosted services also keep a 1 business hour target during business hours. Other severities run in business hours.
- A response time is when a person starts working on the issue. It is not a fix time, an automated recovery, an uptime figure or a recovery objective. Contract references: SLA §4 response targets (v5ultimate.com/legal/sla#s4); SLA §5 hosted service levels (v5ultimate.com/legal/sla#s5); SLA §6 service credits (v5ultimate.com/legal/sla#s6)
2. What happens in a critical outage, and is support 24/7?
A Severity 1 incident gets a human initial response from S.G. Systems within 2 hours, 24/7/365, whether you bought directly or through a reseller, and is worked with engineering until service is restored. You can always report directly to S.G. Systems; the clock starts when your report reaches the S.G. Systems support channel.
- The commitment is set in the S.G. Systems SLA §4.1. Severity 2 to 4 targets run in business hours (09:00-18:00 local, weekdays) unless your Order says otherwise.
- Orders that accepted MSA V1.24 keep their accepted support terms until renewal on the new documents.
- Security incidents follow the notification commitment in Commercial Terms §9.2. Contract references: SLA §4.1 critical support (v5ultimate.com/legal/sla#c4-1); SLA §3 reporting an issue (v5ultimate.com/legal/sla#s3); Commercial Terms §9.2 security incidents (v5ultimate.com/legal/commercial-terms#c9-2)
Hosting and Data Location
3. Who hosts the service?
The V5 Ultimate application runs on Google Cloud Run. The database, sign-in and file storage run on Supabase, which operates on Amazon Web Services. Independent backup and archive copies are kept in Google Cloud Storage. Source code, code review and release approval are managed in GitHub; production builds and releases run on Google Cloud.
- This describes the V5 Ultimate application. The public marketing website is hosted separately and holds no Customer Data from the application.
- Operating servers in more than one location does not by itself provide failover for the database or for a whole provider.
- The sub-processors that process Customer Data are listed on the Sub-processors page.
- Dated supplier assessments (approved 14 October 2026) record our assessment and approval of the hosting, database and source-control suppliers used for the V5 Cloud shared service, with documented conditions and residual risks. They do not cover On-Premises or customer-managed installations.
- Those assessments record our review and acceptance of the applicable Google Cloud and Supabase ISO/IEC 27001 certification and SOC 2 Type II reports for the service roles assessed. This is supplier assurance, not an S.G. Systems certification; a SOC 2 Type II report is an independent assurance report, not a certification.
- As recorded in those assessments (12 and 14 October 2026), multi-factor authentication is enforced for administrative access to the reviewed source-control and database supplier organisation accounts. This does not cover every credential, customer sign-in or deployment. Contract references: Sub-Processors (v5ultimate.com/legal/sub-processors)
4. Where is our data stored geographically?
United Kingdom and European customers are hosted in London, United Kingdom: application, database, sign-in, files, archive copies and backups. Other customers are hosted in Oregon, United States, with independent backup copies in a Google Cloud United States multi-region location. The locations for your deployment are confirmed in your Order.
- London hosting is not an EU-only or all-copies-in-Europe commitment. Support through S.G. Systems' US-hosted support system, authorised international support access, and AI, email and SMS providers are listed on the Sub-processors page.
- Before 2 November 2026 the European application location was the Netherlands, with the database in Oregon. Orders keep the locations stated in the version they accepted.
- On-Premises customers keep data in their own environment. Contract references: On-Premises Specification (v5ultimate.com/resources/on-prem-specification)
Backup and Recovery
5. Could we lose a day's lot and traceability records?
Daily backups are one layer of protection, not the only one. Database point-in-time recovery is enabled to help recover from damaged data while the database provider remains available. For that scenario, we work towards a recovery point within about 5 minutes of the incident; this is still being qualified, not a guaranteed limit. If the primary database provider is unavailable, recovery depends on the independent copy, which can be about 24 hours old, plus capture delay. Recent lot and traceability records not captured in that copy could therefore be lost.
- The Cloud SLA sets a 24-hour recovery point objective (RPO) and an 8-hour service-restoration objective (RTO) for Severity 1 incidents. RPO concerns recent data potentially lost; RTO concerns time to restore service. These are objectives, not guaranteed maximums or a statement that every incident loses a day of data.
- The shorter recovery point depends on the failure scenario. Five-minute file copies are separate and do not mean the whole database is copied every five minutes. Complete end-to-end service recovery timings have not yet been proven.
- If your recall readiness, BRCGS procedures or other record obligations require a shorter loss window, raise this before signing. Review deployment-specific recovery evidence and agree any different commitment in your Order. Choosing Private Cloud alone does not establish a five-minute recovery promise or compliance. Contract references: SLA §5.1 Cloud (v5ultimate.com/legal/sla#c5-1); SLA §5.2 Private Cloud (v5ultimate.com/legal/sla#c5-2)
6. What is the Recovery Time Objective (RTO)?
RTO is the objective for how long restoring the service takes, not how much data could be lost. Contractually, the S.G. Systems SLA sets an RTO of 8 hours for Severity 1 incidents on Cloud and 4 hours on Private Cloud. Internally we work to a 4-hour target for restoring the complete service, but that target is provisional and has not yet been proven in a full recovery exercise. These are restoration objectives, not guaranteed maximum outage durations.
- The internal 4-hour figure is an objective, not a tested result, and does not replace the contract.
- A complete takeover of production at another provider has not yet been exercised end to end (see Latest recovery test). Contract references: SLA §5.1 Cloud (v5ultimate.com/legal/sla#c5-1); SLA §5.2 Private Cloud (v5ultimate.com/legal/sla#c5-2)
7. What is the Recovery Point Objective (RPO)?
RPO describes how far back recovered data may go: recent changes after that point could be lost. Contractually, the S.G. Systems SLA sets an RPO of 24 hours on Cloud and 12 hours on Private Cloud. How much data could be lost in practice depends on what fails: if data is corrupted while our database provider is still running, we aim to recover to within about 5 minutes; if the provider itself is unavailable, the latest independent database copy can be about 24 hours old, plus capture delay. How long restoration takes is a separate measure, the RTO. This does not mean every incident loses a day of data; recent lot and traceability records not captured in the independent copy could nevertheless be lost in a provider outage.
- The 5-minute figure is a working objective for that one scenario and is still being qualified. It is not a guaranteed data-loss limit for the whole service.
- Private Cloud backup timing is deployment-specific. Ask for the evidence for your deployment before relying on a figure other than the SLA. Contract references: SLA §5.1 Cloud (v5ultimate.com/legal/sla#c5-1); SLA §5.2 Private Cloud (v5ultimate.com/legal/sla#c5-2)
8. How often is the database backed up?
Point-in-time recovery is switched on for the database, and a full independent copy of the database and files is taken every day. Files are also copied on a separate 5-minute schedule, and archive transfers run hourly.
- Point-in-time recovery is configured for 7 days. The history actually available varies and has recently been slightly under 7 days, so we do not promise an uninterrupted 7-day window.
- The 5-minute schedule applies to files only. The whole database is not copied every 5 minutes.
- The S.G. Systems SLA commitment for Cloud is encrypted backups every 24 hours (§5.1). Contract references: SLA §5.3 disaster recovery (v5ultimate.com/legal/sla#c5-3)
9. How long are backups and records kept?
Rolling recovery copies are kept for at least 30 days and operational evidence for 365 days. Scoped manufacturing and contract-signature records are also archived with a 15-year minimum retention setting. No automatic deletion of archives is currently enabled.
- The archive retention setting is not yet locked, so it can be changed by administrators. We do not describe it as tamper-proof (WORM) storage, and proving that complete, readable historical records can be produced for the full period is still in progress.
- Backup retention is separate from your contract rights. After termination, Customer Data is retrievable on request for 90 days under Commercial Terms §5.4 (MSA §5.4 for prior Orders), then deleted from active systems subject to the DPA, legal holds and backup rotation. You remain responsible for your own regulatory record retention (§7.3). Contract references: Commercial Terms §5.4 after termination (v5ultimate.com/legal/commercial-terms#c5-4); Commercial Terms §7.3 data retention (v5ultimate.com/legal/commercial-terms#c7-3)
10. When was recovery last tested, and what did it show?
On 30 September 2026 we restored the previous day's real backup copies into an isolated environment. The database tables, rows and available files were checked, stored signature hashes were verified, and a sample of encrypted values was successfully decrypted.
- Not yet proven: a full production takeover at another provider, a hosted point-in-time restore, restoring original passwords, MFA and single sign-on, every external dependency, and end-to-end service timings.
- An earlier test, before the October 2026 region change, showed application traffic rerouting in about 79 seconds. That was an application-only routing test, not a database recovery and not a service-level commitment.
- After the 2 October 2026 move of the application to the Netherlands, routing checks passed and both locations returned to normal routing. No provider outage or customer workflow was simulated and no timing is claimed.
- Our policy requires restore tests at least every 90 days and an annual regional or provider exercise.
11. Do you have a business continuity and disaster recovery policy?
We have a documented backup and recovery policy and operating guide (current versions dated 5 October 2026). A summary and the latest test evidence are available on request, usually under NDA. We do not currently publish a separate, broader business continuity plan, and we don't claim one beyond what those documents cover.
- The infrastructure programme behind the policy closed with recorded exceptions. That is not a blanket compliance approval.
- An approved assessment (rev 3, 25 September 2026) covers the V5 Ultimate 5.10 manufacturing technical controls. It does not cover the QMS or QC areas and is not a disaster-recovery certification.
- The S.G. Systems SLA §5.3 commits to a disaster recovery plan and periodic recovery testing. Contract references: SLA §5.3 (v5ultimate.com/legal/sla#c5-3)
Encryption and Data Protection
12. How is data encrypted?
The Commercial Terms (MSA V1.24 for prior Orders) commit to encryption for hosted services and encrypted backups. Connections from users to the service use TLS. We are confirming the exact algorithms and scope for each layer, and share that confirmation on request rather than publish unverified detail.
- One internal connection, between the database connection pooler and the database, is still being confirmed. For that reason we don't claim end-to-end encryption.
- On-Premises customers manage their own encryption and keys. Contract references: Commercial Terms §7.3 (v5ultimate.com/legal/commercial-terms#c7-3); Commercial Terms §9.1 security (v5ultimate.com/legal/commercial-terms#c9-1)
13. How quickly will you notify us of a breach?
Without undue delay and in any event within 72 hours of becoming aware of a Security Incident, followed by a detailed report within 3 business days. The clock runs from awareness, not from later confirmation. Any shorter period required by law or the DPA applies.
Contract references: Commercial Terms §9.2 (v5ultimate.com/legal/commercial-terms#c9-2)
14. Can we export our data when we leave, and what does it cost?
Yes. You can export using the software's standard export methods during the subscription and for 90 days after termination on request. Standard exports are not charged as migration services. Custom formats or extra work need a separate written agreement.
- Standard exports keep records linked to their audit trail and e-signature information as far as the export format allows. Contract references: Commercial Terms §12.5 data export (v5ultimate.com/legal/commercial-terms#c12-5); Commercial Terms §5.4 after termination (v5ultimate.com/legal/commercial-terms#c5-4)
Insurance and Commercial Terms
15. What cyber and professional indemnity insurance do you hold?
We don't publish insurance limits. Ask us for current certificates and we will share them through the document request below.
16. Can the deposit be reviewed?
Payment and deposit terms are set in your Order and the applicable commercial terms. Requests to change them are reviewed by our commercial team; nothing is agreed until it is confirmed in writing.
Contract references: Commercial Terms Section 6 Fees and Payment (v5ultimate.com/legal/commercial-terms#s6)
17. Can the liability cap be reviewed?
The current Commercial Terms (§17) limit total liability to the fees paid under the applicable Order in the 12 months before a claim, subject to its agreed terms and exceptions. Requests to change the cap are reviewed by our commercial team and apply only once agreed in writing.
Contract references: Commercial Terms §17.1 (v5ultimate.com/legal/commercial-terms#c17-1)
Sources and evidence dates
- S.G. Systems Support & Service Level Agreement Version 1.1 (v5ultimate.com/legal/sla, provided by S.G. Systems, LLC for direct and reseller customers), V5 Commercial Terms for Software and Services Version 2.3 and SG Systems EULA Version 1.2, both dated 19 October 2026 (v5ultimate.com/legal/commercial-terms and v5ultimate.com/legal/eula) — contractual commitments; Orders that accepted Master Services Agreement V1.24 (v5ultimate.com/legal/msa) keep its terms
- SG Systems Supplier Quality Agreement (SQA) Version 1.11, dated 19 October 2026, sets quality responsibilities for regulated customers (v5ultimate.com/legal/sqa); customers who signed Supplier Quality Addendum Version 1.10 (effective 20 April 2026) keep that version and every right in it
- SG Systems backup and recovery policy SG-POL-BR-001 v2.10 and guide SG-GDE-BR-001 v2.8, 5 October 2026 — current operating facts (internal; summarised here, not published)
- Isolated recovery check of 30 September 2026 using 29 September 2026 copies — latest evidence
- Owner confirmation, 2 November 2026: European hosting moved from the Netherlands to London, United Kingdom; United Kingdom and European customers' application, database, files, archives and backups are in London; other customers remain in Oregon (internal)
- SG Systems supplier qualifications for Google Cloud, Supabase/AWS and GitHub, revision 1.1, approved 14 October 2026 (internal; summarised only)
Controlled documents (backup and recovery policy summary, recovery-test evidence, encryption scope, insurance certificates, deployment-specific terms) are shared on request, usually under NDA. Request them at v5ultimate.com/security#procurement.
