Privacy

Who operates the service

The service is published at d365portal.com. During the beta there is no payment gateway: the host covers the Azure cost and ingestion stops at the plan cap.

For a question about your data, use Feedback inside the account. That is the channel we read.

What data exists

Account: the email you sign in with and a short-lived one-time code. There is no password.

Organization: name, identifier, members, a logo if you upload one, and the Azure region you chose.

Connection: the string F&O uses to send telemetry. It is stored encrypted. The portal can reveal it to an administrator so they can paste it into the environment.

Usage: daily ingestion totals, so the cap can be applied. These are not the contents of the traces.

Where telemetry lives

Each organization has its own Log Analytics workspace and its own Application Insights resource, in the region chosen at creation. Batch, DMF, form, SQL, and error traces arrive there from F&O.

The portal database does not keep a second copy of those traces. The dashboard queries them at read time, filtered to that organization's environments.

Cookies and measurement

The sign-in session is required to enter. The sidebar remembers whether it is open. Theme and palette are stored in the browser, in local storage.

Vercel Analytics and Speed Insights load only if you accept visit measurement. If you decline, nothing is sent.

Payment

The beta does not ask for a card. When billing starts, Stripe processes the payment. The portal does not store the card number.

How long, and how to correct

The account and the organization last while the service is active and you have not asked to close them. Trace retention is the plan's retention, on your organization's Azure resource.

You can ask to correct or delete the account from Feedback. Closing the organization stops queries against its telemetry; the Azure resource is removed with the organization.