BeLive Token Hub

Privacy Policy

Effective 21 September 2026Last updated 21 September 2026

This policy explains what personal data BeLive Token Hub collects, how it is used and shared, and the choices you have. Where a term is defined in our Terms of Use it means the same thing here.

1. Who we are

BeLive Token Hub, also referred to in our documentation as BeLive Studio ("Token Hub", "we", "us", "our"), is operated by BeLive AI Studios Pte. Ltd., a company registered in Singapore (UEN 202529171E) with its registered office at 26A Ann Siang Road, #03-00, Singapore 069706.

This policy covers the Token Hub website, console, API and documentation (together the "Service").

2. The two kinds of data we handle

Data about you means your account, your payments and your use of the Service. Inputs means the prompts, files, audio, images and video you submit to models, and Outputs means what comes back. Inputs and Outputs may contain personal data about other people; we process them only to run your requests.

3. Data about you: what we collect

When you register and manage your account. Your username, email address and any profile details you add. Your password is protected with encryption, so it is never stored in readable form and even we cannot see it; we can only check it when you sign in.

When you recharge. Recharge amounts, dates, currency of the balance, order references, payment status, receipts and tax details. Your card details go straight to Stripe, our payment processor, and are never stored by us: we receive and keep only a payment reference, never the full card number.

When you redeem or invite. Promotional codes you redeem, and your invitation code and link together with the connection between your account and the accounts of people who register through it, so that any invitation credits can be applied.

When you use the API. For every request: a request identifier, the time, the API token used, the model, the provider group that served it, token counts including cache tokens, latency, status and cost. For asynchronous tasks such as video and image generation: the task identifier, status and where the result can be collected.

When you contact us. Your messages, our replies, and the details you give us to resolve the matter.

Automatically, from your device. IP address, browser and operating system, device identifiers, time zone, referring pages, and the pages you visit, collected through server logs and cookies. Cookies keep you signed in and remember your language, and Stripe sets its own cookies on payment pages. You can control cookies in your browser, but blocking them will stop sign-in working.

From third parties. Stripe, for payment confirmation and fraud signals.

4. How we use information

We use the information we collect to:

5. Data you send through the Service

5.1 What we do with Inputs and Outputs. We receive your Input at our API gateway, send it to the provider serving the model you requested (or to an alternative serving path for the same model when the primary is unavailable), receive the Output and return it to you. For asynchronous tasks we hold the result so that you can collect it.

5.2 What we keep. Once a request completes, we do not keep the content of your Inputs or Outputs. What remains is the request record listed in section 3: the time, the model, the counts and the cost, never the prompt, the file or the response. Task results are held only for a short period so that you can collect them, then deleted.

5.3 We never train on your data. Your Inputs and Outputs are never used to train, fine-tune, evaluate or improve any artificial intelligence model, ours or anyone else's.

5.4 What providers do. The provider serving a model receives your Input in order to produce the Output, and handles it under its own published terms, including whether and for how long it retains request content and whether it may use it to improve its models. The Model Library shows the provider of every model.

5.5 If you build for other people. When you use the Service in your own product, you are the organisation responsible to your users for the personal data in their Inputs, and we process it on your behalf. You must give your users a privacy notice that covers processing through Token Hub and its providers, including transfers outside your country, and obtain any consent the law requires.

5.6 Images, audio and video of people. Files you submit that show or record identifiable people, including their faces or voices, contain personal data about them. You are responsible for having any consent the law requires before submitting such files, and you must not use the Service to create a synthetic likeness or voice of a real person without their consent. We do not extract or store biometric identifiers from the files you submit.

6. Who we share data with

We share personal information only in the following cases:

We do not sell, rent or otherwise share your personal information with third parties for their commercial purposes.

7. Where your data goes

We are a Singapore company, and the systems and providers that run the Service are located outside Singapore, including in the United States. Your data is therefore transferred outside Singapore. Wherever it goes, it stays protected: we take the steps the PDPA requires so that it receives protection comparable to Singapore law in every place it is processed.

8. How long we keep it

We keep personal data only as long as it is needed for the purposes in section 4, then delete it or make it anonymous, unless the law or a dispute requires us to keep something longer. Inputs and Outputs are not kept by us after a request completes. Payment records and receipts are kept for 5 years, as Singapore law requires.

9. Data security

We protect your personal information against unauthorised access, disclosure, alteration and destruction with security measures built for that purpose: every connection to the Service is encrypted, access to our systems is restricted to the people and processes that need it, passwords are encrypted so that even we cannot read them, API tokens are shown to you only once when created, and every provider we work with is bound by confidentiality and security terms in its contract with us. No method of transmission over the internet or of electronic storage is completely secure, which is why we keep our measures under review, and why you should keep your password and API tokens confidential and tell us at once if you think either has been exposed.

10. Changes to this policy

We may update this policy from time to time, for example when we add a feature, change a provider, or when the law changes. When we do, we will post the new version on this page and update the date at the top, so you can always see which version applies. We encourage you to check this page from time to time. Changes take effect when they are posted, and your continued use of the Service after that means you accept the updated policy.

11. Contact

Data Protection Officer and support: support@belive.sg
BeLive AI Studios Pte. Ltd.
26A Ann Siang Road, #03-00, Singapore 069706