Privacy Policy
Last updated: November 9, 2026
1.When this policy applies
This policy applies where upAPI acts as a controller of personal data — where we decide why and how it is processed. That covers visitors to upapi.io, people who contact us, and developers who create and use an upAPI account and the gateway at app.upapi.io, including through the upAPI browser extension (together, you).
It does not govern the personal data you route through the gateway to build your own products. For that data you are the controller and upAPI is your processor — see “Data you route through the gateway” below. This policy also does not apply to upAPI's own staff or contractors.
2.Personal data we collect
When you use our website and platform, we collect:
- Account and profile data — your name and email when you sign up. If you register through a third-party sign-in provider such as GitHub or Google, we receive basic profile information from them, such as your email, username, and avatar.
- API credentials — we issue API keys for your organization. On our servers, a key is shown to you once and stored only in hashed or truncated form so we can identify, meter, and revoke it. The one place a full key is kept in readable form is on your own device, if you choose to save it in our browser extension — see Browser extension.
- Billing data — paid plans run through our subscription and payment providers. We receive limited billing details such as your plan, status, and the last four digits of a card — never full card numbers.
- Usage and log data — to run and meter the gateway we record technical data about each request, such as the endpoint called, timestamps, response status, latency, request volume, rate-limit counters, your IP address, and device and browser information.
- Support communications — records of your correspondence with us.
- Guest accounts — you can try the marketplace without signing up. A guest session still creates a real account and organization on our side, addressed on an internal domain, so keys and usage can be metered. It carries no name or email of yours unless you convert it into a full account.
3.Data you route through the gateway
When you send a request through upAPI, we transmit the parameters you supply to the API that fulfills it and return the response to you. Those parameters and responses may, depending on what you choose to send, contain personal data about your own users.
For that data we act as your processor: we handle it on your instructions, only to deliver the Services, and never for our own purposes. You are responsible for having a lawful basis to send it and for honoring the rights of the people it concerns. If you are an end user of a product built on upAPI and want to exercise your rights, contact the developer who operates that product, since they control the data.
4.Upstream and third-party APIs
upAPI is a gateway in front of many third-party and community-published APIs. When you call a marketplace endpoint, your request is forwarded to the upstream provider that fulfills it, and whatever you include in that request is shared with that provider so it can return a result. Each provider handles data under its own terms and privacy practices, which we don't control — review them before sending sensitive data through an endpoint.
5.How we use personal data
- Provide, operate, secure, and maintain the gateway and your account.
- Authenticate you and authorize your API keys.
- Meter usage, enforce rate limits and plan quotas, and bill paid plans.
- Respond to your requests and provide support.
- Monitor and improve performance, investigate errors, and develop new features, including through aggregate analytics.
- Detect, prevent, and address fraud, abuse, and security incidents.
- Send you service and administrative messages, which are part of the Services and aren't marketing.
- With your consent or as otherwise permitted, send you product updates.
- Comply with legal obligations and enforce our agreements.
Where the GDPR or similar laws apply, we rely on one or more of these legal bases: your consent, performance of a contract with you, our legitimate interests in running and improving the Services, and compliance with a legal obligation.
6.Analytics and error monitoring — what is actually recorded
Rather than describe this in the abstract, here is the configuration that runs on upapi.io and app.upapi.io today. If it changes, this section changes with it.
- Product analytics — PostHog, self-hosted on our own servers. It runs in memory-only mode: it writes no cookie and no other identifier to your device, so closing the tab ends the session. It records page views and page leaves, automatically captured interactions on the page (clicks and form submissions), and the technical context any web request carries — browser, operating system, screen size and referring page. Your IP address reaches our own infrastructure as part of that request; it is not handed to a third-party analytics vendor.
- Who those events belong to. Signed out, they are anonymous. Signed in, every event is keyed to your internal account identifier — a random database id, never your email address. Attached to that identifier we keep a short profile of the account, so a support or product question can be answered without going to the database: your email address, the name on the account, how and when you signed up, your plan, subscription status, entitlement, subscription product, store and renewal date, your organization id, the app, its version, the platform you are using it on, your browser language and time zone, and — if you arrived from a campaign, an ad or another site — the source of that first visit. Guest sessions carry none of the personal fields: a guest address is generated and identifies nobody.
- Session replay — a sample, and only if you accept. Once you press Accept on the cookie banner, about 1 in 10 sessions on upapi.io and app.upapi.io is recorded in PostHog (a separate, smaller sample is described under error monitoring) so we can see how the product is used. Nothing is recorded before you accept, and recording stops when you withdraw. The contents of every form field are masked, and so are the places that show a secret, such as a new API key. Other text on screen, for example your email address where a page shows it, appears in the recording. Recordings stay on our own self-hosted PostHog and are kept under the Data retention rule below.
- Error monitoring — Sentry, self-hosted. When something breaks we capture the error and its stack trace, the route you were on, and the same account and organization identifiers, plus a sampled trace of the request for performance work. Sentry’s “send default personal information” option is off. On upapi.io and app.upapi.io, and again only after you accept the cookie banner, Sentry also records a replay of about 1 in 10 sessions and of every session in which an error occurs, on our own self-hosted Sentry. All text, all form fields and all media are masked or blocked, so a Sentry replay shows layout and clicks, not what the page says or what you typed.
- Subscriptions — RevenueCat. Checkout and subscription state run through RevenueCat, keyed on your organization id. The customer record carries the same short account profile described above — account identifier, email address, name, how and when you signed up, platform, app version, language, time zone, and the source of your first visit — so a billing question can be answered from the subscription itself, alongside subscription status, entitlement, product id and store. No card numbers, receipts or prices are fed back into analytics.
- Google Analytics — optional, and off until you say yes. The cookie banner switches on Google Analytics, the campaign-attribution cookie below, and session replay (PostHog and Sentry); nothing else on our sites is behind it. The referral-link, preference and sign-in cookies listed under Cookies and similar technologies are set whether or not you have answered it. Decline and the Google script is never loaded at all — not loaded-and-muted.
- Campaign attribution — optional, and off until you say yes. If you opt in to analytics cookies, we store a small first-party cookie (`upapi_ft`, 90 days) on upapi.io that records which campaign or website brought you to us (for example the `utm_source` of the link you clicked, and the site you came from), so we can tell which marketing works when you later create an account. It holds no personal data and is not shared with advertisers. Declining or withdrawing analytics consent removes it. The cookie is set for the whole upapi.io domain so that app.upapi.io can read it when you sign up, and a copy is kept in your browser’s local storage on upapi.io. Withdrawing consent removes both; if you withdraw on app.upapi.io, the local-storage copy goes the next time you visit upapi.io, and nothing reads it in the meantime.
- Browser extension — none of the above. The upAPI browser extension runs no analytics and no error reporting: no PostHog, no Sentry, and no other telemetry code. What it does handle is described in Browser extension.
Ask us for a copy of your analytics record and we will give you the events tied to your account identifier — that identifier is the only key that links any of it to you.
7.Browser extension
The upAPI browser extension has one purpose: to let you search the upAPI catalog and run one operation against the page you are on, from a popup. It is a popup only. It has no content scripts, it does not read the pages you visit, it does not read or set cookies, and it runs no analytics or error reporting. This section says exactly what it handles. Everything else in this policy applies to the requests it makes to upAPI as it does to any other use of the gateway.
- Catalog. When you open the popup it fetches the public catalog from app.upapi.io, with no API key, no cookie and no identifier. Searching the catalog happens on your device: the text you type into the search box is never sent to us or to anyone else.
- The address of your current tab. When — and only when — you open the popup, the extension reads the web address (URL) of the tab you are on, using the browser’s activeTab permission, and shows it in an editable field as a starting value. The extension does not save that address by itself. It is sent to us only if it is still in the request when you press Run, and you can edit or delete it first. The request you run, including any address in it, is then kept on your device as described under “Other data kept on your device”. The extension never reads the content of a page, the text you have selected, or any other tab.
- Your API key. If you save your own upAPI API key in the extension, it is kept in the browser’s local extension storage (chrome.storage.local) on your device until you remove it from the popup or uninstall the extension. It is never put in browser sync storage, so it is not copied to your other devices. It is sent only to api.upapi.io, as the X-Api-Key header on a request you run, and never anywhere else. The popup displays only its last 4 characters.
- Other data kept on your device. The extension remembers which operation you opened last, so the popup reopens where you left off. It also keeps your most recent run temporarily, in the browser’s session storage (chrome.storage.session) on your device: the request you ran, including any web address in it, and the response you got back, which can contain the content of a page you asked it to process. It stays until your next run replaces it or the browser closes. For up to five minutes the same storage also holds a copy of the public catalog so the popup opens quickly. These stored copies are not sent anywhere.
- What you run. When you press Run, the request body you see in the popup goes to api.upapi.io and is processed like any other call to the gateway, as described in “Data you route through the gateway”. Where the operation is fulfilled by a third-party provider, the input is forwarded to that provider, as described in “Upstream and third-party APIs”. To fetch a page, our servers may route the request through a proxy provider (currently Webshare), so that provider, as well as the site you ask about, sees the web address. As with any gateway call, we keep a call record: which operation ran, your key, user and organization identifiers, the time, the response status, the latency and the request and response sizes, but not the request body or the web address. Our hosting and network infrastructure also sees your IP address. We keep these as described under “Data retention”.
The use of information received from the extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. In plain terms: we use that information only to provide the extension’s single purpose described above; we do not sell it or transfer it to anyone except as needed to run the operation you asked for, to comply with the law, or as part of a business transfer described in “How we disclose personal data”; we do not use it for advertising, or to judge creditworthiness or for lending; and our people do not read it except where you ask us to, where it is needed for security or to investigate abuse, or where the law requires it.
To remove what the extension keeps on your device, delete your key from the popup (the last run and the catalog copy clear when you close the browser), or uninstall the extension, which removes all of its local data. Everything the extension sends goes over HTTPS to app.upapi.io or api.upapi.io. To stop a key from working anywhere, revoke it from your dashboard. To ask us to delete data we hold about you, email support@upapi.io and we will act on it within 30 days, or delete your organization yourself as described in Deleting your account and your data.
8.AI assistants and connected apps
You can connect an AI assistant or agent, such as Claude, ChatGPT or Cursor, to your upAPI account through our MCP (Model Context Protocol) endpoint at app.upapi.io/api/mcp. The connection uses OAuth: you sign in to upAPI yourself, and the app gets nothing until you approve it on a consent screen that lists what it is asking for. The app never receives your password or your API keys. A connection needs a full account; a guest account cannot use one.
- What a connected app can do. It can search the upAPI operation catalog and run operations as you, against your workspace’s plan and quota, exactly as if you ran them yourself and billed the same way. A connected app can only do what you ticked on the consent screen (read, create and edit, delete, billing, account, team, connections, support or keys), and you can widen or withdraw that at any time with the request_scopes and disconnect tools or from Connected apps.
- What it learns about you. Depending on what it asks for and you approve, the app receives your upAPI account identifier and your name, profile picture, email address and whether your email is verified.
- What it sends us. The inputs an assistant passes to an operation are handled like any other gateway request, as described in “Data you route through the gateway” and “Upstream and third-party APIs”, and the result goes back to the app.
- What we record. Each tool call writes the same call record as any other gateway call, plus which connected app made it: the operation, your user and organization identifiers, the time, the response status, the latency, the request and response sizes, and an error code if it failed. Our product analytics also record that the call happened, linked to your account identifier: the operation name, whether it succeeded, was refused by your plan or quota, or failed, the error code if any, and the app’s identifier. We also record when you approve or deny an app and the first request each connection makes. When we refuse a request we log why, with a short one-way fingerprint of the token, never the token itself. We do not record the inputs you or the assistant send, or the results returned.
- How long access lasts. Each access token expires after one hour. The app renews it with a refresh token that is valid for seven days, and a new one is issued with each renewal, so a connection in regular use stays connected until you disconnect it. One left unused for more than seven days has to ask for your approval again.
- Disconnecting. Under Settings → Connected apps you can see every app you approved, what it was granted, when you connected it and when it last ran an operation. Choosing Disconnect deletes its tokens and your approval at once, and its next request is refused. Deleting your account also ends every connection.
What you type into an AI assistant, and the results it receives from upAPI, are also handled by the company that provides that assistant, under its own terms and privacy policy, which we do not control. We only receive what the app sends to our endpoint.
9.Connected platform accounts
You can hand upAPI a signed-in session for an account you hold on another platform, such as TikTok, Reddit or LinkedIn, so that the operations you run can act as that account. This is optional and always your choice. Before anything is stored, the connect page shows a “Connect at your own risk” warning and asks you to tick a box accepting it. This section says what we store, what we use it for, how long we keep it and what we do not take responsibility for.
- What we store. The session cookies you supply, the account handle you type, an optional label, your browser’s user agent, and when the account was connected, last checked and last used. Only the cookies upAPI needs for that platform are kept: the rest of what you paste is dropped in your browser, and dropped again on our servers. The cookies are encrypted at rest and kept per workspace. No page, tool or API response shows a cookie value again, only the cookie names, the status and the timestamps.
- What we use it for. Only to run the operations you, or an AI assistant you connected, call against that account, and to check whether the session still works. That check is a metered operation, like any other call. We do not use a stored session for anything else, and we do not sell or share it, except with the platform it belongs to and the proxy provider we route that call through (currently Webshare), as described under “Upstream and third-party APIs”.
- How long we keep it. Until you disconnect the account. Disconnecting erases the session itself at once (the cookies, their names, and any pinned exit address or saved device details); the account handle, label, browser user agent and connection dates remain as a record until you delete your organization. You disconnect by asking the AI assistant you connected to upAPI to disconnect the account. A session that expires, or that the platform rejects, is marked expired and is not used again, but its encrypted copy stays until you disconnect the account or replace it by connecting again. Deleting your organization, as described under Deleting your account and your data, removes every connected account with it.
- Risk and responsibility. Connecting an account is at your own risk. upAPI is not responsible for any leaked or stolen session, account suspension, lockout, rate limit, lost data, or action the platform takes under its own terms of service, and you are responsible for complying with that platform’s terms. Use a dedicated account rather than one you cannot afford to lose. The Terms of Service set this out in full.
To stop upAPI using a session, disconnect the account. To end the session on the platform itself, also log out of that platform everywhere, because disconnecting erases our copy of the session but cannot sign you out of the platform.
11.International data transfers
We and our providers may process personal data in countries other than yours. Where we transfer it across borders — for example out of the EEA or the UK — we put appropriate safeguards in place, such as the European Commission's Standard Contractual Clauses or reliance on an adequacy decision, so your data keeps an equivalent level of protection. Contact us for details.
12.Data retention
We keep personal data only as long as needed for the purposes in this policy, then delete or anonymize it. How long depends on the type of data, why we hold it, and our legal obligations — broadly: account data for the life of your account; gateway call records (operation, key, user and organization identifiers, time, status, latency and sizes) are deleted automatically once they are 30 days old; the results of some operations are cached for up to 24 hours so an identical repeat request can be answered without running it again; and server and network logs, which can contain IP addresses, are kept for up to 90 days. Email support@upapi.io for specifics.
13.Security
We use technical and organizational measures — including encryption in transit, access controls, hashed API keys, and monitoring — to protect personal data against unauthorized access, loss, or misuse. No system is perfectly secure, and you play a part too: keep your API keys secret and, in anything you build, server-side. As our documentation notes, a key should never be exposed in client-side code that other people can load. The one deliberate exception is saving your own key in the official upAPI browser extension, on your own device and for your own use (see Browser extension). If you think a key is compromised, rotate it from the dashboard and tell us.
14.Your rights and choices
Depending on where you live, you may have some or all of the rights below. We may need to verify your identity before acting on a request.
- Access — ask what personal data we hold about you.
- Correction — ask us to fix inaccurate or incomplete data.
- Deletion — erase your account and its data yourself, in one action, from the dashboard. See Deleting your account and your data for exactly what goes and what is legally retained.
- Restriction and objection — ask us to limit or stop certain processing.
- Portability — receive a copy of the data you provided in a portable format.
- Withdraw consent — where we rely on consent, withdraw it at any time without affecting prior processing.
- Complain — lodge a complaint with your local data-protection authority, though we'd appreciate the chance to help first.
To exercise any of these, email support@upapi.io. If it's data we hold on behalf of a customer, contact that customer directly.
15.Deleting your account and your data
Deletion is self-serve and immediate — you do not have to email anyone and wait. In the dashboard, open your settings, scroll to the Danger zone, choose Delete organization, and type the organization name to confirm. Only the organization owner can do it.
That one action removes, in a single database transaction: the organization and your user account; every membership and pending invitation; every API key; your products, operations and hosted functions; your billing subscription record; and your sessions and sign-in credentials. Files you uploaded are swept from object storage immediately afterwards.
Two things deliberately survive, and we would rather say so than let you discover it. Metered call records — the per-request rows we bill and rate-limit from — are not removed with your organization. They carry only internal identifiers, no name or email, and are deleted automatically once they are 30 days old. And payment records held by our payment provider are retained under their own legal obligations. Everything else is gone.
A guest account and its organization are ordinary records and are deleted by the same path. If you would rather we did it for you, or you want a copy of your data first, email support@upapi.io and we will handle it.
17.Children
upAPI is a developer tool and is not directed to children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, contact us and we'll remove it.
18.Changes to this policy
We may update this policy to reflect changes in law or how we operate. We'll post the new version here and update the date above; where a change is significant we'll make reasonable efforts to highlight it.
19.Contact us
Questions or requests about this policy or your personal data? Email support@upapi.io and we'll be glad to help.