Data Retention Policy
We keep personal information, including information from children under 13, only as long as reasonably necessary for the purpose it was collected for, and never indefinitely. The Customer that uses TicketHappy (a school, district, company or other organization) controls its data and can delete it sooner at any time.
Last updated: November 6, 2026 · Part of our Privacy Policy
Why we collect data
Only to provide the Service to Customers: creating accounts; submitting, routing and resolving IT, facilities, HR and other requests; tracking Customer-owned devices; sending notifications; securing the Service; and providing support. We never use it for advertising, and we never sell it.
Retention schedule
| Data | Purpose | Why we keep it | When it is deleted |
|---|---|---|---|
| User accounts name, e-mail address, role |
Sign in and route tickets | Needed while the User is active at the Customer | When the Customer asks us to delete the person’s data, when the person deletes their own account, or when the Customer’s organization is deleted (90 days after its subscription ends). Switching a person off under People keeps their account, inactive, until one of those happens |
| IT and facilities tickets and their attachments |
Resolve requests; the Customer’s service history | Customers use history to fix recurring issues and manage devices | When the Customer’s retention period ends (2 years after the ticket is finished unless the Customer chooses otherwise, from 3 months to 10 years), when the Customer deletes it, or 90 days after the subscription ends |
| HR tickets and their attachments |
Resolve employee HR requests | Customers may be legally required to keep some employment records | The HR department’s own retention period, which the Customer sets to match its records schedule (from 3 months to 10 years), or 90 days after the subscription ends |
| Device and asset records | Track Customer-owned devices | Needed while the device is in the Customer’s inventory | When the Customer removes the record, or 90 days after the subscription ends |
| Deleted items “Recently deleted” |
Allow recovery from mistakes | A short safety window | Permanently removed 30 days after deletion |
| In-app notifications The bell: assignments, replies, mentions |
Tell a User what happened on their tickets | Only until it has been seen, then briefly so it can be found again | 30 days after it is read; 90 days after it was sent, read or not. They hold no ticket text, only which ticket and what kind of event. |
| A User’s own notification sound | Play the sound the User chose, only for them | The User’s setting | When the User removes or replaces it, or their account is deleted |
| Help chat records who, when, how many messages,
articles offered, how it ended |
Let the Customer’s administrators review the help chat | Oversight of an AI feature students may use; no chat text is kept in them | 13 months after the chat, or when the person’s data is deleted |
| Reported help chat answer the question, the answer
and the reason |
Let the Customer’s administrators look into a reported answer | Long enough to review the report with the Customer | 90 days after the report |
| Staff AI assistant records who asked, which ticket,
what happened, whether the suggestion was used or the draft saved, cost |
Let the Customer’s administrators review suggested replies and draft help articles | Oversight of an AI feature used on tickets that may be from students; no ticket or draft text is kept in them | 13 months after the request |
| Audit log | Let the Customer see who did what; investigate misuse | Needed for security investigations | 3 years while the organization exists, then deleted. After the organization is deleted, its entries are kept for up to 12 months, detached from it and only to investigate security incidents, then deleted. A deletion record with no personal details is kept as proof that the deletion happened. |
| Backups | Disaster recovery | Restore the Service after a failure | Overwritten within 35 days |
| Bounced-address marks e-mail addresses that rejected our mail |
Stop sending to addresses that bounce | Protects everyone’s e-mail delivery | 180 days after the last bounce, or when the person’s data is deleted |
| Security and operational logs IP address, browser, timestamps, request paths, errors; no ticket contents |
Secure and run the Service | Security investigations and debugging | 12 months after they are written |
| De-identified, aggregated usage data | Improve the Service | Can’t identify a Customer, student or User | May be kept; never re-identified |
Deletion requests
A Customer may ask us to delete specific data, or its whole organization, at any time. We complete it within 30 days, unless the Customer asks us to keep it or the law requires us to, and we confirm in writing on request.
Parents who want their child’s information deleted can contact the School, which controls the account; we help the School respond.
How we delete
Data is permanently removed from production systems, attachment files included, so it can’t reasonably be recovered. It then ages out of backups within 35 days.
The one exception is security audit entries, which can include names and e-mail addresses. They are kept for up to 12 months after an organization is deleted, only to investigate security incidents, and then deleted (see the table above).
Legal holds
If a valid legal obligation requires us to keep specific data longer, we keep only that data, protect it under our security program, and delete it when the obligation ends.
This policy is reviewed at least annually.