Privacy

You can use Data Lab without creating an account or entering an email address.

Storage in your browser

Analysis boards are saved automatically in this browser’s local storage. You can export an .medopenlab.json file containing your analysis settings when you need to move to another device. The exported file is saved on your device and does not contain observed data.

Optional encrypted Workspace

You can choose to create an encrypted cloud Workspace. Your browser encrypts the analysis settings with AES-GCM before sending them. The decryption key is included in the URL fragment. A URL fragment is not sent to the server in a normal HTTP request.

The server stores encrypted data, format information such as the encryption method, a revision number and timestamps, and one-way verification values used to check access rights. It does not store the decryption key, raw edit secret, or the analysis board in plaintext. If you lose a link containing the key, you may not be able to restore the cloud copy. Export important analyses to a file as well.

Anyone with an edit link can update or delete the cloud analysis. A read-only link does not allow cloud updates or deletion. When deletion succeeds, the Workspace record is deleted. A separate copy in browser storage remains on that device.

Connections and misuse prevention

Google Cloud services used for Hosting, Functions, and Firestore may process connection information and operational logs as part of providing the service. The application is designed not to intentionally write Workspace request bodies, encrypted data, or access tokens to its logs.

To limit misuse, the API converts connection information into a temporary in-memory identifier and limits the number of actions over a short period. The identifier is not stored with Workspace records and does not remain after the server instance stops. Google's policies also govern Google's standard connection logs.

Contact

Operator: 川崎企画
Contact: contact@medopen.jp