Encrypted data
For an instance with encryption, the server cannot read names, dates of birth and some further information. The unlocked browser therefore takes on tasks the server otherwise does, such as searching by name.
How exports, emails and receipts handle encrypted information is described in Exports and receipts with encryption.
What is encrypted
- Name and date of birthof a participant
- Important information for the organizers
- Answers to additional questions
- Last name of a participant account
- Billing address of a receipt
- Receipts and proofs in the archive
- Email addresses, phone numbers, addressesof the accounts, for notifications
- First names of the accountsfor the greeting in emails
- Names of admins and organizers
- Answers fepli calculates withchoice with a surcharge, yes/no questions of the season
- Offers, seasons, organizer profiles
- Pseudonym and year of birthinstead of name and date of birth
| Information | Who can read it | What the server has instead |
|---|---|---|
| First name, last name, date of birth and Important information for the organizers of a participant | the team, the organizer profiles at whose offers the participant is registered, and the family with a key of its own | a pseudonym “Kind {code}” instead of the name, the year of birth and the age of every registration instead of the date of birth |
| Answers to additional questions | the team, the organizer profiles of the registration and the family with a key of its own | nothing |
| Last name of a participant account | the team | the first name |
| Billing address of a receipt | the team and the paying account with a key of its own | nothing. It is readable only at the moment someone saves it. |
| Name under Declared by of a consent | the team and the account with a key of its own | nothing. It is readable only when the consent is given. |
| Receipts, proofs of consent and paper proofs in the archive | the team, the account with a key of its own and the emergency kit | the checksum of the file |
- A pseudonym is a code of 4 characters such as “K7Q2”. It tells siblings apart but gives nobody away.
- The family reads its children's data once its account has a key of its own and the team has confirmed it.
- The paying account is the family account of the debtor or the account that paid at the checkout, never the team member who booked it.
- Whatever was in the archive before the encryption was switched on stays unencrypted until its lock ends.
Year of birth and age
- The server takes the year of birth from a date the team or the family saves when editing, and from the date that was still readable at the first encryption.
- A date of birth that organizers send along when registering does not change the year of birth.
- Without a date, the age of a registration is the age the participant reaches in the year of the offer.
- fepli checks age limits with the date of birth if the browser sends it, otherwise with the year of birth. The limit counts as met if one of the two possible ages fits.
- If no age is known, an offer with an age limit does not take the child.
In plain text
This information stays readable because the server works with it:
| Information | Why the server needs it |
|---|---|
| Email address, phone number and postal address of the accounts | for notifications and text messages |
| Email address, phone number and mobile number of a participant | – |
| First name of the accounts | for the greeting in emails |
| Names of the accounts of admins and organizers | – |
| Answers to a question of the type Choice where one option has a surcharge | The surcharge is part of the participation fee and of the receipt. |
| Answers to yes/no questions of the season | The priority for working parents evaluates them in the lottery. |
| Offers, seasons, organizer profiles | – |
Display in the admin panel
- When the browser is unlocked, lists, side panels, detail pages, the participant list, the search preview and delete dialogs show name, date of birth, age and notes, e.g. “11 years · born 23.11.2014” in the head of the detail page.
- When it is not unlocked, the pseudonym stands there. How to unlock is described in Unlocking and connected devices.
- The title of the browser tab, the breadcrumbs and notices always show the pseudonym.
- Deleting and the erasure run also remove the participant's keys.
Forms
- Encrypted fields are locked until the browser is unlocked. This covers the first name, last name, date of birth and Important information for the organizers of a participant, also in Create participant.
- After unlocking, the values stand in the fields. The bar for unsaved changes does not count them as a change.
- On saving, only the encrypted values go to the server. If a required field is empty, the server reports it as usual.
- Without a last name entered, Create participant takes the account's last name and encrypts it.
- If a form cannot show all encrypted fields, they are locked. The team can change them then.
The browser encrypts new names as soon as they are entered. This applies to new children and new participant accounts on the website, to Create account and New registration in the admin panel, and to people added in the questionnaire under Add someone who came without registering.
On the website, a child the family cannot open shows “On file” in the fields. If the family leaves them empty, the information on file stays. To change it, the family enters everything again. If it has opened the child with the lock, the values stand in the fields.
Searching and sorting
| Task | What happens |
|---|---|
| Search by name | The unlocked browser searches the decrypted names. It sends the server only whom it found, not the search term. |
| Search without unlocking | The search field shows “Names once unlocked”. The server finds only what it can read, e.g. email address and phone number. |
| Search in fields that search more than names | If the browser finds nobody, the term goes to the server, e.g. for titles of offers or receipt numbers. |
| Sorting by name | The unlocked browser sorts by last and first name. Until then, the rows stand in an order of the server's. |
| Duplicates | A team member's browser compares the decrypted names and dates of birth and sends the server only the pairs (Duplicates). |
- Searching by name in the browser applies wherever fepli finds people by name, e.g. in Participants, Accounts, Consents and Payments, in the participant list, the global search and the data subject rights.
- In Participants and Accounts, sorting by name comes after the other sortings. The browser sorts all entries and fetches the rows of the chosen page. The server learns which rows are on a page, not their order.
- Debtors and Registrations under Payments do not offer sorting by name.
On the website
- Where a child is encrypted, “Name on file” or “Born in {year}” stands with a lock beside it. On the pages for children, the notice Names encrypted explains that the lock opens the names in this browser.
- If the account has no key yet, the browser creates it by itself on the visit and is connected with it.
- Once the browser is connected, it shows names and dates of birth in the account, in the consents, in the data usage, in the application form, in the participation and in the receipt (Connected devices).
- Under Draw together, children of other families with the same friend code show by first name only. If their name is encrypted, “Name on file” stands without a lock, because the family's browser does not receive these names.
Messages
| Message | Meaning |
|---|---|
| “Decrypt first to edit.” | The field is encrypted, and the browser is not unlocked. |
| “Stored encrypted. The team can change it.” | The form does not show all encrypted fields. The team changes the information in the admin panel. |
| “{name} cannot take part – the age is not known (…). Please give the date of birth.” | The offer has an age limit, and fepli does not know the age. Enter the date of birth. |
| “Cannot be decrypted: the stored value is damaged.” | A single value cannot be decrypted. |