TICE-IT / TIPP

Exact Synergy Enterprise · TIPP

TIPP usage statistics

How TIPP shares limited usage counts with TICE-IT, what that includes, and how a Synergy administrator turns it off.

TIPP · Section 1

1. Summary

On by default (opt-out) Usage statistics sharing is turned on unless an administrator turns it off. The installer checkbox “Share usage data to help improve TIPP” is pre-ticked. Nothing is sent on the install day itself.
Once a day After the next local midnight on the Synergy server, TIPP may send one JSON report per site for each day that still needs sending.
Includes the licence number in plain text The report includes the TIPP licence number as stored on the site, not hashed. This data is not anonymous: the licence number identifies the customer. The report also includes version, edition, site number, AI-provider names that have a key configured (not the keys), the date, and daily page-open counts.

TIPP · Section 2

2. What is collected

Each day, TIPP builds one JSON object per site. That object is what is sent.

Field	What it contains
`licenceNumber`	The TIPP licence number, as-is (plain text, not hashed).
`siteIndex`	The site number (1 unless multi-site PRO).
`version`	The installed TIPP version.
`edition`	`TIPP` or `TIPP PRO`.
`modules`	`CORE`, and `PRO` when licensed, plus the names of AI providers that have a key configured (ChatGPT, Claude, Gemini, Grok, Mistral, AzureAI). The keys themselves are never sent.
`date`	The day being reported (`yyyy-MM-dd`).
`pages`	Daily open counts per TIPP page name. A customer’s own copies of TIPP pages are reported under a generic custom label. Non-TIPP pages are reported as `other`.

The request also carries a timestamp, a signature, and the user agent TIPP-UsageStats. The local TIPP_AIUsage table is never transmitted; it stays on the customer’s server only.

Example JSON (made-up values for illustration — not a real customer report; version shown as 1.3.x):

{
  "licenceNumber": "TIPP-XXXX-XXXX",
  "siteIndex": 1,
  "version": "1.3.x",
  "edition": "TIPP PRO",
  "modules": ["CORE", "PRO", "ChatGPT", "Claude"],
  "date": "2026-11-08",
  "pages": {
    "TIPP.Assistant": 42,
    "TIPP.Workspace": 18,
    "custom": 3,
    "other": 7
  }
}

TIPP · Section 3

3. Why we collect it

We use these counts so we can:

see which TIPP versions and editions are in use, so we can prioritise fixes and support;
see which TIPP pages are opened most, so we can prioritise stability work and features;
see which AI providers customers have configured (by name only), so we can test and support those paths;
match a report to a licence when a customer asks for help with that installation.

TIPP · Section 4

4. What is not collected

TIPP usage statistics do not include:

prompt or answer text from the assistant;
user names, email addresses or user IDs;
URLs or query strings;
business records (orders, accounts, documents, or other Synergy / Globe data);
AI provider API keys.

Browser headers on the Synergy site are used only locally to skip robots; they are not stored as part of the usage report. TIPP does not log or keep the sending server’s IP address. As with any web service, the network can see that address while the data is in transit.

TIPP · Section 5

5. How and when it is sent

Sending is triggered by the first TIPP page open after midnight (Synergy server time).
Each run can send up to 14 past days, with retries when a send fails.
Transport is HTTPS POST (TLS 1.2) to https://telemetry.tice-it.com/tipp/v1/usage, signed with HMAC-SHA256.
Nothing is sent on the install day. The first send can happen only after the next local midnight. An administrator who unticks sharing in the installer therefore sends nothing.

TIPP · Section 6

6. Where it is stored and for how long

On the customer’s Synergy server

Days that have already been sent are deleted after 35 days.
Days that have not been sent are deleted after 60 days.

At TICE-IT

Reports are received by an Azure Function App and stored in an Azure SQL database hosted in Germany. A copy is then kept on TICE-IT’s production server, which is also hosted in Germany.

In Azure, daily rows are rolled into monthly totals after 24 months. Those monthly totals are kept indefinitely; they hold no per-day detail.

To ask for usage data that has already been sent to be deleted, email info@tice-it.com. We handle deletion requests within 30 days.

TIPP · Section 7

7. How an administrator turns it off

After installation

Open Modules → TIPP → Setup → General → Settings (Synergy administrators only). Turn off the usage-statistics toggle.

Counting stops at once, and any unsent collected data on that site is deleted.
Other servers or processes pick up the change within about five minutes.
A send that is already in progress finishes its current POST.
Turning it off stops new sends. It does not delete data that has already been sent to TICE-IT. To request deletion of that data, email info@tice-it.com (see section 6); we handle requests within 30 days.

During installation

The Usage statistics step (“Help us make TIPP more stable and useful”) appears once per site on a fresh install of TIPP 1.3 and later, or on an upgrade from a version that did not have the feature. The checkbox is pre-ticked. Untick it to leave sharing off.
A repair run can show the same choice as a dialog.

Other ways sharing stops

Blocking outbound HTTPS to telemetry.tice-it.com also stops sends.

See exactly what would be sent

On the same Settings page, use Show what is sent. It shows the exact JSON body the sender builds (indented) for the next pending day — not the request headers. When nothing is pending, it shows today’s counts so far. Opening that view sends nothing.

TIPP · Section 8

8. Contact

Questions about TIPP usage statistics: info@tice-it.com.

To request deletion of usage data already sent to TICE-IT, email the same address. We handle deletion requests within 30 days.

TIPP resources