Date: Thu, 28 Mar 2024 19:44:59 -0400 (EDT) Message-ID: <455047443.63.1711669499899@tyr.mbz.io> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_62_422197098.1711669499898" ------=_Part_62_422197098.1711669499898 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Security is one of the most important considerations for Member.buzz. Th= is outlines some of the security procedures in place to protect your inform= ation as you use our platform.
This outline provides a technical insight into our platform beyond a use= r needs to use our platform. For a functional overview of how Member.buzz i= s secured, see Ca= pabilities or our Security Splash Page.
While this document provides some information on our compliance, our official legal terms is always the best source for our offic= ial policies.
All vendors involved in our payment processing have fully-audited&= nbsp;PCI Service Provider Level 1 certifications, which is the= most stringent level of certification available in the payments industry.&= nbsp; Member.buzz is also PCI certified separate from our vendors.= p>
All traffic on Member.buzz is forcibly encrypted over HTTPS using a seri= es of SSL certificates using the TLS 1.2 Protocol, a SHA 256 Signature, and= an RSA 2048 Key.
All Member.buzz sites, including any Space without a custom domain, leve= rage certificates issues by the COMODO Certificate Authority. Space= s with a custom domain are automatically allocated SSL certificates using t= he Let's Encrypt Certificate Authority.
All data stored in our databases is encrypted at rest (using Transparent= Data Encryption) and in transport (using SSL). Additionally, any Sensitive= Personal Information (SPI) is encrypted before it reaches our databases, w= ith one-way hashing used wherever possible. Whenever sensitive informa= tion is displayed in our user interface, it is either partially or fully ma= sked.
As a payments-focused platform, Member.buzz may handle, transmit, or sto= re sensitive information, including the following:
All sensitive data is encrypted.
Member.buzz is hosted in a series of three data centers, all located in = the continental United States of America.
Each data center is actively monitored and protected with multiple layer= s of physical and network security. Firewalls are regularly patched, tested= for vulnerabilities, and actively report any potential threats to our inte= rnal security team.
The Member.buzz platform is distributed between all of our data centers,= making it impossible for individual spaces to choose where their data is s= tored. This gives us the ability to provide the fastest, most secure experi= ence to all of our users.
Access to our servers is highly restricted using centralized access cont= rols and can only be initiated from within our physical internal network. A= ll devices connected to our internal network are actively monitored, patche= d, and protected against malware.
All data is backed up to multiple sites and, in the event of a p= lanned or unplanned outage, traffic is automatically routed to the rema= ining sites within a few seconds. In the event of an unplanned, catastrophi= c disaster affecting one of our data centers, our platform is designed to a= utomatically failover within less than one hour.