Security Policy

• We have implemented a formal procedure for security events and have educated all our staff on our policies.

• When security events are detected they are escalated, and our team is notified and assembled to rapidly address the event.

• After a security event is fixed, we write up a post-mortem analysis.

• The analysis is reviewed in person, distributed across the company, and includes action items that will make the detection and prevention of a similar event easier in the future.

• GlowPro will promptly notify you in writing upon verification of a security breach of the GlowPro services that affects your data. Notification will describe the breach and the status of GlowPro's investigation.

• We have functioning, frequently used automation in place so that we can safely and reliably roll out changes to both our application and operating platform within minutes.

• We typically deploy code many times a day, so we have high confidence that we can get a security fix out quickly when required.

• We have two-factor authentication (2FA) and strong password policies on GitHub, Heroku, AWS, and Vercel to ensure access to cloud services is protected.

• All of our services run in the cloud. GlowPro does not run our own routers, load balancers, DNS servers, or physical servers.

• We have services and data hosted in AWS facilities and protected by AWS security, as described at https://aws.amazon.com/security/sharing-the-security-responsibility.

• We have services and data hosted on Heroku and protected by Heroku security, as described at https://www.heroku.com/policy/security.

• We have services hosted on Vercel and protected by Vercel security, as described at https://vercel.com/security.

• GlowPro services have been built with disaster recovery in mind. We backup all datastores that contain customer data.

• We use Sentry for application monitoring to quickly identify and resolve incidents. Sentry's security policy is described at https://sentry.io/security.

• All access to GlowPro applications is logged.

• Actions taken on production consoles or in the GlowPro application are logged.

• GlowPro data is hosted in Amazon Web Services (AWS) facilities in the USA (us-east-1).

• GlowPro data is hosted in Heroku, which in turn is hosted on AWS. Refer to Heroku's security policy here.

• Customer data is stored in multi-tenant datastores; we do not have individual datastores for each customer. However, strict privacy controls exist in our application code that are designed to ensure data privacy and to prevent one customer from accessing another customer’s data (i.e., logical separation).

• Each GlowPro system used to process customer data is adequately configured and patched using commercially-reasonable methods according to industry-recognized system-hardening standards.

• GlowPro engages certain subprocessors (AWS, Heroku, Vercel) to process customer data.

• GlowPro is served 100% over HTTPS.

• All data sent to or from GlowPro is encrypted in transit using 256-bit encryption.

• Our API and application endpoints are TLS/SSL only.

• We encrypt all sensitive data using an industry-standard AES-256 encryption algorithm.

• Managing your own user account and organizations on GlowPro.

• Protecting your own account and user credentials by securing your email when accessing GlowPro services.

• Compliance with the terms of services agreement with GlowPro, including with respect to compliance with laws.

• Promptly notify GlowPro if a user credential has been compromised or if you suspect possible suspicious activities that could negatively impact the security of GlowPro services or your account.

• You may not perform any security penetration tests or security assessment activities without the express advance written consent of GlowPro.