TicketHappy
Guide Sign in Start free trial

Privacy policy

How TicketHappy handles the information organizations and their people put into their help desk, with every commitment schools rely on kept.

Effective date: October 23, 2026

Last updated: November 6, 2026

1. Introduction and scope

TicketHappy (“we,” “us”) provides TicketHappy, an IT, facilities and HR help-desk and ticketing system (the “Service”), to schools, school districts, companies and other organizations (“Customers”). A Customer that is a school, school district or other educational institution, or that lets students use the Service, is a “School”, and every commitment this policy makes to Schools applies to it in full. This Privacy Policy explains how we collect, use, protect, share and delete information in the Service.

This policy covers information about the people a Customer invites or serves: its employees and contractors, the people it supports and, at a School, students, parents and guardians (“Users”), that Customers and Users submit to the Service.

Where a Customer’s written agreement with us (including any Data Privacy Agreement) is stricter than this policy, the agreement controls.

2. Our role: the Customer controls the data

The Customer owns and controls all personal data in the Service, student and employee data included. We process it only on the Customer’s behalf and under its direction. Under state consumer-privacy laws we act as the Customer’s “processor” or “service provider”, for every Customer.

If you’re a School. Everything that follows in this section applies to every School, in full.

FERPA. When we receive personally identifiable information from student education records, we act as a “school official” with a “legitimate educational interest” under the Family Educational Rights and Privacy Act (20 U.S.C. § 1232g; 34 CFR § 99.31(a)(1)(i)(B)). That means we:

  • perform a service the School would otherwise use its own staff for;
  • remain under the School’s direct control for the use and maintenance of education records;
  • use those records only for the purposes the School authorized; and
  • do not re-disclose them except as the School directs or as FERPA permits (34 CFR § 99.33).

COPPA. Where children under 13 use the Service, we rely on the School to provide consent on behalf of parents, as the Federal Trade Commission permits when data is collected solely for the School’s educational purposes and not for any commercial purpose. See Section 5.

State law. Under state student-privacy laws we act as an “operator,” “vendor,” “contractor” or “third-party contractor” (the term varies by state).

3. Information we collect

We collect only what is needed to run a ticketing system. Customers can configure the Service to collect less.

CategoryExamplesSource
Account data Name, work or school email, role, department, job title (if the Customer provides it); staff and team descriptions a Customer writes for ticket routing (skills, systems and places of work, and working days and hours) Customer (an administrator’s invitation, or single sign-on) or the User
Ticket content Ticket subject and description, attachments, screenshots, comments, assigned technician, status Users and Customer staff
Device and asset data Device serial numbers, asset tags, which device is assigned to which User Customer or User
HR ticket data Payroll, benefits, leave, onboarding and accommodation requests; may include sensitive data such as health information, SSNs or bank details if a User submits it (kept in a confidential department; our Terms rule out payment card numbers and health information regulated under HIPAA) Customer employees and HR staff
Technical and log data IP address, browser type, timestamps, login events, audit logs Collected automatically
Branding A Customer’s logo, colours, font, help-centre picture and e-mail look. These are shown publicly on the Customer’s help centre and in the ticket e-mails it sends, so they must not include anything private, such as a photo of a student. Customer administrators
AI assistant records When the automatic first reply, the help chat or a staff helper was used and by whom, on which ticket, which help articles it offered, how it ended, whether a staff member used the suggestion or saved the draft, its cost, and any report Collected automatically, for the Customer’s administrators
Satisfaction ratings and comments The rating (1 to 5) and optional comment a User gives about a resolved request, with the request’s department, category, priority, who resolved it and how long it took; used to measure and improve the Customer’s help desk, shown to the Customer’s staff who can see that request and in their reports, and kept and deleted with the request. The User’s name comes off it if their account is deleted. The User who raised the request, if the Customer has the survey switched on

Student records in tickets (Schools). Ticket content can contain education records (for example, a device ticket that mentions a student’s IEP accommodation). We treat any student information in the Service as education records and “student data” under this policy, whatever field it appears in.

What we do not collect. We do not knowingly collect precise geolocation, biometric identifiers, or data from microphones. The mobile apps use your camera only when you choose to: to scan an asset tag (the image isn’t kept) or to attach a photo to a ticket (stored with that ticket). We do not use third-party advertising cookies or tracking pixels in the Service. We use only cookies strictly necessary for login, security and preferences.

We ask Users not to put Social Security numbers, medical details or other sensitive data in tickets unless the request requires it, and never payment card numbers or health information regulated under HIPAA, which our Terms rule out. A Customer can keep HR and other sensitive matters in a confidential department: only that department’s members can open its tickets — the Customer’s owner included, unless they join it — and each time one of its tickets is opened is recorded in the Customer’s audit log.

4. How we use information, and what we never do

We use information only to provide, secure, support and improve the Service for the Customer, as the Customer has authorized. That includes routing and resolving tickets, authenticating Users, sending ticket notifications, preventing fraud and abuse, troubleshooting, and meeting legal obligations.

We will never:

  • sell or rent personal data, student data and employee data included;
  • use personal data for targeted or behavioral advertising, in the Service or anywhere else;
  • build a profile of anyone for any purpose other than providing the Service to the Customer;
  • use personal data to advertise or market products or services to students, parents or the people a Customer serves, or sell or share it for anyone else’s marketing;
  • disclose personal data except as described in Section 6.

We may still send a Customer’s administrators service and account messages, including news about TicketHappy.

TicketHappy does not use Customer data (student data and employee data included) to train artificial-intelligence or machine-learning models, and does not allow its providers to. The Service sends Customer data to an AI service only in the cases described next (the automatic first reply, the help chat, AI ticket routing and the staff helpers), each only for Customers that have turned it on.

Automatic first reply (AI). A Customer’s administrator can turn on an automatic first reply: when a new ticket arrives, the person who raised it may receive suggestions drawn from the Customer’s own published help articles while they wait for a member of staff. It is off unless the Customer turns it on, and the Customer can turn it off at any time.

  • What is sent. The subject and description of the new ticket, and the Customer’s own published help articles. Never attachments or screenshots, never other people’s tickets, and never anything from a confidential department, whose tickets get no automatic reply.
  • Where it goes. To Anthropic, PBC, in the United States, listed on our subprocessor page, under commercial terms that forbid using the data to train models. Anthropic keeps the text only for the short period its terms set for detecting abuse, then deletes it.
  • Who receives one. The Customer decides whether to turn it on for its whole help desk. When it is on, anyone who raises a ticket from a verified address may receive one: staff, the people the Customer serves (at a School, students and parents) and outside senders. Someone without an account at the Customer receives suggestions only from articles the Customer has published on its public help centre. At a School, for children under 13 the School’s choice rests on its consent on the parent’s behalf, for the School’s educational purposes only, as in Section 5. A ticket that appears to be about a member of staff’s pay, leave or similar personal matter, whoever sends it, gets no automatic reply; the usual acknowledgement goes instead.
  • Built for minors. Because a Customer may let students or other minors raise tickets, every automatic reply, to everyone, is written and checked as if a child will read it: it says it was written by an AI assistant, not a person, and that a member of staff will still respond; it reminds the reader never to share passwords; it only relays the Customer’s own published articles and is held back if it cites none; it never claims to be a person, never asks for personal details and never makes decisions about anyone; and if a ticket suggests someone may be at risk, no automatic reply is sent and the ticket is flagged for a member of staff.
  • Review and reporting. The Customer’s administrators can see every automatic reply, and anyone who receives one can report it to those administrators from the reply itself. We review reports with the Customer and can switch the feature off for a Customer at once.

Help chat (AI). A Customer’s administrator can also turn on a help chat. Signed-in members of the Customer can type a question on the Raise a ticket and help-article pages and get an answer drawn from the Customer’s own published help articles, before or instead of raising a ticket. It is off unless the Customer turns it on, the Customer can turn it off at any time, and it is not offered on the public help centre.

  • What is sent. The question the person types, the earlier messages of the same chat (at most six messages of up to 500 characters each), and the Customer’s own help articles published for its members. Never attachments or screenshots, never tickets, and never anything from a confidential department. A message that appears to state a password, or that contains a Social Security number or a payment card number, is not sent at all and is not kept.
  • Where it goes. To Anthropic, PBC, in the United States, on the same terms as the automatic first reply.
  • Who can use it. Signed-in members of the Customer: staff and, at a School, students. People without an account at the Customer cannot use it.
  • Built for minors. The help chat follows every safeguard listed for the automatic first reply. Before the first message it says it is an AI assistant, not a person, and every answer is labelled as written by one. It answers only from the Customer’s articles, gives no answer when it cannot point to one, and does not help with homework or other topics. If a message suggests someone may be at risk, the chat gives no answer and stops, and the conversation is passed to the Customer’s staff as a flagged ticket, with any password or number taken out. A ticket raised from the chat is also checked for words that suggest someone may be at risk, without sending it to the AI service. The chat says this before anyone types.
  • What we keep. We do not keep chat conversations. We keep a record that a chat took place (who used it, when, on which page, how many messages, which articles were offered and how it ended) for the Customer’s administrators, and delete it after 13 months. The words of a chat are kept only when the person turns the chat into a ticket (they are then part of that ticket), when someone reports an answer (that question and answer and the reason given are kept with the report for 90 days), or when a message suggests someone may be at risk (they go into the flagged ticket).
  • Review and reporting. The Customer’s administrators can see the record of every chat and every reported answer, and the person chatting can report an answer from the chat itself.
  • No new data. The automatic first reply collects no information beyond what Section 3 already lists. The help chat adds only the records described above, and neither adds anything to a student’s record.

AI ticket routing. A Customer’s administrator can turn on AI ticket routing: when a new ticket arrives in a department that isn’t confidential, an AI service chooses which of the Customer’s teams and help-desk staff in the ticket’s own department should handle it, and the ticket is assigned there. It is off unless the Customer turns it on, the Customer can turn it off at any time, and staff can always reassign a ticket. It works only alongside the automatic first reply, in the same request, and a department can be left out.

  • What is sent. The subject and description of the new ticket, and short descriptions the Customer writes of its teams and help-desk staff (their skills, systems and places of work, working days and hours, and how many open tickets they have), labelled by number, not by name. Names of the Customer’s members, e-mail addresses, phone numbers and similar details are removed first. Never attachments or screenshots, never other tickets, and nothing from or about a confidential department.
  • Where it goes. To Anthropic, PBC, in the United States, on the same terms as the automatic first reply. See the automatic first reply.
  • What it decides. Only where a ticket is assigned. It makes no decision about the person who raised it and is not used to evaluate staff. A ticket that appears to be about a member of staff’s pay, leave or similar personal matter, whoever sends it, is not assigned by the AI service and gets no automatic reply; it goes where the Customer has chosen, or is left for an administrator.
  • Built for minors. A ticket that suggests someone may be at risk is not routed by the AI service; it is flagged for staff as described above.
  • What we keep. For each routed ticket, where it was sent, when, and which descriptions it matched, kept with the ticket for the Customer’s administrators.
  • No new data. AI ticket routing adds only the staff and team descriptions and the routing record described above.

AI help for staff. A Customer’s administrator controls four helpers for the Customer’s own help-desk staff: suggested replies, suggested help articles, suggested troubleshooting steps, and draft help articles from solved tickets. All four are on unless the Customer turns them off, and suggested help articles and suggested troubleshooting steps can also be turned off for a single department. The Customer can turn any of them off at any time. Requesters, students and parents included, never use them.

  • What they do. When a member of staff asks, a suggested reply drafts troubleshooting steps for a ticket. The staff member reads it, changes it as they see fit and sends it as their own reply, or discards it. A draft help article rewrites a solved ticket’s fix as a general how-to. The staff member edits it and saves it as a draft, which is published only if someone at the Customer publishes it. Suggested help articles show the member of staff working a ticket up to three of the Customer’s own help articles that may help, each with a one-line reason. Suggested troubleshooting steps show them, on their own department’s tickets, steps taken from their department’s own help articles, each naming the article it came from. Both appear only to that member of staff, on the ticket; nothing is sent to anyone or added to the ticket unless they choose to. Nothing is sent to anyone or published automatically.
  • What is sent. The ticket’s subject and description, its most recent replies and staff notes (limited in length), for a draft help article how it was resolved, and, for a suggested reply or suggested troubleshooting steps, the Customer’s own published help articles that member of staff can read; for suggested help articles, only those articles’ titles and summaries. Before anything is sent we automatically remove the names of the Customer’s members and of people on the ticket, e-mail addresses, phone numbers, ID numbers, room numbers, asset tags and serial numbers, and anything that looks like a password, Social Security number or card number. This removal is automatic and can miss something, which is one reason a person checks every draft. Never attachments or screenshots, never other people’s tickets, and nothing from a confidential department, whose tickets the helpers don’t work on.
  • Where it goes. To Anthropic, PBC, in the United States, listed on our subprocessor page, under commercial terms that forbid using the data to train models. Anthropic keeps the text only for the short period its terms set for detecting abuse, then deletes it.
  • Built for minors. Because a ticket may be from a student or other minor, drafts are written and checked as if a child will read them. They never ask for passwords or personal details, never give health, mental-health or self-harm advice, and contain no links except to the Customer’s own help articles. If a ticket suggests someone may be at risk, no draft is written and the ticket is flagged for a member of staff.
  • What we keep. A record of each request (who asked, which ticket, what happened, whether the suggestion was used or the draft saved, and its cost) for the Customer’s administrators to review. It holds no text from the ticket. A suggestion’s one-line reasons and steps are kept for a day, so opening the ticket again doesn’t ask again, and are then removed from the record. Records are deleted after 13 months. A draft the staff member saves becomes one of the Customer’s own help articles, kept and deleted like any other.
  • No new data. The helpers collect no information beyond what Section 3 already lists, and add nothing to a student’s record.

We may use de-identified or aggregated data that cannot reasonably be linked to a Customer, student or User to improve the Service. We will not try to re-identify it, and we will not share it with third parties except as state law allows.

If we are acquired or merge with another company, personal data may transfer only to a successor that agrees to be bound by this policy and our Customer agreements, and we will notify Customers in advance.

5. Children under 13 (COPPA)

This section applies to Schools. The Service is used by children under 13 only through accounts a School creates or authorizes, for its educational purposes. We do not offer accounts directly to children, and a Customer that is not a School must not let children under 13 use the Service.

  • Consent. The School consents on the parent’s behalf, for the School’s educational purposes only. Schools agree in their contract to obtain this authority and to tell parents about the Service, including by making this policy available.
  • What we collect. The information in Section 3, limited to what a child needs to report or track a technology issue. We do not require a child to disclose more information than reasonably necessary to use the Service.
  • How we use it. Only to provide the Service to the School. Never for advertising or any commercial purpose unrelated to the School.
  • Disclosure. Only to the service providers listed in Section 6, who are bound to protect it. We do not disclose children’s information to third parties for any other purpose.
  • Parent rights. Parents may review their child’s information, ask us to delete it, and refuse further collection. We direct these requests to the School, which controls the account, and help it respond. A parent can also contact us at [email protected].
  • Retention. We keep children’s information only as long as needed to provide the Service to the School, then delete it as described in Section 8. Our written data retention policy is at tickethappy.app/privacy/retention/.
  • Automatic replies and help chat. A child receives an automatic (AI) first reply, or can use the help chat, only if the School has turned that feature on. Then only the child’s own ticket text or chat messages and the School’s published help articles are sent, to the provider in Section 4, solely to help the child for the School’s educational purposes; they are never used to train AI models or for any commercial purpose. Every answer is labelled as written by an AI assistant and follows the safeguards in Section 4.
  • Ticket routing. If the School has turned on AI ticket routing, a child’s ticket text is sent to the same provider solely to assign the ticket to the right staff, with names of the School’s members and contact details removed first; nothing is sent back to the child and it is never used to train AI models. See AI ticket routing.
  • Staff helpers. Staff helpers (suggested replies, suggested help articles, suggested troubleshooting steps and draft help articles) are used only by School staff; a child never receives their output except as a reply a member of staff has read, edited and chosen to send.

Compliance statement. In providing the Service, including its automatic first reply, help chat, AI ticket routing and staff helpers, TicketHappy complies with COPPA, with FERPA as a school official under the School’s direct control, and with state student-privacy laws, including Colorado’s Student Data Transparency and Security Act (C.R.S. § 22-16-101 et seq.). Student data is used solely for the School’s educational purposes, is never sold, used for advertising or used to train artificial-intelligence models, and is handled by subprocessors only under written terms at least as protective as this policy.

Operator contact for COPPA purposes: Kooster Bear LLC, doing business as TicketHappy, 9627 W Chatfield Ave Unit C, Littleton, CO 80128, (970) 281-7919, [email protected].

6. When we share information

We share information only in these cases:

  1. Within the Customer. Ticket data is visible to the Customer’s staff and technicians according to the roles and permissions the Customer sets.
  2. Subprocessors. Vendors that help us run the Service (hosting, email delivery, customer support tools). Each is bound by a written contract at least as protective as this policy, may use data only to serve us, and is prohibited from re-disclosing it. Our current list is at tickethappy.app/privacy/subprocessors/, and we notify Customers at least 30 days before adding a new subprocessor that will handle Customer Data.
  3. At the Customer’s direction. For example, an integration the Customer turns on, such as an SIS, MDM or HRIS connector.
  4. Legal requirements. To comply with a valid subpoena, court order or law. Where FERPA applies, we will notify the School in advance so it can seek protection, unless the order legally prohibits notice. We will disclose only what is required.
  5. Health and safety emergencies. Where disclosure is needed to protect the health or safety of a student or others, consistent with 34 CFR § 99.36.

All data is stored and processed in the United States, with one exception, in transit only: web requests and e-mail sent to TicketHappy pass through our network provider’s global network, which handles each one at the data centre nearest the sender, sometimes outside the United States, and passes it to us straight away over an encrypted connection without storing its content.

7. Security and breach notification

We maintain a written information security program with administrative, technical and physical safeguards appropriate to the sensitivity of personal data, student and employee data included, aligned with the NIST Cybersecurity Framework 2.0. A designated coordinator (our Privacy Officer) owns it and reviews it at least once a year and after any significant change. It includes:

  • encryption of data in transit (HTTPS with TLS 1.2 or newer, including connections to our database) and at rest (AES-256), with keys Google manages and rotates;
  • role-based access inside the Service, each Customer’s data isolated from every other Customer’s by database row-level security, and production access limited to the people who run the Service, each protected by multi-factor authentication;
  • support for single sign-on, passkeys and two-step sign-in, including requiring them for everyone at the Customer;
  • audit logging of sign-ins, changes, exports and downloads of personal, student and HR data, of who opens tickets in confidential departments, and of any access by TicketHappy staff, which the Customer can read at any time;
  • automated vulnerability scanning of our code and dependencies on every change, and of our dependencies every week, pinned and verified dependencies, and critical patches applied within seven days;
  • We monitor the Service continuously and are alerted by e-mail when it can’t be reached, when it returns server errors, when background jobs or the database fail, and when failed sign-ins spike, or when e-mail stops going out.
  • daily encrypted backups with point-in-time recovery, restore-tested every quarter;
  • security and operational logs, which may include IP addresses and account identifiers but not ticket contents, kept for 12 months and then deleted;
  • a documented incident response plan.

Breach notification. If we discover unauthorized access to or acquisition of Customer Data, we will notify the affected Customer without unreasonable delay and no later than 72 hours after confirmation. The notice will describe what happened, the data involved, what we are doing, and a contact person. We will cooperate with the Customer on any notices it must send to Users, parents, employees or regulators, and we will meet any shorter deadline required by state law or our agreement with the Customer.

8. Retention, return and deletion

We keep data only as long as needed to provide the Service or as the Customer directs.

  • During the contract. Customers can delete individual tickets, attachments and accounts at any time, and can set automatic retention rules: finished tickets are deleted after a period the Customer chooses (2 years unless it chooses otherwise), which a department such as HR can set separately. Deleted data is purged from active systems within 30 days. In-app notifications, which hold no ticket text, are deleted 30 days after they are read and 90 days after they are sent, read or not; a User’s own notification sound is deleted when they remove it or their account is deleted. Help chat records, which hold no chat text, are deleted after 13 months; the text of a reported chat answer and the reason given are deleted 90 days after the report. When a person’s data is deleted, their help chat records go too. Staff assistant records, which hold no ticket or draft text, are deleted after 13 months. People can also delete their own account, from their profile. How to delete your account, with or without the app. Their sign-in and personal details are deleted at once, and so are their saved views, saved reports and dashboard layout; a report they shared is removed for the people they shared it with. The Customer keeps the tickets, replies and history they took part in, with their name and e-mail address replaced by “Former member”, and the satisfaction ratings they gave, without their name, and keeps its security audit records as described below. An organization’s only owner must first make someone else an owner.
  • On request. Within 30 days of a Customer’s written request, we delete the specified personal data, unless the Customer asks us to keep it or law requires us to.
  • At contract end. 90 days after termination, we permanently delete the Customer’s data, having returned it in a standard format (CSV or JSON) if requested, and confirm deletion in writing on request. Security audit records, which may include names and email addresses, are kept for up to 12 months after an organization is deleted, only to investigate security incidents, and then deleted. We also keep a record that the deletion happened, with no ticket content or personal details.
  • Backups. Backup copies are overwritten on a rolling basis within 35 days and are not restored except for disaster recovery.

We may keep de-identified data as described in Section 4, and records we are legally required to keep, which remain protected under this policy.

9. Your rights and choices

Because the Customer controls the data, most requests go through the Customer. If you contact us directly, we will forward your request to the Customer within 5 business days and help it respond.

  • At a School: parents and eligible students (FERPA). You may inspect and review education records held in the Service, ask for corrections of inaccurate or misleading information, and ask about disclosures. A student becomes an “eligible student” at 18 or on entering postsecondary education.
  • At a School: parents of children under 13 (COPPA). See Section 5.
  • A Customer’s employees and other Users. You may ask to access, correct or delete your information, subject to the Customer’s records-retention duties and employment law. California residents have additional rights under the CCPA/CPRA, which the Customer, as the business, responds to with our help.
  • Residents of other states. You may have rights under your state’s student-privacy or consumer-privacy laws. See the State Law Addendum.

We will not discriminate against anyone for exercising privacy rights.

10. State Law Addendum

For Schools, the commitments in Sections 4 through 8 are written to meet the strictest common requirements of state student-privacy laws, so they apply in every state. Where a state requires something more, we follow it. Key examples:

StateLawAdditional commitments
California SOPIPA (Bus. & Prof. Code § 22584); Ed. Code § 49073.1; CCPA/CPRA Contract terms on ownership, parent review, and deletion; service-provider terms for employee personal information
Colorado Student Data Transparency and Security Act (C.R.S. § 22-16-101 et seq.) Contract with required terms; public disclosure of data elements collected and their purpose; breach notice to the School; destruction of student data when no longer needed
Connecticut Conn. Gen. Stat. §§ 10-234aa to 10-234dd Contract with required terms; student data owned by the School; breach notice to the School
Illinois SOPPA (105 ILCS 85) Written agreement; breach notice to the School within 30 days; deletion on request; help the School publish its vendor and subprocessor list
New York Education Law § 2-d; 8 NYCRR Part 121 Parents’ Bill of Rights and data security plan in each contract; NIST CSF alignment; breach notice to the School within 7 calendar days
Texas Education Code § 32.151 et seq. SOPIPA-style limits on advertising, profiling and sale; deletion at the School’s request

Most other states have similar student-privacy laws, often modeled on California’s SOPIPA. State comprehensive consumer-privacy laws (for example in Virginia, Colorado, Connecticut and Texas) generally exempt FERPA-covered data, and where they apply we act as the Customer’s processor. All 50 states have data-breach notification laws, which we support as described in Section 7.

State-specific DPA exhibits are available on request at [email protected].

11. Changes and contact

We will notify Customers at least 30 days before any material change to this policy. We will not make a material change to how we use personal data already collected without the Customer’s consent, and, at a School, where COPPA requires it, parental consent obtained through the School. Earlier versions are available on request.

Questions, requests or complaints:

Kooster Bear LLC, doing business as TicketHappy, Attn: Privacy Officer
9627 W Chatfield Ave Unit C, Littleton, CO 80128
(970) 281-7919
[email protected]

Parents and eligible students may also file a FERPA complaint with the U.S. Department of Education’s Student Privacy Policy Office, and anyone may report a COPPA concern to the Federal Trade Commission.

Are you sure?