Security Measures
Last updated: November 7, 2026
These Security Measures describe how PortlandLabs protects Customer Data in Neighborhood.online. They are the "Security Measures" under Section 3.2 of the Standard Terms. We use reasonable, industry-standard measures. No system is perfectly secure, and we do not promise that the Service will be free of every security incident.
1. Hosting
- The Service runs on Amazon Web Services in the United States. AWS is independently certified under SOC 2 and ISO 27001. PortlandLabs is pursuing its own SOC 2 Type II and ISO 27001 certifications.
- Databases, file storage, and application servers run in private networks. Databases and caches accept connections only from the Service's own application servers.
- Uploaded documents are read and converted in an isolated environment with no internet access.
2. Encryption
- Data is encrypted in transit using TLS. Browsers are told to use HTTPS only.
- Databases, file storage, caches, and backups are encrypted at rest with managed keys that are rotated.
- Contact details, such as email addresses, phone numbers, and mailing addresses, are also encrypted field by field.
- Passwords are stored only as one-way hashes.
3. Access
- An association's records are available only to people with an active role in that association and to people the association chooses to share them with.
- Users can turn on two-factor authentication. Repeated sign-in attempts are limited.
- PortlandLabs staff must use two-factor authentication. Staff access Customer Data only when needed to operate, support, or secure the Service. Staff access to an association's account is logged and read-only unless a senior administrator allows changes.
- Passwords, keys, and other secrets are kept in a managed secrets store, not in our code.
4. Protecting the Service
- A web application firewall filters traffic to the Service.
- Uploaded files are scanned for malware before they are accepted.
- Software dependencies are checked for known vulnerabilities when we build the Service, and server images are scanned when they are created.
- We keep logs of network traffic, requests, and administrative actions to help detect and investigate problems.
5. Backups
- The database and stored files are backed up daily. Backups are kept for up to 35 days and then expire.
6. Security incidents
- We follow procedures to detect and respond to security incidents. If a security incident affects personal information in Customer Data, we will notify Customer as described in the Data Processing Addendum.
7. Reporting a problem
- Report security problems to legal@neighborhood.online.
8. Changes
- We may update these Security Measures as allowed by Section 19.6 of the Standard Terms. Changes will not materially reduce the overall protection of Customer Data during a subscription term.
