IRF for NGOs

What the board keeps

The board keeps very little, and this page lists all of it. The operator of blockchainframeworks.org, Matthew Breen, is responsible for it. Write to him at the Nordic Blockchain Association, Højbro Plads 10, 1., 1200 København K, Denmark, or at the addresses under Questions. The board is published with the Nordic Blockchain Association. "We" on this page means the operator.

What the board stores

When an NGO posts a tender, we store the anonymised text it chose to publish, with its use cases, the parts of the solution it asks for, the countries, the sector and the deadline. That is public.

We also store the reply address the NGO gave, so that responses can reach it. It is never shown to anyone on the board. We delete it 30 days after the deadline, or at once if the NGO takes the tender down with the link in the first email.

We store a scrambled code made from the reply address. It ties the confirmation link to that mailbox and stops one address posting many tenders in a day. The code is zeroed 30 days after the deadline. The confirmation email itself is sent and not stored.

When a supplier responds, we store that a response to that tender was passed on, and the time. We do not store who sent it.

A tender that the NGO never confirms by email is deleted after 2 days. When a tender closes and its text is gone, a row stays with its dates, the sector and the number of responses passed on, so that we can say how many tenders the board has carried.

What the board does not store

There are no supplier accounts. We hold no supplier email addresses, company names or lists of interests. We hold no bid, no price, no response text and no file.

A response goes from the supplier's browser through our mail server to the NGO's reply address, and we forget it. We do not write it to the database, to a log or to disk. The mail server's own handling is set by the hosting company.

The board does not know who has used IRF for NGOs, and the assessment does not know who is on the board. No assessment answer reaches the board.

Email alerts

Email alerts are run by the Nordic Blockchain Association in its own mailing tool, under its privacy notice. The board links to the sign-up form and nothing more. We do not see the list, and the board stores nobody on it.

The feed needs no sign-up. A feed reader asks for it like any web page, and we keep no record of who asked.

Short-lived records

To limit how fast anyone can use the forms, we keep a scrambled code made from your IP address and the action you took. It is deleted after a day. The address itself is not kept. Visitors get no cookie, and the pages use no browser storage. Staff who sign in to the administration page get a sign-in cookie.

Who can see it

The operator and Nordic Blockchain Association staff with a sign-in can see the tender list: reference, sector, countries, use cases, parts, dates and how many responses were passed on. The administration page shows no reply addresses and has no response texts to show. Whoever manages the hosting account can open the database, which holds the reply addresses of open tenders.

The hosting company, IONOS, keeps ordinary web server logs, as every web host does. We do not read them for anything. How long it keeps them is up to IONOS.

We do not sell, share or publish any of it. There are no advertising or tracking scripts on the board.

Questions

To ask what the board holds about you, to correct it or to have it deleted, write to privacy@blockchainframeworks.org. For anything else, write to contact@nordicblockchain.com.