Add Business Associate Agreement (BAA) page and docs#3039
Add Business Associate Agreement (BAA) page and docs#3039atharvadeosthale wants to merge 1 commit into
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Ephemeral API keys are generated automatically for each function execution |
Greptile SummaryThis PR adds a Business Associate Agreement (BAA) legal page at
Confidence Score: 3/5The footer and HIPAA doc changes are straightforward, but the BAA page itself should not go live until the legal entity name is confirmed — a HIPAA contract with the wrong contracting party name is a material defect. The BAA page uses "Appwrite Code Inc." while every other existing policy page uses "Appwrite Code Ltd." Publishing a HIPAA-required contract with a mismatched entity name is a meaningful risk that warrants legal sign-off before merge. src/routes/baa/+page.markdoc needs a legal review to confirm the correct contracting entity name; src/routes/docs/advanced/security/hipaa/+page.markdoc has a hardcoded price and inconsistent plan eligibility description. Important Files Changed
Reviews (1): Last reviewed commit: "Add Business Associate Agreement (BAA) p..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| @@ -0,0 +1,85 @@ | |||
| --- | |||
| layout: policy | |||
There was a problem hiding this comment.
The BAA uses "Appwrite Code Inc." as the contracting entity, while the existing Cookies Policy and Privacy Policy both reference "Appwrite Code Ltd." If these are the same legal entity, one of the documents has the wrong name — a material error in a HIPAA-required contract. If they intentionally represent different entities, please add a clarifying comment for future reviewers. Either way, a legal review of the entity name should confirm correctness before this page goes live.
|
|
||
| A Business Associate Agreement (BAA) is a HIPAA-required contract between you (the covered entity) and Appwrite (the business associate) that governs how protected health information (PHI) is handled. You need a BAA in place before storing or processing PHI on Appwrite Cloud. | ||
|
|
||
| You can enable a BAA yourself from the Appwrite Console. Open your **Organization settings**, find the **BAA** section, and select **Enable BAA**. The BAA is a paid add-on that costs $350 per month, prorated for your current billing cycle, and applies to your entire organization. |
There was a problem hiding this comment.
| You can enable a BAA yourself from the Appwrite Console. Open your **Organization settings**, find the **BAA** section, and select **Enable BAA**. The BAA is a paid add-on that costs $350 per month, prorated for your current billing cycle, and applies to your entire organization. | |
| You can enable a BAA yourself from the Appwrite Console. Open your **Organization settings**, find the **BAA** section, and select **Enable BAA**. The BAA is a paid add-on, prorated for your current billing cycle, and applies to your entire organization. See [pricing](https://appwrite.io/pricing) for current rates. |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
|
||
| A Business Associate Agreement (BAA) is a HIPAA-required contract between you (the covered entity) and Appwrite (the business associate) that governs how protected health information (PHI) is handled. You need a BAA in place before storing or processing PHI on Appwrite Cloud. | ||
|
|
||
| You can enable a BAA yourself from the Appwrite Console. Open your **Organization settings**, find the **BAA** section, and select **Enable BAA**. The BAA is a paid add-on that costs $350 per month, prorated for your current billing cycle, and applies to your entire organization. |
There was a problem hiding this comment.
The HIPAA docs describe the BAA add-on as available on "eligible paid plans", while the BAA page itself states it "applies to clients under the Scale plan or the Startups program." These descriptions don't match — the docs are more vague and could set incorrect expectations for users on other paid plans who may not qualify. Aligning the docs with the specific plan names from the BAA would reduce confusion.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
/baa