reveliQ

Privacy

What we keep about you and your organization, who can see it, and what you can ask of us.

Draft. The operator has not finished this notice yet, so some details below are marked as missing. Do not rely on it until they are filled in.

Who runs this service

This service, reveliQ Data & AI Readiness Assessment, is run by [not yet filled in by the operator]. Questions, and requests about your data, go to [not yet filled in by the operator].

What we keep

Your account: your email address and your name. Your password is kept only as a one-way hash, so nobody, including us, can read it.

What you enter: your answers to the questionnaire (a level for each question, and the evidence, owner, priority and comment you may add), the numbers you enter, and what your organization tells us about itself: company profile, project scope, baseline figures, systems and how data enters them.

What we produce from it: scores, reports and the PDF files made from them, a record of who was given access to what, and an audit log of sensitive actions.

Who can see it

You can see your own answers. A person who administers your organization can see every participant's answers in the organization's projects; other members see only their own. Reports quote free-text comments without names.

The reveliQ team can read a client's answers to deliver the service, for example to prepare a report. Every time the team looks at or exports a client's information, the audit log records who did it and when.

Nobody outside your organization and the reveliQ team can see your answers, and your answers are not compared with, or shown to, other organizations.

Reports

PDF reports are kept in private storage. They can be downloaded only by people allowed to see that project: the app checks who is asking each time, and no public storage link is ever given out.

Website statistics

We count visits to our public pages with our own anonymous counter. We do not use cookies or a third-party analytics service for this. We keep the page (with identifiers removed), the website that referred the visit, campaign tags in the link, a coarse device type, and a visitor code made from the day, the network address and the browser. The code changes every day, so it counts visitors per day but cannot follow anyone from one day to the next. The network address itself is never stored.

We honour Do Not Track and Global Privacy Control, and we do not count visits by crawlers or the team's own area. Counts older than thirteen months are removed.

Cookies and browser storage

We set only the cookies needed to keep you signed in, which the service cannot work without. Your browser also remembers your light or dark preference, and the PDF theme you last chose. We use no advertising or tracking cookies.

Where it is kept, and who processes it

Your data is kept in [not yet filled in by the operator]. Companies that process data for us: [not yet filled in by the operator].

How long we keep it

[not yet filled in by the operator]

Your choices

You can take your data with you: an organization administrator can export a project's answers and reports, or everything the organization holds; any member can download their own answers. Exports contain no colleagues' email addresses.

You can ask us to correct or erase your data, or your organization's, by writing to [not yet filled in by the operator]. The team can erase a project or a whole organization, including its files and, on request, its accounts. You also have the right to complain to your data protection authority.

Back to overview