A vault database entrusted to Filarr
Who can entrust a shared vault database to the hosted gate, what members see, who can take it back, and what an organization can forbid.
In questa pagina
Sezioni della guida
A database of a shared vault can serve an API from the gate hosted by Filarr. Since that database is then no longer end-to-end encrypted, everyone who shares it knows.
Who decides
| who | entrust the database | take it back | see the mark |
|---|---|---|---|
| the vault's owner | yes | yes | yes |
| a vault admin | yes | yes, even without having created the access | yes |
| a member, with write or read access | no | no | yes |
What members see
- Before entrusting, the agreement flags each vault database with "vault database: its members will be told".
- On the database, for everyone, on the web, the desktop and, since version 1.8.0, the mobile app: "API hosted by Filarr · not end-to-end encrypted". A member's bubble adds who entrusted it and when, that the database and the calls to its API are no longer end-to-end encrypted while it stays entrusted, and that only the vault's owner and admins can take the key back.
- At the top of the vault: "1 database entrusted to Filarr".
- When the vault opens, a notice, once per entrusted database: "Camille entrusted a database of this vault to Filarr to serve an API (box "Website"). While it stays entrusted, that database is no longer end-to-end encrypted. Your other databases and notes are not affected."
- In the vault's activity feed: the database entrusted, then taken back.
The mark is read from the server: no setting hides it, and it stays visible while you edit the database.
Take back a database someone else entrusted
The vault's owner or an admin who did not create the access takes the database back from its mark: open the bubble, then Take back the key…, and confirm with Withdraw the database and change its keys.
- The database leaves the hosted gate without stopping it: the gate's other databases are unchanged.
- The hosted service erases this database's key and its copy, and an erasure receipt is kept for it.
- The database's keys change: anything written to it afterwards is end-to-end encrypted again. If the vault key is not available on your device yet, Filarr says so: the keys change as soon as it is, on your device or on the device of the person who created the access.
- That person sees it in their access journal, and the vault's members in its activity feed.
The person who created the access takes the key back from Settings → API access: see The gate hosted by Filarr.
Writing in an entrusted database
What a member writes in an entrusted database is not end-to-end encrypted, like the rest of the database, while it stays entrusted: our servers decrypt it to serve the API. Your other databases, notes and files of the vault are not affected.
An organization can forbid it
An organization's policy can forbid hosted gates. The ban applies to its members and to the databases of its vaults: creation is refused ("Your organization does not allow the hosted box. Filarr Gate on your side is still possible."). Gates already created are not cut off at once: they go to sleep, their key stays managed by our servers for 30 days, then it is erased with a receipt.