New Relic's Terms Require You to Sign Separate Agreements

New Relic is a dev tools platform for monitoring and observability. Their terms are split across multiple documents. You need to know what you're actually agreeing to.

🔴 They require a Data Processing Addendum if you use personal data. This isn't just in the main terms. It's a separate agreement with its own compliance obligations. No DPA, no legal cover.

🟡 Paid accounts, free accounts, trials, and community forums all have different rules. What you can do with a paid account isn't what you can do on the free tier. The terms don't live in one place.

🟡 They mention HIPAA BAA and California privacy notices. This means they handle regulated data (health information) and acknowledge state-specific privacy laws. Those obligations layer on top of the standard agreement.

🟢 The terms do clearly separate different service types and user groups. At least they're not burying the variations.

🟡 Developer terms and the partner portal have their own conditions. If you're integrating with New Relic or running a partner program, you're under different rules than the main platform.

Read the DPA before you process any personal data. Check which account type you're actually using. The terms are modular — that's better than hiding everything in one wall of text, but it means you have to actually look at all of it.

This breakdown is based on New Relic's publicly available Terms of Service and/or Privacy Policy. It may contain mistakes. Spot one? Let us know.