Contact

Email works and we read it. There is no contact form here on purpose — a form is state we would have to keep working, and an address that works beats one that might not.

Support address: [email protected]

Reporting a problem with a reading

If a report or a session gave you something that does not look right, include the three things that let us reproduce it:

• The loop tag (for example FIC-101).
• The control system platform (for example DeltaV or Ovation).
• Roughly when it happened, and what you expected to see instead.

A screenshot of the report helps, but the tag and platform are the part we cannot guess.

Response time

We aim to reply within two working days. If a reading looks wrong, say so in the subject line and we will treat it as a priority.

Refund claims

Refunds are handled by the session itself — see how refunds work. A mechanical or safety result inside the first two iterations is refunded automatically; after that it is claimed with a button on the session page. If you believe a refund was missed, write to [email protected] with the loop tag, and we will look at the ledger.

Security reports

If you have found a security problem, do not include sensitive detail in a public post. Write to [email protected] with "Security report" in the subject. We treat those separately from ordinary support and will acknowledge within one working day.