Effective Date: 11/05/2026
Rock Physics Templates (RPTs) is an interactive web app for rock physics analysis, data visualization, and machine learning workflows. This policy describes, as accurately as we can, what data the app processes, what is stored on our server, for how long, and how it is removed.
| Data | When it is stored | How long / how it is removed |
|---|---|---|
| Table data you work with (loaded, pasted, or computed values) | Sent to the server with each request and processed in memory only. | Discarded when the request finishes. It is not written to a database or file. The table lives in your browser and is lost when you refresh or close the page. |
| Uploaded LAS files | Written to a uniquely named temporary file on the server so it can be parsed. | Deleted immediately after parsing, within the same request. |
| Plots and statistics images (QC plot, pairplot, heatmap, statistics, missing-data QC) | Generated in server memory and returned directly to your browser. | Not saved on the server and not available at any public URL. They are visible only in your own browser tab. |
| Trained neural-network models (model weights, normalization values, and metadata such as feature/target column names and epochs) | Saved when you train a model, so you can apply it later for prediction. |
Guests / visitors without an account: stored in a private folder tied to your browser session. It is deleted when you log out, and automatically after about 24 hours without new training or prediction. Registered users: stored in your account's folder. Only your latest model is kept: each new training run replaces the previous one. It is kept until you train again or ask us to delete it. Models are only shown to and used for the user or session that created them. |
| Account details (username and password) | When you sign up. | The username and a salted hash of your password are stored. We never store your password in plain text. They are kept until you ask us to delete your account. |
| Contact / "Need Help" form (name, email, community, message) | When you submit the form. | Stored on the server so we can reply. They are kept only as long as needed to handle your request and are deleted when you ask. |
| Session cookie | Set by the app to keep you logged in, to keep your guest session's models separate from other users, and to remember a verified purchase for a short time. If you start a checkout from a suggestion inside the tool, it also remembers which tool it came from (for example "QC plot") until the purchase completes. | A browser-session cookie that is cleared when you log out or close your browser. It does not track you across other websites. |
| Technical logs | The app records simple events (for example "Heatmap displayed") without your data values. Our hosting provider may also keep standard web server logs, such as IP address, time, and requested URL. | Kept for troubleshooting and security, and rotated or deleted under the hosting provider's normal retention. |
| Anonymous usage events | When you view a page or use key features (load a dataset, run a QC plot or neural network, view or buy a premium download), your browser sends the event name and the page path to our own server. A few fixed values may be included, such as the name of a built-in example dataset, the plot type, the premium item, or where a premium suggestion was shown (for example "after a QC plot"). | Written to a log file on our server with the time of the event. It does not include your IP address, browser details, account or session identifier, cookies, uploaded file names, or any table values, so events cannot be linked to you or to each other. Kept for up to 12 months, then deleted. |
Premium downloads are paid through Stripe. Card details are entered on Stripe's checkout page and are processed by Stripe under Stripe's privacy policy. We do not receive or store your card number. Prices are set by our server; they are not taken from the browser.
We measure how the app is used with anonymous event counts recorded on our own server (described in the table above). No tracking cookies are set for this.
We do not use third-party analytics services, and we do not use advertising trackers.
We do not sell or rent your data, and we do not share it except with the service providers listed above as needed to run the app.
We take reasonable steps to protect stored data. These include hashed passwords, per-user and per-session isolation of trained models, and not keeping plots or uploaded files. No online service can guarantee absolute security.
We may update this Privacy Policy when the app changes or when legal requirements change. Updates will be posted on this page with a revised Effective Date.
Thank you for using Rock Physics Templates (RPTs) for your rock physics analysis!