Dados B3 › Privacy

Privacy

Privacy policy

This page says which data Dados B3 receives, where it keeps it, for how long and who else sees it. It describes what the site's code does today. Updated on October 17, 2026.

Who is responsible

Dados B3 is operated by Lemon Tech (RENATA ESTRELA SILVA GUIMARÃES SERVIÇOS DE TI, CNPJ 47.918.130/0001-71). Lemon Tech is responsible for the data described here. Contact: contato@dadosb3.com.

Visiting the site

No response from the site sets a cookie. There is no Google Analytics, no ad pixel and no other tracker: the site's security policy only lets the browser load scripts from the site itself and from the TradingView widget.

To count visits, for each page viewed we record: the page path (without its parameters), the domain of the site that sent you (not the full address), the kind of visitor (person, robot or AI assistant, deduced from the browser name, which we do not store), the campaign tag of the link (utm_source, utm_medium, utm_campaign), if any, and the time. We do not record your IP address in this count, nor the ad click identifier (gclid). The count does not link one visit to another and identifies no one.

The site runs on Render. Like any web server, the hosting keeps technical logs of each request, which may include the IP address. Those logs do not go into our visit count.

Third parties that load in your browser

• TradingView: the page of each security (stocks, REITs, ETFs and BDRs) shows a 15-minute delayed quote in a TradingView widget. The widget loads straight from TradingView into your browser, so TradingView receives your IP address and the usual browser data, under its own privacy policy. That price never passes through our server.
• Google Fonts: the typefaces come from fonts.googleapis.com and fonts.gstatic.com, fetched by your browser directly from Google.
• jsDelivr: the interactive API documentation (/docs and /redoc) loads its scripts from cdn.jsdelivr.net.

API key

To create the free key you give only an e-mail address. The question "how did you find us" is optional, and its answer goes to the count of keys created, never next to the e-mail. We use your email to identify your account and, rarely, for service notices, with one click to stop.

Your e-mail and your key are stored at Stripe, our payment processor, in a customer record. Our server keeps the key only in memory, to check each call.

To apply the daily limit and to know whether the service is used, we count calls per day, per key and per kind of resource. We store a hash (SHA-256) of the key, not the key itself, and the company code is removed before recording: we do not keep which company you looked up. When a call is refused for limit or plan, we record the key hash, the path requested and the reason.

If you send the key in the URL (?chave=), it may stay in your browser history and in the hosting logs. Prefer the X-API-Key header.

If you ask the API screener for a research receipt, we keep the question, the result and the key hash. The receipt is public at the address the response gives you.

Payment

Pro is paid on Stripe pages. Card and Pix details go straight to Stripe; our server never sees the card number. Pix is processed by Stripe with its partner EBANX. Stripe tells us the subscription status, the customer e-mail and, for Pix, the payment date, so we can compute how long Pro lasts.

E-mails

E-mails are sent through Resend, from alertas@alertas.dadosb3.com. We send e-mail only in these cases:

• Company alerts, the weekly bulletin and the Monday portfolio (Pro): only after you confirm by the link we send. A request not confirmed in 7 days is deleted. Every e-mail has a link to leave. For the Monday portfolio we keep the e-mail, the portfolio (tickers and quantities from the /carteira address) and a hash of the Pro key, never the key.
• Pix: one notice up to 5 days before Pro expires.
• Unfinished checkout: a single reminder with the link to resume, only if you accepted communications on the Stripe payment screen.
• News to free key holders: one e-mail per campaign, at most once per person, with a one-click link to stop.

To stop news and reminders, click the link in the e-mail (it opens /parar). We keep only a hash of your e-mail on the "do not send" list, so we do not write again; that list is kept for good, because it is what prevents a resend. If the e-mail provider fails, the message stays stored on our server and is deleted after 365 days.

MCP connector

When your AI uses the connector, our server receives the tool name and its arguments: the stock or fund code, the filters and, if you gave it, the key (argument chave_api). It does not receive your conversation with the AI, only the tool call.

We record only the tool name and the time, to count use. We do not record the arguments, the ticker or the key. The key is used to check the plan and the daily limit, as in the API.

Where and for how long

• Visit, usage and refusal counts: in a database on our server's disk, deleted automatically after 365 days.
• Unconfirmed e-mail requests: deleted after 7 days.
• Alerts, bulletin and Monday portfolio: kept while active. When you leave, nothing else is sent, and the request, with your e-mail, is deleted 365 days after you left.
• Campaign and reminder log: after 365 days the e-mail is replaced by its hash, which is enough to keep the "at most once per person" rule.
• The "do not send" list (/parar): only hashes, kept for good.
• A daily backup of these databases stays on the same disk for 7 days. It does not go to any other service.
• E-mail and key at Stripe: while the customer record exists at Stripe; we delete it on request.

Who else receives data

Only the providers that make the service work: Stripe (payment and the key record), Resend (sending e-mail) and Render (hosting). In your browser: TradingView, Google Fonts and, on /docs, jsDelivr.

Legal basis (Brazil's LGPD)

We use the e-mail and the key to do what you asked: deliver the key, Pro and the alerts (performance of a contract, LGPD art. 7, V). The aggregate count of visits and use keeps the service running and improves it (legitimate interest, art. 7, IX). The checkout reminder depends on the consent you give on the Stripe screen (art. 7, I).

Your rights

Under the LGPD you can ask for access to your data, correction, deletion, and to know who else receives it. Write to contato@dadosb3.com from the e-mail address you registered; we answer within 15 days. Subscribers manage the plan at /portal. The terms of use are at /termos.

If this policy changes, the date at the top changes too.