The YNAB Team does not access or interact with customers’ budget data as part of normal operations. There are cases where a customer requests that YNAB access their budget, or where required by law. All budget data is access-controlled, accompanied by customer approval, and carries with it documentation surrounding the reason for access and the access start and end time. A YNAB Team member’s violation of our customer data access policy will result in immediate dismissal.
Your YNAB account password is one-way salted and hashed using multiple iterations of a key derivation function for passwords. (Those sound like made up words, but these are best practices!) Even if someone were to steal the YNAB database of passwords, they would not know your password and would be forced to (very slowly!) guess every possible password in order to find it.
We prevent brute force password attacks (where an attacker attempts to guess the password for an account many times in a row). We also help you choose stronger passwords by 1) requiring that passwords be eight characters or longer, and 2) specifically preventing you from using the top 2,085 most commonly used passwords. (It’s quite an interesting list, should you choose to Google it.)
Your data is encrypted at rest when stored on our servers. That means that even IF someone could break in and steal the hard drives where your data is stored, they couldn’t read it. Also, should you (sadly) choose to delete your YNAB account, all of your budget data is completely and irreversibly removed from the YNAB database. We do not simply mark your account as inactive. We completely destroy all account data. (To be clear, you explicitly request this nuclear deletion. If you happen to let your account lapse accidentally, we don’t assume you mean DESTROY ALL MY DATA. That’d be a horrible assumption.)
We retain account data for a period of time after an account expires, whether through trial expiration or subscription expiration, unless you delete your account as described above.
Once an account has become inactive beyond the period of time described below, we will delete its budget data – if you don’t need YNAB, we don’t need your account data, and you probably don’t want us to have it. (Keep in mind that if you cancel your account, it remains active until the end of your subscription. The timeline below doesn’t start until that subscription expires.)
We will delete accounts and their data:
- For an expired trial, a minimum of one hundred-twenty (120) days after the expiration of the trial;
- For an expired subscription, a minimum of three years after the expiration of the subscription.
Our entire infrastructure is built on Heroku, which in turn is built on the technology of Amazon Web Services (AWS). This is the same technology trusted by government agencies, including our favorite, the CIA. Amazon continually manages risk and undergoes recurring assessments to comply with industry standards. Heroku’s entire security policy is here. Amazon’s physical infrastructure (and thus Heroku’s), are accredited under:
- ISO 27001
- SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
- PCI Level 1
- FISMA Moderate
- Sarbanes-Oxley (SOX)
PCI is an arduous security standard that companies must adhere to when processing credit cards. We use a PCI certified payment provider (Recurly) to process our credit cards, and have engineered our payment forms in such a way that your payment details are sent directly to Recurly’s systems rather than ours, further increasing security.
We partner with Finicity, MX, Quovo, and Plaid as providers of Direct Import financial data aggregation from institutions, and you can find specifics related to their security policies and practices on the Finicity, MX, Quovo, and Plaid websites. YNAB does not store your bank credentials, but relies upon our partners and their industry-leading security precautions.
All data sent between your computer and YNAB is bank-grade or better encryption. YNAB forces your browser to use an encrypted connection and won’t let your computer talk to our servers unless that connection is secure.
Specifically around the traffic encryption, we use 128-bit encryption (AES_128_GCM). This provides an extremely high level of encryption, considered industry standard.
We take advantage of a new security feature in your browser called “Content Security Policy” settings. This makes certain types of attacks against YNAB impossible.
Social Engineering Security
This massive technical feat resulting in a moat of fire-breathing space dragons surrounding your data is useless if someone cons you into handing them your username and password.
- No YNAB Team member will ever initiate communication with you and ask for your username or password. If someone asks you for either of those, it’s not us. Only provide your username and password when logging into YNAB.
- YNAB will always use https://app.youneedabudget.com as the domain name. Always look for this when logging into YNAB, or following any link clicked from a bookmark or email.
At YNAB, we subject our servers, source code and staff to regular 3rd-party security audits from teams that audit other large security-conscious companies such as Github, AT&T, Digital Ocean and Node.
Bug Bounty Program
We have also taken a page from companies like Google and Amazon, and have a public bug bounty program where we pay “good guy” hackers that find any vulnerabilities or weaknesses in our systems. If you would like to report a vulnerability, please do so on our Bugcrowd Bounty Page.