Insert your registered company name (“we“, “us”, “our”) are committed to protecting and respecting your privacy.
For the purposes of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016, (“GDPR”), the Data Protection Act 2018 and any applicable national implementing laws, regulations and secondary legislation relating to the processing of personal data (together “Data Protection Law”), the data controller is Evercast LLC.
LEGAL BASIS FOR PROCESSING
We collect and use the personal data described below in order to provide you with access to our Site and Services in a reliable and secure manner. We also collect and use personal data:
To the extent we process your personal data for any other purposes, we ask for your consent in advance or require that our partners obtain such consent.
INFORMATION WE MAY COLLECT FROM YOU
We may collect and process the following information about you:
Information you give us. You may give us information about you by filling in forms on our Site or by corresponding with us by phone, email or otherwise. This includes information you provide when you register to use our Site, apps, subscribe to our services (“Services”) or newsletter, perform searches, provide payment information, share real-time audio or video, participate in discussion boards, change settings, and when you report a problem with our Site or Services. The information you give us may include your name, address, email address and phone number, financial and credit card information, personal description and photograph, video recordings, audio recordings, email addresses of invitees, project titles, project information, computer configurations and settings, billing subscription information, project timing and duration, and project participants.
Information we collect about you. With regard to each of your visits to our Site we may automatically collect the following information:
Information we receive from other sources. We may receive information about you if you use any of the other websites we operate or the other services we provide. In this case we will have informed you when we collected that data that it may be shared internally and combined with data collected on this Site.
We are also working closely with third parties (including, for example, business partners, sub-contractors in technical, payment and delivery services, advertising networks, analytics providers, search information providers, credit reference agencies, industry information databases) and may receive information about you from them.
What are cookies
Cookies are small text files that are placed on your computer by websites that you visit. They are widely used in order to make websites work, or work more efficiently, as well as to provide information to the owners of the Site. Cookies can be “persistent” or “session” cookies.
We use persistent cookies and session cookies on our Site.
A persistent cookie is stored on a user’s device in between browser sessions which allows the preferences or actions of a user across the Site (or in some cases across different websites) to be remembered. We use persistent cookies to save your login information for future logins to the Site.
A session cookie allows the Site to link your actions during a browser session. We use session cookies to enable certain features of the Site, to better understand how you interact with the Site and to monitor aggregate usage by users and web traffic routing on the Site. Unlike persistent cookies, session cookies are deleted from your computer when you log off from the Site and then close your browser.
Which cookies we use and why
The table below explains the cookies we use and why we use each of them.
Google Analytics (_ga)
We use analytics cookies to tell us whether you have visited the Site previously, and to gather statistics about visits to a page.
These cookies are used by software which tries to work out what country you are in from information supplied by your browser when it requests a web page. This cookie is completely anonymous, and is only used to help target content.
When you sign in, we generate cookies that let us know whether you are signed in or not. Our servers use these cookies to work out which account you are signed in with.
We use site performance cookies to remember preferences you may have set on our Sites.
We embed videos from our official YouTube channel using YouTube’s privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode.
For 2-factor authentication and device preferences, and track logins.
Analytics for Intercom support
Session authentication protection
You can set up your browser options, to stop your computer accepting cookies or to prompt you before accepting a cookie from the websites you visit. If you do not accept cookies, however, you may not be able to use the whole of the Site or all functionality of the Services.
To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.aboutcookies.org or www.allaboutcookies.org. To opt out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout.
USES MADE OF THE INFORMATION
We use information held about you in the following ways.
Information you give to us. We will use this information:
Information we collect about you. We will use this information:
Information we receive from other sources. We may combine this information with information you give to us and information we collect about you. We may use this information and the combined information for the purposes set out above (depending on the types of information we receive).
We will not sell or rent your personal data to anyone.
DISCLOSURE OF YOUR INFORMATION
Information we share with third parties. We may share your information with selected third parties including:
Information we disclose to third parties. We may disclose your personal data to third parties:
WHERE WE STORE YOUR PERSONAL DATA
Our Services are global and your information (including personal data) may be stored and processed in any country where we have operations or where we engage service providers, and we may transfer your information to countries outside of your country of residence, which may have data protection rules that are different from those of your country of residence.
The personal data that we collect from you may therefore be transferred to, and stored at, a destination outside the European Economic Area (“EEA“). It may also be processed by staff operating outside the EEA who work for us or for one of our suppliers or partners. Such staff or subcontractors may be engaged in, among other things, the fulfilment of your order, the processing of your payment details or the provision of support services. By submitting your personal data, you agree to this transfer, storing or processing outside of the EEA.
Our Site and Services are accessible via the internet and may potentially be accessed by anyone around the world. Other users may access the Site or Services from outside the EEA. This means that where you chose to post your data on our Site or within the Services, it could be accessed from anywhere around the world and therefore a transfer of your data outside of the EEA may be deemed to have occurred. You consent to such transfer of your data for and by way of this purpose.
PROTECTION OF YOUR INFORMATION
All information you provide to us is stored on our secure servers. Any credit card information or payment transactions will be encrypted using SSL technology. Where we have given you (or where you have chosen) a password which enables you to access certain parts of the Site or Services, you are responsible for keeping this password confidential. We ask you not to share any password with anyone.
Unfortunately, the transmission of information via the Internet is not completely secure. Although we will endeavour to protect your personal data, we cannot guarantee the security of your data transmitted to our Site or the Services. Any transmission is at your own risk. Once we have received your information, we will use strict procedures and security features to try to prevent unauthorised access.
LINKS TO OTHER WEBSITES
Our Site and Services may, from time to time, contain links to and from the websites of our partner networks, advertisers and affiliates. If you follow a link to any of these websites, please note that these websites have their own privacy policies and that we do not accept any responsibility or liability for these policies. Please check these policies before you submit any personal data to these websites.
You have the right under Data Protection Law, free of charge, to request:
Please note that where we process your personal data for marketing purposes, if you change your mind about being contacted in the future, you can also “opt out” at any time by clicking the “unsubscribe” link at the bottom of any email. Once you “opt out”, you will no longer receive any marketing emails from us. We will continue to communicate with you regarding your service billing and support via email.
We send push notifications from time to time in order to update you about any service updates, events and promotions we may be running. If you no longer wish to receive these communications, please disable these in the settings on your device.
We retain personal data for as long as necessary for the relevant activity for which it was provided or collected. This will be for as long as we provide access to the Site or Services to you, your account with us remains open or any period set out in any relevant contract you have with us. However, we may keep some data after your account is closed or you cease using the Site or Services for the purposes set out below.
After you have closed your account or ceased using the Site for a period of at least 30 days, we usually delete personal data, however we may retain personal data where reasonably necessary to comply with our legal obligations (including law enforcement requests), meet regulatory requirements, maintain security, prevent fraud and abuse, resolve disputes, enforce our Terms and Conditions, or fulfil your request to “unsubscribe” from further messages from us.
We will retain de-personalised information after your account has been closed.
Please note: After you have closed your account or deleted information from your account, any information you have shared with others will remain visible. We do not control data that other users may have copied from the Site or Services. Your profile may continue to be displayed in the services of others (e.g. search engine results) until they refresh their cache.
For individuals located in the EU: your local data protection supervisory authority in the country in which you are located or our lead supervisory authority – insert name, address located in insert country.
For all other individuals: The Information Commissioner’s Office at, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF, England.
AGE OF USERS
This Site and the Services are not intended for and shall not be used by anyone under the age of 16.
By post: insert address.
By email: insert email.
Evercast is a media collaboration platform which combines video conferencing and high quality live streaming so creative teams can work together on content development in real time from anywhere in the world.
Feedback from project stakeholders is extremely important when it comes to meeting release dates and the overall quality of the final product. Instead of waiting for file reviews or in person feedback, Evercast’s ultra low latency (200-300 milliseconds), HD live stream enables creative teams to instantly give feedback and work together.
Evercast can stream anything. Avid, Premiere, Divnici, Pro tools, After effects, live shot cameras…literally anything. This is all accomplished without the need for specialized hardware. Only a computer is required.
Evercast enables you to draw, point, circle, and type on the screen for everyone in the virtual room to see.
New use cases for Evercast keep appearing. Primarily, the platform has been used for:
DATA PROCESSING AGREEMENT
This DPA is entered into between the Controller and the Processor and is incorporated into and governed by the terms of the Agreement.
Any capitalised term not defined in this DPA shall have the meaning given to it in the Agreement.
“Affiliates” means any entity that directly or indirectly controls, is controlled by, or is under common control of a party. “Control,” for purposes of this definition, means direct or indirect ownership or control of more than 50% of the voting interests of a party;
“Agreement” means the agreement between the Controller and the Processor for the provision of the Solution and Services;
“Controller” means the Customer;
“Data Protection Law” means all laws and regulations, including laws and regulations of the European Union, the European Economic Area, their member states and the United Kingdom any amendments, replacements or renewals thereof, applicable to the processing of Personal Data, including where applicable the Data Protection Act 2018, the GDPR and any applicable national implementing laws, regulations and secondary legislation relating to the processing of Personal Data and the privacy of electronic communications, as amended, replaced or updated from time to time, including the Privacy and Electronic Communications Directive (2002/58/EC) and the Privacy and Electronic Communications (EC Directive) Regulations 2003 (SI 2003/2426);
“Data Subject” shall have the same meaning as in Data Protection Law;
“DPA” means this data processing agreement together with Exhibits A, B and C;
“GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016;
“Personal Data” shall have the same meaning as in Data Protection Law;
“Processor” means the Company;
means the Processor’s security policy document as updated from time to time, and accessible via https://policy.evercast.us/ or otherwise made reasonably available by the Processor/as set out in Exhibit B of this DPA;
“Standard Contractual Clauses” means the EU model clauses for Personal Data transfer from controllers to processors c2010-593 – Decision 2010/87EU, set out in Exhibit C of this DPA;
“Sub-Processor” means any person or entity engaged by the Processor or its Affiliate to process Personal Data in the provision of the Solution and Services to the Controller.
2.1 The Processor has agreed to provide the Solution and Services to the Controller in accordance with the terms of the Agreement. In providing the Solution and Services, the Processor shall process Customer Data on behalf of the Controller. Customer Data may include Personal Data. The Processor will process and protect such Personal Data in accordance with the terms of this DPA.
3.1 In providing the Solution and Services to the Controller pursuant to the terms of the Agreement, the Processor shall process Personal Data only to the extent necessary to provide the Solution and Services in accordance with the terms of the Agreement, this DPA and the Controller’s instructions documented in the Agreement and this DPA, as may be updated from time to time.
3.2 The Controller and Processor shall take steps to ensure that any natural person acting under the authority of the Controller or the Processor who has access to Personal Data does not process them except on the instructions from the Controller unless he or she is required to do so by any Data Protection Law.
4. Processor Obligations
4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.
4.2 The Processor confirms that it shall process Personal Data on behalf of the Controller and shall take steps to ensure that any person acting under the authority of the Processor who has access to Personal Data shall only process the Personal Data on the documented instructions of the Controller.
4.3 The Processor shall promptly inform the Controller, if in the Processor’s opinion, any of the instructions regarding the processing of Personal Data provided by the Controller, breaches any Data Protection Law.
4.4 The Processor shall ensure that all employees, agents, officers and contractors involved in the handling of Personal Data: (i) are aware of the confidential nature of the Personal Data and are contractually bound to keep the Personal Data confidential; (ii) have received appropriate training on their responsibilities as a data processor; and (iii) are bound by the terms of this DPA.
4.5 The Processor shall implement appropriate technical and organisational procedures to protect Personal Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons.
4.6 The Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In accessing the appropriate level of security, account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed.
4.7 The technical and organisational measures detailed in Exhibit B shall at all times be adhered to as a minimum security standard. The Controller accepts and agrees that the technical and organisational measures are subject to development and review and that the Processor may use alternative suitable measures to those detailed in the attachments to this DPA, provided such measures are at least equivalent to the technical and organisational measures set out in Exhibit B and appropriate pursuant to the Processor’s obligations in clauses 4.5 and 4.6 above.
4.8 The Controller acknowledges and agrees that, in the course of providing the Solution and Services to the Controller, it may be necessary for the Processor to access the Personal Data to respond to any technical problems or Controller queries and to ensure the proper working of the Solution and Services. All such access by the Processor will be limited to those purposes.
4.9 Where Personal Data relating to an EU Data Subject is transferred outside of the EEA it shall be processed in accordance with the provisions of the Standard Contractual Clauses, unless the processing takes place: (i) in a third country or territory recognised by the EU Commission to have an adequate level of protection; or (ii) by an organisation located in a country which has other legally recognised appropriate safeguards in place, such as the EU-US Privacy Shield or Binding Corporate Rules.
4.10 Taking into account the nature of the processing and the information available to the Processor, the Processor shall assist the Controller by having in place appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Controller’s obligation to respond to requests for exercising the Data Subject’s rights and the Controller’s compliance with the Controller’s data protection obligations in respect of the processing of Personal Data.
5. Controller Obligations
5.1 The Controller represents and warrants that it shall comply with this DPA and its obligations under Data Protection Law.
5.2 The Controller represents and warrants that it has obtained any and all necessary permissions and authorisations necessary to permit the Processor, its Affiliates and Sub-Processors, to execute their rights or perform their obligations under this DPA.
5.3 All Affiliates of the Controller who use the Solution or Services shall comply with the obligations of the Controller set out in this DPA.
5.4 The Controller is responsible for compliance with Data Protection Law, including requirements with regards to the transfer of Personal Data under this DPA and the Agreement.
5.5 The Controller shall implement appropriate technical and organisational procedures to protect Personal Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons. The Controller shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In accessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed.
5.6 The Controller may require correction, deletion, blocking and/or making available the Personal Data during or after termination of the Agreement. The Processor will process the request to the extent it is lawful and will reasonably fulfil such request in accordance with its standard operational procedures to the extent possible.
5.7 The Controller acknowledges and agrees that some instructions from the Controller, including destruction or return of data, the Processor assisting with audits, inspections, DPIAs or providing any assistance under this DPA, may result in additional fees. The Processor shall be entitled to charge the Controller for its costs and expenses in providing any such assistance.
6.1 The Controller acknowledges and agrees that: (i) Affiliates of the Processor may be used as Sub-processors; and (ii) the Processor and its Affiliates respectively may engage Sub-processors in connection with the provision of the Solution and Services.
6.2 All Sub-processors who process Personal Data in the provision of the Solution and Services to the Controller shall comply with the obligations of the Processor set out in this DPA.
6.3 The Controller authorises the Processor to use the Sub-Processors already engaged by the Processor as at the date of the Agreement and the Processor shall make available to the Controller a list of Sub-processors (if any) at https://policy.evercast.us/ authorised to process the Personal Data which shall include the identities of Sub-processors and their country of location. During the term of this DPA, the Processor shall provide the Controller with prior notification, via email, of any changes to the list of Sub-processor(s) before authorising any new or replacement Sub-processor(s) to process Personal Data.
6.4 The Controller may object to the use of a new or replacement Sub-processor, by notifying the Processor promptly in writing within ten (10) Business Days after receipt of the Processor’s notice. If the Controller objects to a new or replacement Sub-processor, the Controller may terminate the Agreement with respect to those Solution and Services which cannot be provided by the Processor without the use of the new or replacement Sub-processor. The Processor will refund the Controller any prepaid fees covering the remainder of the Term of the Agreement following the effective date of termination with respect to such terminated Solution or Services.
6.5 All Sub-Processors who process Personal Data shall comply with the obligations of the Processor set out in this DPA. The Processor shall: (i) prior to the relevant Sub-Processor carrying out any processing activities in respect of the Personal Data; (ii) appoint each Sub-Processor under a written contract containing materially the same obligations to those of the Processor in this DPA enforceable by the Processor; and (iii) ensure each such Sub-Processor complies with all such obligations.
6.6 The Controller agrees that the Sub-Processors may transfer Personal Data for the purpose of providing the Solution and Services to the Controller in accordance with the Agreement to countries outside the European Economic Area (EEA). The Processor confirms that such Sub-processors: (i) are located in a third country or territory recognised by the EU Commission to have an adequate level of protection; or (ii) have entered into Standard Contractual Clauses with the Processor; or (iii) have other legally recognised appropriate safeguards in place, such as the EU-US Privacy Shield or Binding Corporate Rules.
7.1 The Processor shall make available to the Controller all information reasonably necessary to demonstrate compliance with its processing obligations and allow for and contribute to audits and inspections.
7.2 Any audit conducted under this DPA shall consist of examination of the most recent reports, certificates and/or extracts prepared by an independent auditor bound by confidentiality provisions similar to those set out in the Agreement. In the event that provision of the same is not deemed sufficient in the reasonable opinion of the Controller, the Controller may conduct a more extensive audit which will be: (i) at the Controller’s expense; (ii) limited in scope to matters specific to the Controller and agreed in advance; (iii) carried out during UK business hours and upon reasonable notice which shall be not less than 4 weeks unless an identifiable material issue has arisen; and (iv) conducted in a way which does not interfere with the Processor’s day-to-day business.
7.3 This clause shall not modify or limit the rights of audit of the Controller, instead it is intended to clarify the procedures in respect of any audit undertaken pursuant thereto.
8. Data Breach
8.1 The Processor shall notify the Controller without undue delay after becoming aware of (and in any event within 72 hours of discovering) any accidental or unlawful destruction, loss, alteration or unauthorised disclosure or access to any Personal Data (“Data Breach”).
8.2 The Processor will take all commercially reasonable measures to secure the Personal Data, to limit the effects of any Data Breach, and to assist the Controller in meeting the Controller’s obligations under applicable law.
9. Compliance, Cooperation and Response
9.1 In the event that the Processor receives a request from a Data Subject in relation to Personal Data, the Processor will refer the Data Subject to the Controller unless otherwise prohibited by law. The Controller shall reimburse the Processor for all costs incurred resulting from providing reasonable assistance in dealing with a Data Subject request. In the event that the Processor is legally required to respond to the Data Subject, the Controller will fully cooperate with the Processor as applicable.
9.2 The Processor will notify the Controller promptly of any request or complaint regarding the processing of Personal Data, which adversely impacts the Controller, unless such notification is not permitted under applicable law or a relevant court order.
9.3 The Processor may make copies of and/or retain Personal Data in compliance with any legal or regulatory requirement including, but not limited to, retention requirements.
9.4 The Processor shall reasonably assist the Controller in meeting its obligation to carry out data protection impact assessments (DPIAs), taking into account the nature of the processing and the information available to the Processor.
9.5 The Controller shall notify the Processor within a reasonable time, of any changes to applicable data protection laws, codes or regulations which may affect the contractual duties of the Processor. The Processor shall respond within a reasonable timeframe in respect of any changes that need to be made to the terms of this DPA or to the technical and organisational measures to maintain compliance. If the parties agree that amendments are required, but the Processor is unable to accommodate the necessary changes, the Controller may terminate the part or parts of the Solution and Services which give rise to the non-compliance. To the extent that other parts of the Solution and Services provided are not affected by such changes, the provision of those Solution and Services shall remain unaffected.
9.6 The Controller and the Processor and, where applicable, their representatives, shall cooperate, on request, with a supervisory data protection authority in the performance of their respective obligations under this DPA and Data Protection Law.
10.1 The limitations on liability set out in the Agreement apply to all claims made pursuant to any breach of the terms of this DPA.
10.2 The parties agree that the Processor shall be liable for any breaches of this DPA caused by the acts and omissions or negligence of its Sub-processors to the same extent the Processor would be liable if performing the services of each Sub-processor directly under the terms of the DPA, subject to any limitations on liability set out in the terms of the Agreement.
10.3 The parties agree that the Controller shall be liable for any breaches of this DPA caused by the acts and omissions or negligence of its Affiliates as if such acts, omissions or negligence had been committed by the Controller itself.
10.4 The Controller shall not be entitled to recover more than once in respect of the same loss.
11. Term and Termination
11.1 The Processor will only process Personal Data for the term of the DPA. The term of this DPA shall coincide with the commencement of the Agreement and this DPA shall terminate automatically together with termination or expiry of the Agreement.
11.2 The Processor shall at the choice of the Controller, upon receipt of a written request received within 30 days of the end of the provision of the Solution and Services, delete or return Personal Data to the Controller. The Processor shall in any event delete all copies of Personal Data in its systems within 60 days of the effective date of termination of the Agreement unless: (i) applicable law or regulations require storage of the Personal Data after termination; or (ii) partial Personal Data of the Customer is stored in backups, then such Personal Data shall be deleted from backups up to 1 year after the effective date of termination of the Agreement.
12.1 This DPA sets out the entire understanding of the parties with regards to the subject matter herein.
12.2 Should a provision of this DPA be invalid or become invalid then the legal effect of the other provisions shall be unaffected. A valid provision is deemed to have been agreed which comes closest to what the parties intended commercially and shall replace the invalid provision. The same shall apply to any omissions.
12.3 Subject to any provision of the Standard Contractual Clauses to the contrary, this DPA shall be governed by the laws of England and Wales. The courts of England shall have exclusive jurisdiction for the settlement of all disputes arising under this DPA.
12.4 The parties agree that this DPA is incorporated into and governed by the terms of the Agreement.
Overview of data processing activities to be performed by the Processor
The Controller transfers Personal Data identified in sections 3, 4 and 5 below, as it relates to the processing operations identified in section 6 below.
The Controller is the Customer.
The Processor received data identified in sections 3, 4 and 5 below, as it relates to the processing operations identified in section 6 below.
The Processor is the Company.
3. Data Subjects
The Personal Data transferred includes but is not limited to the following categories of Data Subjects:
• Employees, freelancers and contractors of the Controller.
• Authorised Users, Affiliates and other participants from time to time to whom the Controller has granted the right to access the Solution and Services in accordance with the terms of the Agreement.
• Ad-Hoc users, users who have been invited as temporary, guest, or invited participants to the Services.
• Clients of the Controller and individuals with whom those end users communicate with by email and/or other messaging media.
• Employees of clients of the Controller.
• Suppliers and service providers of the Controller.
• Other individuals to the extent identifiable in the content of emails or their attachments or in archiving content.
4. Categories of Data
The Personal Data transferred includes but is not limited to the following categories of data:
• Personal details, names, user names, passwords, email addresses of Authorised Users.
• Personal Data derived from the Authorised Users use of the Solution and Services such as records and business intelligence information.
• Personal Data within email and messaging content which identifies or may reasonably be used to identify, data subjects.
• Meta data including sent, to, from, date, time, subject, which may include Personal Data.
• Video, image and sounds recordings containing personal conversations.
• Financial data.
• Consumption habits.
• Data concerning education and profession.
• File attachments that may contain Personal Data.
• Survey, feedback and assessment messages.
• Information offered by users as part of support enquiries.
• Other data added by the Controller from time to time.
5. Special categories of Data
Personal Data transferred includes but is not limited to the following special categories of data:
• Video recordings which can be used to identify authorized users of the system.
• Video stills which can be used to identify authorized users of the system.
• Visual biometric profiles for authorized users of the system.
6. Processing operations
The Personal Data transferred will be subject to the following basic processing activities:
• Personal Data will be processed to the extent necessary to provide the Solution and Services in accordance with both the Agreement and the Controller’s instructions. The Processor processes Personal Data only on behalf of the Controller.
• Processing operations include but are not limited to: management of user recordings, verification of email addresses, verification of contact information, monitoring of user connections, tracking user access, extracting metadata from video recordings, extracting attendee lists from video recordings, transcribing video recordings, archiving video recordings, extracting biometric (identification) data from video images. These operations relate to all aspects of Personal Data processed.
• Processing operations additionally include but are not limited to: management of employees and intermediaries, monitoring of the workplace, client management, appraisals, performance reviews, feedback, objectives and personal development tracking, making comments and updates on these, management of lists of employees, intermediaries and other users, providing support to user and other HR functions. These operations relate to all aspects of Personal Data processed.
• Technical support, issue diagnosis and error correction to ensure the efficient and proper running of the systems and to identify, analyse and resolve technical issues both generally in the provision of the Solution and Services and specifically in answer to a Controller query. This operation may relate to all aspects of Personal Data processed but will be limited to metadata where possible.
• Virus, anti-spam and Malware checking in accordance with the Solution and Services provided. This operation relates to all aspects of Personal Data processed.
• URL scanning for the purposes of the provision of targeted threat protection and similar service which may be provided under the Agreement. This operation relates to attachments and links in emails and will relates to any Personal Data within those attachments or links which could include all categories of Personal Data.
Technical and Organisational Security Measures
The Processor is routinely certified through e security audit proceses and in particular has been approved for use by the majority of the major studios. The Processor will continue to maintain these audit standards and/or other substantially similar or equivalent standards for the term of the Agreement.
The Processor utilises third party data centres. Our primary cloud provider (Amazon AWS) is ISO 27001 and PCI DSS certified. AWS has many other certifications, as well, which can be read about here: https://aws.amazon.com/compliance/programs/ The Processor will not utilise third party data centres that do not maintain the aforementioned certifications and/or attestations, or other substantially similar or equivalent certifications and/or attestations.
Upon the Controller’s written request (no more than once in any 3 month period), the Processor shall provide within a reasonable time, a copy of the most recently completed certification and/or attestation reports (to the extent that to do so does not prejudice the overall security of the Solution and Services). Any audit report submitted to the Controller shall be treated as Confidential Information and subject to the confidentiality provisions of the Agreement between the parties.
The Processor’s Security Overview can be found at https://policy.evercast.us/, under “Technical Application and Security Measures“
The security overview provides an overview of the technical and organisational security measures implemented. It should be noted however that, in some circumstances, in order to protect the integrity of the security measures and in the context of data security, detailed descriptions may not be available, however additional information regarding technical and organisational measures may be found in the Security Policy. It’s acknowledged and agreed that the Security Policy and the technical and organisational measures described therein will be updated and amended from time to time, at the sole discretion of the Processor. Notwithstanding the foregoing, the technical and organisational measures will not fall short of those measures described in the Security Policy in any material, detrimental way.
Commission Decision C(2010)593
Standard Contractual Clauses (processors)
For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection
the Controller, (the data “exporter”)
the Processor, (the data “importer”)
each a “party”; together “the parties”,
HAVE AGREED on the following Standard Contractual Clauses (the “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Exhibit A of the DPA.
For the purposes of the Standard Contractual Clauses all terms used in capitals shall have the meaning given to them in the DPA unless defined otherwise below:
(a) ‘personal data’, ‘special categories of data’, ‘process/processing’, ‘controller’, ‘processor’, ‘data subject’ and ‘supervisory authority’ shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data ;
(b) ‘the data exporter’ means the controller who transfers the personal data;
(c) ‘the data importer’ means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Standard Contractual Clauses and who is not subject to a third country’s system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
(d) ‘the subprocessor’ means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Standard Contractual Clauses and the terms of the written subcontract;
(e) ‘the applicable data protection law’ means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
(f) ‘technical and organisational security measures’ means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
Details of the transfer
The details of the transfer and in particular the special categories of personal data where applicable are specified in Exhibit A of the DPA which forms an integral part of the Standard Contractual Clauses.
Third-party beneficiary clause
1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Standard Contractual Clauses.
4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
Obligations of the data exporter
The data exporter agrees and warrants:
(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter’s behalf and in accordance with the applicable data protection law and the Standard Contractual Clauses;
(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in the Security Policy;
(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
(e) that it will ensure compliance with the security measures;
(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
(h) to make available to the data subjects upon request a copy of the Standard Contractual Clauses, with the exception of the Security Policy, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Standard Contractual Clauses, unless the Standard Contractual Clauses or the contract contain commercial information, in which case it may remove such commercial information;
(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Standard Contractual Clauses; and
(j) that it will ensure compliance with Clause 4(a) to (i).
Obligations of the data importer
The data importer agrees and warrants:
(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Standard Contractual Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Standard Contractual Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
(c) that it has implemented the technical and organisational security measures specified in the Security Policy before processing the personal data transferred;
(d) that it will promptly notify the data exporter about:
(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
(ii) any accidental or unauthorised access, and
(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred;
(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Standard Contractual Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority;
(g) to make available to the data subject upon request a copy of the Standard Contractual Clauses, or any existing contract for subprocessing, unless the Standard Contractual Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of the Security Policy which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11;
(j) to send promptly a copy of any subprocessor agreement it concludes under the Standard Contractual Clauses to the data exporter.
1. The parties agree that any data subject, who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.
The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Standard Contractual Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Standard Contractual Clauses.
Mediation and jurisdiction
1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Standard Contractual Clauses, the data importer will accept the decision of the data subject:
(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;
(b) to refer the dispute to the courts in the Member State in which the data exporter is established.
2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law.
Cooperation with supervisory authorities
1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b).
The Standard Contractual Clauses shall be governed by the law of the Member State in which the data exporter is established.
Variation of the contract
The parties undertake not to vary or modify the Standard Contractual Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Standard Contractual Clauses.
1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Standard Contractual Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Standard Contractual Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Standard Contractual Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor’s obligations under such agreement.
2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Standard Contractual Clauses.
3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
4. The data exporter shall keep a list of subprocessing agreements concluded under the Standard Contractual Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.
Obligation after the termination of personal data processing services
1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
1. These Standard Contractual Clauses take priority over any other agreement between the parties, whether entered into before or after the date these Standard Contractual Clauses are entered into.
2. Unless the Standard Contractual Clauses are expressly referred to and expressly amended, the parties do not intend that any other agreement entered into by the parties, before or after the date the Standard Contractual Clauses are entered into, will amend the terms or the effects of the Standard Contractual Clauses, or limit any liability under the Standard Contractual Clauses, and no term of any such other agreement should be read or interpreted as having that effect.
3. The parties intend that these Standard Contractual Clauses should only become effective if Art 44 of the GDPR applies to a transfer of personal data from the EEA to the UK, because the UK has left the European Union, and the transfer is not permitted under Art 45 of the GDPR.
4. On that basis, the Standard Contractual Clauses will become effective on:
(a) the first date Article 44 GDPR applies to a transfer of personal data from the EEA to the UK, and that transfer is not permitted under Article 45 GDPR; or
(b) the date the parties enter into the DPA, if later.
5. In this clause, ‘a transfer of personal data’ has the same meaning as in Article 44 of the GDPR.
All terms defined in this SLA shall have the meaning set out in the Terms and Conditions, unless defined otherwise in this SLA.
Hosting services shall include hosting of the Solution together with related components and Customer owned content as set out below.
The Company will use commercially reasonable measures in terms of redundancy, monitoring and platform management to make the Solution available via the Internet 24 hours a day 7 days a week.
The infrastructure and security provided by the Company and the data centres it uses to provide the Solution is set out in detail in the DPA.
Support services shall include maintenance of the Solution and Customer platform including corrective maintenance and enhancements and a customer support service for the Solution and Customer platform as set out below.
Maintenance and support services shall not be provided for issues arising from: (i) modifications, alteration or configuration of any part of the Solution by the Customer or a third party that has not been authorised in writing by the Company; and/or (ii) technology or IPR that has not been provided by the Company pursuant to the terms of the Agreement.
The Company provides support services from a US support centre which is available to named support users. Support services are provided in English.
Problems may be reported to the support centre by email, telephone or via the Internet, using the help desk tool.
Upon receipt of a problem notification the Company shall respond to the Customer, within the time frame set out in clause 4.2 of this SLA as applicable, based on the severity and type of problem. Such response shall specify the severity level and type of problem.
The Company offers support for the Solution during Business Hours on Business Days in English.
Problems with the Solution will be dealt with in accordance with their level of severity. The time frame in which problems will be resolved will depend upon whether they are classified as a bug or incident as set out below.
A problem is classified as medium if a key feature or service is unavailable and the availability of the Solution is not affected.
A problem is classified as low if there is any other problem that does not fall into another severity category.
A problem is classified as high if the Solution is not available, or the Customer or Authorised Users cannot log in or if there appear to be serious performance or access problems.
7 Business Days
Permanent work around
Within 1 Business Day
1 Business Day
3 Business Days
3 Business Hours
Within 4 Business Hours
3 Business Hours
4 Business Hours
1 Business Hour
Within 1 Business Hour
Temporary work around
Target Resolution Time
Target Resolution Time
5. MAINTENANCE SERVICES
Releases will contain new or amended features. There may be some need for configuration and additional user training in order to obtain the maximum benefit of the new features. Releases do not significantly impact the existing technical setup of the Customer or training materials. Releases are numbered as follows: 3.1, 3.2, 3.3, etc.
The Company reserves the right to vary the frequency of Releases.
All releases are penetration tested by an external third party provider according to our periodic testing schedule.
Patches provide bug fixes, performance and SLA improvement. Such features and functionality do not impact the current configuration of the Customer, nor require additional training.
There are 2 categories of patches:
Normal Patches which include fixes on medium or low severity bugs, as well as a combination of change requests and small features. These patches are deployed weekly during the maintenance window.
Emergency Patches include fixes on issues that are qualified as urgent by the Company, or relate to high severity bugs, security threats, performance, or availability. Emergency patches are deployed as and when necessary.
Patches are deployed as required for all Customers of a given release. Deployment usually takes place during low system traffic time. The deployment is usually 100% automatic. All existing setup and data will remain unchanged. No user or administrator intervention is required. No manual intervention of the Customer administrator is required.
The Company usually carries out planned maintenance in the maintenance windows set out below. If planned maintenance is to be performed outside of these windows the Company shall give the Customer at least 48 hours prior notice.
Normal Patches, Releases, and Platform Upgrades
Upfront Notice Period
Maximum interruption of service
Interruption of service
Around 8AM EST M-Th
The Company shall where possible, provide the Customer with prior notice of emergency maintenance. However, work may commence at any time and shall continue until completed.
Upfront Notice Period
Maximum interruption of service
Interruption of service
The Customer has the following obligations under this SLA:
The Company shall not be liable for, and shall have no obligation to fix, any errors, Incidents, problems or bugs or any lack of availability of the Solution caused by the following:
February 2019 (4 pages total)
Technical Application and Security Measures
Evercast is an HTML5 WebRTC-based collaboration tool. Media is transmitted from the user’s browser and/or Evercast Broadcasting Software (EBS) client to an Evercast video relay server (the SFU). The SFU either then relays the RTP traffic to the other participants in the room and then immediately discards that RTP traffic, or (if the room is set to be recorded by the room’s host) the SFU writes the media traffic to a file which gets persisted in an encrypted (AES 256 SSE-C) and private S3 bucket.
Evercast’s internal network and servers, including the API and the video servers, are protected by AWS EC2 security policies and IAM (Identity and Access Management) policies. Additionally, the images that makeup our servers are hardened from the inside out, including a limited number of processes, exposed ports, and elevated permissions.
Our vulnerability management policies include server vulnerability testing. The server baselines are audited routinely and built from trusted images. Administrative privileges are restricted to and within the infrastructure team.
Unmanaged hardware access is prevented using a virtual cloud, which allows access only to the resources created inside our cloud infrastructure and to authenticated VPN clients. Other devices are prevented from physically accessing the cloud-based network. Amazon AWS Network provides a secure network infrastructure to control and monitor communications internally and at the boundary. The boundary devices employ configurations and ACLs to control the flow of information.
Evercast is built with extra security features to help prevent idle-session hijacking. Because the integrity of the software running on a user’s device (i.e. endpoint) is outside the control of Evercast, we provide “Best Practices” documentation to help users stay safe:
1) Users should always connect from a trusted network. Examples include a secured office environment, or a trusted home network. In addition to our efforts to use secure encryption, this further reduces risk of attacks on the transport encryption used to protect the media stream between your endpoint and our servers.
2) Antivirus and firewall protections can be enabled on users devices as routine ways to bolster their security. Additionally, operating system and application security updates should be maintained on client endpoints to reduce risk of endpoint compromise.
3) Evercast sessions are protected from hijacking attacks and expire after a period of time by default. Additionally, idle sessions result in connection token expiration. Users can further protect themselves by closing their browser window after they have finished with an Evercast session.
Client content (both video content and metadata) is encrypted at rest. This includes both the database and S3 buckets. AES 256 encryption is applied using SSE-C, and additional configuration options are available for enterprises. These include having dedicated S3 buckets with their own SSE-C keys, and granting our system access via IAM roles.
In transit, data is encrypted with standard SSL via HTTPS and DTLS / SRTP. Our servers earn an A+ rating on SSLLabs, and we have a long duration for our HTTP Strict Transport Security (HSTS) caching. We routinely undergo third-party assessments, and our most-recent assessment is available for client review.
It is worth noting that Evercast exists as a multi-tenant environment. We utilize role-based access control and row-level security features at the database-level to segregate client data. We go to great lengths to protect against session hijacking and other situations which can compromise the privacy of a user’s content and data. Recordings are managed by the Evercast application, which does not provide the user with any way to download those recordings. All access is managed through the Evercast application.
All data access from the Internet will happen using the application authorized endpoints, and the application has been hardened against attacks. For non-application data access from the Internet, proper firewall rules, upgrade policies, authentication and encryption will prevent access. Direct access from the Internet to the data storage/database will not be allowed. A defense-in-depth approach is used, consisting of multiple security layers (firewall, private networking, authentication and authorization).
Every issue is escalated to the infrastructure team. Urgent vulnerabilities are handled on an immediate basis. If there is a breach or an incident, we work continuously on the the issue until it is remediated with highest priority. Affected clients are notified immediately after the incident is contained and not later than appropriate periods after discovery of any incident. If there are issues reported during a vulnerability assessment or through responsible disclosure then these issues will be addressed on a priority basis (depending on the complexity), and integrated into the next major release.
To further mitigate risk and manage vulnerabilities, we also take a proactive approach to incident response by self-auditing our application. In addition to automated tools like Snyk, Cloudsploit, Burpsuite, OpenVAS, and others, our developers are both educated about and use in daily practice, secure coding standards (i.e. stored procedures, database-level security and type-checking, etc).
Automated security scans are conducted throughout the software development lifecycle. On every pull-request, Snyk.io checks the open source dependencies listed in our package.json files for vulnerabilities. To check for new vulnerabilities in the entire cloud infrastructure, a Cloudsploit scan is performed every 6 hours. Cloudsploit executes over 700 automated tests on Amazon AWS infrastructure.
Internal security reviews and application audits using both automated vulnerability scanners and manual hacking are conducted quarterly, and semi-annual third-party security reviews are scheduled. The first internal security review and application audit was conducted at the end of 2017.
Logging and Monitoring
Our application, server, and network auditing logs are collected using specific tools provided by our cloud vendor. These tools include Amazon AWS Cloudtrail for collecting administrative actions, and Amazon AWS Config for collecting configuration changes. Correct configuration of Amazon AWS Cloudtrail and Amazon AWS Config is monitored using Cloudsploit. Logging is enabled on all application servers as well, and logs are centrally collected and secured in Sumo Logic with a one year retention. Quarterly, we review the logs for signs of malicious behavior.
For clients that want a real-time feed of logs relevant to their data, we provide access to these
To use Evercast requires access to standard HTTP/HTTPS and TCP on select ports (configurable). An example range would be TCP/8989 and UDP 8000-9000. Video can be tunneled through standard TCP though performs best with UDP access.
Access to the site is filtered through Cloudflare, which protects against SQLi, XSS injections, DoS, and known malicious IP addresses.
Developers work remotely on their own networks, separated entirely from production / testing / development servers. Production, testing, and development servers can only be accessed via a VPN. Only privileged users have access to VPN and relevant server keys.
Amazon AWS network offers additional protection and identification of several types of attack, including Distributed Denial-of-Service (DDoS), port scanning and packet sniffing.
Policy and Governance
Our cloud provider (Amazon AWS) is ISO 27001 and PCI DSS certified. AWS has many other certifications, as well, which can be read about here: https://aws.amazon.com/compliance/programs/
Some of the guidelines for application development include:
AWS-access is granted on a need-to-know basis to senior members of the development and infrastructure teams. All AWS users / keys are granted the minimum privileges required to accomplish their task. Application-level access management prevents users from joining each other’s private rooms when they are not invited.
We implement RBAC policies for all of our tables and database stored procedures. This ensures that unauthenticated users cannot access data meant for logged-in users. Additionally, it prevents logged-in users from accessing super-user features. At the system-level, users are not added once the image is built. When building the image, user accounts are added and hardened by the infrastructure team.
JSON Web Tokens (JWTs) provide a cryptographic identity to our users at the application level, allowing them access to their content in the database. Double-submit tokens, also known as nonces, protect our API from cross-site scripting attacks. JWTs are assigned to clients after authentication, and passwords are stored using pgcrypto / blowfish. These tokens are stored in secure cookies (i.e. __Host-prefixed cookies).
In AWS, programmatic access keys and restrictive security policies are provisioned by the Evercast tech-lead as business needs dictate. Credentials for production environments are only provided to the development team-lead and the infrastructure team-lead. AWS Infrastructure is protected by security groups and log trails. Infrastructure is manually audited semi-annually and automatically audited multiple times each day.
Vendor recommends running a malware scan using Avast, Malwarebytes, or similar app that helps enable Authorized Users to detect and delete any malicious software that could be lurking in their computer.