Is PressureTrend free to use?

Yes. The core tool is currently free for everyone.

Does PressureTrend upload my pressure data or test results?

Nothing is sent to any external server for analysis unless you choose Send Report(s) or Start Session. All file parsing, calculations, chart rendering, and report generation runs in your web browser. Beyond loading the page itself, only aggregated usage analytics are collected by default. Optional Send Report(s) and Start Session send only what you explicitly choose to transmit. Private by default: Imports and analysis stay in your browser until you opt into email or a cloud session. Works well offline: While the page stays open, import, analysis, and PDF export continue without an internet connection. Session persistence: Your work is saved locally. You can refresh the page and continue where you left off. You control your exports: Only you decide when to generate a PDF, email a report, or start a shareable cloud session.

Can I use PressureTrend offline?

While the page stays open, import, analysis, and PDF export continue without an internet connection.

Do I need to install any software?

No installation is required. PressureTrend runs directly in your web browser after you export CSV or Excel from your logger software.

Is my work saved if I refresh the page?

Your work is saved locally. You can refresh the page and continue where you left off.

Which file formats are supported?

Keller: LOGGER_5, LEO Record, and PressureSuite exports (CSV · Excel). Auto-detects native Keller layouts on CSV and Excel. Import setup picks channel and time source when several are present. Crystal nVision: Standard nVision CSV and Excel exports (CSV · Excel). Pressure time series with run metadata on CSV and Excel. Import setup confirms gauge serial and calibration when the file lists several. Wonderware: Trend / historian CSV exports (CSV). Trend exports with timestamp and tag columns. Pressure columns are discovered automatically; import setup confirms the right ones when several are present. External A: UTC historian CSV (Sample Time + tag columns) (CSV). Auto-detects Sample Time plus one or more tag columns with ISO-8601 UTC timestamps. Import setup can keep UTC or convert to a local timezone such as Europe/Oslo. ModScan: Headerless Modbus logger exports (TXT). Auto-detects ModScan lines with a Modbus address and one or more value columns. Import setup lets you mark temperature columns (including several) versus pressure. Other tabular exports: Flexible column fallback (CSV · Excel). When the file is not a known native layout, detection tries flexible time and pressure columns so many logger exports still import without a dedicated parser.

My file is not recognised automatically. What should I do?

Confirm time calibration and test start before analysis. If your file contains multiple time sources, gauges, or pressure channels, pick the correct ones. Standard Keller and nVision exports rarely need extra choices. If your logger export is not recognised well, email contact@pressuretrend.com with your device and export format. We improve parser support for CSV and Excel from real user files without accessing your data.

Can I import multiple files at the same time?

Yes. You can queue and work with up to 50 files per session.

Which Keller and Crystal devices are supported?

Keller: LOGGER_5, LEO Record, and PressureSuite. Pressure time series with run metadata on CSV and Excel. Import setup confirms gauge serial and calibration when the file lists several. When the file is not a known native layout, detection tries flexible time and pressure columns so many logger exports still import without a dedicated parser.

How does the pass/fail logic work?

Passed or Not passed combines pressure change against your criteria %, optional minimum test pressure, and delta trend (all red delta checkpoints can fail the test). Falling hold: pass when drop ≤ criteria %. Rising hold: pass when rise ≤ criteria %. Stable hold: pass when |change| ≤ criteria %. Allow below test pressure is off by default. Pressure anywhere in the window must stay at or above the nominal test pressure. That check is separate from drop %. If it is why the test is not passed, a dialog explains it and lets you turn the check off when your procedure allows a dip. Inflow tests do not use this floor. Start-to-end change vs criteria %; minimum test pressure can fail independently. Direction ↓ / ↑ / — when |change| is below 0.05% of start pressure. Delta colours show flattening vs steepening; red deltas can fail ↓ holds and — holds with net loss.

Can I adjust the pass/fail criteria?

Set start and end of your hold test on the chart; set nominal test pressure, criteria %, and 2–8 delta checkpoints in the test controls beside it. Optional minimum floor pressure can fail the test independently.

How do I export my results?

Review pass/fail, start-to-end change, delta trends, and temperature insight in the workspace. Export a PDF via your browser print dialog or save a JSON project file to continue later.

What are the coloured deltas in the results?

Green: this step does not move against hold direction (no rise on ↓ holds, no fall on ↑ holds) and |Δ| is not steeper than the previous step (flattening or stable rate of change). Red: the interval rose on a falling hold, fell on a rising hold, or the |Δ| magnitude grew compared with the step before. A red delta checkpoint can fail the test on any hold direction.

How is drop % calculated on a hold test?

Passed or Not passed combines pressure change against your criteria %, optional minimum test pressure, and delta trend (all red delta checkpoints can fail the test). Falling hold: pass when drop ≤ criteria %. Rising hold: pass when rise ≤ criteria %. Stable hold: pass when |change| ≤ criteria %. ↑ next to the result means net pressure rose during the window; ↓ means it fell; — means the change was very small. A rising hold is common when the system warms. The app shows rise %, not a misleading negative drop %. Check temperature and your band limits before signing off a warming hold.

Does API 16C allow 5% pressure variation during a hold?

API 16C hydrostatic hold acceptance commonly requires no visible external leakage and that pressure during the hold does not vary by more than 5% or 500 psi, whichever is less. Your job is governed by the approved procedure and the API edition cited on your test pack; verify exact wording there. In PressureTrend, set criteria % in the test controls (for example 5%) and evaluate drop or rise over your hold window; when the dual limit applies, also check the absolute 500 psi cap against start pressure before sign-off.

Is PressureTrend a replacement for CrystalControl or PressureSuite?

No. Those tools export the data from your logger. PressureTrend analyses the export, helps you read pass/fail, and builds a hold-test report.

Where is my data processed?

All file parsing, calculations, chart rendering, and report generation runs in your web browser. Beyond loading the page itself, only aggregated usage analytics are collected by default. Optional Send Report(s) and Start Session send only what you explicitly choose to transmit.

Who can see my pressure test data?

Nothing is sent to any external server for analysis unless you choose Send Report(s) or Start Session. Imports and analysis stay in your browser until you opt into email or a cloud session.

Is PressureTrend suitable for offshore use?

While the page stays open, import, analysis, and PDF export continue without an internet connection. Local browser processing suits restricted connectivity and sensitive environments.

My logger export doesn't work well. Can you help?

We actively improve support for different logger formats. Reach out with your device and export format. We improve parsers from real user files without accessing your data.

Where can I find more help?

Start-to-end change vs criteria %; minimum test pressure can fail independently. Pass/fail, hold direction (↑ ↓ —), delta colours, temperature, and test-pressure checks: the same rules as the result card. See the full guide for hold direction, delta colours, temperature, and test-pressure checks. Logger workflow guides live on the Guides page and in Resources below.

Privacy Policy

PressureTrend ("we", "us", or "our") operates the website https://pressuretrend.com (the "Service"). This Privacy Policy explains how we collect, use, and protect your information when you use our Service.

Last updated: August 14, 2026

Local Processing and Data Minimization

PressureTrend is designed to process pressure log files locally in your browser by default. Imported files and pressure data are not uploaded to our servers for analysis unless you explicitly start an optional cloud session. All calculations, charts, and Download PDF (browser print) happen on your device. If you use Send Report(s), we render the PDF attachment(s) on our server and send them with the email you compose through our email provider so the message can be delivered. If you use Start Session (cloud share), the session payload you choose to upload (including pressure series and report fields) is stored so others can open View or Edit links you create.

Information We Collect

We collect very limited information:

Usage Data: We use Vercel Web Analytics, Google Analytics, and PostHog to collect aggregated, anonymized data such as page views, referrers, general device/browser information, and product events (for example: demo loaded, import completed, PDF exported, report email sent). This does not include the content of your imported files or email addresses. Cloud session pages (/s/view/… and /s/edit/…) are excluded from analytics page paths so capability tokens in those URLs are not sent to analytics providers.
Report email: When you use Send Report(s), the PDF attachment(s), subject, message, and recipient addresses you enter are sent through our email provider (Resend) from no-reply@pressuretrend.com so the message can be delivered. We do not use those addresses for marketing.
Cloud sessions: When you explicitly start a cloud session, we store the session payload you upload (pressure trends, report text, settings, and compressed logos if present) so View and Edit links work. Access is via secret links and optional PINs you set. We do not create cloud sessions automatically.
Error Reports: PostHog collects anonymous error reports (JavaScript exceptions) so we can find and fix bugs. These never include your pressure data or file contents.
Session Data: We use your browser’s localStorage to save your current private session (settings, report text, and optionally pressure data) so you can resume work later. Private session data stays on your device.
Technical Data: Standard web server logs may be collected for security and operational purposes.

Cookies and Local Storage

We do not use cookies. Our analytics run in cookie-free mode: Vercel Web Analytics is cookieless by design, Google Analytics runs with storage consent denied (cookieless pings only), and PostHog keeps its state in browser localStorage instead of cookies.

We use browser localStorage to persist your private session data and analytics state. You can clear this data at any time by clearing your browser’s site data for pressuretrend.com.

Data Retention

Aggregated analytics data is retained according to the retention policies of our analytics providers (Vercel, Google, and PostHog), typically up to 24 months.
Private session data stored in localStorage remains until you delete it or clear your browser data.
Cloud sessions are deleted after 30 days without access (opening a valid View or Edit link resets that timer), or sooner if an editor destroys the session. Expired sessions are removed by scheduled cleanup.
We do not store your pressure test files on our servers unless you start a cloud session. Rendered PDF files are not stored as part of cloud sessions.

International Data Transfers

Some third-party services we use (including Vercel, Google, PostHog, and, when cloud sessions are enabled, our database provider) may process data outside the European Economic Area (EEA). Where personal data is transferred outside the EEA, we rely on appropriate safeguards such as Standard Contractual Clauses approved by the European Commission.

Legal Basis for Processing (GDPR)

We process data based on:

Our legitimate interest in operating and improving the Service.
Your consent (where applicable for analytics and when you acknowledge starting a cloud session).

Your Rights

If you are located in the EEA or United Kingdom, you have rights under the GDPR, including the right to access, correct, delete, or restrict processing of your personal data.

For private browser data, most requests can be resolved by clearing your browser data for this site. For a cloud session you created, use the Edit link to destroy the session, or contact us at privacy@pressuretrend.com. We aim to respond within one month.

Children’s Privacy

Our Service is not directed to children under 16. We do not knowingly collect personal data from children.

Security

We implement reasonable technical and organizational measures to protect our systems, including hashed session secrets and optional PINs for cloud links. However, since core analysis occurs in your browser, the security of your data also depends on the security of your own device and browser. Treat Edit links like passwords.

Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new "Last updated" date.

Contact Us

If you have any questions about this Privacy Policy, please contact us at:

privacy@pressuretrend.com