Agreements · version 0.1.0 · effective: DRAFT

Service Levels (draft)

DRAFT — requires review by qualified counsel in each jurisdiction. Not in force.

In one line

Our draft targets for uptime, support response, and publishing. They are aims, not guarantees, until we can measure them reliably.

The short version

This short version helps you understand the full text. Read the full text for the complete terms.

  • These are draft targets. They are not contractual commitments yet. (Full text, section 1)
  • Uptime target: 99.5% a month for app.qypu.ai. (Section 2)
  • Support: first reply within 1 working day. (Section 3)
  • Signed posts: published within 15 minutes of their scheduled time, unless a platform is down. (Section 4)
  • We tell you about planned maintenance at least 48 hours in advance. (Section 5)

Full text

Read the full text (about 1 minute)

1. Status

These service levels are draft targets. They become commitments only when your order says so, and after we publish 3 months of measured results.

2. Availability

Target: app.qypu.ai available 99.5% of each calendar month, excluding planned maintenance and outages of third-party platforms.

3. Support

PriorityExampleFirst reply target
UrgentA post you did not sign was published, or a security concern4 working hours
HighYou cannot sign or publish1 working day
NormalQuestions and requests2 working days

Working hours: Monday to Friday, 09:00 to 17:00 [TIME ZONE], excluding public holidays.

4. Publishing

Signed posts are sent to the platform within 15 minutes of the scheduled time. If a platform rejects or delays a post, we tell you and retry where it is safe.

5. Maintenance

We give at least 48 hours' notice of planned maintenance that could affect publishing, on our change log and by email.

6. Service credits

Planned. We will define credits when targets become commitments.

Change log

  • 2026-10-10 · 0.1.0 · First draft.

Open questions for counsel

We publish these while the page is a draft, so you can see what is not settled yet.

  • Keep clearly non-binding until monitoring exists; the "Urgent" example is also an incident under the Incident Policy.

Useful for: Business owners, IT and security reviewers. To save this page as a PDF, use your browser's Print command. Back to the trust centre.