Trust centre

The questions diligence teams ask.

Search 29 direct answers about Vericode's current controls. Weak answers are labelled honestly instead of omitted.

29 answers shown

Data protection

Hosting, encryption and the information that moves through Vericode.

Identity and engineering

Access, authentication, testing and change management.

Privacy and governance

Legal requests, incidents, retention and assurance.

Resilience and lifecycle

Backups, recovery, continuity and service exit.

Need evidence for your review?

Ask for current supporting documentation and explain the scope of your questionnaire.

Security and trust Send a questionnaire

The questions diligence teams ask.

Data protection

How is data encrypted in transit?

How is data encrypted at rest?

Where exactly is customer data hosted?

Who are your service providers?

Do verification messages leave Vericode?

What does Vericode store?

Do you use customer data to train AI models?

What physical-security controls apply?

Identity and engineering

Is MFA required for staff?

Do customers get SSO?

How is access controlled?

Is access logged?

How often do you run penetration tests?

How are code changes reviewed?

Do you scan dependencies?

Do you hold independent security certifications?

Privacy and governance

How do you respond to a suspected breach?

What is your breach-notification timeline?

How do you address the NDB scheme?

What are your retention periods?

Can data be deleted on request?

Is a DPA available?

What is your GDPR position?

Can customers audit Vericode?

Do you carry cyber insurance?

Resilience and lifecycle

How are backups configured?

What are your RPO and RTO?

Do you have a business-continuity plan?

What happens if Vericode shuts down?

Need evidence for your review?