Effective date: May 2026 (file retention corrected September 2026; AI training and Connected Systems sections added September 2026; Transcribe, recording consent, biometric, AI Act, and data processing terms added October 2026, applying to new accounts immediately and to existing accounts from October 22, 2026) · Entertainment Technologists Inc.
Please read these Terms carefully before using Botverse. By creating an account, generating an API key, or making any call to the Botverse API, you agree to be bound by these Terms. If you are agreeing on behalf of a company or other legal entity, you represent that you have authority to bind that entity.
Contents
Botverse is a cloud API platform operated by Entertainment Technologists Inc. ("ETI", "Botverse", "we", "us", "our"), a company incorporated in Arizona, USA. Botverse provides programmatic cloud services — including video transcoding, document conversion, image processing, speech transcription, and other file operations — via REST API and Model Context Protocol (MCP) tool interfaces (the "Services"). Services are designed to be consumed directly by software agents, scripts, and automated systems.
Access to the Services is provided on a prepaid wallet basis. The Services available, their pricing, and their technical specifications are described in the documentation at botverse.cloud/docs. ETI reserves the right to add, modify, or retire Services with reasonable notice.
Botverse may operate some Services in beta or limited-access phases. Beta Services may be less stable, may change materially, and are provided without the standard uptime commitments.
Every Botverse account must be held by a legally accountable human being or corporate entity. Bots, AI agents, and automated systems cannot create accounts. A real person is always responsible for everything done via API keys issued to an account — including every action taken by every bot those keys power.
Who may create an account. Botverse accounts may be created by: (a) individual human beings acting on their own behalf; or (b) employees, officers, or authorised representatives of a company, partnership, trust, or other legal entity acting on behalf of that entity. In either case, account creation requires email verification and two-factor authentication (2FA) enrollment — both of which are gates that confirm a human being is in the loop.
Age requirement. Individual account holders must be 18 years of age or older. Individuals under 18 may not create accounts.
Accurate information. You must provide accurate and complete information at registration and keep it up to date. We may verify your identity or your authority to bind a corporate entity at any time. Failure to complete a verification request may result in account suspension.
One responsible person per account. Each Botverse account has one designated responsible party — the individual or entity that created the account. That party is legally accountable for all activity under the account, including all API key issuances and all actions taken by any system or agent using those keys.
Corporate accounts. When a company creates a Botverse account, the company is the responsible entity. The individual who creates the account represents that they have the authority to bind the company to these Terms. The company is liable for all charges incurred and all actions taken by API keys issued to the account, regardless of which employee or system generated those API calls.
You cannot transfer accountability to a bot. "The bot did it" is not a defence under these Terms. If an automated system acting on an API key issued by your account causes harm, violates these Terms, or incurs charges, you — as the account holder — are responsible.
Key issuance. After completing email verification, 2FA enrollment, and an initial wallet top-up, you may generate API keys through the dashboard. Keys are shown once at generation. We store only a hashed fingerprint — we cannot recover a key after its initial display. Store your keys securely.
Service scoping. Each API key can be scoped to one or more specific Services (e.g., transcoding only, or transcoding plus document conversion). Scoped keys cannot call Services outside their scope.
Your keys are your responsibility. You are responsible for all API calls made using your keys, whether made by you directly, by a system you deployed, by a third-party application you authorised, or by any other automated agent you gave a key to. Treat API keys with the same care as passwords.
Compromised keys. If you believe a key has been compromised or is being used without your authorisation, revoke it immediately from the dashboard and contact support@botverse.cloud. You remain responsible for any charges and actions that occurred before revocation.
Key limits. Each account may maintain up to 10 active API keys simultaneously. Sensitive key operations (creation, deletion, rotation) require 2FA re-confirmation regardless of session age.
Botverse is built for bots. But bots operating without human guardrails create real liability. These obligations exist to ensure you maintain meaningful oversight of every automated system that uses your API keys.
As a Botverse account holder, you are required to:
Maintain a kill switch. You must be able to halt all bot activity under your account immediately by revoking API keys. Do not deploy production systems without a tested procedure for revoking keys within minutes. The dashboard provides one-click key revocation at any time.
Set spend caps. You must configure a monthly spend cap or auto-refill limit that prevents any bot using your keys from incurring unlimited charges without a human-set ceiling. The dashboard allows you to set a maximum monthly spend per account and maximum auto-refill amounts. Do not deploy production bots without these limits in place.
Monitor activity. You must review your account's API activity log regularly — at least monthly — to detect anomalous usage, unexpected job submissions, or calls that you did not authorise. The dashboard provides a full audit log of every API call made under your account. Botverse may alert you to unusual activity patterns by email, but such alerts do not replace your obligation to monitor.
Do not delegate account creation to bots. Bots may not create Botverse accounts, request API keys, or modify billing settings. Account management is a human-only function. Any attempt to automate account creation or key generation will result in immediate account termination.
Supervise your agents. You are responsible for reviewing, testing, and overseeing the behaviour of any AI agent or automated system you deploy with access to your Botverse API keys. Deploying an agent without adequate testing and monitoring is not a defence against Terms violations caused by that agent's behaviour.
Ensure authorisation for submitted content. Before any automated system submits a file to Botverse for processing, you must have the right to submit that content — including the necessary licences, permissions, and consents. You are responsible for ensuring your agents do not submit content you are not authorised to process.
Botverse is designed for legitimate cloud processing by developers, businesses, and AI agents. Permitted uses include:
All use must comply with applicable law, these Terms, and all policies referenced in them. You must not use Botverse in any jurisdiction where doing so would be unlawful.
Violations of this section may result in immediate account termination and may be reported to law enforcement where required.
Illegal and harmful content
Platform abuse
Misuse of processing services
Identity and security
ETI reserves the right to determine, in its reasonable judgement, whether a use falls within this section. We use automated monitoring to detect unusual job patterns and content that may violate these Terms. Such monitoring is for platform safety and does not imply that ETI reviews all content submitted to the Services.
Botverse is a processing service, not a storage service. We do not retain your files after processing. Input and output files are deleted automatically 7 days after they are created. We do not index, analyse, or retain the content of files you submit beyond what is necessary to complete each job.
How file processing works. When you submit a job, your input file is uploaded to a temporary, isolated storage object under your account. The processing job runs on our infrastructure. The output file is written to a separate temporary object. Both the input and output objects are automatically deleted 7 days after they are created. Download links expire after 24 hours and can be regenerated while the file exists. You are responsible for downloading your output within the 7-day window.
Job metadata. We retain job metadata — job ID, job type, input and output format, file size in bytes, processing duration, timestamp, and billing deduction — for 90 days. This metadata does not include file contents and is used for billing verification, dispute resolution, and abuse detection.
Your content rights. By submitting a file for processing, you represent and warrant that: (a) you own the file or have the necessary rights and licences to submit it for the requested processing; (b) processing the file in the manner requested does not infringe any third party's intellectual property rights; and (c) the file content does not violate these Terms or applicable law.
No content review. ETI does not review the content of files submitted to the Services. We rely on you to comply with these Terms. However, we reserve the right to suspend or terminate accounts where there is credible evidence of prohibited content being submitted.
Malicious files. Do not submit files designed to exploit or compromise processing infrastructure. You are solely responsible for the content of files submitted by automated systems or agents operating under your API keys.
No AI training on your content. ETI will not use your content to train, fine-tune, evaluate, or otherwise improve any machine learning or artificial intelligence model, whether ours or anyone else's. "Your content" includes files you submit, files retrieved from a connected system on your behalf (Section 7A), outputs, transcripts, and the attendee names and other hints you provide. The only Botverse service that uses third-party AI models is Transcribe: speech recognition runs on our cloud infrastructure provider, and the optional speaker-naming step (used only when you supply attendee names) sends short excerpts to an AI provider. Both are listed as sub-processors in our Privacy Policy. Both are bound not to use the data we send to train or improve their models, and we send only what each step needs. Transcoding, conversion, conform, and every other service run entirely on Botverse infrastructure without any third-party AI model.
Where Botverse offers connections, you can connect it to a third-party system you use, such as a media asset management (MAM) platform or cloud storage, so that jobs can read files from it and deliver results back into it (a "Connected System").
Your authority. By creating a connection, you represent that you, or the organization you act for, are authorized by the Connected System's account owner or administrator to grant Botverse the access you are granting, and that using a service provider in this way is permitted under your agreement with that system's vendor. You remain responsible for complying with that agreement.
We act only for you. Botverse accesses a Connected System solely as your service provider, only to perform the jobs and requests that you or agents using your API keys make, and only within the scope and any collection or folder limits you set. We do not browse, index, or retrieve anything from a Connected System for any other purpose, and we never make one customer's Connected System available to anyone else.
Credentials. Connection credentials are entered only in the Botverse dashboard, stored encrypted, and used only to carry out your requests. They are never returned through the API or shown to agents. Grant Botverse a dedicated, least-privilege credential (not a person's own login). When you disconnect a Connected System or ask us to, we delete its credentials and tokens immediately, and any files retrieved from it are deleted under the retention rules in Section 7.
Delivery. When a job delivers results to a Connected System, Botverse creates new assets and writes metadata and relationships. Botverse does not delete or overwrite your existing assets.
Third-party charges. Some vendors charge for API use, downloads, egress, or credits. Any such charges from your Connected System's vendor are your responsibility and are separate from Botverse fees.
Vendor restrictions pass through to you. Content retrieved from a Connected System remains subject to that vendor's terms. In particular, content, data, or outputs received or derived from Adobe services (including Frame.io) must not be used to create, train, test, or otherwise improve any machine learning or artificial intelligence system, or for technologies designed to identify natural persons. Botverse may disable or limit features, such as AI speaker naming, for content from a Connected System where that vendor's terms require it.
Availability. Connected Systems are operated by third parties. Their availability, API changes, rate limits, and outages are outside our control, and a connector may stop working or be withdrawn if a vendor changes its service or terms.
Botverse does not record anyone. Transcribe does not join, attend, or listen in on calls or meetings. It only processes audio or video files that you already hold and choose to submit. Whether a recording was lawful to make, and whether it is lawful to transcribe it, is entirely your responsibility. ETI does not become responsible for a recording because it transcribed it.
Our role. ETI is not a party to any conversation in a file you submit, and it does not intercept, eavesdrop on, or record any communication. Transcribe receives a finished file after the event, at your instruction, and processes it only as your service provider and, for personal data, your data processor (Section 7C). You decide what is recorded, whose voices it contains, why it is transcribed, who receives the transcript, and what it is used for.
Consent is your obligation. Before you or any agent using your API keys submits a recording, you must have given every notice and obtained every consent that applies to the people in it. You must comply with every applicable local, state, provincial, regional, national, and international law, both the laws in force where and when the recording was made and the laws in force where and when you submit it and use the outputs. Where those laws differ, you must meet the strictest. Consent that satisfied the law when a recording was made does not excuse a stricter rule that applies when you submit it, and a law that has since relaxed does not cure a recording that was unlawful when it was made. That includes the laws that require the consent of all parties to a conversation (for example California Penal Code §632, the Illinois Eavesdropping Act, 720 ILCS 5/14, and similar laws in other US states and other countries), employee-monitoring notice laws, and a lawful basis under the GDPR or UK GDPR for recording and transcribing anyone in the EEA or UK. Every Transcribe submission returns a consent notice, and the same notice is printed in the transcript. Submitting a job is your confirmation that you hold those consents.
Voices and biometric data. Transcribe separates the voices in a single file so the transcript can show who said what. It does not identify anyone from the sound of their voice. It does not build, store, or reuse voiceprints or any other biometric identifier, and it does not compare voices across recordings or accounts. Speaker names come only from the attendee list you supply and from what is said in the conversation, such as introductions and how people address each other. Any acoustic features used to tell voices apart exist only while that job runs. If a law nonetheless treats your recordings or your use of the outputs as involving biometric identifiers or biometric information, you are responsible for every notice, written release, retention schedule, and other duty that law imposes. Such laws include the Illinois Biometric Information Privacy Act (740 ILCS 14), the Texas Capture or Use of Biometric Identifier Act, and the Washington biometric identifier law.
AI-generated output. Transcripts are produced by automated speech recognition. Speaker names are inferred by an AI model and labelled with a confidence score. Both can be wrong: words can be misheard, lines can be attributed to the wrong speaker, and names can be wrong. Outputs are best-effort and are not a verified or verbatim record. You must have a person review a transcript before you rely on it for any decision, record, or publication that affects anyone. Where the law requires you to disclose that content was machine-generated, you must make that disclosure when you share or publish it.
Prohibited Transcribe uses. In addition to Section 6, you must not use Transcribe or its outputs to:
EU AI Act. Speech recognition and AI speaker naming are AI systems under Regulation (EU) 2024/1689 (the EU AI Act). As Botverse offers them, they are not prohibited or high-risk AI systems, and the restrictions above exist to keep them that way. ETI supports transparency by documenting what each AI step does and its limits (this section and the Transcribe documentation), labelling AI-inferred speaker names with a confidence score, keeping speaker naming optional, and leaving every job under human control. If you use Transcribe in the EU, you are the deployer. You are responsible for the AI literacy of your staff (Article 4), for any transparency owed to the people affected (Article 50), and for meeting the deployer obligations that apply if you put Transcribe to a high-risk use listed in Annex III.
No liability for your recordings. To the maximum extent permitted by law, ETI accepts no liability for, and you waive all claims against ETI arising from, any recording you submit, including how and whether it was made, the consents and notices given, the transcription of it, the use of AI speaker naming on it, and any use of the outputs. You must indemnify ETI for these matters as set out in Section 14.
Roles. For personal data contained in files you submit, files retrieved from a Connected System, outputs, and attendee names and hints (together, "Customer Personal Data"), you are the controller (or the "business") and ETI is your processor (or "service provider"). For your account, billing, and job metadata, ETI is the controller, as described in the Privacy Policy. This section applies to Customer Personal Data under the GDPR, the UK GDPR, the Swiss FADP, the CCPA/CPRA, and similar laws, and forms part of these Terms.
ETI's commitments. For Customer Personal Data, ETI will:
Your commitments. You must have a lawful basis for every processing instruction you give, including any consent required to process special category data. You must give the people concerned any privacy notice the law requires, and you must not instruct ETI to process Customer Personal Data in a way that breaks the law.
International transfers. Customer Personal Data is processed in the United States. Where the GDPR, UK GDPR, or Swiss FADP applies, transfers are made under the European Commission's Standard Contractual Clauses (Module 2, controller to processor, or Module 3, processor to processor, as applicable) with the UK Addendum where relevant, which are incorporated into these Terms by reference. Customers who need a signed Data Processing Agreement can request one at privacy@botverse.cloud.
Prepaid wallet model. Botverse operates on a prepaid wallet. You add funds to your wallet in USD; the platform deducts the per-operation cost of each completed job. Jobs are only executed when your wallet balance is sufficient. If your balance is insufficient, jobs are rejected with a 402 Insufficient balance response. Your balance never goes negative.
Minimum top-up. The minimum wallet top-up is USD $5.00 and applies to all manual top-ups. Top-up charges are real charges — not free credits.
Promotional credit. Botverse may grant promotional credit (for example, a one-time trial credit at account creation). Promotional credit is not purchased funds: it may only be spent on eligible platform operations, has no cash value, is non-refundable and non-withdrawable, may expire (trial credit expires 30 days after grant), and is limited to one grant per person and account. Botverse may withhold or revoke promotional credit where it reasonably suspects duplicate accounts or abuse.
Per-operation pricing. The cost per operation for each Service is published at botverse.cloud/pricing. Current rates include: video transcoding at $1.00/job; document conversion at $0.05/job; HEIC image conversion at $0.001/image. Rates are deducted at job completion, not at submission. A job that fails before producing output is not charged.
Balance expiry. Wallet balances do not expire and are not subject to inactivity fees.
Auto-refill. Account holders may opt in to automatic wallet refill. You set a threshold balance (e.g., "$5.00") and a refill amount (e.g., "$20.00"). When your balance falls below the threshold, Stripe charges your stored payment method for the refill amount. Auto-refill is off by default. You may also set a monthly spending cap — auto-refill will not execute if doing so would exceed your monthly cap.
No refunds on wallet balance. Wallet balances are not refundable except: (a) where required by applicable law; or (b) at ETI's sole discretion in the event of a documented platform error that caused incorrect billing. Top-up charges that result from disputed auto-refill triggers will be reviewed on a case-by-case basis.
Payment processing. All payments are processed by Stripe. We do not store card details on our servers. Your use of Stripe's payment services is also subject to Stripe's terms.
Billing disputes. If you believe a job was incorrectly charged, contact billing@botverse.cloud within 30 days of the charge with your job ID. We will review the job metadata and respond within 10 business days.
Taxes. Where required by applicable law, sales taxes, VAT, GST, or similar charges will be added to top-up amounts. You are responsible for all taxes applicable to your use of the Services.
You retain rights to your content. ETI does not claim any ownership over files you submit or outputs you receive. Your content is yours. The limited licence you grant us by submitting content is solely to perform the requested processing job and is revoked when the job lifecycle ends and files are deleted.
Botverse platform. ETI owns all rights in the Botverse platform, API design, documentation, dashboard, brand assets, and all original software developed by ETI. Nothing in these Terms transfers any intellectual property rights from ETI to you, other than the limited right to use the Services as described here.
Feedback. If you provide ETI with suggestions, feature ideas, or feedback about the Services, you grant ETI a perpetual, worldwide, irrevocable, royalty-free licence to use that feedback without obligation to you.
Botverse's video transcoding services use industry-standard video codecs. Some codecs are subject to third-party patent rights. This section discloses relevant patent licensing.
H.264 / AVC encoding. Botverse's H.264 encoding capability is provided under a patent licence from Via Licensing Alliance LLC (Via-LA), which administers the AVC/H.264 patent pool (formerly administered by MPEG-LA). This licence covers encoding and decoding operations performed on the Botverse platform. The Via-LA AVC licence does not extend to you, your applications, or your end users. If you encode H.264 video outside of Botverse (e.g., on your own infrastructure), you are responsible for obtaining any required H.264 licences from Via-LA independently.
H.265 / HEVC encoding. H.265 (HEVC) video encoding is subject to patent rights held by multiple parties across several independent licensing programmes, including Access Advance (formerly HEVC Advance), Via Licensing Alliance, and individual patent holders including InterDigital/Technicolor. If Botverse offers H.265 encoding, we endeavour to maintain licences with the relevant patent pools, but we cannot guarantee that all HEVC patent rights are covered. If H.265 encoding is critical to your workflow, we recommend evaluating royalty-free alternatives such as AV1 (Alliance for Open Media), which is available as a Botverse output format.
No downstream licence. Nothing in these Terms constitutes a licence to you to practice any patent claims in any codec standard. Patent licences for your own encoding operations outside the Botverse platform are your responsibility.
HEIC / HEIF image conversion. HEIC image format conversion may implicate HEVC codec patents as described above. ETI endeavours to maintain appropriate licences for this capability.
Botverse's Services incorporate open-source software. Key components and their licences are listed below. A full open-source notices page is maintained at botverse.cloud/legal/notices.
FFmpeg (LGPL v2.1+). This Service uses code from FFmpeg, licensed under the LGPLv2.1. Source code is available at ffmpeg.org/download.html. FFmpeg is used unmodified as a separate binary process; ETI does not distribute modified FFmpeg binaries.
Chromium (BSD 3-Clause). HTML-to-PDF rendering uses a headless Chromium instance. Chromium is licensed under the BSD 3-Clause licence.
libheif (LGPL v3) / libvips (LGPL v2.1). Image conversion services use libheif (HEIC processing) and libvips (general image processing), both under LGPL licences.
Sharp (Apache 2.0). Additional image processing uses the Sharp Node.js library, licensed under Apache 2.0.
The inclusion of LGPL-licensed components in Botverse does not impose any obligations on you as an API caller. You are not distributing or linking against these libraries. ETI runs them server-side and provides you with a processed output.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE BOTVERSE SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY.
ETI SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.
ETI DOES NOT WARRANT THAT: (A) THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE; (B) PROCESSING RESULTS WILL MEET YOUR SPECIFICATIONS IN ALL CASES; (C) ANY ERRORS WILL BE CORRECTED; OR (D) THE SERVICES WILL BE COMPATIBLE WITH ALL FILE FORMATS, CODECS, OR AGENT PLATFORMS.
BETA SERVICES ARE PROVIDED WITH NO WARRANTIES WHATSOEVER. THEIR AVAILABILITY, BEHAVIOUR, AND PRICING MAY CHANGE AT ANY TIME WITHOUT NOTICE.
Some jurisdictions do not allow exclusion of implied warranties; the above exclusions apply to the fullest extent permitted in your jurisdiction.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ETI, ITS OFFICERS, DIRECTORS, EMPLOYEES, AND AGENTS SHALL NOT BE LIABLE FOR:
Where liability cannot be excluded, ETI's total cumulative liability for all claims arising out of or relating to these Terms or the Services shall not exceed the greater of: (a) the amounts you paid to ETI in the 3 months preceding the event giving rise to the claim, or (b) USD $100.
These limitations apply regardless of the legal theory under which a claim is brought and even if ETI has been advised of the possibility of such damages.
You agree to indemnify, defend, and hold harmless ETI and its officers, directors, employees, agents, and licensors from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable legal fees) arising out of or relating to:
Voluntary closure. You may close your account at any time from the dashboard. On closure, your remaining wallet balance is forfeited unless ETI elects to refund it at its discretion. All API keys are immediately revoked and all pending jobs are cancelled without charge.
ETI's right to suspend or terminate. ETI reserves the right to suspend, restrict, or permanently terminate any account at any time, with or without prior notice, if ETI determines in its reasonable judgement that: (a) the account or any API key is being used in violation of these Terms; (b) the account poses a risk to platform security or stability; (c) the account holder has provided false or misleading information; (d) the account has a zero or negative wallet balance; (e) we are required to act by law; or (f) continued operation of the account creates legal, regulatory, or reputational risk for ETI.
Immediate termination without notice. The following violations result in immediate termination without warning: submission of CSAM or content that sexualises minors; deliberate attacks on Botverse infrastructure; use of the platform to circumvent DRM or TPM systems; submission of content that violates OFAC sanctions; or any activity that constitutes a criminal offence under applicable law.
Effect of termination. On termination, all API keys are revoked immediately, all pending jobs are cancelled, and your dashboard access is removed. Job metadata is retained for the standard 90-day period for audit purposes. Wallet balances are forfeited on termination for cause. On voluntary closure or termination without cause, ETI will return any remaining wallet balance to your payment method within 30 days, subject to a minimum refund threshold of $1.00.
These Terms are governed by the laws of the State of Arizona, USA, without regard to conflict of law provisions.
Informal resolution first. If you have a dispute, contact legal@botverse.cloud. We will try to resolve it within 30 days.
Binding individual arbitration. If informal resolution fails, any dispute arising out of or relating to these Terms or the Services shall be resolved by binding individual arbitration under the American Arbitration Association (AAA) Commercial Arbitration Rules, in Maricopa County, Arizona, or remotely by mutual agreement. The arbitrator's award is final and binding. This arbitration clause does not apply where prohibited by applicable law.
Class action waiver. To the fullest extent permitted by law, all claims must be brought on an individual basis. No class actions, class-wide arbitrations, or representative actions.
EU/UK businesses. If you are a business in the European Economic Area or United Kingdom, nothing in these Terms prevents you from bringing a claim in the courts of your country of establishment under applicable law. Arizona choice of law applies to the extent it does not conflict with mandatory EU or UK law applicable to your situation.
ETI may update these Terms at any time. For material changes — those that meaningfully affect your rights or obligations — we will notify you by email at least 14 days before the changes take effect. Minor corrections and clarifications may be made without advance notice.
Your continued use of Botverse after the effective date of updated Terms constitutes your acceptance of those changes. If you do not agree, you may close your account before the changes take effect.
The current effective version of these Terms is always available at botverse.cloud/legal/terms.
Entertainment Technologists Inc.
Sedona, Arizona, USA
General: support@botverse.cloud
Legal: legal@botverse.cloud
Billing: billing@botverse.cloud
botverse.cloud