Data retention, deletion and privacy

WaitScope keeps the minimum: the trace leaves the server when the analysis finishes, and the report stays for the retention period. This page summarizes what is stored, who sees it and how to ask for help.

What is stored and for how long

The Analyses screen shows the period in effect, in the sentence “Each report is available for ...”. If the period increases, you receive an email notice beforehand, and the new period also applies to the analyses already stored, counted from the upload date. If it decreases, it applies as soon as it is saved, also with notice.

What the report stores

The report stores the SQL text as it is in the trace, with the literals written in it, and also the CLIENT ID, the module, the action, the host and the path of the trace file. For statements that differ only in their literals and become one shape, it stores the text with :s and :n and the literals of the variants that cost the most. In deadlocks, it stores the database user, the machine and the program of each session. The analysis also stores the name of the uploaded file and a SHA-256 digest of the file and of the trace, used to recognize the same trace uploaded again. Bind values are never included.

The literal mask hides the quoted text and the numbers of the SQL in what you see and download, and also the SQL ID of the variants, without changing the stored report: see Hidden literals in the SQL.

Uploading the same file again opens the analysis that already exists. The same trace in another file, for example with another compression or inside a zip, creates a new analysis, which replaces the previous one when it is done. The details are in limits and repeated upload.

Delete an analysis before the period ends

1. In the console, open Analyses, in the menu at the top of the page.
2. In History, find the analysis by the file name.
3. Click Delete, on the analysis row.

Result: the console shows “Analysis deleted.” and the analysis leaves the history.

To delete several at once, check the analyses, or Select all, and click Delete selected. The console asks for confirmation: “Delete N analyses? This cannot be undone.” In the Android app, the list of analyses has the same options.

Deletion cannot be undone: to get the report again, upload the trace again. A deleted analysis disappears from the backups when they are replaced, within 5 days, or later if the daily copy fails.

Download the report

On the report page, Download HTML saves a file that opens in the browser without the console, Download JSON saves the analysis result in JSON, and Download PDF opens the full report to save as PDF. The name follows that of the uploaded file: the trace exemplo-10046.trc becomes exemplo-10046-relatorio.html and exemplo-10046-resultado.json. The HTML and the PDF follow the number of Statements per list chosen at the top of the page.

In the Android app, the report opens and is shared in HTML. All formats come out with the literal mask of your account. Once downloaded, the file is yours: protecting it and deleting it is up to you.

Who sees your analyses

• You: your analyses, in the console and in the app.
• Other users: nothing from your account. For them, an analysis of yours responds as if it did not exist.
• Console administrator role: the account data and the sessions of each user, to manage access. It does not open the analyses.
• Whoever operates the server: has technical access to the database and to the backups, where the reports are stored unencrypted. The content is opened only when you ask for support, to handle a security incident or when the law requires it.

Isolation between accounts is enforced by the application, on every screen and every API route: the console and the app never show one account's analysis to another, nor to the administrator.

Server in Brazil

The analysis runs on a server in Brazil, where the database, the reports and the backups are also kept. Through the address https://app.waitscope.com/, the connection goes straight to this server, over HTTPS.

The previous address, https://waitscope.io, reaches the same server: it still serves the Android app that uses this address and sends the browser to https://app.waitscope.com. Use https://app.waitscope.com in the browser and in the app.

Two-step verification

Every account signs in with the password and with the 6-digit code from the authenticator app. At sign-up, the console shows 10 recovery codes, only once: keep them in a safe place. Each code works once, in place of the app code.

In My account (click your username, at the top of the screen), Set up another app (new phone) moves the account to a new phone, and Generate new recovery codes replaces the codes; both actions ask for the current password. In Connected devices, you see where the account is signed in and can use End all other sessions.

Ask for help without sending the trace

Do not send a trace or a report by email, because WaitScope email goes through companies in the United States. Describe the problem and say which analysis it is. Write to contato@waitscope.com with:

• the file name, as it appears in History, and the date and time of the upload;
• the status of the analysis and the error message, if any;
• the report section and the statement number (#) or the SQL ID of what looks wrong;
• what you expected to see and what appeared;
• the console version, in the page footer (for example, WaitScope 1.7.0), and the app version, in Settings, if the upload was made through the app.

With this, support finds the analysis in your account and opens it only because you asked. The trace is no longer on the server: support sees the report. Do not delete the analysis before the reply.

What to remove before sharing an excerpt

If the problem can only be explained with an excerpt, such as a trace line or a piece of the SQL, copy only that excerpt and remove first:

• the SQL literals: the quoted text and numbers such as taxpayer IDs, phone numbers or customer codes;
• the values of the BINDS block;
• the CLIENT ID, the module, the action, the host and the file path, which the report shows unmasked;
• in deadlocks, the database user, the machine and the program of each session.

The same care applies to a downloaded report you pass on to a colleague: the literal mask does not cover these fields.

Where to go next

• Hidden literals in the SQL: what the mask hides and how to turn it on or off.
• Limits and repeated upload: the size limits and the same trace uploaded again.
• What WaitScope does not do: what is out of the service's reach.