Keeping our customers' data protected at all times is our highest priority. This security overview provides a high-level overview of the security practices put in place to achieve that objective.
Have questions or feedback? Feel free to reach out to us at [email protected]
Our security.txt can be accessed here.
All of our services run in the cloud. We don't host or run our own routers, load balancers, DNS servers, or physical servers.
Our service is built on Google Cloud Platform primarily. They provide strong security measures to protect our infrastructure and are compliant with most certifications. You can read more about their practices here:
Network level security monitoring and protection
Our network security architecture consists of multiple security zones. We monitor and protect our network, to make sure no unauthorized access is performed using:
- A firewall that monitors and controls incoming and outgoing network traffic.
- An Intrusion Detection and/or Prevention technologies (IDS/IPS) solution that monitors and blocks potential malicious packets.
- IP address filtering
We use Distributed Denial of Service (DDoS) mitigation services powered by an industry-leading solution.
Encryption in transit: All data sent to or from our infrastructure is encrypted in transit via industry best-practices using Transport Layer Security (TLS). You can see our SSLLabs report here
Data retention and removal
Every user can request the removal of usage data by contacting support.
Read more about our privacy settings at e1.lc/privacy.
Business continuity and disaster recovery
We back up all our critical assets and regularly attempt to restore the backup to guarantee a fast recovery in case of disaster. All our backups are encrypted.
Application security monitoring
- We use technologies to monitor exceptions, logs and detect anomalies in our applications.
- We collect and store logs to provide an audit trail of our applications activity.
Application security protection
- We use a runtime protection system that identifies and blocks OWASP Top 10 and business logic attacks in real-time.
- We use security headers to protect our users from attacks. You can check our grade on this security scanner.
- We use security automation capabilities that automatically detect and respond to threats targeting our apps.
We develop following security best practices and frameworks (OWASP Top 10, SANS Top 25). We use the following best practices to ensure the highest level of security in our software:
- We review our code for security vulnerabilities
- We regularly update our dependencies and make sure none of them has known vulnerabilities
If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly. Please avoid automated testing and only perform security testing with your own data. Please do not disclose any information regarding the vulnerabilities until we fix them.
You can report vulnerabilities by contacting [email protected]. Please include a proof of concept. We will respond as quickly as possible to your submission and won't take legal actions if you follow the rules.
- Dev/staging environments
Accepted vulnerabilities are the following:
- Cross-Site Scripting (XSS)
- Open redirect
- Cross-site Request Forgery (CSRF)
- Command/File/URL inclusion
- Authentication issues
- Code execution
- Code or database injections
While researching, we'd like to ask you to refrain from:
- Denial of Service (DoS)
- Attacks that could harm the reliability/integrity of our business
- Spam attacks
- Social engineering
- Exploits that require physical access to a user's machine
Account takeover protection
We protect our users against data breaches by monitoring and blocking brute force attacks.
- All payment instrument processing is safely outsourced to Stripe which is certified as a PCI Level 1 Service Provider. We don't collect any payment information and are therefore not subject to PCI obligations.
- Our strict internal procedure prevents any employee or administrator from gaining access to user data. Limited exceptions can be made for customer support.