Legal

Legal

The agreements and policies that apply when you use Bazm, and the details of the company behind it.

Documents

• Terms of Service

  The agreement between you and Bazm: what the platform does, what organisers and attendees are each responsible for, payments, and the limits of our liability.

• Privacy Policy

  What personal data we handle, why, who it is shared with, how long it is kept, and the rights you have over it.

• Cookie Policy

  Every cookie and browser-storage item Bazm sets, what each is for, and how to control them.

• Acceptable Use Policy

  What you may not do with Bazm, and what happens if you do.

• Data Processing Addendum

  The terms on which Bazm processes personal data for conference organisers. It forms part of the Terms of Service.

• Sub-processors and service providers

  The companies that help us run Bazm, what each one does, and where it processes data.

Company

Version history

• 2 November 2026 · Version 2026-11-02

  In the mobile app, the Cloudflare Turnstile check on sign-in, sign-up and password recovery now runs in a web page inside the app rather than in your phone's browser; the data involved and the provider are unchanged, Turnstile sets no cookie of its own, and the Cloudflare cookies the page may set stay in the app on your phone, not in your browser. Business cards gain Nearby: while its screen is open, the app uses Bluetooth to find other people close to you who have it open, so you can swap cards. Your phone broadcasts a random ID that we issue each time Nearby starts and replace with a new one before it runs out (it is not your name or your account, and each ID lasts 60 seconds at most), and the people close to you see the name and photo on your card; nothing is broadcast or scanned while Nearby is stopped, and Nearby does not use your location. We delete the IDs and the requests to share a card about a day after they were made. The Privacy Policy says so (the mobile app section, the retention table and how a received card reached you), and the Cookie Policy says where the security check runs and what it sets.

• 30 October 2026 · Version 2026-10-30

  Direct messages now belong to the two people in them rather than to a conference: one conversation per pair, kept for as long as both accounts exist, also after a conference ends or is removed; when an account is erased only the messages it sent are emptied and the other person's stay. The Privacy Policy and the Acceptable Use Policy say who can read a reported or filter-held direct message: Bazm always, and also the moderators of the conference the message belongs to, for a report made while that conference is running and also after it ends (they include the organiser's Owner and Admin and read only reported or held messages). A message belongs to a conference only if both people take part in one that has direct messages switched on and has not ended when it is sent, and the server decides that, not the people. The Privacy Policy lists what a block covers (the directory, matches and suggestions, chat, business cards, community posts and comments, shared travel and meeting requests, but not live and virtual sessions); says a suspension applied by Bazm stops direct messages (sending, starting a chat and sharing a card in one) and nothing else; and its retention table lists the reports Bazm answers and those suspensions (a record of a suspension, with its reason, stays in the audit log for 13 months), and says erasing an account empties the details its owner typed into reports they filed and keeps the report, unlinked. Business cards: the Privacy Policy says that Bazm, not the conference organiser, is responsible for them; what a card holds; that the people you share a card with keep a copy, also after you delete the card or your account, but that the copy stops updating once you stop taking part in the conference or either of you blocks the other; that your notes on cards you received are private to you; that a block also stops card sharing; who reads a reported card (the conference's moderators for a report made while the event is running, including after it ends; Bazm after it or when the conference has no moderators); that the automatic word filter now also checks business cards shared in chats; that the retention table now lists the notices about your cards (who saved your card or shared theirs with you), kept until you delete your account; and that the camera is also used to scan business cards.

• 11 October 2026 · Version 2026-10-11

  Cloudflare is now named as the provider that delivers and protects bazm.io (proxy and firewall), checks sign-in, sign-up and password-recovery requests with Turnstile, and counts page loads with Web Analytics. The Privacy Policy, the Cookie Policy and the list of sub-processors describe this, and the cookie table gains cf_clearance.

• 3 October 2026 · Version 2026-10-03

  First full publication of the Terms of Service, Privacy Policy, Cookie Policy, Acceptable Use Policy, Data Processing Addendum and the list of sub-processors.