What we collect, and what we never do

Plain-language summary. Last updated September 5, 2026.

This is a summary, not the full policy. It covers the two places data reaches us: the form on this site, and the health signals our automations send back.

The binding documents are the Master Services Agreement and the Data Processing Addendum, provided before you sign. This summary has not yet been through legal review, and a full policy will replace it.

The form on this site

The signup form collects your name, work email, community or operator name, unit count, role, what you are asking about, and anything you choose to write in the free-text box.

Ask us to delete it and we will.

What our automations send back

Every automation we build reports its own health so we can tell when it stops working. That signal is a fixed, published list of fields. It never includes:

The signal says which automation ran, whether it succeeded or failed, when, and where it stopped. It does not carry the contents of the work.

Protected health information

We do not accept protected health information through this form or through our monitoring. If a workflow you want touches PHI, tell us on the first call. It is not a no. It needs a different agreement in place first, and that is better known now than mid-spec.

Where your data lives

Nothing runs on our infrastructure. Every automation we build is deployed into accounts you control, under your name, on your billing. Your operational data stays in your systems. We hold no standing credentials to reach into them; when a repair needs access, you grant it for that repair and it ends when the repair does.

What this page does not yet cover

Being straight with you: a complete policy needs to name our retention periods, our subprocessors, and how to exercise your rights over the data we hold. Those are being written alongside the agreement. If you need them before then, ask and we will tell you what we know today.

Questions

Write to us from the signup form, or ask on the first call.