Security & Privacy

01Physical Access Control

Felt runs on public clouds, including Amazon Web Services and Render, and doesn’t operate its own servers. Felt employees have no physical access to the data centers, servers, or storage.

02Render

Render is a Platform as a Service provider. Felt uses Render’s services in its Oregon, US datacenter.

Render is independently audited for SOC 2 compliance. All sensitive Felt data stored on Render is encrypted at rest.

03Amazon Web Services (AWS)

AWS is the leading cloud provider used by enterprises and governments worldwide. Felt uses AWS’ services in the US and, for workspaces that choose another region, in the EU, UK, Canada, or Australia. By using AWS, Felt inherits all the security and compliance features built by AWS and relied on by the world’s biggest companies, including most of the world’s leading financial institutions.

04Logical Access Control

All Felt employees use designated accounts to access our infrastructure. Employees are not allowed to share access credentials. All access is further protected behind two-factor authentication. All private keys are stored with strong encryption. Access controls are monitored automatically every day and manually quarterly.

05Penetration Testing

Felt employs annual penetration testing by an independent third-party. The third-party engages with the production instances of the Felt service and is under contract.

Any findings from the penetration testing are investigated by Felt’s security team and prioritized accordingly. Penetration testing schedule is monitored automatically.

06Third-Party Audits

Both Render and AWS are rigorously audited by third-parties. Both Render and AWS hold SOC 2 Type 2 compliance as well as ISO 27001 certification.

Felt undergoes SOC 2 compliance audits and has obtained our SOC 2 Type 2 report.

07Intrusion Prevention and Detection

Felt aims to make unauthorized intrusion as hard as possible. All Felt compute instances both on AWS and Render run in their own virtual private networks. No Felt compute instance allows SSH access and all compute instances on AWS use a Serverless infrastructure, meaning all instances are ephemeral and automatically killed when their task is complete or they reach their age-limit, currently set to 24 hours.

Furthermore, Felt uses AWS’s CloudTrail technology to monitor access to its services and Cloudtrail logs are further automatically monitored daily for unauthorized access.

01Provisioning

Felt is over-provisioned, meaning all non-transient services like compute instances and databases have a lot of extra capacity in case of a demand spike. Our compute platform on Render is automatically spread across different availability zones and our platform on AWS is automatically horizontally scalable via Amazon’s Serverless stack.

02Business Continuity Planning (BCP)

All customer data is uploaded to AWS’ S3 service. Felt uses version-controlled S3 buckets with 99.99% availability. All data that is stored on Render is backed up daily. Felt also runs annual business continuity recovery exercises and their schedule is monitored automatically.

03Disaster Recovery

All Felt data is uploaded to AWS’ S3 service and all Felt buckets are versioned controlled with no public access permissions. In the unlikely case of a disaster, Felt is able to recover the original data from S3 buckets.

01Data Encryption

All customer data uploaded to Felt is encrypted in transit and at rest. Customer data uploads from the browser happen over HTTPS via transport layer security (TLS) encrypted connections and the data is stored on versioned AWS S3 buckets that are server-side encrypted. The settings on these buckets are monitored daily automatically.

Application data that is stored on Render databases are also stored with encryption at rest. Felt never stores your password in cleartext.

All Felt web traffic happens over HTTPS and certificates are managed automatically via Render and Cloudflare. Felt’s HTTPS settings are monitored automatically.

02Data Residency

Felt stores data in the United States by default. On the Enterprise plan, an admin can choose to host a workspace in the US (Oregon), the EU (Frankfurt), the UK (London), Canada (Montréal), or Australia (Sydney). Uploaded files, features, tiles, and analysis results are stored in that region. See what’s stored in each region.

03Self-Hosted Deployment

Enterprise customers can run Felt as a single-tenant instance in their own AWS account, including GovCloud. Maps, data, and user activity stay in their infrastructure, and Felt has no access to data at rest or in transit within their network.

04Felt AI

Felt AI runs on frontier models through Amazon Bedrock. Data processed by Felt AI is never used to train models, and none of it becomes public. Felt AI can reach only the data you have access to.

05Personal Information

Felt collects limited personal information from users, including name, email address, and password. Felt also complies with applicable data protection laws like CCPA. More information is available in our privacy policy.

06Data Access

Felt employees access customer data only for documented reasons and for a limited time. All access happens via individual accounts tied to each employee and is logged for potential audits. Felt employees can store data on their systems for technical troubleshooting or customer support only for a limited time and only if their systems are end-to-end encrypted. Felt employees’ personal devices used for such access are monitored hourly automatically.

01Single Sign-On (SSO)

Enterprise workspaces can have their team log in through their identity provider with SAML 2.0, including Okta, Google, Microsoft Entra ID, OneLogin, JumpCloud, Duo, and Rippling, so IT manages access in one place. Two-factor authentication is handled by the identity provider.

02Google Sign-in

Felt allows users to sign-in via Google in lieu of a password. Signing in via Google allows users to benefit from Google’s world-class authentication safety features such as multi-factor authentication, passkey authentication and federated logins. Many Felt users integrate their federated login systems with Google, allowing them to have a Single Sign-On provider via Google.

03Personal Access Tokens

Felt allows users to create personal access tokens (PAT) to access Felt resources programmatically via application programming interfaces (APIs). PATs are stored with encryption on Felt databases and are exposed in cleartext only during creation. They are never logged. Users can revoke their PATs any time, or create multiple ones for various use-cases.

04Email Security

Felt uses a strong domain-based message authentication, reporting, and conformance (DMARC) setup for its email. This makes spoofing (pretending to be Felt) or phishing scams much harder to employ. Felt’s DMARC settings are monitored automatically daily. For all domain name service setups, including DMARC, Felt uses AWS’ Route 53 service, inheriting the security and audit capabilities of AWS services.

01Continuous Delivery (CD)

Felt uses a continuous delivery methodology to deliver its software, meaning every single code change is delivered quickly to production. This allows quick resolution of customer issues, including security patches.

02Continuous Integration (CI)

Felt uses a continuous integration methodology to develop its software, meaning all code is continuously tested at each step of the progress. These tests include static analysis of our code against vulnerabilities, introduction of unexpected dependencies against supply-chain attacks, as well as unit and integration tests against bugs that might impact users and their security.

03Version Control

All Felt code is version controlled. Code changes must be requested via cryptographically verified methods and all code change must be approved by another person before it can be delivered to production via the CI/CD pipeline.

01Malware Protection

All Felt provided computers are registered to our Mobile Device Management (MDM) software. This MDM ensures that each workstation has correctly configured password managers, automatic updates, antivirus software, full disk encryption, and screensaver lock. These settings are checked for every employee’s workstation every day.

02Contingency Planning

Felt runs regular business continuity and disaster recovery tabletop scenarios to plan for unforeseen events. These events include but are not limited to loss of key personnel, degradation of key infrastructure, and operational force majeure events. The remediations for these possible events are discussed annually.

03Policies

Felt maintains a wide array of policies regarding security. These policies are reviewed and updated annually where necessary.

• Acceptable Use Policy
• Asset Management Policy
• Backup Policy
• Business Continuity Plan
• Code of Conduct
• Controls Assessment Program
• Data Classification Policy
• Data Classification, Handling, and Retention
• Data Protection Policy
• Disaster Recovery Plan
• Encryption Policy
• Incident Management Policy
• Incident Response Plan
• Information Security Policy
• Password Policy
• Physical Security Policy
• Responsible Disclosure Policy
• Risk Assessment Policy
• Software Development Lifecycle Policy
• System Access Control Policy
• Vendor Management Policy
• Vulnerability Management Policy

04Background Checks

Felt runs a background check for all new hires globally. This check contains information such as:

• Enhanced Identity Verification
• US Criminal Record Check
• National Sex Offender Registry Scan
• Security Watchlist Scan
• Fraud Scan
• OFAC Global Sanctions Scan
• Criminal Record Scan
• Federal Record Scan
• Single State County Record Scan
• All State County Record Scan

05Security Training

All Felt employees are required to go through annual security training, as well as be presented with the policies. Acceptance of these policies and completion of security training is monitored automatically before employees can access any internal systems that include customer data.

06Disclosure Policy

Felt aims to notify customers of any data breaches as soon as possible via email and has documented policies for doing so.

01SOC 2 Type 2

Interested parties can reach out to support@felt.com to request a copy of our SOC 2 Type 2 report.

02Data Privacy Addendum

Felt works with many educational institutions with their unique needs such as Family Educational Rights and Privacy Act (FERPA) and Children’s Online Privacy Protection Rule (COPPA) requirements. Felt maintains a strong Data Protection Addendum (DPA). Interested parties can reach out to support@felt.com to request our DPA.

Security researchers are encouraged to reach out to Felt’s security team at security@felt.com via a working proof of concept. Felt does not have a bug bounty program, and encourages researchers to disclose issues responsibly.