This policy covers curators who run events on the WSPR Screening and applicants who complete a screening through a Screening Link. The plain summary is on the main page; this is the full version.
The suite is operated by [ legal entity name — set before deploy ] ("WSPR", "we", "us").
For applicant screenings, the curator running the event decides what to ask and what to do with the answers; WSPR provides the software that collects, scores, holds and deletes them. If you screened for an event and want to know how a curator handled your answers, ask that curator.
When you complete a screening: the FetLife username you enter; your answers to the situational questions and to any custom questions the curator added; the scores and archetype derived from those answers; the written reading generated from them; and the time the screening was submitted.
Nothing else is asked for and nothing else is kept. The suite does not collect your legal name, date of birth, address, phone number, email address, photographs, government identification, payment details, or location. There is no applicant account, no password, and no profile that persists between events. Screening twice for the same event replaces your earlier submission rather than creating a second record.
Your display name; the username you choose and a hash of the password you choose, from which the password itself is not readable back; the events you create and their dates and window lengths; your referral relationships and credit balance; sign-in times; and, at enrolment, the fact and time that you accepted the Terms of Service and this policy, and the version you accepted.
To limit repeated failed sign-in and enrolment attempts, the suite counts attempts against a hashed form of the network address they came from. The address itself is not stored. Session cookies are used to keep a signed-in curator signed in; they are strictly necessary and there are no advertising, analytics, or tracking cookies on the suite.
Our hosting provider keeps its own operational and security logs of requests made to the site, in the ordinary way, under its own retention arrangements.
Applicant answers exist so that the curator of one specific event can decide on one specific admission. Curator information exists to operate accounts, events, credits, and billing. Technical information exists to keep the suite working and to resist abuse. None of it is used for advertising, profiling across events, training, or resale.
An event's screenings and reports can be opened by the curator running that event. If the event is transferred to another curator, they take it over, applicants included; applicants are told this can happen before they answer anything, and every transfer is logged. The suite offers other curators and WSPR moderators no way to open an event's applicants.
While an event is live, WSPR holds the key that unlocks its reports. Encrypting the data at rest limits what an intruder into our storage would obtain; it does not mean we are technically unable to read it, and we do not claim otherwise. We access an event's data only where it is necessary to operate or repair the service, or where we are legally required to.
We use third-party infrastructure providers to host the site and store data. They process it on our behalf under their own terms. We do not sell personal information, and we do not share it with advertisers, data brokers, or other curators.
When an event is created, a deletion date is stamped on it. Every applicant on that event is shown that date before they answer a single question. The suite deletes an event's screenings, scores, reports and the key that reads them 72 hours after the event, or on the stamped date, whichever comes first. Postponing an event does not move the stamped date past its limit; an event pushed beyond it has its applicant data deleted and starts again. Cancelling an event deletes its applicant data immediately.
Afterwards an event record retains only its name, its dates, and how many people screened. It names nobody and contains nothing anybody answered.
Curator accounts and their event history are kept until the account is removed. Acceptance records are kept while the account exists and for as long afterwards as we may need them to establish that the terms were accepted.
Two honest limits. First, deletion applies to what the suite holds; it cannot reach anything a curator exported, printed, screenshotted, or wrote down, and it cannot reach anything you sent a curator by direct message outside WSPR. Second, our infrastructure providers operate their own backups and logs on their own schedules, which we neither control nor audit; a record deleted from the suite may persist in a provider's systems for a period after that.
Screening data is encrypted at rest. Passwords are stored as salted hashes. Sign-in is rate limited and locks after repeated failures. Sessions are checked against the server rather than trusted from a cookie alone. Administrative actions are logged.
These are measures, not guarantees. No system is immune, and we make no claim that the suite cannot be breached.
Screening is voluntary. If you do not want to answer, do not begin a screening; a curator may still admit you by whatever means they used before.
Depending on where you live, you may have the right to ask for a copy of the information held about you, to have it corrected, or to have it deleted, and to be free from discrimination for exercising those rights. Ask at the address in section 12 and we will respond within the time the applicable law allows. Two practical notes: a screening usually deletes itself sooner than a request can be processed, and because the suite deliberately holds no way to identify or contact an applicant, we may be unable to locate your record from your name alone — the event and the FetLife username you used are what let us find it.
The suite is for adults. It is not directed at anyone under 18, and we do not knowingly collect information from anyone under 18. If we learn that we have, we delete it.
We may update this policy. The version identifier at the top of the page changes when we do, and curators are told directly before a material change takes effect.
Privacy questions and requests: [ contact address — set before deploy ].
The short version, which the rest of this page only makes precise: the answers exist for one night, one curator can read them, and then they are gone.