Privacy Policy

Version dated October 27, 2026.

Translation for convenience. If there is any difference, the Portuguese version prevails.

This policy explains how WaitScope processes personal data on the website, in the console, in the Android app and in contact emails: which data, for what purpose, on what legal basis, where they are kept, for how long and how you exercise your rights. The articles cited are from the Lei Geral de Proteção de Dados Pessoais (LGPD, Brazil's General Data Protection Law, Lei nº 13.709/2018), unless otherwise stated.

1. Who is responsible

WaitScope is a service provided by Johab Benicio de Oliveira, a natural person based in Brazil. No company (CNPJ, Brazilian corporate taxpayer ID) is linked to the service yet. The person responsible is the controller, that is, the person who decides for what purposes and how the personal data described in this policy are processed, except for the content of the traces (section 3). In this policy, “WaitScope” means the service and the person responsible for it.

• Contact and channel for requests about personal data: contato@waitscope.com. WaitScope replies within 15 days.
• CPF (Brazilian individual taxpayer ID) and postal address: provided to anyone who asks through that channel.
• Data Protection Officer (DPO): none. WaitScope is a small-scale processing agent under art. 2, I, of Resolução CD/ANPD nº 2/2022 (the regulation for small-scale processing agents issued by the ANPD, Brazil's data protection authority) and has not appointed a DPO (encarregado), as art. 11 of that resolution allows. The channel above is the channel of communication with data subjects, the persons to whom the data refer.

2. What this policy applies to

• The website waitscope.com, in English, and its versions in Portuguese and Spanish. The address waitscope.com.br redirects to the website, usually to the Portuguese version.
• The console, the service itself, at waitscope.io, and its old address, jb-profiler.tail47afbc.ts.net, which works during a transition period and will be shut down.
• The WaitScope Android app.
• Emails exchanged with contato@waitscope.com.

WaitScope reads Oracle trace files (event 10046) uploaded by the customer and builds a response time report. It is a service for companies and professionals, in early access and free of charge. There is no public sign-up: access is requested by email, and the person responsible creates the account.

Links to third-party websites, such as the Oracle documentation cited in the reports, lead to services with their own policies.

3. WaitScope's two roles

Controller: website, contact, account and security

WaitScope decides for what purposes and how it processes the data of those who visit the website, write to the contact address and use the console and the app. This processing is described in sections 4 to 8.

Processor: the content of the traces

A trace may contain personal data in the SQL text and, sometimes, data about the customer's own patients, clients or users. For that content, the controller is the customer, that is, the company or professional who uploads the trace. WaitScope is the processor: it processes the content only to generate the report and never uses it for its own purposes, such as statistics or product improvement. The rules for this role are in section 8 of the Terms of Service.

• The uploaded file is deleted from the server as soon as the analysis ends, whether it completed or failed. An upload interrupted before completion is deleted after 24 hours without receiving data.
• The report is kept for the retention period and then deleted. The default period is 7 days. WaitScope may set another period, from 1 to 365 days, with prior notice when the period increases (Terms of Service, section 8.3), and the console home screen shows the period in force. You can download the report as HTML or JSON and delete the analysis before the period ends. If you upload the same file again, the console opens the existing analysis; if the same trace comes in another file, the new analysis, once ready, replaces the previous one.
• The report stores the SQL text as it appears in the trace, including the literals written in the SQL, as well as the CLIENT ID, module, action, host and trace file path. For deadlocks, it stores the database user, machine and program of each session involved. The analysis also stores the name of the uploaded file and a digest (SHA-256) of the file and of the trace, used to recognize the same trace. Bind values are not stored.
• By default, quoted text and numbers with 6 or more digits appear as *** on screen, in the app and in the reports downloaded as HTML and JSON. You can turn this option off in “My account”, in the console. The report stored on the server keeps the original text. CLIENT ID, module, action, host, file path and, for deadlocks, the database user, machine and program appear unmasked.

To reduce the personal data in the trace, generate it without bind values and upload only the files of the operation you want to analyze.

4. Data, purposes and legal bases

The tables below show what WaitScope processes as controller. None of this processing depends on consent. WaitScope does not sell personal data and does not use them for advertising or for behavioral profiling.

The account data and the two-step verification data are a condition for using the console and the app: without them, there is no way to provide access to the service. Your rights over these data are in section 11.

Website and contact email

Account, access and security, in the console and the app

If you use WaitScope on behalf of a company, the service is provided to that company. In that case, where the table says “performance of a contract”, the legal basis for your data is the legitimate interest in providing the company with the service it requested (art. 7, IX). The same applies to a request for access to the service made on behalf of a company.

Android app

The app stores on the phone only what it needs to keep you signed in, resume uploads and remember your preferences: the session token, encrypted with an Android Keystore key; the server address, the language, the biometric lock (on or off) and the last username; the state of the upload in progress (file names and sizes, how much has already been uploaded and the result); and, when the trace comes from another app, a copy of it in the app's private storage until the upload ends. The legal basis is performance of a contract (art. 7, V). The retention periods are in section 7.

Biometrics are verified by Android itself: the app stores only whether the lock is on and receives no biometric data. The app has no third-party libraries for usage analytics, advertising, crash reporting or notifications. The notice that an analysis is ready comes from the app's own query to the server. The reports you download remain on the phone after you sign out of the app: on Android 10 or later, in the Downloads/WaitScope folder, until you delete them; on Android 8 and 9, in the app's own downloads folder, until you delete them or uninstall the app.

Legitimate interest: necessity and impact on you

Where the legal basis is legitimate interest, WaitScope weighs the necessity of the processing against its impact on you (balancing test):

• Website visit and NEL: these are the minimum technical data needed to deliver pages; the website sets no cookies, runs no scripts and does not measure its audience.
• Other email messages: you chose to write, and the message is used only for the reply.
• Use on behalf of a company: you act for whoever requested the service, and only the data needed to provide access are used.
• Session IP address and device: showing where the account is open helps you notice unauthorized access. These data leave the session list when the session ends, and the IP address of each login is also kept in the audit log, for 180 days.
• Login attempts: the name entered and the IP address stay in the lockout table for 1 day and serve only to stop anyone trying to guess passwords. A failed login also goes into the audit log, with the IP address and, if the account exists, the username, for 180 days.
• Audit: the log is minimal, has a fixed period of 180 days, does not appear on any screen and protects your own account.
• Server logs: these are technical data about each request, with no other use, and the oldest entries give way to new ones.
• Backup: without a copy, a failure would erase accounts and reports; the copies stay on the same server in Brazil for up to 5 days.

You may object to this processing through the channel in section 1 (see section 11).

5. Where the data are kept and who processes them

The console, the database and the backups are on a Magalu Cloud (Magazine Luiza S/A) virtual machine in Brazil, region br-se1. The connection to waitscope.io goes directly to that server, with a TLS certificate from Let's Encrypt: Cloudflare only operates the domain's DNS, and Tailscale is not in that path.

At the console's old address, the connection passes through relay servers of Tailscale Inc., a Canadian company. These servers are in the United States and see the IP address of whoever accesses it, but not the content, because the encryption (TLS) terminates at the server in Brazil.

The website is hosted on Cloudflare Pages, from Cloudflare, Inc. Messages to contato@waitscope.com pass through Cloudflare's email routing and arrive in a Gmail mailbox, from Google LLC. WaitScope's replies and notices are sent from that mailbox.

Apart from these providers, WaitScope discloses personal data to an authority only when the law requires it, such as to comply with a court order.

6. International data transfer

Part of the personal data described in this policy is processed outside Brazil, by three providers headquartered abroad. Sessions, analyses and reports are not handed over to them and remain on the server in Brazil. When WaitScope writes to you, the message and your email address are kept in the Gmail mailbox.

• Where to and what: the United States, with Cloudflare, Inc. (connection data of whoever opens the website, NEL reports and contact emails in transit) and Google LLC (contact emails received and sent through the Gmail mailbox); Canada and the United States, with Tailscale Inc. (IP address of whoever accesses the console's old address).
• How the data get there: over the internet, when you open the website, write to the contact address, receive an email from WaitScope or use the console's old address. At that address, the content passes through Tailscale encrypted, without Tailscale being able to read it.
• Purpose: hosting the website, operating the DNS and forwarding email (Cloudflare); receiving, sending and storing contact messages (Google); carrying the connection from the old address to the server in Brazil (Tailscale).
• Duration: for as long as WaitScope uses each service. Emails are kept for the period in section 7. The routing through Tailscale ends when the old address is shut down. Technical records kept by the providers follow their own retention periods.
• Controller: Johab Benicio de Oliveira, who can be contacted at contato@waitscope.com (section 1).
• Sharing: WaitScope uses these providers only for the purposes above and does not share these data with anyone else.
• Responsibilities and security: WaitScope is accountable as controller to you and to the Agência Nacional de Proteção de Dados (ANPD, Brazil's National Data Protection Agency); the providers process these data to provide the contracted service, under their own terms of service. The website and the console use HTTPS, the website has no cookies or scripts, and at the old address the encryption terminates at the server in Brazil.
• Your rights: those in section 11, through contato@waitscope.com, including the right to lodge a complaint with the ANPD.

To learn more about these transfers, including which terms of each provider apply to them, write to contato@waitscope.com.

Do not send traces, reports or third-party data by email. The message passes through Cloudflare and is kept in a Gmail mailbox, in the United States.

7. How long the data are kept

The cookie periods are in section 8.

8. Cookies

The waitscope.com website sets no cookies. The console uses only four first-party cookies, all HttpOnly and SameSite=Strict. Three are necessary: __Host-latena_session (session, up to 12 hours or 30 minutes without use), __Host-latena_login (login form protection, 1 hour) and __Host-latena_codigo (two-step verification code, 10 minutes). The fourth, latena_idioma, stores the language for 365 days and is set only when you choose the language. There are no analytics, advertising or tracking cookies, the console does not use browser storage and the Android app does not use cookies.

The three necessary cookies do not depend on consent, and the language cookie is set only at your request. Their purposes, legal bases and how to delete them are in the Cookie Notice. The NEL and Report-To headers that Cloudflare includes in the website's responses are not cookies (section 4).

9. Security

Security measures in use:

• HTTPS on all website and console addresses.
• Password stored only as an Argon2id hash, never the password itself.
• Mandatory two-step verification, through the authenticator app. The authenticator app secret is encrypted with AES-256-GCM, with the key kept outside the database, and the recovery codes are kept only as hashes.
• The database stores only the hash of each session token. The console cookies are HttpOnly and SameSite=Strict.
• Per-user isolation: each account sees only its own analyses, and the console administrator role does not see their content.
• Request limits per IP address and temporary login lockout after several wrong passwords.
• Trace deleted at the end of the analysis and literals hidden by default on display.
• Automatic security updates on the server and administrative access (SSH) only with a cryptographic key, without password login.
• In the Android app, the token encrypted with an Android Keystore key and no third-party libraries for usage analytics, advertising or crash reporting.
• Daily database backup.

No measure eliminates all risk. Who has technical access to the reports is described in section 10.

10. Who sees your data, and technical access to the server

• You: your account data, the open sessions and your analyses.
• Other users: nothing from your account.
• Console administrator role: the account data and sessions of each user (username, email, dates, type of two-step verification, device and IP address), to manage access. It does not see the analyses.
• Providers: only what is described in section 5.

The reports are stored in the database without encryption. Isolation between accounts is enforced by the application: through the console and the app, no other user and no administrator role sees another account's analyses. The person who operates the server, who is the person responsible himself, Johab Benicio de Oliveira, has technical access to the database and the backups. He accesses the content only when necessary for support requested by the customer, to handle a security incident or because of a legal obligation.

11. Your rights and how to exercise them

Under the LGPD (art. 18), you may ask WaitScope for:

• confirmation that it processes your data, access to them and an electronic copy of the account data, in a format that allows their reuse (art. 19, § 3);
• correction of incomplete, inaccurate or outdated data;
• anonymization, blocking or deletion of unnecessary or excessive data or data processed in breach of the law;
• portability of your data to another provider, in accordance with the ANPD's regulations;
• deletion of your account and its data;
• information about whom your data are shared with (section 5);
• revocation of consent, when consent is the basis for the processing (currently, no processing described here depends on consent);
• review of decisions made solely by automated means that affect your interests, with information about the criteria used (art. 20). The only decision of this kind is the temporary login lockout after several wrong passwords, which lasts at most 1 hour;
• objection to processing carried out without consent that does not comply with the LGPD.

How to make a request

• Write to contato@waitscope.com stating what you want. The request is free of charge and may be made by you or by a representative holding a power of attorney.
• Before fulfilling the request, WaitScope confirms your identity, usually by asking for a reply from the email address registered in your account, or by other reasonable means.
• WaitScope replies within 15 days of the request.

What you can do directly in the console

In “My account” (click your username at the top of the screen), you can see your data and the open sessions and change your password, language, privacy choices and two-step verification. You can also download reports as HTML or JSON and delete analyses whenever you want.

Account deletion

The account is deleted on request, through the channel above, until the console has an option for you to do it yourself. Deletion erases the account data, the sessions and the analyses. After it, only the following remain:

• the audit log, until it reaches 180 days;
• login attempts, for up to 1 day;
• server logs, until they are replaced by newer entries;
• backups, for up to 5 days;
• the messages exchanged with contato@waitscope.com, for the period in section 7.

If your data are in a trace

If you do not use WaitScope but your data appear in a trace uploaded by a customer, the controller is that customer (section 3). Make your request directly to them. If the request reaches WaitScope, the reply explains that WaitScope acts as processor and, when the customer can be identified, that the request has been forwarded to them.

Complaints

You may also lodge a complaint with the ANPD, at gov.br/anpd, and with consumer protection bodies (art. 18, §§ 1 and 8).

12. Children and adolescents

WaitScope is a service for companies and adult professionals and is not intended for anyone under 18. If a trace contains data of children or adolescents, those data are the responsibility of the customer, who is the controller (section 3).

13. Security incidents

A security incident is unauthorized access to, or the leak, loss or alteration of, personal data.

• If an incident involving data for which WaitScope is the controller may cause significant risk or harm, WaitScope notifies the ANPD and the affected persons. The deadline is the one set by Resolução CD/ANPD nº 15/2024 (the ANPD regulation on security incident reporting), counted from when WaitScope becomes aware of the incident.
• The notice to you is direct and in plain language, sent to your account email or to the email address you used to contact WaitScope. When that is not possible, the notice is published on the website for at least 3 months.
• The notice states what happened, which data were affected, the security measures that protected them, the risks, what was done to reduce the effects, when WaitScope learned of the incident, the reason for any delay, and how to obtain more information.
• If the incident affects the content of traces or reports, WaitScope notifies the customer, who, as controller, assesses the case and makes the required communications to the data subjects concerned and to the ANPD.

If you notice anything unusual in your account, write to contato@waitscope.com.

14. Changes to this policy

This policy may change when the service or the law changes. Each version shows its date at the top of the page. A new version is announced by email with the same advance notice as changes to the Terms of Service.

From console version 1.5.0 onward, the first time you sign in, you accept the Terms of Service and confirm that you have read this Privacy Policy. This confirmation is not consent: it only records that you have received this information and does not change the legal bases in section 4. When the version of either document changes, the console shows the new version the next time you sign in and asks for a new confirmation. The console records the user, the version of the documents and the date and time.

If there is a translation of this policy, the Portuguese text prevails in case of any difference.