This policy describes what information Crossover Central ("the Service", "we") collects when you use the platform — including the Outlook Web Add-in, the admin console, and the standalone management board — and how we handle it.
What we collect
Identity from Microsoft Entra ID
When you sign in, we receive your Object ID (OID), display name, email, user principal name, tenant ID, and your group memberships from Microsoft Entra ID via Microsoft Graph. We use these to authenticate you, determine your role (team member, supervisor, manager, admin), and route your reports to the correct department and shift. We do not store passwords; sign-in is delegated to Microsoft.
Shift report content
The data you enter into shift report templates is stored in your facility's database — a SQL Server or SQLite instance you configure during setup and run on your own infrastructure. Reports include the field values you submit, attached files, the audit trail of edits and reviews, and metadata such as the shift date, template used, and who submitted/reviewed/approved.
Operational telemetry
The application logs request paths, status codes, and error messages to local files on the server for the operator's debugging use. We do not transmit these logs to Brantner Solutions unless you explicitly send them to us for support.
What we do not collect
- Email content from your mailbox. The Outlook Add-in declares the
ReadItempermission, which lets it know which item the task pane was opened from but does not allow it to read the message body, send mail on your behalf, or modify your mailbox. - Personal Microsoft account data. The add-in is restricted to work accounts.
- Behavioral or marketing tracking. There are no third-party analytics, advertising trackers, or session recordings.
How we use it
- To run the product. Identity to authenticate you; report content to render summaries, dashboards, and the trends board.
- To send shift summary emails. When an admin approves and sends a summary, the recipient list configured for that template receives a branded email with the report content. Email is sent through the SMTP server you configure during setup.
- To support you. If you contact support, we may ask you to share log excerpts or screenshots. We never read these without your action.
Where data is stored
Crossover Central is self-hosted: your data lives entirely on your own infrastructure. The installer runs as a Windows service on a server you control; the database is on your SQL Server or local SQLite file; attachments are written to a directory you configure. Brantner Solutions operates no production copy of the Service and has no access to this data.
Who can see your data
- Authenticated users in your tenant, scoped to the role assigned to them by your Entra group configuration. Team members see their own department's templates and reports; supervisors and admins see broader.
- Recipients of summary emails you explicitly send.
- Not Brantner Solutions. Because the Service is self-hosted, we have no access to your database or reports; support uses only the log excerpts or screenshots you choose to send us.
Data retention
Reports, history rows, and email summaries persist for the lifetime of your installation. There is no automatic purging. Because the Service is self-hosted, you control retention and deletion directly through your own database administration.
Sub-processors
Crossover Central is self-hosted, so it relies only on the services you connect it to. Depending on your configuration, these may include:
- Microsoft Entra ID + Microsoft Graph — identity and group lookups (required for sign-in).
- Google Fonts — the admin console and Outlook add-in load the Inter typeface from
fonts.googleapis.com/fonts.gstatic.com. Google logs IP addresses of font requests for abuse prevention; no user identifiers or page content are sent. - The SMTP provider you configure — for sending summary emails. This is commonly your own Exchange or Microsoft 365 mailbox.
Your rights
If you are an end user in a customer's tenant, your rights are governed by your employer's data policies. If you are a customer (the entity that purchased the license), you hold your own data and may copy, correct, or delete it at any time directly through your own database administration.
Security
All connections are HTTPS-only. Authentication is delegated to Microsoft Entra ID; we never see or store passwords. Tokens are short-lived (one hour) and validated server-side on every request. The API requires a valid bearer token for all data endpoints; the only anonymous endpoints are the standalone management board's read-only feeds (board configuration and KPI summaries).
Changes to this policy
We may update this policy as the product evolves. Material changes will be reflected in the "Last updated" date and posted on this page. Continued use of the Service constitutes acceptance.
Contact
Brantner Solutions LLC
[email protected]