Weet Security FAQ

Only you or the persons you share your Weets with can access your content. Besides that, we implement security principles like need-to-know and least-privileges to prevent unauthorized access to your data. Only specific employees  can access user data. Access data is monitored and tracked. We store access logs for a year.

Weet hosts Service Data primarily in GCP data centers that have been certified as ISO 27001, PCI DSS Service Provider Level 1, and/or SOC 2 compliant.

Learn more about Compliance at GCP.

GCP infrastructure services include backup power, HVAC systems, and fire suppression equipment to help protect servers and your data. GCP on-site security includes several features such as security guards, fencing, security feeds, intrusion detection technology, and other security measures. 

Learn more about Data Center Controls at GCP.

Our hosting provider (GCP) maintains industry standard fully redundant and secure network architecture with reasonably sufficient bandwidth as well as redundant network infrastructure to mitigate the impact of individual component failure. Our security team utilizes industry standard utilities to provide defense against known common unauthorized network activity, monitors security advisory lists for vulnerabilities, and undertakes regular external vulnerability scans and audits.

Our infrastructure is well-architected using cloud performance and security best practices.

• Weet is highly available and scalable
• Storage is redundant
• We leverage a global CDN to provide fast access to your content
• Firewall rules segregate our network components 
• Traffic is monitored with IDS technology
• The application is regularly tested against vulnerabilities during the SDLC (DAST/SAST)

Weet is developed and maintained by the Speach team, leveraging its business experience and infrastructure. Speach undergoes an annual SOC2 Type II audit. Our latest SOC2 report can be requested here.

In addition to our extensive internal scanning and testing program, each year, Weet employs third-party security experts to perform a broad penetration test on its application and infrastructure.

• Encryption in Transit

All communications with Weet UI and APIs are encrypted via industry-standard HTTPS/TLS (TLS 1.2 or higher) over public networks. This ensures that all traffic between you and Weet is secure during transit. Additionally, for email, our product leverages opportunistic TLS by default. Transport Layer Security (TLS) encrypts and delivers email securely, mitigating eavesdropping between mail servers where peer services support this protocol. 

• Encryption at Rest

Service Data is encrypted at rest in GCP using AES-256 key encryption.

Weet uses the AWS CDN network, known as Cloudfront, to deliver your videos and images contents more rapidly. Cloudfront offers a way to secure your content by using “Signed URLs.” A signed URL is a URL that provides limited permission and time to make a request. Once the signature appended to the URL has expired, the content cannot be requested anymore, mitigating potentially unauthorized leaks. For authenticated users accessing restricted content through Weet, the signed URL security mechanism will be fully transparent.

We leverage redundant storage technologies to store your data. Additionally, your data is backed up in an encrypted format and stored in a different data center to ease disaster recovery.

While you do not rely on Google or Microsoft for your authentication, Weet follows secure credential storage best practices by never storing passwords in human-readable format, and only as the result of a secure, salted, one-way hash.