Terms

Who may use it

Accounts exist because a Pisteyo operator created them. There is no self-serve registration and no waiting list; an address that was not invited cannot reach anything here. Your account is yours alone: do not share your sign-in, and tell Pisteyo if you think somebody else has it.

You may use Autolace to run and review your own discovery sessions. You may not use it to probe, overload or reverse-engineer the service, to reach an engagement you were not attached to, to feed it anybody else's confidential material without their permission, or to put anything unlawful into a session. Automated access is limited to the one machine door described in the privacy policy, using a token Pisteyo issued.

Who owns what

You own your product idea, your answers, and the brief produced from them. Without qualification: the ideas you describe in a session are yours, the words you say are yours, and the brief that comes out is yours to take anywhere, including to a builder who is not Pisteyo. Nothing becomes ours by having been said here, and nothing in these terms grants us a licence to your idea beyond running the service you are using.

Pisteyo owns the software that ran the conversation: the application, the way it asks, and everything it is built from. Aggregate figures about how the instrument performs, which contain nothing about you or your business, are ours and are what the stopping rule is tuned from.

What the software does, and does not do

Autolace records a conversation and writes a brief. It does not build software, it does not start a build, and it makes no commercial commitment on anybody's behalf. A brief is a description of what you said you need. It is not a quote, not a contract, and not a promise that what it describes can be built, should be built, or will work.

Questions, assumptions and brief prose are generated by a language model from what was said in the session. The list of what a session assumed exists precisely because generated content can be wrong: every decision nobody was asked about is written down where you can see it and correct it. Read the brief before anybody builds from it.

Availability, and what is promised

The service is provided as it is, without warranty of any kind, express or implied, including any implied warranty of merchantability or fitness for a particular purpose. Sessions run against third-party model providers, and when one of them is unavailable the application says so in words rather than pretending otherwise. No uptime is promised on this page; anything Pisteyo has agreed with you in an engagement agreement is what governs there.

Limitation of liability

To the fullest extent the law allows, Pisteyo is not liable for indirect, incidental, special or consequential loss, for lost profits, or for a decision taken on the basis of a brief. Pisteyo's total liability arising out of the service is limited to the amount you paid for it, which for this application is nothing, since it charges nobody. Nothing here limits liability that cannot lawfully be limited, including liability for fraud or for death or personal injury caused by negligence.

Ending it

You may close your account at any time from Settings, then Account. Pisteyo may revoke an account, at which point access ends immediately. In both cases the engagement record stays intact and stays attributed to the session rather than to you, and the privacy policy explains exactly what that means and how engagement content is destroyed when it is asked for.

Changes, and the law that applies

If these terms change, the review date at the top changes with them, and anybody holding an account is told by email before the change takes effect. Continuing to use the service after that is how a change is accepted.

These terms are governed by the law of the place where Pisteyo is established, and the courts of that place settle any dispute arising from them. The engagement agreement Pisteyo signs with a client names that place in full and is the document to read for it; nothing on this page overrides it. If one clause here turns out to be unenforceable, the rest continues to apply.