Skip to content

baa page#2893

Open
eldadfux wants to merge 1 commit intomainfrom
feat/trademarks-legal-page
Open

baa page#2893
eldadfux wants to merge 1 commit intomainfrom
feat/trademarks-legal-page

Conversation

@eldadfux
Copy link
Copy Markdown
Member

Made-with: Cursor

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

@appwrite
Copy link
Copy Markdown

appwrite bot commented Apr 16, 2026

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Failed Failed View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Processing Processing View Logs Preview URL QR Code


Tip

Sites auto-generate unique domains with the pattern https://randomstring.appwrite.network

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 16, 2026

Greptile Summary

This PR adds a new HIPAA Business Associate Agreement (BAA) page at /baa and a redirect from /policy/baa/baa, following the same pattern used for the existing Terms and Privacy Policy pages.

  • The BAA identifies the contracting company as Appwrite Code Inc., while all other legal documents on the site (privacy/+page.markdoc, cookies/+page.markdoc) use Appwrite Code Ltd. — this should be verified and aligned before publishing a legally binding document.

Confidence Score: 3/5

Not safe to merge until the legal entity name discrepancy is resolved.

One P1 finding: the BAA uses "Appwrite Code Inc." while every other legal document on the site uses "Appwrite Code Ltd." Publishing a BAA with the wrong legal entity name could make it unenforceable. The rest of the PR (redirect pattern, layout, structure) is correct.

src/routes/baa/+page.markdoc — verify the correct legal entity name

Important Files Changed

Filename Overview
src/routes/baa/+page.markdoc Adds HIPAA BAA page with correct layout and structure, but uses "Appwrite Code Inc." while all other policy pages use "Appwrite Code Ltd."
src/redirects.json Adds /policy/baa → /baa redirect, consistent with the existing /policy/terms and /policy/privacy redirect pattern.

Reviews (1): Last reviewed commit: "Add HIPAA BAA page and /policy/baa redir..." | Re-trigger Greptile


This Business Associate Agreement ("**BAA**") applies to Pro or Enterprise customers that have added HIPAA support to their subscription, as described in Appwrite documentation, and that use Appwrite services in a manner involving Protected Health Information ("**PHI**") as defined in 45 CFR 160.103.

This BAA is entered into by and between the customer entity that has entered into or accepted the [Terms and Conditions](/terms), any order form, checkout, or other agreement governing use of Appwrite services (collectively, the "**Agreement**") ("**Customer**," "**Covered Entity**"), and Appwrite Code Inc. ("**Company**," "**Business Associate**"). Customer and Company are each a "**Party**" and together the "**Parties**."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Legal entity name mismatch

The BAA identifies the company as Appwrite Code Inc., but all other legal documents on this site (privacy/+page.markdoc, cookies/+page.markdoc) consistently use Appwrite Code Ltd. This inconsistency could undermine the enforceability of the agreement or create confusion about which legal entity is the contracting party. Please verify and align the entity name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant