Vindicia Business Continuity Statement – COVID-19
Incident Report for Vindicia
Vindicia has a robust Business Continuity Plan in response to the COVID-19 situation. Our cross-functional committee is meeting daily to ensure business continuity in support of our customers, partners and employees around the globe.

We are taking all precautions to ensure our business will carry on as normal, including when and if our employees are required to work from home. Our systems have been tested and checks are in place to make sure Vindicia is able to function as well remotely as it does when our employees are on-site. These systems are regularly tested and backed up as part of our ongoing risk management processes.

As the outbreak develops, we will continue to follow the advice of local authorities and make pragmatic decisions where necessary. Currently there is no impact to Vindicia that would affect services to our customers, and we have contacted all our suppliers to mitigate any risk from them as well.

Our top priority is to ensure we are doing all we can to minimize risk and keep our employees, customers and partners safe and healthy and your business fully operational.

We have taken a number of precautionary measures in our offices to protect against the virus, including reminding all our employees about the guidance given by local health officials and regularly updating all employees across all markets.

We will instruct our employees to work from home where that is advised by local authorities and we are advising employees to avoid travel where possible. Where travel is necessary, we are following guidelines from health authorities and our customers.

Should you have any questions regarding Vindicia’s business continuity plan for COVID-19, please contact your Account Manager or myself.

Thank you for your trust and loyalty. We are confident and committed to serving your business. If there is any way we can help you further as you deal with this evolving global situation please let us know.

Sharath Dorbala
Posted Mar 18, 2020 - 17:19 UTC
This incident affects: API.