Your tenant holds it all.
Celest receives no ticket data.

What the Package touches, and where it stays

The Package is client-side code that runs in your Microsoft 365 tenant as the signed-in user, with that user’s existing SharePoint permissions. It reads and writes SharePoint lists your organization owns: tickets, proposals, approvals, decisions, run records and your routing vocabulary. It also remembers the last site URL it used in the operator’s own browser storage, and nothing else.

It shows the queue and one ticket at a time to the operator and to Microsoft 365 Copilot, records every decision, approved or denied, as a run row naming the operator, and writes the approved fields to the ticket only after the operator approves in the card. None of it reaches Celest.

What Celest receives

Only the email you send to [email protected]. If your organization acquires the Package through Microsoft’s marketplace, Microsoft may report the acquisition to Celest (such as a tenant or organization identifier, the package version, the acquisition state and time and, where the channel supplies it, the acquiring account’s identifier). Celest operates no runtime, API, MCP server, database or inference service for the Package, collects no telemetry from it, and engages no subprocessor for ticket data.

Microsoft 365 Copilot

Copilot’s reading of the queue and the proposals it writes are Microsoft’s processing under your Microsoft agreements, not Celest’s. The Package hands Copilot the queue as it loads it: one summary line for every ticket in the tickets list (id, title, status, priority, department, category, queue, assignee, requester name, affected users and exception), the routing vocabulary (including assignee names and email addresses), the description of the ticket the operator opens, and the proposal under review with its receipt.

What setup creates in your tenant

Each item below is created only when you click for it in the setup card, and each is yours to remove; the uninstall page walks through it.

• Three lists: Celest Helpdesk Tickets, Celest Triage Runs and Celest Helpdesk Configuration, with their columns.
• One “Default routing” item in the configuration list, written when that list is empty.
• The product terms acceptance, recorded on that configuration item: the accepted version, the administrator’s account and the time.
• Eight sample tickets with fictional people, only if you ask for them.
• The site agent file, Celest Helpdesk.agent, in the site’s Site Assets library, grounded on the tickets and configuration lists.
• A “Helpdesk queue” and “Triage ticket” command on the tickets list, registered as a list custom action.
• The site’s main-agent setting, set with the agent install when the site had no main agent.

Retention and deletion

The Package stores nothing with Celest. Ticket, proposal and run records live in your SharePoint lists under your own retention settings; deleting the lists deletes them, and removing the Package does not. Support mail is kept as long as reasonably necessary to answer the request and for ordinary business records, then deleted. Website analytics are described in the site privacy notice.

Providers

Microsoft hosts SharePoint and Microsoft 365 Copilot under your agreements with Microsoft. Celest’s only providers touch this website and the support mailbox: Cloudflare serves the website and the sandbox, and support mail is handled in Celest’s own Microsoft 365 tenant. The site privacy notice describes the website’s providers.

The sandbox on this site

The try page runs the Package’s cards on sample data held in your browser’s storage on the sandbox origin. The sandbox server answers the page’s tool calls, stores no sample data and sets no cookies; Cloudflare hosts it and keeps ordinary request logs for a few days. The sandbox scripts its proposals; no model key is deployed on it, and the developer bench on the same origin is not linked from this site. It is not part of the Package.

Security

The Package uses the identity, permissions and security controls of your tenant. It stores no secrets, calls no third party and adds no service of its own. The security page describes where it runs; report a concern to [email protected] with the minimum context needed to route it.

Questions and requests

Write to [email protected] about this notice or about support mail. Requests about product data go to your own organization, which controls the lists. Do not email ticket contents, secrets or unnecessary personal data. Celest versions this notice, records each version’s effective date on this page, and keeps every version at its own address.