TicketHappy
Guide Sign in Start free trial

Terms of Service

The agreement between TicketHappy and the school, district, company or other organization that signs up for it.

Effective date: November 6, 2026 · Version 2026-11-06

These Terms of Service (“Terms”) are an agreement between Kooster Bear LLC, doing business as TicketHappy (“TicketHappy,” “we,” “us”) and the school, district, company or other organization that signs up for TicketHappy (“Customer,” “you”). The person who accepts these Terms confirms that they have authority to bind the Customer.

1. The Service

1.1 TicketHappy is a hosted help-desk service: ticketing by web and email, service-level targets, a knowledge base, equipment inventory, reports, and related features, available at tickethappy.app and through our apps (the “Service”).

1.2 We may improve and change the Service. We won't materially reduce the core functionality of a paid plan during a paid billing period.

1.3 Features marked “beta” or “preview” are provided as-is and may change or be withdrawn.

2. Accounts and Users

2.1 The Customer creates a workspace and invites its staff, students and others (“Users”) and gives them roles. The Customer is responsible for its Users' activity and for keeping sign-in credentials secure, including turning on single sign-on or two-step sign-in where it wants them.

2.2 Students and children. If the Customer lets students, including children under 13, use the Service, the Customer: (a) does so only for its educational purposes; (b) gives any consent needed under the Children's Online Privacy Protection Act (COPPA) on parents' behalf, where the law allows a school to do so; and (c) tells parents about the Service as the law requires. We don't offer accounts directly to children. A Customer that is not a school or other educational institution must not let children under 13 use the Service.

2.3 Tell us promptly at [email protected] if you suspect unauthorized access to your workspace.

3. Customer Data

3.1 You own your data. “Customer Data” means everything the Customer and its Users put into the Service, including tickets, attachments, contacts and inventory records. As between the parties, the Customer owns all Customer Data.

3.2 Our limited license. You give us permission to host, copy, process, transmit and display Customer Data only as needed to provide, secure and support the Service, and as described in our Privacy Policy and any Data Privacy Agreement.

3.3 No ads, no selling. We do not sell Customer Data, use it for advertising, or use personal data to build profiles for any purpose other than providing the Service.

3.4 Privacy Policy and DPA. Our Privacy Policy is part of these Terms. If the Customer and TicketHappy sign a Data Privacy Agreement, such as the Student Data Privacy Consortium National DPA, the DPA controls over these Terms for student data.

3.5 Retention you control. The Customer sets how long finished tickets are kept, by organization and by department. When a period ends, those tickets and their attachments are permanently deleted. Deleted items go to a “Recently deleted” area for 30 days, then are permanently removed.

3.6 Export. The workspace owner can download a full export (JSON, CSV and attachment files) at any time, including while the workspace is read-only.

3.7 Aggregated data. We may use de-identified, aggregated information that can't reasonably identify the Customer, any User or any student, such as total ticket volumes, to run and improve the Service.

3.8 Automatic replies (AI). The Customer chooses whether to turn on the automatic first reply for its help desk; when it is on, any User or sender who raises a ticket may receive one. Automatic replies are suggestions drawn from the Customer’s own help articles, are labelled as written by an AI assistant for every recipient, students included, and are not advice; a person remains responsible for every ticket. The Customer is responsible for deciding whether the feature is appropriate for its Users, including students, and for the consents in Section 2.2. We may hold back or stop automatic replies at any time, and we do not warrant their accuracy. Ticket text sent to our AI provider is handled as the Privacy Policy describes and is never used to train models.

4. Acceptable use

The Customer and its Users will not:

  1. use the Service for anything unlawful, or to store content they have no right to store;
  2. upload malware, or try to break into, probe, overload or get around the security or usage limits of the Service or other customers' data;
  3. resell or sublicense the Service, or use it to build a competing product;
  4. copy, decompile or reverse-engineer the Service except where the law allows it;
  5. put into the Service, in a ticket or anywhere else: (a) full payment card numbers or card security codes; or (b) health information regulated under HIPAA, because the Service isn't designed for it and we don't sign Business Associate Agreements, so a Customer that is a HIPAA covered entity or business associate must keep such information out of the Service. Social Security numbers, bank account numbers and other sensitive personal data belong in a ticket only where a request truly needs them, and then in a confidential department restricted to authorized staff. If we find data that (a) or (b) rules out in the Service, we may remove it and will tell the Customer;
  6. use the branding settings to impersonate another person or organization, to ask anyone for a password or other credentials, or to track who opens or reads e-mail;

We may suspend access that threatens the Service's security or breaks this section. We'll tell the Customer promptly and restore access once the problem is fixed.

Branding. The Customer is responsible for its logo, colours, pictures and e-mail templates, and for having the right to use them. Ticket e-mails sent in the Customer's look may carry its branding and support information only, never promotional or marketing content such as newsletters or fundraising. We may switch a custom e-mail template back to TicketHappy's standard look at any time, without notice, if we believe it breaks this section or puts our ability to deliver e-mail at risk.

Fair use. Each organization's subscription includes up to 25 GB of stored files (attachments, images and sounds) and the e-mail that ordinary help-desk work sends. If an organization goes well beyond that, we'll contact the Customer to agree a way forward, such as removing old files or an added charge, before changing anything.

5. Plans, trial and payment

5.1 Price and seats. The Service is priced per agent (technician) seat: owners, administrators, managers and agents each use a seat; requesters are free. There's no minimum: a subscription can be for a single seat. It's billed monthly, or yearly at a discount. Current prices are on the Billing page and at tickethappy.app.

5.2 Free trial. A new organization starts a 30-day free trial after adding a payment card through our payment processor, Stripe. At the end of the trial, the card is charged automatically for the seats chosen unless the Customer cancels before then. A free pilot we agree with a Customer lasts 30 days unless we agree otherwise in writing.

5.3 Automatic renewal. Subscriptions renew automatically at the end of each month or year until cancelled. The Customer can cancel at any time from the Billing page. Cancellation takes effect at the end of the current billing period.

5.4 Changing seats. The Customer can add or remove seats from the Billing page (not below 1, or below the seats in use). Changes apply to the existing subscription and are prorated.

5.5 Failed payments.

  • If the first payment after the trial fails, the workspace becomes read-only right away until the invoice is paid.
  • If a later renewal payment fails, the Customer has 14 days to pay before the workspace becomes read-only.
  • Read-only means Users can view and export data but can't create or change anything, and emailed tickets are refused. Paying the outstanding invoice restores full access.

5.6 Refunds. If the Customer cancels within 30 days of a payment, we refund that payment in full. After 30 days, a yearly subscription that's cancelled is refunded for the whole months left in its year; monthly payments aren't refunded after 30 days. We may also refund where the law requires it, or where we decide to for a particular Customer.

5.7 Taxes. Prices don't include taxes. The Customer pays any sales, use or similar taxes that apply, except taxes on our income. Tax-exempt Customers (for example, public schools, districts and nonprofit schools) should enter their exemption number on the Billing page and send their exemption certificate to [email protected]; we stop charging tax once we've checked the certificate, and while it remains valid.

5.8 Invoices and purchase orders. If we agree to invoice a Customer (for example, an annual plan paid by purchase order), payment is due within 30 days of the invoice date. Terms printed on a purchase order don't change these Terms.

5.9 Price changes. We'll give at least 30 days' notice by email before a price increase applies to an existing subscription.

5.10 Founding price. The first 100 Customers (each an organization, not an individual User) to pay their first invoice are founding Customers; complimentary accounts don't count. For two years from the date the founding Customer's account was created, we won't raise its price above $10 per agent per month on monthly billing or $100 per agent per year on yearly billing, at whichever billing interval it chooses, including for agent seats it adds during that time; 5.9 doesn't let us raise a founding Customer's price during those two years. Taxes aren't part of this promise. The founding price lasts only while the subscription stays active: if the subscription is cancelled or ends, the founding price ends with it and isn't restored. A late payment that's made before the subscription is cancelled doesn't end it. After the two years, 5.9 applies.

6. Ending a subscription and deletion of data

6.1 When a subscription is cancelled or remains unpaid, the workspace becomes read-only and shows the date its data will be deleted.

6.2 90 days after the subscription lapses, and at least 7 days after we email the workspace owner and administrators a warning, we permanently delete the organization's data, including attachments. People who belong to no other organization lose their accounts too. Two exceptions: (a) security audit records, which may include names and email addresses, are kept for up to 12 months after deletion, only to investigate security incidents, and then deleted; and (b) we keep a record that the deletion happened (organization name, dates and counts, with no ticket content or personal details).

6.3 Paying again before that date stops the deletion. Export your data before the deletion date. It can't be recovered afterwards.

6.4 A Customer may also ask us in writing to delete its organization sooner. We confirm the deletion in writing when it's done.

6.5 Sections 3.1, 3.7, 7, 8, 9, 10, 11 and 13 survive the end of these Terms.

7. Intellectual property and feedback

7.1 TicketHappy owns the Service, including its software, design, documentation and the TicketHappy name and logo. Apart from the right to use the Service under these Terms, nothing here transfers any of our rights to the Customer.

7.2 If the Customer sends suggestions or feedback, we may use them freely without any obligation to the Customer.

8. Confidentiality

Each party will protect the other's non-public information shared in connection with the Service, using at least reasonable care, and use it only for purposes of these Terms. Customer Data is also protected under Section 3 and the Privacy Policy. This doesn't apply to information that is public, already known to the recipient, independently developed, or received lawfully from someone else. Either party may disclose information when legally required to, after giving notice where the law allows.

9. Warranties and disclaimers

9.1 We'll provide the Service with reasonable skill and care, using industry-standard safeguards as described in the Privacy Policy.

9.2 EXCEPT AS STATED IN THESE TERMS, THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE EXTENT THE LAW ALLOWS, WE DISCLAIM ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. WE DON'T PROMISE THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE. The Customer is responsible for keeping any records it is legally required to keep, including by exporting them before deletion.

10. Limitation of liability

10.1 TO THE EXTENT THE LAW ALLOWS, NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE OR DATA, EVEN IF IT WAS WARNED THEY WERE POSSIBLE.

10.2 EACH PARTY'S TOTAL LIABILITY ARISING OUT OF THESE TERMS IS LIMITED TO THE AMOUNT THE CUSTOMER PAID TO TICKETHAPPY IN THE 12 MONTHS BEFORE THE EVENT THAT GAVE RISE TO THE CLAIM.

10.3 These limits don't apply to the Customer's payment obligations, to a party's breach of Section 4, or to liability that can't legally be limited.

11. Indemnification

11.1 By TicketHappy. We'll defend the Customer against a third-party claim that the Service, as we provide it, infringes that party's U.S. intellectual property rights, and pay the resulting damages, costs or settlement. We may instead change the Service so it doesn't infringe, get a license, or end the subscription and refund prepaid fees for the unused period. This doesn't cover claims caused by Customer Data or by combining the Service with things we didn't provide.

11.2 By Customer. To the extent its law allows (see Section 12), the Customer will defend TicketHappy against third-party claims arising from Customer Data or from the Customer's breach of Section 4.

11.3 The party being defended must give prompt notice, give reasonable help, and let the defending party control the defense and settlement.

12. Public schools and government customers

If the Customer is a public school, district or other government body:

  1. Any obligation that its state's law doesn't allow it to accept (for example, indemnifying us, agreeing to another state's law or courts, or paying interest) applies only to the extent that law allows.
  2. If the money for a later fiscal period isn't appropriated, the Customer may end its subscription at the end of the funded period by giving written notice.
  3. We'll respond to public-records requests as the Customer's law requires, and we'll ask the Customer to protect our confidential information where the law allows.

13. General

13.1 Governing law and venue. Colorado law governs these Terms, without regard to its conflict-of-law rules. Disputes go to the state or federal courts in Jefferson County, Colorado, except as Section 12 provides.

13.2 Changes to these Terms. We'll post updated Terms and give at least 30 days' notice by email or in the Service before a material change takes effect. If the Customer keeps using the Service after that, the change applies to it. If the Customer doesn't agree, it may cancel before the change takes effect.

13.3 Assignment. Neither party may assign these Terms without the other's consent, except to a successor in a merger or sale of substantially all its business or assets. Any successor of ours must honor our privacy commitments.

13.4 Force majeure. Neither party is liable for delays caused by events beyond its reasonable control, except for payment obligations.

13.5 Notices. We send notices to the workspace owner's email. Notices to us go to [email protected] and 9627 W Chatfield Ave Unit C, Littleton, CO 80128.

13.6 Entire agreement. These Terms, the Privacy Policy, any signed order form and any signed DPA are the entire agreement. If they conflict, the order of precedence is: (1) a signed DPA, for the data it covers; (2) a signed order form; (3) these Terms; (4) the Privacy Policy.

13.7 Other terms. If a part of these Terms is unenforceable, the rest stays in effect. Failing to enforce a term isn't a waiver of it. The parties are independent contractors. There are no third-party beneficiaries.

Contact: Kooster Bear LLC, doing business as TicketHappy, 9627 W Chatfield Ave Unit C, Littleton, CO 80128, [email protected].

Are you sure?