Terms

Software for running a live session in front of an audience (a keynote, a webinar, an all-hands, a lecture) and for setting the same content to be worked through later. It is used from a browser. Participants join with a code and need no account; hosting is for members and admins of a workspace, and needs an account.

BamzIQ is offered by Primituz, Singapore, and Primituz is who you are agreeing these terms with. Anywhere below that says "the operator", that is who it means.

This is the clearest commitment on the page, and it applies to the free plan as much as to any pass. You may use BamzIQ for:

• Conferences, trade-show stands and paid events
• Webinars and product launches
• Recruitment and hiring events
• Client work, including work you bill on to a client
• Internal communications, onboarding and training
• Teaching, in any setting, paid or not

Pricing is per event, not per presenter. A licence here does not attach to the person at the front of the room, so a dozen occasional facilitators cost no more than one. What is priced is the size of the room.

There is no cap on session length, on any plan.

An account belongs to a person, not to a role, and you are responsible for what is done with it. Workspace administrators can invite members, set roles, issue password resets and remove people. There is no email service in the product: invitations and password resets are produced as links for an administrator to send however they already communicate with that person.

Do not share a password. Do not use somebody else’s account. Tell an administrator if you think an account has been reached by somebody who should not have it.

• Put content into a session that is unlawful, or that you have no right to display, including on a screen in front of other people, which is where most of this content ends up.
• Attempt to reach a room you were not invited into, or to obtain control of a session you are not hosting. A game code authorises playing and nothing else.
• Attempt to extract answer keys, other participants’ responses, or another workspace’s content.
• Use automated clients to flood a room, or to join it under false identities.
• Resell access to BamzIQ itself, as distinct from running paid events with it.

Hosts are responsible for moderating what their audience submits. The tools exist: audience questions are held for a moderator before they can reach a screen, submissions can be frozen, and the projected screen can be blanked in one press. But the judgement is the host’s.

Quizzes, events, images and everything else you author remain yours. The operator claims no ownership of them and does not use them to train any model. The permission taken is only the one needed to run the service: to store your content, to show it to the participants you show it to, and to keep the backups that make recovery possible.

Reports keep their own copy of the details they need (a session’s quiz title is stored at the time it was played), so a report remains a historical record even after the content behind it changes or is deleted.

BamzIQ ships with no model, no key and no AI backend of its own. If you want AI drafting, review or report insight, you connect your own account with an AI provider and supply your own key. Each feature is switched on separately, and each toggle is recorded.

That has two consequences worth stating. Your provider’s own terms govern what you send them, and the cost is theirs to charge, at their price: the operator adds no markup, because there is nothing being resold. And the model output is a draft: it is shown to you to accept, edit or discard, and nothing generated is published to a room without a person putting it there.

No payment is taken anywhere in BamzIQ, and no payment provider is connected. Recording a purchase writes it down and issues the pass it bought; settlement happens by invoice, outside the product. The billing screen inside the application says the same thing. No prices are published on this site at present: nothing charges for them yet, so a pass is quoted and invoiced rather than listed.

A pass is a one-time purchase with a participant ceiling and a 30-day window, counted as a duration from the moment it starts rather than by the calendar. The ceiling is inclusive: a pass for a thousand admits the thousandth person. Where more than one pass is valid at once, the largest ceiling applies.

Prices can change. A pass already issued keeps the price it was issued at. A new price is a new entry in the catalogue, never an edit to the one somebody already bought.

Nothing is being charged for at present, so there are no payment, invoicing, tax, refund or cancellation terms. This section describes how passes work if and when they are sold. Until then every ceiling described above is available at no cost.

There is no uptime commitment and no service level agreement. No availability percentage is offered, and none should be inferred from the engineering described elsewhere on this site.

What is true is narrower and testable: a room that loses its server comes back, sessions are snapshotted every couple of seconds so a planned deploy loses nothing, and the capacity figure quoted on this site was measured rather than estimated, on a single node, in one set of conditions, which is stated wherever the number appears. None of that is a promise about a particular day.

No compliance certification is claimed. No SOC 2 report, no ISO certification, no attestation of any regulatory regime.

BamzIQ is provided as it is, with no warranty of any kind. No promise is made that it will be uninterrupted, error free, or fit for a particular purpose, and no warranty is implied beyond what Singapore law does not allow to be excluded.

The operator is not liable for indirect or consequential loss. That includes lost profit, lost business, lost goodwill, and the cost of a session that did not run. Where liability cannot be excluded, it is limited in total to the greater of what you paid for BamzIQ in the twelve months before the claim, or one hundred Singapore dollars. Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not permit to be limited.

The practical reading, stated plainly because a cap is easy to write and easy to misjudge: BamzIQ is free, it makes no availability promise, and it should not be the only plan for a session that would be expensive to lose. Run a rehearsal, and keep a way to carry on without it.

You can stop using BamzIQ at any time. An administrator can delete an account, and is asked what should happen to the content that account authored. Export your reports first: CSV export is available on every plan and at any size.

The operator may suspend an account that is being used to do the things listed under what you must not do. Suspension for that reason can be immediate, because the harm is usually happening while you read about it. Otherwise, either side may end this with thirty days notice, which is also the notice given before these terms change in a way that matters to you.

If your account is suspended you can ask for it to be looked at again, and a person will. Write to the operator and say why.

Data on termination follows the retention schedule in the privacy notice rather than a second timetable here, so the two cannot drift apart. Export your reports before you go: CSV export is available on every plan and at any size.

These terms are governed by the laws of Singapore, and the courts of Singapore have exclusive jurisdiction over any dispute arising out of them.

How BamzIQ handles personal data is set out in the privacy notice.