What we run, what we hold, and what we will not claim.
One page that states where things stand today, so nobody has to take a marketing line on faith.
What the parent company holds
The PrairieStack site itself holds no customer records. What arrives here is email sent to the addresses published on this site, plus what the site needs to run: request logs and a release history.
Each product holds its own data under its own terms. A product's records are not pooled into a parent-company warehouse, and PrairieStack does not sell, rent, or broker data.
Where things run
PrairieStack runs its own infrastructure on virtualised hosts it controls, with separate hosts for development and production.
A change is tested, staged on a development slot first, and only then released. An install that fails its own verification is rolled back rather than left half-applied.
Every release carries a build identity — a build number and the commit it was built from — and that identity is readable from the running service.
Published records
These are the documents that describe what we do with data and what we promise. Each one is written to be read, not to be skimmed for a coverage list.
How we tell people about problems
When something affects an account, we tell the affected account holders directly by email, with what happened and what to do. Marketing language is not used to describe an outage.
A public status service is planned and is not published yet.