Privacy Policy

Oratora is a live audience-engagement platform. Organizers run live sessions (polls, quizzes, word clouds, Q&A) and publish async forms; audiences respond from their own phones.

The data controller is registered entity name, registered at registered address, country. Where this policy says “we”, “us” or “Oratora”, it means that entity.

For privacy questions, contact privacy@yourdomain. Our grievance officer, as required under India’s Information Technology Rules, is officer name, reachable at grievance@yourdomain.

The distinction matters for the rest of this policy, because we hold very different amounts of data about each.

• Organizers create an account, build events and forms, and pay for passes or subscriptions. We are the controller of organizer account data.
• Participants join an event with a room code or a form link. Participants never need an account. For the responses a participant submits into an organizer’s event, the organizer decides what is asked and why; we act as a processor on their behalf.

From organizers

• Account details — name and email address. If you sign up with a password we store a bcrypt hash, never the password itself. If you sign in with Google we receive your name, email address and whether that email is verified.
• Session records — for security and to let you see and revoke active sign-ins, each session stores an IP address and a browser user-agent string alongside its expiry.
• Content you create — organization and event names, activities, questions, options, form fields and their settings.
• Billing records — your plan, subscription status, and the identifiers our payment processor returns. We never see or store your full card number; card details are collected by Razorpay directly.
• API and integration credentials — API keys you generate, and tokens issued when you connect Oratora to Claude, Zoom, Microsoft Teams, Google Slides or PowerPoint. Keys are stored hashed.

From participants

• Your answers— the option you picked, the words you submitted, your quiz answers, ratings, open-ended text and Q&A questions and upvotes.
• A participant token — a random identifier stored in your browser so the event knows you are the same person across questions, can score a quiz and can stop double-voting. It is not linked to a name, an email address or an account.
• A display name, only if asked — some formats (leaderboards, team events) ask for a nickname or handle. You choose what to type. If the organizer has made the activity anonymous, your response is not tied to a display name.

We do not ask participants for an email address, a phone number or a real name, and we do not build advertising profiles from participant responses.

When you contact us

Our contact and demo-request forms collect your name, email, message, and for demo requests optionally your company, role, use case, audience size and timeframe. We also store a hash of your IP address and your user-agent, purely to rate-limit and de-duplicate submissions. We do not store the raw IP for these forms.

We use the minimum needed to make the product work, and we do not run advertising or cross-site tracking cookies.

• Session cookie (organizers) — keeps you signed in. Strictly necessary.
• Participant token — stored in your browser for the duration of an event so your responses stay consistent. Strictly necessary.
• Theme preference — remembers light or dark mode.
• Consent record — stores your answer to the cookie prompt, so we do not ask again on every page. Strictly necessary.
• Google Analytics (_ga, _ga_*) — only if you accept. See below.

Analytics runs on our public marketing and documentation pages only — oratora.live and docs.oratora.live. It is not present in the organizer dashboard, and it is not present on any participant surface: joining an event, answering on your phone, the big screen, and public forms carry no analytics at all, whatever you choose here.

On those pages we use Google Analytics 4to understand which pages people arrive on. It runs in Google’s consent mode with storage denied by default, which means no analytics cookie is written to your device unless you accept. Advertising, ad-personalisation and ad-user-data storage are denied permanently — we never turn those on.

To be straight with you about what declining does and does not do: if you decline, nothing is stored on your device and you are not identified across visits, but Google still receives an anonymous, cookieless signal that a page was viewed, which it uses to estimate aggregate totals. That is how consent mode works, and we would rather say so than imply the page goes silent.

You can change your mind at any time with Cookie settings — in the footer on oratora.live, and in the top navigation on docs.oratora.live. Declining is a single click, exactly like accepting. The two sites keep separate records, because a browser cannot share this setting across domains; choose on each.

This section is deliberately specific, because it is the part of the product that sends content outside our own systems.

Oratora’s mood meter and AI summaries work by sending the responses collected in a session or form to Google’s Gemini API, which returns a sentiment reading or a plain-language recap. In practice this means free-text participant answers, Q&A questions and open-ended responses are transmitted to Google for processing when an organizer uses those features.

• We send the response content and the question it answers.
• We do not send organizer account details, billing data, or participant tokens.
• Summaries are generated on request or at the end of a session — not continuously.

If you are an organizer running a session where responses may contain personal or sensitive information, you should tell your audience before enabling these features, and you should avoid asking questions that invite sensitive disclosures.

confirm Gemini data-retention terms and whether your tier trains on submitted content

We do not sell personal data. We share it only with the service providers below, each of which processes it on our instructions.

If you connect Oratora to Claude, Zoom, Microsoft Teams, Google Slides or PowerPoint, data flows to that service under its privacy policy, at your instruction and only for what you connected.

We may also disclose data where we are legally required to, or to establish or defend legal claims.

Our providers operate globally, so your data may be processed outside your country, including in list hosting regions. Where data leaves the UK/EEA we rely on transfer mechanism, e.g. Standard Contractual Clauses.

• Organizer accounts — for as long as the account is open, then retention period after closure.
• Event and form responses — retained for the organizer until they delete the event, the form or their account. Deleting an event deletes its activities and responses.
• Sign-in sessions — until they expire or you revoke them.
• Billing records — kept as long as tax and accounting law requires, retention period.
• Contact and demo enquiries — retention period.

Depending on where you live, you may have the right to access, correct, delete, export or restrict use of your personal data, to object to processing based on legitimate interests, and to withdraw consent. Under India’s Digital Personal Data Protection Act you may also nominate someone to exercise your rights on your behalf.

Organizers can export every response to CSV and delete events, forms and their account from the dashboard at any time.

Participants: because we do not collect your name or email, we usually cannot identify which responses are yours. Contact the organizer who ran the event — they control that data and can remove it. If you can identify your responses another way, write to privacy@yourdomain and we will help.

To exercise any right, email privacy@yourdomain. You can also complain to your local data protection authority.

Passwords are stored as bcrypt hashes and API keys as hashes. Traffic is encrypted in transit with TLS. Access to production data is limited to staff who need it. Sessions record their IP and user-agent so you can spot and revoke one you do not recognise.

No system is perfectly secure. If we become aware of a breach affecting your personal data we will notify you and the relevant regulator where the law requires it.

Oratora is not directed at children, and organizers must not use it to knowingly collect personal data from children below the age of age threshold for your markets without verifiable parental consent. If you run events in classrooms, you are responsible for the consents your institution requires.

We will update this page when the product changes, and we will move the “last updated” date at the top. If a change materially affects how we use your data, we will tell account holders directly.

Questions? Contact us or email privacy@yourdomain.