//Integrations

Last updated September 18, 2026

Integrations & Connected Accounts

UpliftOS connects to other people's services on your behalf — payment processors, email and messaging providers, model providers, storage, analytics, code hosts. This document covers what happens when you connect one: whose relationship it is, what we do with the credentials you give us, and what happens when you disconnect.

It sits under the Terms of Service. What crosses to a third party and how it is recorded is also covered by the Data Processing Addendum and the Subprocessor List.

1. The Distinction That Governs Everything Here

There are two kinds of connection and they have different owners.

Running on our key. For some vendors we hold a platform account and your usage runs through it. We are the vendor's customer; you are ours. We bill you for the usage.

Running on your key. You bring your own credential and your usage runs through your own account with that vendor. You are the vendor's customer. Their terms apply to you directly, their bill goes to you, their rate limits are yours, and if they suspend your account we cannot restore it.

Which of the two applies is shown per integration before you enable it, because it decides who you are in a dispute. Some integrations only ever run on your own key.

2. The Third Party's Terms Are Between You and Them

Connecting a service does not make us a party to your agreement with it, and does not make it a party to yours with us.

  • We do not control what a third party does, how it changes, what it charges, or whether it stays available. A vendor removing a feature, changing its pricing, or discontinuing an API is not a failure of UpliftOS.
  • You are responsible for complying with their terms, including any restriction on automated access, on the data you send, or on the regions you send it from.
  • We are not liable for a third party's acts, omissions, outages, security incidents or data handling. Where we act as your processor for data we hold, the Data Processing Addendum governs; it does not extend to what happens inside a vendor's system.

Where a vendor processes personal data on our behalf as part of providing UpliftOS, it is a subprocessor and it appears on the Subprocessor List, with the notice period that list promises. A vendor you connect on your own key for your own purposes is yours, not ours, and does not appear there.

3. Credentials You Give Us

How we hold them. API keys and secrets you store are encrypted at rest. Encryption and decryption happen in the data layer, at a single point every reader and writer passes through, so a credential cannot be read out of the system in the clear by some path that forgot to decrypt.

One thing we will state rather than gloss. This encryption was introduced after the platform already held credentials. Keys stored before it landed remain as they were stored until they are next saved, at which point they are encrypted. If you supplied a credential early in your use of UpliftOS and want it encrypted now, re-enter it — saving it again is what converts it. We would rather tell you this than let "encrypted at rest" imply a backfill that has not happened.

What we do with them. We use a credential only to make the calls the integration you enabled exists to make. We do not use it for any other purpose, we do not use it for other customers, and we do not sell or share it. Staff access follows the Privacy Policy.

Scopes. Grant the narrowest scope that makes the integration work. Where a vendor offers read-only access and you do not need writes, use read-only. We ask for what an integration needs; we cannot reduce a scope you granted more broadly.

Your responsibility. Use a credential issued for this purpose, rotate it on your own schedule, and revoke it here and at the vendor if you believe it is exposed.

4. What Data Crosses, and the Record of It

Using an integration means data leaves UpliftOS for that vendor. That crossing is governed and recorded: the platform classifies the payload, applies redaction where the crossing is regulated, checks it against the destinations your organization has approved, and writes a receipt.

The receipt is the record — what was sent, to which service, when, and with what outcome. Your organization's administrators can read that ledger. This is the mechanism behind the commitments in the Data Processing Addendum, and it exists so that "what regulated data left, to whom" is answerable from evidence rather than from memory.

Where a regulated crossing has no approved destination, the platform refuses it rather than sending it. A refused crossing is a visible error, not a silent drop.

5. Usage, Limits and Cost

Integration usage is metered. Where you run on our key, usage is billed to you per the Billing & Credits terms. Where you run on your own key, the vendor bills you and we meter for your visibility.

Your organization can set a monthly budget, a daily limit and a rate limit per integration, and can be alerted at a threshold. These are yours to configure; we do not set them for you, and an integration without limits will use what it is asked to use.

6. Disconnecting

You can disable or disconnect an integration at any time.

  • Anything depending on it stops working. An application, agent or workflow built on a disconnected integration will fail rather than silently degrade.
  • Revoke at the vendor too. Disconnecting here removes our ability to use the credential. It does not revoke the credential at the vendor, and you should do that as well if the credential exists only for us.
  • Records of past use remain. Usage records and crossing receipts are retained per the Data Retention & Deletion Schedule, because they are the audit trail of what already happened. Disconnecting an integration does not erase the history of having used it.

7. We May Suspend an Integration

We may disable an integration where it is being used in breach of the Acceptable Use Policy, where a vendor requires it, where it is causing harm to the platform or to another customer, or where the law requires it. We will tell you which integration and why.

8. Changes to This Document

We update this document as the integration platform changes. Material changes are notified as the Terms of Service requires, and the date at the top always reflects the current version.

Questions: [email protected].

9. Related Documents