This Third-Party Services Notice (“Notice”) explains how Oath (“Oath,” “we,” “us,” “our”) relies on third-party services and how issues with those services can affect your experience, verification, and payments. This Notice supplements the Oath Terms of Service, Privacy Policy, Wallet & Payments Terms, and Contract Rules. If there is a conflict, the applicable Terms/Rules control.
1) Oath depends on third-party services
Oath uses third-party services to provide core functionality. These may include, without limitation:
- Authentication: Firebase Authentication (Google sign-in)
- Payments and payouts: Stripe (Checkout, webhooks, Connect onboarding, payouts)
- Data storage and infrastructure: Supabase (Postgres), hosting providers, logging/monitoring tools
- Verification sources: LeetCode (MVP verification source) and related endpoints/tools
- Strava: OAuth-based activity data (type, distance, moving time, start date, activity ID, athlete ID) used solely to verify completion of running and cycling oaths the user has staked on; never used for ML training or any other purpose
Oath does not control third-party services and is not responsible for their performance, availability, security practices, or changes.
2) What this means for you (impact on key features)
A) Verification may be delayed or unavailable
Contract verification (MVP: LeetCode) may be impacted by:
- service outages or degraded performance,
- API rate limits,
- data delays, caching, or timestamp differences,
- changes to third-party APIs or pages,
- account linking issues (wrong username, private profile settings, etc.).
As a result, Oath may:
- retry verification automatically,
- delay settlement until we can confirm results,
- or apply contract fallback handling consistent with the Contract Rules and Terms.
B) Payments, deposits, and withdrawals may be delayed or reversed
Payment processing and payouts may be impacted by:
- payment network delays,
- risk checks or compliance reviews,
- disputes, chargebacks, or ACH returns,
- webhook delays or delivery failures,
- outages or changes by the payment provider.
Because of this:
- deposits may appear as Pending before becoming Available,
- withdrawals may require identity verification and may be delayed or denied,
- funds may be held for fraud/compliance reasons,
- and transactions may be reversed if a payment fails or is disputed.
C) Authentication and sessions may fail
Sign-in and account access may be impacted by identity provider outages, browser security policies, redirects, or SDK changes, which can affect session persistence and login flow.
3) No affiliation and no endorsement
References to third-party services (e.g., LeetCode, Stripe, Firebase, Strava) do not imply affiliation with or endorsement by those services. Their names and logos are the property of their respective owners.
4) Changes to third-party services
Third-party services may change their functionality, pricing, availability, or terms at any time. Oath may update integrations, replace providers, or modify features to respond to third-party changes.
5) Your responsibilities
You are responsible for:
- maintaining accurate account linkage for verification sources (e.g., correct LeetCode username),
- keeping your contact info current,
- completing identity verification steps required for withdrawals,
- ensuring you meet checkpoint deadlines regardless of third-party performance variability (to the extent possible).
6) Limitation of responsibility
To the maximum extent permitted by law:
- Oath is not liable for losses or damages caused by third-party outages, API changes, payment network failures, or verification data issues.
- Oath does not guarantee uninterrupted access or error-free operation of third-party-dependent features.
7) Where this Notice is referenced
- Included (or linked) in the Terms of Service and Privacy Policy
- Referenced in the Contract Rules under the verification section
- Linked anywhere verification or payments are displayed (e.g., Wallet, contract details)