Privacy

1. About Bino

Bino was developed for idealistic reasons, and has no incentive to store, process or share any informasjon except exactly what is required for the website to function. Bino is Free Software licensed under GNU Affero GPL V3, which requires that the source code be freely available, both the original website and any modified works. You can read the source code on Github to verify for yourself that what happens when you interact with the site is in line with the privacy policy.

2. What we store

Bino only saves the information required for you to have an account and to organize information about patients:

  1. Information you have provided: name, email, profile picture from Google, preferred language.
  2. Cookies are stored in your browser to avoid losing text in certain forms.
  3. Any content you have created on the site, such as pictures of patients and patient history.

Bino does not share any information with third parties.

3. Logging

3.a. No logging by default

Bino does no tracking or fingerprinting, regardless of your privacy settings. There is no logging of your activity at all unless you have explicitly consented to this using the form below. Actions that are visible to all logged-in users may be logged, such as checking in a patient, editing the capacity settings for your home, or marking yourself as unavailable.

3.b. Opt in to temporary logging

To help solve certain technical issues, you can choose to let us log the activity on the site, for instance when you click on links or submit forms, for a short period of time. Do not enable this setting unless an administrator has requested it in order to solve a specific problem. You can revoke the consent at any time, and consent is automatically removed after 14 days.

4. Deletion

When you leave the organization, you have the right to have your data deleted according to GDPR. There is a delete-button which lets the administrator delete as much information as possible; patients will be associated with an anonymous ID, but your profile will be marked as deleted.

It is the administrator's responsibility to ensure any additional data (such as logs generated according to 3.b.) are deleted.