Policies

Xive Developer Policy

Version 1.0 Last updated 2026-10-11

1. About this Policy

This Policy sets out the rules for applications and chat bots built on the Xive streaming developer platform. It is part of the Xive Developer Agreement, and words defined there (such as Application, Channel, Creator, Viewer, Scopes and Xive Data) mean the same here.

Applications for Xive Hubs follow the separate Xive Hub Developer Policy. The Xive Terms of Service and Community Standards apply to everything your Application posts or does.

2. Core principles

  • Creators are in charge of their Channels. Your Application acts only where it has been added, only with the Scopes granted, and only in the way the Creator configured it.
  • Viewers should always know when they are talking to a bot.
  • Take only the data you need, keep it only as long as you need it, and never use it against the people it came from.
  • Be honest about what your Application is, who runs it and what it costs.
  • Request only the Scopes your Application actually uses, and explain on your own site or listing why it needs each one.
  • Do not pressure Creators to add your Application or grant extra Scopes, for example by withholding features that do not need them.
  • When a Creator removes your Application, stop acting on their Channel immediately, and delete the Xive Data you hold from that Channel within 30 days.
  • Do not add your Application to Channels yourself, ask Creators to share their sign-in, or act on a Channel through anyone else’s account.

4. Chat data and privacy

  • Use chat messages and other Xive Data only to run your Application’s features in the Channel they came from.
  • Keep chat message content no longer than your Application needs it, and never longer than 30 days, unless the Creator has asked you to keep it longer for their own Channel. Counters and settings (for example points totals or command lists) may be kept while the Application stays on the Channel.
  • Never sell, rent or give away Xive Data, or use it for advertising.
  • Do not track Viewers across Channels, build profiles of them, or publish searchable logs, “who chats where” lookups or leaderboards drawn from more than one Channel.
  • Do not try to identify a Viewer’s real-world identity, location or other accounts.
  • Do not use Xive Data to train machine-learning models other than for features delivered back to the same Channel.
  • Honour deletion requests from Creators, and from Xive on behalf of Viewers, promptly.

5. Behaviour in chat

Your Application’s messages appear in chat with a BOT label. In addition to the Community Standards, your Application must not:

  • pretend to be a person, or present itself as Xive, Xive staff, the Creator or one of the Channel’s moderators;
  • spam — flooding chat, repeating the same message, or posting links, promotions or advertising the Creator has not set up;
  • send unsolicited messages to Viewers, or collect their contact details;
  • ask Viewers for passwords, sign-in codes, payment details or other personal information;
  • run gambling, betting, raffles for money, “send money to win” or similar schemes, or promote them;
  • post sexual content, hate, harassment, threats, or content that targets or mocks Viewers;
  • post more than 20 messages in any 30-second period in one Channel — Xive enforces this limit and may lower it for an Application that causes problems.

6. Moderation bots

  • Take moderation actions only as the Creator has configured your Application to, and give Creators a way to review and reverse them.
  • Never use moderation to harass, silence or retaliate against a Viewer, or on behalf of anyone other than the Creator and their moderators.
  • Do not try to act on the Creator, their moderators, or Xive staff — Xive blocks these actions and repeated attempts may be treated as abuse.
  • Moderation actions are recorded in the Channel’s moderation log under your Application’s name.

7. Security

  • Keep application secrets on your server. Never put them in client-side code, browser extensions, mobile apps, public repositories, screenshots or chat.
  • If a secret may have been exposed, create a new one and revoke the old one in the Console straight away.
  • Use the APIs only as documented, respect rate limits and back off when asked to, and do not scrape Xive pages.
  • Keep the systems that hold Xive Data patched and access-controlled.
  • Report security vulnerabilities in Xive to [email protected] and give us reasonable time to fix them before disclosing them. Do not access other people’s data while testing.

8. Names, branding and listings

  • Your Application’s name must not include “Xive” or read as Xive, staff, a moderator or an official account. “for Xive” or “works with Xive” in your description is fine.
  • Do not use Xive’s logos, or imply that Xive endorses, partners with or operates your Application.
  • Do not use another company’s or person’s name, brand or likeness without permission.
  • Describe your Application accurately, including what it does, what data it uses and who runs it, and keep the description current.

9. Charging Creators

  • You may charge Creators for your Application, but state the price and what it includes before they pay, and make it easy to cancel.
  • Do not take payments from Viewers through chat, or sell or trade Xive credits, gifts, Sparks, subscriptions, channel points or accounts.
  • Do not reward Viewers with money or prizes of monetary value for watching, chatting or following.
  • Do not offer to inflate viewers, followers, chatters or other numbers.

10. Audience

Xive is for people aged 18 and over. Do not design your Application to appeal to children, and do not knowingly collect data from anyone under 18.

11. Enforcement and appeals

When an Application breaks this Policy, we usually start with a warning and time to fix it. Depending on how serious, repeated or harmful the breach is, we may instead or also:

  • lower the Application’s rate limits or remove Scopes;
  • remove the Application from some or all Channels;
  • suspend the Application, which stops all of its secrets at once;
  • delete the Application or end the developer’s access to the developer platform, and take action on their Xive account under the Terms of Service.

We may act without warning to protect Creators, Viewers or Xive, or when the law requires it. A suspended Application shows the reason in the Console. To appeal, email [email protected] from the address on your Xive account within 30 days, with the Application’s client ID and what you have changed. We aim to reply within 14 days.

12. Changes and contact

We may update this Policy as the developer platform grows. We will post the new version with its date; material changes will be announced in the developer documentation and must be accepted in the Console before you create new applications or secrets.

Questions: [email protected]. Legal notices and security reports: [email protected]. Privacy: [email protected].

More policies
← Back