Oarbank

Where your data lives

The coordinator keeps its database, console accounts, module store, results and logs on the computer you run it on. Each node keeps its keys, caches and job folders on itself. Removing Oarbank and its data folders removes them.

Nodes talk only to your coordinator, over mutual TLS on your network. They send it what it needs to schedule work: the computer’s hardware facts, its load, host protection’s decisions and the jobs’ results. A coordinator also announces itself on the local network so that nodes can find it; you can turn that off.

When Oarbank uses the internet

Oarbank itself never calls a Codonic server. It reaches other places only where you point it: the network hosts and container images you approved for a module, used from inside its sandbox; the origins of datasets you register; a rescue location you name for moving the coordinator; and the notification server you set, if you turn notifications on.

Updates reach your nodes through your own coordinator, after you upload and sign them.

Your rights

Privacy law in the European Economic Area, the United Kingdom, California and elsewhere gives you rights over personal data a company holds about you: to see it, correct it, delete it, take it elsewhere, and object to its use. It also gives you the right to complain to your national data protection authority.

We hold no personal data about you through Oarbank, so there is nothing for us to hand over, correct or erase. What you create in the app stays under your control. We do not sell personal information.

If you have written to us by email, that correspondence is the one thing we do hold. Ask at dev@codonic.dev and we will delete it.

Changes to this policy

If this policy changes, the new version will be posted at this same address with a new “last updated” date above. The address does not change.

Contact

Codonic
dev@codonic.dev

Related: Oarbank · all privacy policies · support