Projects are stored on KinetiRO's server, in a database, under the
account that creates or opens them, and are solved in the browser:
the calculation never runs anywhere else. The browser keeps a copy
so the editor stays fast and a project opens on the next visit
without a round trip; a project follows the account to any browser
or device it signs in from, and clearing the browser's site data
no longer deletes it. The design — the flowsheet, every block and
its parameters, the equipment, the sizing, the layout and the
project's name — is encrypted in the browser before it is stored,
under a passphrase the account holder sets once and enters on each
device; KinetiRO cannot read it unless the user shares it. A
forgotten passphrase loses every design, with no recovery by
KinetiRO, because the same property that keeps the design
unreadable makes it unrecoverable — so export anything that
cannot be lost. Isolation is enforced by the database rather
than by the application — the policy on the table lets an
account read and write only the rows it owns, and every change
to the schema is tested against that policy. Nothing is shared
with any other user's account: no company visibility, no
colleague access.
KinetiRO can see the initial characterisation of the water and the
characterisation of every outlet stream of the design — water,
permeate, concentrate, sludge, and the air and biogas. It cannot
read the design itself — the flowsheet, the equipment and the
sizing. An account may choose, in Settings, to share its designs
with KinetiRO; the choice is off unless the holder turns it on.
It applies to every design of the account. A shared design
can be opened by KinetiRO. Turning the choice on shares the
designs already held, not only those saved afterwards; turning it
off stops sharing them from the browser that holds them, and what
has already been shared cannot be taken back. The initial
characterisation is the influent's parameters, and the outlet
streams are readable once the project has been calculated; with
them, KinetiRO can see the account and its company, when the
project was made and last saved, how many blocks and streams it
has, and how many projects the account holds.
The free plan keeps five projects, counted by the server per
account, so a second device does not reset it. During the beta
every account holds a licence and no limit applies. After the
beta, an account above five keeps and can edit every project and
cannot add one until it is under five or licensed: nothing is
removed when the beta ends — the limit governs what can be added,
not what is kept. Projects that were in a browser before this
build are uploaded the first time the account is reached from that
browser, after the passphrase is set, and are kept, all of them,
whatever their number.
A Team licence does not today put projects in a shared workspace
It administers seats. There is nothing shared to share yet, and no
page on this site may say otherwise until there is. Sealed files are
intended to be how a deliverable moves between people — encrypted to
a named recipient and signed so authorship is provable — and they are
not built yet either. So the truthful description of collaboration
today is that there is not one.
