Overview
At FeedOtter we take the protection of customer data extremely seriously. This FeedOtter Security Policy describes the measures FeedOtter implements platform wide designed to prevent unauthorized access, use, alteration or disclosure of customer data. The FeedOtter services operate on Amazon Web Services ("AWS"); this policy describes activities of FeedOtter within its instance on AWS unless otherwise specified. As you continue to learn more about FeedOtter we recommend you also review our Terms of Service, Privacy Policy and Data Processing Amendment.
Incident Response
- We have implemented a formal procedure for security events.
- When security events are detected we are notified immediately and our phones are paged in order to rapidly address the event.
- After a security event is fixed we write up a post-mortem analysis.
- The analysis is reviewed and includes action items that will make the detection and prevention of a similar event easier in the future.
- FeedOtter will promptly notify you in writing upon verification of a security breach of the FeedOtter services that affects your data. Notification will describe the breach and the status of FeedOtter's investigation.
Infrastructure
- All of our services run in the cloud. FeedOtter does not run our own routers, load balancers, DNS servers, or physical servers.
- The vast majority of our services and data are hosted in AWS facilities in the USA and protected by AWS security, as described at http://aws.amazon.com/security/sharing-the-security-responsibility. Our services which are hosted outside of AWS include:
- FeedOtter services have been built with disaster recovery in mind.
- All of our infrastructure is spread across 2 AWS data centers (availability zones) and will continue to work should any one of those data centers fail unexpectedly. Amazon does not disclose the location of its data centers. As such, FeedOtter builds on the physical security and environmental controls provided by AWS. See http://aws.amazon.com/security for details of AWS security infrastructure.
- All of our servers are within our own virtual private cloud (VPC) with network access control lists (ACL’s) that prevent unauthorized requests getting to our internal network.
- FeedOtter uses a backup solution for datastores that contain customer data.
Data Storage
- All customer data is encrypted at-rest and stored in the USA.
- 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 to ensure data privacy and prevent one customer from accessing another customers data.
- Database backups are performed daily and retained for three days. All backup data is encrypted.
- Each FeedOtter system used to process customer data is adequately configured and patched using commercially-reasonable methods according to industry-recognized system-hardening standards.
- FeedOtter engages certain subprocessors to process customer data, including the following list which may be updated from time to time:
- Amazon Web Services, Inc.
- Digital Ocean, Inc.
- Intercom, Inc.
- Stripe, Inc.
Data Transfer
- All data sent to or from FeedOtter is encrypted in-transit using 256-bit encryption.
- Our API and application endpoints are TLS/SSL only and score an "A+" rating on SSL Labs' tests. This means we only use strong cipher suites and have features such as HSTS and Perfect Forward Secrecy fully enabled.
Authentication
- FeedOtter is served 100% over https. FeedOtter runs a zero-trust corporate network.
- There are no corporate resources or additional privileges from being on FeedOtter's network.
- We have two-factor authentication (2FA) and strong password policies on AWS, DNS Made Easy, GitHub, Intercom, Help Scout, Postmark, Stripe and Google to ensure access to cloud services are protected.
Application Monitoring
- On an application level, we produce audit logs for all activity, ship logs to AWS for analysis, and use S3 for archival purposes.
- All access to FeedOtter applications is logged and audited.
- All actions taken on production consoles are logged.
- Bastion hosts are used to login to devices.
Security Audits
We use technologies such as AWS Cloudtrail, AWS Cloudwatch Logs and Loggly to provide an audit trail over our infrastructure and the Prefinery application. Auditing allows us to do ad-hoc security analysis, track changes made to our setup and audit access to every layer of our stack.
Payment Processing
All payment instrument processing for purchase of the FeedOtter services is performed by Stripe. For more information on Stripe's security practices, please see https://stripe.com/docs/security/stripe.
Customer Responsibilities
- Protecting your account and user credentials, including passwords and API keys.
- Compliance with the Terms of Services agreement with FeedOtter, including with respect to compliance with laws.
- Promptly notifying FeedOtter if a user credential has been compromised or if you suspect possible suspicious activities that could negatively impact security of the FeedOtter services or your account.
- You may not perform any security penetration tests or security assessment activities without the express advance written consent of FeedOtter.
