Business Continuity

Owner: ALL Last revision: 04.01.2020

Objective#

To ensure that the organization can still accomplish its mission and it would not lose the capability to process, retrieve and protect information maintained in the event of an interruption or disaster leading to temporary or permanent loss of computer facilities.

Risks#

• The organization’s inability to accomplish its mission after re-starting its operations
• To inability to retrieve and protect the information maintained
• To inability to keep intact all the organizational activities after the disaster
• The loss in terms of money, goodwill, human resources and capital assets needed by the organization to start its operations on full scale at the earliest

Emergency Contact Persons#

Our organization’s two emergency contact persons are: Peter ILLÉS ([email protected]) and Norbert ZSOMBORI ([email protected]).

These names will be updated in the event of a material change or when one of Contact Persons leaves the firm.

Succession Planning#

If the Managing Partner becomes incapacitated or perishes, all business operations fall to the other Partners.

If all Partners become incapacitated or perishes, all business operations fall to the Technical Lead.

Customer’s Right to Functional Software#

In case the software runs on customer’s server, Further Digital Solutions (C4WEB STUDIO SRL) has no responsibility for the correct functioning of software.

In other cases, Further always employs the services of Linode LLC for the hosting of the software. In the case of a serious business disruption (SBD), clients may turn directly to the above noted firms.

Data Backup and Recovery#

• Information belonging to Further and its customers should be stored in the cloud whenever possible. Only keep local copies of information when it is absolutely necessary. Immediately dispose of copy when it becomes no longer necessary to keep a local copy.
• Project files (brief, design document, tasks, etc.) shall be stored in our project management tool (productive.io)
• Project source code shall be stored in our code versioning system (bitbucket.org)
• Project files on the server (database, uploaded media, server configs) shall be always backed up. Backup frequency is determined for each project in part, but should never be less frequent than weekly.
• All other non-project files and information shall be stores on Google Drive
• Emails are shall be exclusively run through G Suite. If a desktop/mobile email client is used to access emails, the IMAP protocol shall be used to preserve cloud copies.

Operational Assessment#

In the event of an SBD, we will immediately identify what means will permit us to communicate with our customers, employees and critical third-parties. Although the effects of an SBD will determine the means of alternative communication, the communications options we will employ will include our website, phone, and e-mail.

Responsibility#

The Technical Lead, with the help of the development and DevOps teams, is responsible for data recovery and ensuring all IT systems and networks are functional in minimal time.

The Managing partner is responsible for reporting and notifying all third-parties or customers of an SBD.