1 — The batch
How many people, and how they are grouped. A single year, a department, a mixed cohort. If it is several batches, say how many and whether they can sit separately.
Talking to us
Book a session.
There is no form here. Write to us with four things about your batch and we will reply with a straight answer about whether this is the right instrument for it — including saying no, which happens often enough that it is worth mentioning on the page rather than discovering later.
Write to us
Four things, and we can answer properly.
Anything less and the first reply is a list of questions, which wastes a week for both of us.
2 — The setting
A hall, a lab, a classroom. Whether everyone can see one shared screen, and whether participants will use lab machines or their own phones.
3 — The slot
Roughly when, and whether you can protect 45 to 60 uninterrupted minutes. A session split across two shorter slots does not work, and it is better to know that now.
4 — Why you want it
The most useful line in the message. If the answer is assessment or screening, we will say so immediately rather than after a proposal.
Write to hello@democrez.com — subject “INSTITUTION ENQUIRY”
You are booking a room full of people's honest answers. That is worth a paragraph of context rather than a one-line enquiry, and it changes what we can tell you back.
From your side of the table
Six questions you
should be asking us.
If we were evaluating this for an institution, these are the questions we would push with. The answers are already on this site, but they are worth hearing directly before you sign anything.
| Ask us | The answer you should get |
|---|---|
| Can you give us anything about individual students? | No — and not because of a policy, but because no link between a student and their answers is recorded |
| Does the report include national comparison today? | No. Not until enough cards have been sealed on the public record |
| How long do you keep the phone verification? | Raw verification documents: up to 30 days; verification result / compliance logs: up to 1 year (unless longer period is legally required) |
| What happens if our batch is small? | We say so before agreeing a date, rather than producing a report that could identify somebody |
| Can students opt out without consequence? | They must be able to — and if they cannot at your institution, the session collects the wrong thing |
| What do you get out of this? | Verified, deduplicated responses from real people. It is on the overview page, in a table, in both columns |
The full exchange, stated plainly. What you get, and what we get
Weigh these before booking
Two things that are
not settled yet.
Both would be easy to leave until you asked. Neither should change your mind on its own, but both should be in front of you when you decide.
Not available yet
National comparison
The report describes your batch on its own. The comparison against wider public figures arrives when enough cards have crossed their thresholds and been sealed — and no date can honestly be attached to that. What the report contains
Policy
Retention period
Raw verification documents: up to 30 days after successful verification; verification results and audit/compliance logs: up to 1 year. Student privacy
Where we decline
Four reasons we would
turn a booking down.
The purpose is assessment
If the session is meant to inform placement, counselling or screening of named students, it cannot serve that and would occupy a slot you need for something else.
The batch is too small
Below the size where a group report stays genuinely anonymous, we decline rather than produce a document that could identify somebody in practice.
Opting out carries a cost
If declining would in practice count against a student at your institution, the session will collect compliance. That is worse than no data, because it looks identical to real data.
The slot cannot be protected
A session interrupted midway, or split across two sittings, does not produce a reading worth having. Better to move the date than to run it badly.
Questions
Straight answers.
Why is there no booking form?
Because a form would store what you type, on a website that otherwise holds no data, and because a useful reply depends on four things a form would flatten into boxes. An email leaves the record of what you asked in your hands as well as ours.
What does a session cost?
Pricing depends on batch size and is discussed directly rather than published, so that a quote reflects what you actually need. Tell us the size and setting and you will get a figure rather than a range.
How far ahead should we write?
Far enough that the slot can be protected in a timetable, which is usually the binding constraint rather than anything on our side. A session that has to be squeezed into a gap is the one most likely to be interrupted.
Can we run it for several batches at once?
Several batches means several sessions, each in its own sitting. The limit is one session per batch, and a combined sitting would produce a group picture of a group that does not exist outside that room.
Do you need anything from our IT department?
Usually nothing. The session runs in a browser from a link, with no installation and no account creation. If your network blocks unfamiliar domains, that is worth checking before the day — it is the one thing that has to work.
Will you say no?
Sometimes, and we would rather do it in the first reply. The four reasons above cover most of them. Saying yes to a session that cannot produce anything useful costs you a slot and costs us a batch of answers that mean nothing.
Can we see a sample report first?
We can walk you through what a report contains, section by section, and that page already does most of it. What we will not do is hand over a sample filled with invented figures, because a plausible-looking document is exactly the thing this platform refuses to produce.
Send us the four things.
Batch, setting, slot, and why you want it. We will tell you plainly whether it fits.