Qué guardamos sobre usted
Esta página enumera cada tipo de información personal que Roles, Profiles and Flows guarda, por qué la guardamos y durante cuánto tiempo.
Por qué podemos guardarla
Legitimate interest in operating a closed standards service, deciding who may use it, and protecting it from bulk copying.
Where your data is kept and processed.
RPF's database is in Ireland and the app runs in Belgium. Our sign-in service, CID, also runs in Belgium, with its data in Ireland. Documents you upload, and the CVs and work samples you add as evidence, are stored and read in Belgium, and RPF's AI features run on Google's servers in the European Union. Four things go outside the EU. When you ask our evidence library, SMC, to find material for a scenario, your request goes to its service in the United States, and RPF asks you to agree first. When you take an assessment through Assessor.io, it runs in Montréal, Canada, and the levels you agree to send come to RPF from there. Reference documents that RPF's editors add to the catalogue are converted by our document service in the United States, which uses Mistral AI in France to read scanned pages. Emails are sent through Amazon's service in Sydney, Australia, by scheduled jobs that run on GitHub's servers in the United States.
These are the places we know RPF keeps and processes your information. The services we rely on use their own suppliers, and information can cross other countries on its way between them, so we cannot promise that it never leaves these places. If you need that assurance, contact us before you use RPF.
Qué guardamos 11
- An enquiry sent from the front page: the name, email address, organisation, role and question someone gives, the two emails it produced (to the RPF team and the receipt to the sender), and a keyed hash of the connection it came from. Not the address of the connection itself.
- To reply to the person who asked, to keep a record of what they asked, and to limit how many enquiries one connection can send.
- 24 months from the enquiry.
- The IP address of an anonymous reader, and how much they read that day.
- To keep the public catalogue from being copied wholesale, and to keep costs bounded.
- 12 months from the reading day.
- The contact email and affiliation of an approved API consumer.
- To identify who holds a credential, and to reach them about it. Also the record of the terms they agreed to.
- For as long as the key exists, and for 24 months after it is revoked.
- A practitioner record in an organisation: who the member is, the active years they declared in each domain, when they ticked the rights box, who granted the role, their visibility setting, the scenarios they saved privately inside the workspace, and how much AI processing each of their Wayfinder cycles used (counted in tokens). If the member resolves a private scenario, the role, profile, flow, diagram, statements and evidence links it creates are kept as private records linked to their practitioner record, visible only to them (and to their organisation's member managers if they choose full visibility), and deleted with that record.
- To give a member of a client organisation a private, persistent record in RPF Wayfinder that only they, and their organisation as far as their visibility setting allows, can see.
- For as long as the member holds the practitioner role, and for 24 months after the role is revoked or the member leaves the organisation.
- The member's Wayfinder profile: the role they started from, the Action Statements and Information Uses they confirmed (what they can do, and the information they work with), the level they gave themselves for each, the kind of evidence behind each one, their notes on the intelligence and attitude each group of statements needs, and a copy of every version they downloaded.
- So the member has a record of what they can do today, which they can download, share and compare with a role they are aiming for.
- Kept while the practitioner record exists, and deleted with it.
- The CVs, work samples, web pages and text the member adds as evidence, the text RPF reads from them, a code that identifies each file, who confirmed RPF may use it and in which language, and whether the member allows quotes from it to be shown when they share their profile.
- To back up what the member says they can do.
- Kept for 24 months after the member last changed or downloaded their profile. Deleted sooner if the member deletes the document, and always deleted with the practitioner record.
- A practitioner's pathways: the target each one was worked out against, how each statement in it compares with the practitioner's profile, the learning, experience and demonstration threads, their titles, explanations, dates and status, and every earlier version of the pathway. Whether they asked for an email when a pathway changes, and when one was last sent.
- To show the member the way from their current profile to a target, and how it changes from one cycle to the next.
- Kept with the practitioner record and deleted with it.
- The results of assessments the member takes through Assessor.io and agrees to send to RPF: which assessment, the organisation that ran it and the target it was based on, the level an auditor confirmed or corrected for each statement, when the review was finalised, when the member agreed to send it, the identity the result came with, and whether the member applied or declined it. Not the member's written answers, the auditor's notes or the auditor's name.
- So an assessed level can count as evidence for what the member says they can do.
- Kept while the practitioner record exists, and deleted with it. If the member declines a result, or Assessor.io withdraws it, its levels are deleted at once and only a note that it arrived is kept.
- A note of each message Assessor.io sends RPF about an assessment: what kind of message it was, when it arrived, what RPF did with it and which result it carried. Not the levels, and not the identity the result came with.
- To show that each message from Assessor.io arrived once, and to find any that did not.
- 12 months from arrival.
- A record that a Readiness Check was run: which published scenario, how it was given the CV (pasted or uploaded), whether it finished, when, and, if you were signed in, your account. Never the CV or anything in it.
- To count how often each published scenario is checked, and to see where the check fails.
- 12 months from the check.
- The email address of anyone who has attempted to sign in, INCLUDING people who were refused, because the account row is created before access is checked.
- To hold an account. For a refused sign-in the row is a by-product rather than a purpose, which is why it has the shortest period here.
- 12 months, for rows that hold no roles and no organisation membership. An account in use is kept for as long as it is in use.
Cuando usted navega por el catálogo público, guardamos una cookie llamada rpf_catalogue_pass. Sirve para que el catálogo siga siendo utilizable para las personas cuando lo inunda el tráfico automatizado. Solo contiene la hora en que se emitió, firmada para que podamos comprobar que la emitimos nosotros, y nada que lo identifique. Dura siete días. Es estrictamente necesaria, por lo que la guardamos sin preguntarle.
Sus opciones
Puede preguntar qué guardamos sobre usted, pedir que se corrija o pedir que se elimine. Escríbanos y le responderemos.
Un profesional puede descargar todo lo que Wayfinder guarda sobre él, en un solo archivo, desde su página de perfil.
Escriba a privacy@bimexcellence.org