Security

Version of 18 November 2026

What you give us

To connect a service, you give APIUniCon a key that the service itself issues in your account there (it may be called an API key or a token). We never ask for your password to that service, and we get no access to your account there beyond what the key allows.

You decide what the key may do. Where the service lets you choose a key's permissions, create a separate key for APIUniCon with only the permissions you need. To ask questions about your sales, orders and stock, a read-only key is enough.

You paste the key on a page of this site, by a one-time link your AI assistant gives you. The key is never typed into the chat, and neither ChatGPT nor Claude sees it.

What a connection can and cannot do

A connection sends requests only to the addresses of the service you connected, over HTTPS. You approve the list of addresses on the page where you paste the key. A request to any other address is refused, and so is a request to a private or internal network address.

It runs only the requests described for that connection. On the Free plan these only read data. On the Pro and Business plans your assistant can also ask to change data, and by default every change waits for your confirmation; a deletion always waits for it.

Requests run on your instructions, which your AI assistant passes on from your chat. The assistant gets what the service answers, never the key: if an answer repeats the key, its value is hidden before the answer reaches the assistant.

How keys are stored

Keys are stored only encrypted, with AES-256-GCM. Each account has an encryption key of its own, derived from a master key that is kept outside the databases. A key is decrypted only at the moment your request runs, to be sent to the service it belongs to.

Each account's connections and keys are kept in a database of its own, separate from other accounts. The servers are in Poland (European Union), rented from Hostkey. Every connection to the site and to your services uses HTTPS.

The password to your APIUniCon account is stored only as a hash (argon2id), never the password itself.

Who can reach them

No page of the service shows a key once it is saved: not to you, not to your AI assistant, not to the administrator.

To get a broken connection working again, the administrator may look at its request descriptions (addresses and parameters, without keys). The administrator neither sees nor changes your keys. Administrator sign-in requires a second factor.

Our call log keeps the time, the operation and the response status of a request, not its arguments and not what the service answered. The two logs that keep more, the change log and the failure log, are described in the Privacy Policy.

How to revoke access

Delete a connection: open Connections in your account and press Delete. Its keys are erased.

Revoke the key at the service: delete or reissue the key in your account at the service that issued it. From that moment the key works nowhere, here included, and you do not need to sign in to APIUniCon to do it.

Replace a key: ask your assistant to replace the connection's keys. It gives you a link to our page, where you paste the new key.

Disconnect ChatGPT or Claude: on the Account page, under Connected apps, press Disconnect.

Delete your account: on the Account page. All your connections, keys and adapters are erased, and Claude and ChatGPT lose access.

What we do not share

We do not sell your keys or your data and do not hand them to anyone. A key goes only to the service it belongs to, together with your request, just as if you called that service directly.

Other companies receive only what the Privacy Policy lists: Hostkey hosts the servers, Resend delivers our emails and receives your email address, and Gumroad takes payments for paid plans on its own page. None of them receives your keys.

Source code and reports

The source code of the core of APIUniCon, the part that stores keys and sends requests, is public: https://github.com/A1exZabr/apiunicon. Anyone can read how it works.

Found a vulnerability? Write to support@apiunicon.online with the subject Security, or report it privately on the Security tab of that repository. Please do not put keys or passwords in the message.