HighStructure
Integration Partner Addendum is drafted as if it could incorporate Master Partner Program Agreement
Integration Partner Addendum is a binding and Master Partner Program Agreement is a perimeter document. ¶3 reads: "This Addendum is subject to Supabase's standard Master Partner Program Agreement, currently available on Supabase's website at https://supabase.com/legal/partner-resources/master-partner-program-agreement unless otherwise agreed by the Parties in writing ("MPP…"
- IPA ¶3
“This Integration Partner Addendum (this "Addendum") contains terms and conditions that govern your participation in Supabase's Integration Partner Program (the "Program") and is a contract between Supabase and Partner. T…”
- MPPA — first clause
“Master Partner Program Agreement”
Wrong? Ask for access to correct it.
HighStructure
Open Authorization Integration Addendum is drafted as if it could incorporate Master Partner Program Agreement
Open Authorization Integration Addendum is a binding and Master Partner Program Agreement is a perimeter document. ¶3 reads: "This Addendum is subject to Supabase's standard Master Partner Program Agreement, currently available on Supabase's website at https://supabase.com/legal/partner-resources/master-partner-program-agreement unless otherwise agreed by the Parties in writing ("MPP…"
- OAIA ¶3
“This Open Authorization Integration Addendum (this "Addendum") contains terms and conditions that govern your participation in Supabase's OAuth Partner Program (the "Program") and is a contract between Supabase and Partn…”
- MPPA — first clause
“Master Partner Program Agreement”
Wrong? Ask for access to correct it.
HighPrecedence
Acceptable Use Policy | Supabase reads as a commitment, but nothing incorporates it into the agreement
Master Partner Program Agreement ¶98 mentions Acceptable Use Policy | Supabase. No clause anywhere in the published set states that Acceptable Use Policy | Supabase forms part of the agreement.
Wrong? Ask for access to correct it.
HighStructure
Integration Partner Addendum reads as part of the agreement, and nothing in the set refers to it
Integration Partner Addendum is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
Wrong? Ask for access to correct it.
HighStructure
Open Authorization Integration Addendum reads as part of the agreement, and nothing in the set refers to it
Open Authorization Integration Addendum is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
Wrong? Ask for access to correct it.
HighRegister
The availability commitment is stated 2 times, in 2 different figures
The availability commitment appears in 2 documents. The figures stated are 99.99, 99.9. These may each be right for a different thing. What the corpus does not do is say which figure governs which question.
- DPA ¶111 — states 99.99
“Backups are stored on a storage system independent of the Customer's project resources, and aim for 99.99% availability.”
- SLA ¶30 — states 99.9
“Each product is individually covered by a 99.9% uptime commitment for customers with an Enterprise tier subscription.”
Wrong? Ask for access to correct it.
MediumGap
DPA names a Supabase Terms we could not find published
Data Processing Addendum ¶3 refers to a Supabase Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
Wrong? Ask for access to correct it.
MediumGap
TOS names a Business Associate Agreement we could not find published
Enterprise SaaS Subscription Agreement | Supabase ¶62 refers to a Business Associate Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
- TOS ¶62
“Customer will ensure that its Customer Data, and its use of such Customer Data, complies with this Agreement and any applicable local, state, federal and international laws, regulations and conventions, including, withou…”
Wrong? Ask for access to correct it.
MediumGap
TS names a Arbitration Agreement we could not find published
Terms of Service ¶105 refers to a Arbitration Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
Wrong? Ask for access to correct it.
MediumGap
IPA names a Service Terms we could not find published
Integration Partner Addendum ¶14 refers to a Service Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
- IPA ¶14
“In the case of Partner, ensure that the Technology Integration(s) comply with the standards and requirements described in the User Guide, including the Supabase Shared Responsibility Model available at https://supabase.c…”
Wrong? Ask for access to correct it.
MediumGap
MPPA relies on a price list that is not published
Master Partner Program Agreement ¶15 relies on a price list. No price list was found anywhere in the published set.
- MPPA ¶15
“During the term of the Agreement, Partner shall conduct itself in a professional and competent manner, consistent with the Agreement. Unless separately authorized in writing by Supabase, including via an applicable Progr…”
Wrong? Ask for access to correct it.
Held back
14 readings, on top of the 11 above
Each puts two clauses side by side that answer the same question differently, and quotes both.
Sign up free — €5 of free drawing credit, enough for your first drawing — and come back here to unlock them.
