Service Level Agreement

CanvaScreens is operated by BuiltPOS LLC. Last updated: 3 September 2026

In short

We commit to 99.5% uptime each month for the management console and the device API. If we miss it, you get a service credit against a future invoice.

The thing most people want to know first: your screens keep playing during an outage. The player holds its content locally. If our service is unreachable, a board carries on showing the last content it received. What you lose is the ability to publish changes, sync menus and see live status — not the boards themselves.

1. What this covers

This SLA applies to customers on a paid plan, and to two things:

  • The management console at app.canvascreens.com — where you design, schedule and publish.
  • The device API at api.canvascreens.com — where players collect content, report status and send screenshots.

It does not cover the marketing site, trial accounts, beta features labelled as such, or anything provided free of charge.

2. What an outage does and does not do

The player is built to survive us. It downloads content and caches it on the device, then plays from that cache. It does not stream frames from our server, so a loss of connectivity — ours or yours — does not blank the board.

During an outage of our service:

  • Screens keep displaying the last content they received.
  • Scheduled dayparts still change over, using the device clock.
  • You cannot publish a change or push an emergency broadcast.
  • Menu syncs from Toast or Clover pause and resume afterwards.
  • Last-seen times and screenshots stop updating, so the console will show screens as stale even though they are playing correctly.
This is the honest trade. We would rather a price change wait an hour than a dining room go dark, so the player is deliberately independent.

3. The commitment

99.5% availability per calendar month, measured separately for the console and the device API.

In a 30-day month that allows about three and a half hours of downtime. We are stating a number we can stand behind rather than a number that sounds impressive, and section 6 explains why.

4. How it is measured

An external check runs against both services every 60 seconds and the results are published at status.canvascreens.com. A minute counts as unavailable if the check for that minute fails.

Monthly uptime is (total minutes in the month minus unavailable minutes, minus excluded minutes) divided by (total minutes in the month minus excluded minutes), expressed as a percentage.

Our monitoring is the record of first resort. If your own monitoring disagrees, send us what you have and we will look at both.

5. What does not count as downtime

  • Scheduled maintenance announced at least 48 hours in advance, capped at four hours in any calendar month and scheduled outside US mealtimes wherever possible.
  • Emergency security patching, where waiting would put customer data at risk. We announce it as soon as we can, which is sometimes afterwards.
  • Failures in your own network, internet connection, TVs, streaming devices or local power.
  • Outages at Toast, Clover or Stripe. A Toast outage stops menu syncs; it is not a CanvaScreens outage.
  • Suspension for non-payment or for a breach of the Acceptable Use Policy.
  • Problems caused by your own configuration, or by traffic from your account that exceeds published rate limits.
  • Force majeure: events genuinely outside our control, including a datacentre-wide failure, a regional network failure, or a natural disaster.

6. What we are honest about

CanvaScreens runs on a single server in one datacentre. There is no second region, no automatic failover and no load balancer in front of a warm standby. That is a deliberate choice at our size: it keeps the system simple enough to be understood completely and priced honestly. It also means we will not claim four nines, because we could not deliver them and you would be right not to believe us.

What that means in practice:

  • Recovery point objective: 24 hours. Database backups are taken daily, so in a total-loss scenario the most recent 24 hours of console changes could be lost.
  • Recovery time objective: 24 hours. Recovering from a complete server failure means provisioning new hardware and restoring from backup. That is measured in hours, not minutes.
  • Your screens are the exception. Both of the numbers above concern the service, not the boards. Through a total outage, the screens keep playing.

If your business genuinely needs a redundant, multi-region signage platform with a sub-hour recovery time, tell us before you sign and we will tell you honestly whether we are the right choice.

7. Service credits

Monthly uptimeCredit
99.5% or aboveNone. We met the commitment.
Below 99.5% but at least 99.0%10% of that month's fee
Below 99.0% but at least 95.0%25% of that month's fee
Below 95.0%50% of that month's fee

A credit is calculated against the fee for the affected month. If both the console and the device API miss the commitment in the same month, the credit is not doubled; the larger of the two applies. The total credit for any month will not exceed 50% of that month's fee.

8. How to claim

What to send

Email hello@canvascreens.com with "SLA credit" in the subject, the month you are claiming for, and the dates and times you saw the service unavailable.

When

Within 30 days of the end of the affected month. We will confirm or explain our decision within 30 days of receiving the claim.

What you get

An approved credit is applied to a future invoice. Credits are not paid in cash and are not refundable, and they cannot be transferred between accounts.

Service credits are your sole and exclusive remedy for any failure to meet the availability commitment in this document, as set out in the Terms of Service.

9. Support response targets

PriorityWhat it meansFirst response
P1The console or device API is unreachable, or every screen at a site has stopped receiving content.4 business hours
P2A major function is broken — menu sync failing, a screen stuck on old content, publishing not working.1 business day
P3Everything else: questions, small faults, feature requests.3 business days

Business hours are Monday to Friday, 09:00 to 18:00 US Eastern, excluding US public holidays. These are targets for a first human response, not for a fix; a fix takes as long as the fault takes. Missing a response target does not itself earn a service credit.

10. Changes to this SLA

We may update this document. If a change reduces the commitment or the credits, we will email account administrators at least 30 days before it takes effect, and it will not apply to a month already under way. Improvements apply immediately.