Data, and how we arrive at it

That one is live and covers the session you are in. This one keeps every session, compares them across a course and a term, and can be opened by someone who was never in the room. Most institutions use both.

On RIADVICE infrastructure, in one location that is named in your agreement. We are the processor and you are the controller, and we will tell you in writing which datacentre it is before you commit to anything. If your policy will not allow a shared platform, we can stand one up for your institution alone.

No. It works from the session data BigBlueButton already produces. Teachers and students see no change at all.

It reads the event stream BigBlueButton itself produces. That covers every session whatever started it: Moodle, another LMS, a portal, a direct API call. It also records which of those it was, so an LMS class and a departmental room stay separate in a report instead of being averaged together.

Yes, and we scope it with you. A tool reading the modelled tables becomes something we keep stable for you across upgrades. We would rather agree to that deliberately. Tell us the tool and what you need out of it.

Access is granted per person, per dashboard. A quality lead sees the dashboards you gave them, and an external reviewer sees only what you granted for the review. If your policy needs the analytics on a platform of your own rather than one we also run for others, we build that and quote for it.

Yes. Tell us the question and we build the view. The meeting metadata your LMS sends is already stored, so if it passes something like a course or a group, that is what we group by.

We report what happened, not what will happen. Every meeting counts the students who sat through it without speaking, writing or answering a poll. Every participant carries how much of the session they spent that way. A tutor can act on that the same week. We stop short of turning it into a dropout prediction: who spoke in a video call is thin evidence for a claim that large. If you already run such a model, this is a clean and documented source to feed it.

It follows how many sessions you run and how many people need access. Book a short call and you will get a figure, not a range.

Directly and in writing. You are the controller and we are the processor, under a data processing agreement. The data sits in one named location on our infrastructure. We read the events BigBlueButton produces about a session, including the chat teachers already see. We do not analyse recordings, read cameras or infer anything about a person. We handle access and erasure requests for a named individual, and we name our sub-processors. The same facts answer FERPA.

No. They describe what can be observed in a recorded session: who spoke, who wrote, which tools were used. Learning is not one of those things, and any product that tells you otherwise is selling you a number it cannot stand behind. These exist to support a conversation about teaching, not to grade anyone.