How we protect the system that holds your compliance evidence
A GRC platform holds an unusually concentrated picture of where an organisation is weakest. This page sets out how Govrly is built and hosted, what we can state plainly, and what we will send you when your security team asks.
This page describes our hosting architecture and the controls we operate. Platform-level guarantees inherited from Google Cloud are documented by Google. For anything specific to your assessment, contact us — we would rather answer your actual question than publish a general statement.
Why this page exists
Most vendors publish a security page because procurement asks for one. A GRC platform has a more specific reason.
The data in a compliance platform is unusual. A CRM holds customer names. Govrly holds a structured account of every control an organisation has not yet implemented, every audit finding still open, and every risk currently accepted. Aggregated across entities, that is a map of where an organisation is weakest.
That concentration is why security reviewers examine GRC vendors more closely than most — and why the answers below are stated plainly rather than in the usual reassuring generalities.
Infrastructure
Govrly runs on Google Cloud Platform, which means a substantial part of the security baseline is inherited rather than reimplemented.
Where a control is inherited from Google Cloud, we say so rather than presenting it as something we built. Reviewers check, and the distinction matters to them.
Application workloads run on Cloud Run. Physical and environmental security, hardware lifecycle, and the underlying network are inherited from Google Cloud's own controls and audited under Google's certification programme rather than ours.
Traffic reaches the application through Cloudflare, which handles TLS termination, DDoS protection, and web application filtering before any request touches Govrly.
Google Cloud encrypts customer data at rest by default, using AES-256, with no configuration required. This applies to storage and to backups. It is a platform guarantee documented by Google, not a setting we could disable.
Each customer organisation is logically isolated. Within a multi-entity customer, each entity is separated again, so entities cannot see one another's controls, evidence, risks, or audit records while a parent with oversight rights sees across them.
Running on Cloud Run means no long-lived servers for us to patch and no operating system layer under our management — a meaningful reduction in the surface we are responsible for.
Access within a customer organisation is scoped by role, and in multi-entity deployments by entity, so users see only the records within their remit.
What we secure, and what you secure
Most security incidents involving SaaS platforms happen on the customer side of this line, not the vendor side. It is worth being explicit about where it falls.
The evidence point deserves attention. Compliance evidence often contains system detail, findings, and sometimes personal data — so what you upload is a decision with privacy consequences, not just an administrative step.
- The application and its code
- Hosting configuration on Google Cloud
- Edge protection and TLS termination
- Logical isolation between customers and between entities
- The role and permission model
- Availability and integrity of the platform
- Notifying you of incidents affecting your data
- Who you invite, and with what role
- Removing access when people change role or leave
- The strength and handling of your users' credentials
- What data you choose to upload as evidence
- Whether uploaded evidence contains personal data, and the lawful basis for it
- Your own retention decisions within the platform
Sub-processors
Under the Saudi PDPL you remain the controller for personal data held in Govrly. Anyone we use to deliver the service who may process that data is your sub-processor too, so you need to be able to see the list.
If you need the list in a specific format for your vendor register, or notification when it changes, ask and we will provide both. We would rather you had it than discovered a gap during your own assessment.
| Provider | Purpose | Relationship to your data |
|---|---|---|
| Google Cloud | Application hosting, storage, backups | Stores and processes customer data, encrypted at rest by default |
| Cloudflare | Edge protection, TLS termination, DDoS and application filtering | Processes traffic in transit; does not store customer records |
What we send security reviewers
Some answers are specific to your assessment, your jurisdiction, and your contract. Publishing a general version of them helps nobody, so we send the actual answer instead.
Available on request, under NDA where appropriate:
- Hosting region and data location details
- Encryption and key management specifics
- Backup frequency, retention, and restoration testing
- Authentication options, including SSO where required
- Our personnel access model for production systems
- Audit logging scope and retention
- Vulnerability management and patching approach
- Secure development and release process
- Incident response and customer notification commitments
- Data export and deletion on termination
- Availability commitments, as set out in the customer agreement
- Completed responses to your own security questionnaire
If your assessment requires something not on this list, ask. A specific question gets a specific answer, and that is more useful to your reviewer than a page of general assurances would have been.
If you are assessing us as a vendor
Your own obligations are what generate the assessment, and we would rather make it quick than make it comfortable.
The ECC includes a third-party and cloud computing domain. When a government entity assesses us, it is discharging its own regulatory obligation — which is why the questions are detailed and why general assurances are not enough.
Third Party Cyber Security is a scored domain. Our posture becomes part of your maturity assessment, not just your procurement paperwork — so we answer at that level of detail.
Third-party security is one of the six CRF control domains, applied at your assigned compliance level.
Where Govrly acts as a processor, your notification obligations depend on us telling you promptly. We treat that as an operational commitment rather than a contractual formality.
Send us your standard form. We would rather answer your format than ask you to accept ours.
If your assessment requires you to test the platform, contact us to agree scope and timing rather than testing a shared environment unannounced.
Security and hosting — FAQs
Govrly runs on Google Cloud Platform, using Cloud Run for application workloads, with Cloudflare providing edge protection and TLS termination. For hosting region and data location details specific to your requirements, contact us — that answer depends on your obligations and we would rather give you the accurate one than a general statement.
Yes. Each customer organisation is logically isolated, and within a multi-entity deployment each entity is separated again — so entities cannot see one another's controls, evidence, risks, or audit records, while a parent organisation with oversight rights sees across them.
Yes. Google Cloud encrypts customer data at rest by default using AES-256, with no configuration required, and this extends to backups. It is a documented platform guarantee rather than a setting, which means it is not something that can be inadvertently turned off. For key management specifics, ask and we will provide them.
Traffic reaches the application through Cloudflare, which terminates TLS and applies DDoS and web application filtering before any request reaches Govrly. If your assessment requires specific protocol and cipher details, we will provide them on request.
Access to production is restricted and governed by our internal access model. Because the specifics matter to a reviewer — who, under what circumstances, with what approval, and whether it is logged — we set that out in writing as part of a security review rather than summarising it here.
Authentication options, including SSO where your organisation requires it, are covered as part of a security review. Tell us what your identity provider is and what your policy requires, and we will confirm what is available.
We build Govrly against the same frameworks the platform manages, and we inherit a substantial part of our infrastructure baseline from Google Cloud, which maintains its own certifications for that layer. For our current certification position and roadmap, ask us directly — we will give you the accurate answer rather than language designed to imply more than it says.
Export and deletion arrangements are set out in the customer agreement, and we will walk through them before you sign rather than after. If you have specific retention or deletion requirements driven by the PDPL or your own policy, raise them during the review and we will address them in writing.
Where Govrly acts as your processor, your own notification obligations depend on us telling you promptly, so we treat this as an operational commitment rather than a formality. The specific commitment and timeframe form part of the customer agreement.
Google Cloud, for application hosting, storage and backups; and Cloudflare, for edge protection and TLS termination. If you need the list in a specific format for your vendor register, or notification when it changes, ask and we will provide both.
Yes. Send us your questionnaire and we will complete it in your format. If your assessment requires testing the platform directly, contact us first so we can agree scope and timing rather than having a shared environment tested unannounced.
Reviewing us as a vendor?
Send us your security questionnaire, or tell us what your assessment needs and we will provide it.
