How a subscription works
Plain-language summary. Last updated September 5, 2026.
This is a summary, not the agreement. It describes how we intend to work with you, in ordinary words, so you can see the shape of it before the first call.
The binding documents are the Master Services Agreement and the Data Processing Addendum. We provide both before you sign anything, and where they differ from this page, they govern. This summary has not yet been through legal review.
What we do
CensusDeck builds administrative automations and integrations inside the systems your community already runs. We do not provide clinical, regulatory, or legal advice.
Your term
- Every plan starts with a three-month initial term.
- After that it runs month to month.
- You can pause after your first month. Paused days extend your term rather than counting toward it.
- You can cancel whenever you like. Cancellation takes effect at the end of the term you are in, not on the day you ask.
We do not say "no contract" or "cancel anytime," because neither would be true. What is true is that there is no lock-in: leaving costs you the queue and the monitoring, not the work.
What you get, and the honest limit on it
- An unlimited request backlog, covering every community you operate.
- A limited number of active builds at a time, set by your plan. We finish each one before starting the next. That constraint is the reason quality and turnaround stay predictable.
- A written spec for every build, which you approve before anyone starts.
- Monitoring of every live automation while you are subscribed. Response times are set by your plan and stated before you sign.
Ownership
- Everything we build is deployed into accounts you control, under your name, on your billing.
- Nothing runs on our infrastructure.
- When your subscription ends, every automation keeps running exactly as it did.
- No exit fees, no export process, nothing to migrate.
Access
Each automation runs on credentials you control and reports its own health outward to us. We can see that something failed without being able to reach into anything. When a repair needs access, you grant it for that repair, we log it, and it ends when the repair does. We hold no standing credentials.
Where we stop
These stay with your team, and this is not a "not yet":
- Clinical judgment of any kind.
- The resident record, care plans, and medication administration.
- Whether an incident is reportable. We track the deadline; your team makes the call.
- Assessments, care-level determination, coding, and claims decisions.
What we do not promise
We make no promises about occupancy, conversion, or hours saved. We do not offer a service level agreement. We say we usually catch a failure before you notice it, and we mean usually.
Protected health information
What reports back to us is a fixed, published list of fields. It never includes a name, a date of birth, a care level, or anything clinical. If a workflow you want touches protected health information, tell us on the first call. It is not a no. It needs a different agreement in place first.
Questions
Ask on the first call, or write to us from the signup form. If something here does not match what you were told, tell us and we will fix the page.