Local well data
The tools read files you select, bundled samples, text passed to the in-page API, and the original LAS you choose to share with Lock dock. Normal LAS loading, plotting and Lock dock do not upload LAS contents or plot settings to a server. With Lock dock off, datasets stay in page memory. With Lock dock on, the original LAS text and filename are kept in this browser’s IndexedDB so all four tools on the same website origin can reuse them across tabs, navigation and later visits. Scripts, result curves and view settings are not stored by Lock dock; save a project to retain them.
Turning Lock dock off or using Remove file deletes the stored active LAS. Turning it off leaves already open local datasets in page memory. Clearing this site’s browser data also removes the stored state; browser cleanup or private-session expiry can remove it. This is local device storage, not an encrypted vault or a backup. Notifications contain only a change marker and do not transmit the well over the network. Sharing is limited to one browser profile and origin; other devices and website addresses do not receive the LAS.
Optional GPT chat
When you send a chat message, its text and up to four recent exchanges from that chat are sent through the site's chat server to OpenAI to generate a response. The assistant receives public documentation about the site's tools. LAS files, plotted curves, well names and plot settings are not automatically attached. Anything you type or paste into a message is sent, so include only the information you intend to share.
The chat history stays in the page's memory. New conversation clears it; reloading, closing or leaving the page discards it. The chat does not connect to your ChatGPT account, subscriptions, saved chats, projects or memory. It explains workflows but cannot see or operate your plots.
The chat server does not maintain a conversation database or log message bodies. API requests use store: false; this does not override OpenAI's applicable data retention and safety policies. See OpenAI API data controls. Hosting providers receive ordinary request information. Replies are generated by AI and should be checked against the actual data and model assumptions.
Early partner enquiries
When you submit the early-partner form, your contact details, selected intent, optional message, server timestamp and a random submission reference are saved in a private database file on a Render-hosted service controlled by Danila Karnaukh. A hash of the enquiry content is also kept to recognize retries. Only the random reference is kept in the form page’s browser history to support safe retries. Danila uses the details to review your enquiry and reply, and can download them through a password-protected page. They remain in the file and any owner backups until the owner deletes them. The form does not attach LAS files, plots, Python scripts or chat history. Render receives ordinary hosting request information. You can contact Danila through the LinkedIn link on the partner page to ask about or request deletion of your enquiry.
Homepage button clicks
The seven large module buttons on the homepage send their button name and a fresh random event reference to the partner service when clicked. The service stores total and daily counts, the last click time for each button, and a counting-start timestamp. Random event references are kept for a 48-hour duplicate-protection window; expired references are removed on the next accepted click. The code sets no analytics cookies, keeps no persistent visitor ID and stores no IP address, user agent, referrer, LAS data, image, script or chat message in the click database. Render receives ordinary request information under its hosting policies. Counts and exports are available only to the owner through the existing password-protected admin page. Aggregate counts remain until the owner deletes them.
Module controls
The seven module pages also count activations of registered buttons and links, plus completed dropdown and toggle changes. Each event contains only a fixed catalog action ID and a fresh random event reference. The application does not send button text, input values, file names, curve names, library source, API keys, passwords or chat contents for these counters. Dynamic buttons referring to user data are grouped by their action. These module counters are separate from the homepage counters; the WellMask counter covers its website manual, not the installed Windows application.
Ordinary website requests
Your browser requests site pages, scripts and images. Some existing pages load fonts from Google Fonts. Hosting and font providers receive ordinary request information under their own policies. Homepage button counting is described above. The bundled synthetic example is public and is loaded only when you open an example link.
Downloads and sharing
PNG output includes plotted values, labels, well/file names and a shortened source fingerprint. JSON settings include a filename, full normalized-text SHA-256, row count, curve references and selected row indices where applicable. Review these before sharing. Downloads are created locally through the browser; the site does not publish them.
Browser extensions, your AI client and screen-sharing tools have their own access and data handling. This page describes the Petrophysics.io code in v30.
Python workspace
Python runs in a local browser Worker. The runtime and scientific packages are downloaded from the pinned Pyodide distribution on cdn.jsdelivr.net; normal application calculations do not upload well data. Script authors can explicitly use network APIs, so running untrusted code may transmit supplied data. Worker isolation is for responsiveness, not a guarantee of script confidentiality.
Python code and computed curves remain in memory until the page closes unless you save them. Save .py downloads code; Save project includes the current code, producing scripts and actual Python result arrays with original row alignment. Project import validates and restores arrays without executing code. Review downloaded project contents before sharing. The optional AI chat does not automatically receive these scripts or curves.
Hosted Python libraries · v24
Hosted library guide: owner-managed Python source, versioned saves, published JSON functions and external Python calls. Only inputs you explicitly submit to a remote function leave the browser; normal LAS tools remain local. Saved source requires owner authentication and stays on the backend disk.