Unify API

Datenschutz

Was wir erheben, warum wir es erheben und was mit Ihren Prompts geschieht.

Zuletzt aktualisiert 1. Oktober 2026

Diese Übersetzung dient nur der Information; maßgeblich ist die englische Fassung.

Who we are

Unify API is a UnifyAI product operated by FelixSphere LLC, 6 Karen Ct, CA 94010, United States. FelixSphere LLC is the data controller for the personal data described in this policy.

What we collect

Account details you give us: your email address, and optionally a display name and company.

Usage records for each API request: timestamp, the model requested, token counts, computed cost, the API key used, and the response status. We record these because they are what your bill and your dashboard are built from.

Operational data needed to run the service: IP address and request metadata, used for rate limiting, abuse prevention, and debugging.

Prompt and response content

We do not store the content of your prompts or model responses as part of normal operation. Requests are relayed to the upstream provider and the response is streamed back to you.

Usage records retain metadata about a request — model, token counts, cost, latency — not the text of the request or reply.

Tracking Technologies and Cookies

We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include

  • Cookies or Browser Cookies. A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
  • Web Beacons. Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).

Cookies can be "Persistent" or "Session" Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. You can learn more about cookies on TermsFeed website article.

We use both Session and Persistent Cookies for the purposes set out below:

Necessary / Essential Cookies

  • Type: Session Cookies
  • Administered by: Us
  • Purpose: These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.

Cookies Policy / Notice Acceptance Cookies

  • Type: Persistent Cookies
  • Administered by: Us
  • Purpose: These Cookies identify if users have accepted the use of cookies on the Website.

Functionality Cookies

  • Type: Persistent Cookies
  • Administered by: Us
  • Purpose: These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.

For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.

Upstream providers

To serve a request we forward it to the model provider you selected. That provider receives the content of your request and handles it under their own terms and privacy policy.

Which provider receives a request depends on the model you name and on routing and failover. If your data must stay with a specific provider or in a specific region, tell us before you send production traffic and we will confirm what we can support.

We use HubSpot to provide live chat on this website; HubSpot acts as our Service Provider and may set the cookies described above.

How we use it

To operate the service: authenticate keys, route requests, meter usage, and bill you.

To keep the service working and secure: investigate errors, prevent abuse, and enforce limits.

To contact you about your account and material changes to the service.

We do not sell your data, and we do not use your prompts or responses to train models.

Retention

Usage records are retained while your account is open, because they are your billing history.

If you close your account we delete account details and usage records, except where we must keep records to meet a legal, tax, or accounting obligation.

Your rights

You can ask us for a copy of your data, ask us to correct it, or ask us to delete it. Write to privacy@unifyapi.ai and we will respond.

Depending on where you live you may have additional rights under laws such as the GDPR or the CCPA. We will honour them.

Security

Traffic to the API and the console is encrypted in transit. API keys are stored so that they can be verified but not recovered — if you lose a key, create a new one and revoke the old one.

You can scope each key to specific models and give it its own spend limit, so a leaked key has a bounded blast radius.

Changes and contact

If we make a material change to this policy we will tell account holders before it takes effect.

Questions: privacy@unifyapi.ai