Where your data lives
Your data is stored in Amazon Web Services (AWS) in the US-East region. That includes the database and every file you upload, such as documents, recordings, and images.
The application itself is delivered through Cloudflare's global network. Cloudflare sits in front of everything and filters traffic before it ever reaches the servers that hold your data. More on that below.
Encryption
In transit. Every connection between your browser, our application, and our backend uses TLS 1.2 or TLS 1.3. Connections to the database require SSL. There is no unencrypted path to your data.
At rest. The database, its backups, and all stored files are encrypted with AES-256. If someone walked off with the physical disk, they would have nothing they could read.
Keeping your data separate from everyone else's
Every MSP on Built To Run shares the same platform, so the most important question is simple: can another company see your data? No.
Separation is enforced inside the database itself using PostgreSQL Row-Level Security. Every request runs under the signed-in user's identity and is limited to that user's company. We do not rely on the application screen to hide other companies' records. Even if someone tampered with a request in their browser, the database would refuse to return data that belongs to another company.
Inside your company, roles and sharing settings control who sees what. A team member sees the documents, forms, and scorecards their role or a direct assignment allows, and nothing else.
Sign-in and passwords
Passwords. We never store your password. We store a bcrypt hash of it, with a unique random salt for every password. When you set a password, we also check it against the Have I Been Pwned database of known breached passwords, using their k-Anonymity method so your password never leaves our system. If it has shown up in a breach, we will ask you to pick a different one.
Sessions. Once you sign in, your session runs on short-lived tokens that expire on their own.
Multi-factor authentication. MFA is required on every developer and super admin account on our side.
Protection at the front door
All traffic to Built To Run passes through Cloudflare before it reaches our servers. Most attacks are stopped there.
- Web application firewall. Cloudflare's managed rules inspect every request and block common attacks such as SQL injection and cross-site scripting.
- DDoS protection. Floods of traffic meant to knock a site offline are absorbed at Cloudflare's edge, at the network level and the application level.
- Bot protection. Automated scraping and credential-stuffing attempts, where attackers try stolen passwords at scale, are detected and blocked.
- Forced encryption. Browsers are required to use HTTPS (HSTS with preloading), and standard security headers are set on every response.
Traffic that gets past Cloudflare's checks still has to get through AWS network isolation and firewall rules before it reaches the application and database.
Backups and recovery
The database is backed up automatically every day, and each daily backup is kept for 14 days. If something goes wrong, we restore the full database, structure and data, to the most recent good daily backup. In the worst case, that means losing up to one day of changes.
Files you upload are stored in AWS S3 across multiple data centers. AWS designs S3 for 99.999999999% durability, so a hardware failure in one location does not lose your files. Like the database, those files are encrypted with AES-256.
AI and your data
Several Built To Run features use AI, including the chapter builders, session copilots, and Quick Doc and Record Doc. When you use them, the relevant content is sent to one of these providers: OpenAI, Anthropic, Google, or xAI.
We use each provider's business API, not their consumer chat apps. Under those business terms, your prompts and documents are not used to train their models. Every request and response travels over encrypted HTTPS.
These providers may keep requests for a short period, typically up to 30 days, to watch for abuse, and then delete them. This short term storage is standard across the industry.
Who on our team can see your data
Very few people. Access to customer data on our side is limited to the small number of team members who need it to run and support the platform, and every one of those accounts requires MFA.
We do not browse customer data. When we need to look at your account to fix a problem, it is because you asked us to.
All access to customer data is logged and regularly reviewed.
Our infrastructure providers
Built To Run runs on providers that are independently audited. Our application platform and hosting providers hold current SOC 2 Type 2 reports. We review those reports every year.
| Provider | What they do for us |
|---|---|
| Amazon Web Services | Database and file storage (US-East) |
| Cloudflare | Web application firewall, DDoS protection, content delivery |
| OpenAI, Anthropic, Google, xAI | AI features |
| Microsoft | Optional Teams Integration |
If something goes wrong
If we confirm a security incident that affects your data, we will notify you within 72 hours of confirming it. You will hear what happened, what data was involved, what we have done about it, and what, if anything, you need to do.
When you leave
Your field guide is yours. You can export it at any time, including before you cancel.
After your account ends, we keep your data for up to 12 months in case you come back, then delete it. If you want it gone sooner, tell us and we will delete it within 30 days of your request. Deleted data disappears from our backups as those backups expire, within 14 days.