Privacy

What BiomassFlux keeps about you, why, who sees it and how to have it removed. It describes what the site does today.

Last updated

Who runs BiomassFlux

BiomassFlux runs at biomassflux.ai4wa.com, linked from ai4wa.com. In this page, “we” means the people who run the site.

What you can do without signing in

The home page, the data catalogue, the FAQ and this page open without an account. Your browser still talks to Cloudflare, every page loads Google Analytics, and pages with a map talk to Mapbox (see services we use).

Signing in

Your email address signs you in: type it and the map opens. If there is no account for that address yet, one is made, with no password, and nothing is emailed. Signing in with an email alone does not prove the address is yours, so it opens the map and assessments only. Saved scenarios need a one-time code: the first time you open, save, run or export a saved scenario, or email a report, we email a six-digit code to the address and you type it in. A code works once and expires after 10 minutes; after that, this sign-in can reach your scenarios until you sign out. The first time an address is confirmed with a code, a welcome email is sent to it. It contains no password. Your saved scenarios are kept under the address, and only a sign-in confirmed with a code sent to that address can open them.

What we collect and why

  • Your email address. It is your account: we use it to sign you in, email you a code when you open saved scenarios, keep your scenarios under it and send you the welcome email.
  • A password. New accounts have no password, and none is emailed. Accounts made before sign-in codes were required had one made and sent in the welcome email; we store it hashed, and it works only on the site’s own login page. The map workspace does not use it.
  • Saved scenarios. The name, description, the region you drew, the model and its settings, the assessment, and each run of the scenario with its inputs and result. Runs are deleted a year after they were made (see how long we keep it); the scenario stays.
  • Assessments you do not save. They are worked out and sent back to your browser; we do not store them.
  • Reports you email. We send the recipients’ addresses, your message and the PDF to our email service, with your email address in the subject, in the message and as the address replies go to. We do not store them; our server log notes your email address and the number of recipients.
  • JSON export. A scenario exported as JSON includes your email address as its owner.
  • Sign-in codes. Opening saved scenarios emails you a six-digit code. We store it only as a keyed hash, with the address, when it was made and used, how many wrong tries there were and the network address the request reached our server from. Codes expire after 10 minutes.
  • Sign-ins. To stop one network from making accounts in bulk, the server counts email sign-ins from each network address for an hour, in its memory. The count is not stored with your account.
  • Server logs. Our server writes your email address to its log when it sends the welcome email, a code or a report you email.

Who can see your data

  • Your saved scenarios are shown only to you, once you have entered a code sent to your email address. Nobody else can list, open, change, run or delete them, even by signing in with your address.
  • The people you email a report to get the PDF, your message, your email address and a link that opens the same region on the map.
  • The people who run the site can see accounts, scenarios and code records in the site’s admin.

Services we use

  • Cloudflare carries every request to the site and to its API (biomassflux-api.kaiaperth.com), so it handles your network address and the pages and data you ask for.
  • Microsoft Azure Communication Services sends our email: the welcome email, sign-in codes and the reports you email. It receives the recipients’ addresses and the content of each email.
  • Mapbox serves the base map, so your browser asks Mapbox for map tiles, styles and fonts, and Mapbox’s map library sends Mapbox its own usage events. Our server asks Mapbox for road distances between the points of a haul, and the PDF report’s map picture is made by Mapbox from the outline of your region and the plant’s position.
  • Google Analytics (Google Analytics 4) counts visits and shows us which pages are used. Your browser loads Google’s analytics script, which sends Google the address of each page you open and sets two first-party cookies, _ga and _ga_CTTTX5GTZJ. We do not send it your email address or your scenarios. Google Analytics 4 does not log or store IP addresses. The data is processed by Google: see how Google uses information from sites that use its services. To opt out, install the Google Analytics opt-out browser add-on or block cookies for this site.
  • We use no advertising trackers and no AI service. The site’s fonts are served from BiomassFlux itself.

Where it is stored

Accounts, scenarios and code records are in a PostgreSQL database on our own server, which reaches the internet through a Cloudflare Tunnel.

How long we keep it

Your account and your saved scenarios, with their settings and saved assessment, stay until you delete them or ask us to.

A clean-up job runs on our server a few minutes after it starts and then every 24 hours. Each time, it deletes:

  • Scenario runs made more than 365 days ago. The scenario they belong to is not deleted.
  • Sign-in code records made more than 365 days ago.
  • Sessions from the site’s own login page and admin, once they have expired.
  • Expired AI-tool connection tokens. If you connect an AI tool to your account through the site’s own login page, it is given tokens tied to your account. The clean-up deletes refresh tokens that have been replaced, revoked or left without an access token; access and ID tokens that have expired (they last 10 hours) and no longer belong to a connection; and connection codes once they expire (after one minute). A connection that has not been used for 365 days stops working, and its tokens are then deleted. A connection in use keeps its current tokens.

Server logs are not kept by date. Each part of the site keeps at most five log files of 10 MB; when they are full, the oldest file is deleted. A part’s logs are also deleted when that part is replaced during an update of the site. How long a log line lasts therefore depends on how busy the site is.

In your browser, a sign-in lasts up to 90 days; each access token lasts 60 minutes.

Your choices and deleting your data

  • Scenarios: you can delete any scenario you saved from your list of scenarios. Its runs go with it.
  • Your account: there is no delete button. Email us and we will delete it, with its scenarios and their runs. Code records and server log lines that carry your address are not removed with it; they are deleted as described under how long we keep it.
  • Signing out removes your sign-in from this browser.

Cookies and browser storage

Google Analytics sets the cookies _ga and _ga_CTTTX5GTZJ (see services we use); apart from those, the site sets no cookies while you use the map. Your sign-in is kept in your browser’s local storage as bf_auth, and whether your screen is a touch screen in session storage as bf_touch. The site’s own login page and its admin set a session cookie and a security (CSRF) cookie when you use them.

Contact

To ask what we hold about you, or to have it deleted, email [email protected].