Operational GRC for audit-ready organizations in Saudi ArabiaBook a Demo
Company · Trust and securitySaudi Arabia

We sell compliance. Ask us the same questions

Most of this site tells you how to assess a vendor. This page is us on the other side of that process — the questions we expect, the commitments we make, and the things we will tell you plainly rather than imply with a badge.

§ 01Govrly
Company · Trust and security

We are a vendor too

A GRC platform holds a concentrated picture of an organisation's weaknesses — every open finding, every accepted risk, every control that is not working yet. That makes us a supplier worth assessing carefully, and we would think less of a buyer who did not.

Which puts us in an unusual position. We publish a page explaining how to assess your suppliers, and another explaining how to answer your customers when they assess you. This page is where we are the supplier — subject to exactly the process those pages describe, and judged by the standard they set.

So the criteria we suggest you apply to us are the ones written on those pages. Tier us by what we touch. Read our answers against your own thresholds. Turn anything inadequate into a finding with a date. We would rather be assessed properly than trusted casually.

§ 02Govrly
Company · Trust and security

What you can ask for

Available to any customer or prospect under NDA, without a procurement process to unlock it.

01
Our security documentation

How the platform is built, hosted, segregated and backed up, in the detail a security team needs rather than the summary a marketing page carries.

Yours, in your format. We do not insist you use ours, and we do not charge for the time.
Our answers to your questionnaire
03
Our current certification position

Including what we do not hold yet. A vendor who describes their roadmap as though it were their status is telling you something about how they will handle your data.

04
Our sub-processor list

Who else touches your data and what for. Maintained in the privacy policy so there is one authoritative version rather than several.

05
Data handling specifics

Processing location, what leaves the deployment, retention on termination and what happens to backups. Answered for your deployment and put in the contract.

06
Our contract terms

The data processing terms and security commitments, before you are asked to commit to anything.

If any of this requires escalation, a signature or a follow-up call to obtain, that is worth noticing about a vendor. It should take an email.

§ 03Govrly
Company · Trust and security

Where we are, stated plainly

The section most vendor trust pages replace with a row of badges.

We hold ourselves to the argument we make elsewhere on this site: a number or a badge that cannot be opened is not a position anyone can defend. That applies to our own claims first.

How we answer
Status, not aspiration

Ask about any certification or framework and you will get one of three answers: we hold it, we are working toward it with a realistic position on where we are, or we do not and here is what we do instead.

The third answer is the one worth having. A vendor who cannot say it is a vendor whose other answers you should check.

Why not badges
A logo is not a control

A certification mark on a webpage tells you a body issued something at a point in time. It does not tell you the scope, the date, the exclusions or whether the thing you care about was in it.

So we would rather send you the actual position, with its scope and its limits, than a graphic. Ask and it comes by email.

§ 04Govrly
Company · Trust and security

What we commit to

Operational commitments rather than achievements — the things you can hold us to as a supplier.

Incidents
You hear it from us

If an incident affects your data, we tell you — with what we know, what we do not know yet, and what we are doing. Notification timing and detail go in the contract rather than being left to goodwill.

Sub-processors
Notice before change

Adding a sub-processor changes your processor chain and therefore your PDPL position. You should know before it happens, not discover it in a review.

Your data
Yours, and exportable

Your compliance records belong to you. Export terms, retention on termination and backup deletion are contractual, so leaving is a decision rather than a negotiation.

Access
Least privilege, including ours

Our own access to customer environments is scoped and accountable. Ask what our support staff can see and under what circumstances — it is a fair question and it has a specific answer.

Changes
No quiet expansion

If what we do with your data changes, that is a conversation rather than a policy update you are deemed to have accepted.

Honesty
Including when it costs us

If we are not the right fit, or a capability is not there yet, we say so during evaluation. Discovering it after signature is worse for both of us and much worse for you.

§ 05Govrly
Company · Trust and security

Reporting a vulnerability

If you have found something, we want to hear about it, and we would rather hear it from you than from someone else.

Vulnerability reports and security questions about the platform.
Security
Data subject requests and questions about how we handle personal data.
Privacy
Assessment packs, questionnaires, contract terms and commercial questions.
Everything else
  1. 01
    /05
    Send it to our security address

    With enough detail to reproduce it. Include how you found it if that matters, and tell us how you would like to be credited, or not.

  2. 02
    /05
    We acknowledge that it arrived

    Promptly, from a person rather than an autoresponder, so you know it is being looked at.

  3. 03
    /05
    We tell you what we found

    Whether we could reproduce it, what we assess the impact to be, and what we intend to do. Including if we disagree with your assessment, with reasons.

  4. 04
    /05
    We keep you updated until it closes

    Rather than going quiet after the first reply, which is the most common complaint researchers have about disclosure processes.

  5. 05
    /05
    We will not pursue good-faith research

    Testing that avoids other customers' data, avoids degrading the service, and stops at proving the issue rather than exploiting it.

§ 06Govrly
Company · Trust and security

This page, or platform security?

Most vendor assessments need both, and they usually arrive as one questionnaire split across two teams. Send us the whole thing — we will answer it in one pass rather than sending you between departments.

This page
How the company operates

Governance, our own compliance position, sub-processors, the commitments we make as a supplier, and how to report a vulnerability.

Written for procurement, legal and whoever runs your vendor assessment.

Platform security
How the product is built

Architecture, hosting, segregation, encryption, backups and the technical detail a security review needs. Security and hosting →

Written for the engineer who has been asked to sign off on the technical position.

§ Company · Trust and securityNCA · SAMA · CST · PDPL

Assess us properly

Ask for the pack, send us your questionnaire, and hold us to the criteria we suggest you apply to everyone else.

Govrly's risk register: inherent and residual risk heat maps, scored by likelihood and impact№ 04B&W
Risks · inherent → residualPlate IV