← Dashboard About Privacy Terms Contact Metrics Methodology Status API docs Pricing Roadmap Security

Contact

Support, data corrections, security disclosures.

Who operates this service

Operator	not published yet
Support	[email protected]
Security	[email protected] (also in security.txt)
Jurisdiction	not published yet

Fields marked not published yet are the operator's own details and are deliberately blank rather than filled with a stand-in. A plausible-looking placeholder on a contact page is a statement a reader can act on — and act on wrongly. The operator name and jurisdiction are not published yet; real-money payments are open while they are still missing. The official contact email is published above: [email protected] Real-money payments are open on Base: deposits (ETH or USDC) and subscriptions are made from your account's My Wallet (see pricing). Until the operator details are published, the roadmap lists them under not done yet, and the official accounts below reach us today.

Community

𝕏	@DeepGyre
Discord	discord.gg/gnHvFRuUP
Telegram	t.me/DeepGyre
LinkedIn	Deep Gyre

These are the only official accounts. Staff never send the first direct message and never ask for a seed phrase or a private key.

What to include

Account or billing	The email address on the account. Never send a password, a seed phrase or a private key. Nobody here will ever ask you for one, and any message that does is not from us.
A number looks wrong	The tab, the card, the value shown, and what you compared it against — a screenshot with the timestamp visible is ideal. Data disagreements are treated as defects, not opinions.
Security	What the issue is and how to reproduce it. Please report privately first and allow a reasonable window to fix it before publishing.
API or partnership	What you want to build and the request volume you expect.

Response times

This is a small operation: replies are measured in days, not minutes. A security report is read first.

Before you write about a wrong number

It is worth reporting even when you are not sure which side is wrong. Several of this platform's own corrections started exactly that way — the difference between a real defect and a difference of definition is usually only visible once both are put side by side. Where a figure could not be read at all, the card says so rather than showing a zero; that is a stated absence, not a bug.

Frequently asked

Which address do I write to?

Accounts, billing and a number that looks wrong go to the support address. A vulnerability goes to the security address, which is the one published in security.txt; it is read first.

Will someone message me first?

No. Staff never send the first direct message on any channel. A message that opens a conversation in DeepGyre's name, or asks for a password, a seed phrase or a private key, is not from us — please report it.

An address is labelled with the wrong owner. Can it be corrected?

Yes. Send the address, the chain and what you believe is right, with a public source if you have one. Labels are attributions from public data and are corrected when the evidence says so; a label is never proof of ownership.

Can I use the data in my own product?

The developer API is described on API docs and the plans that include it on pricing; for anything larger, write with what you want to build.

Also useful

Live status shows how many data feeds are answering right now, and Methodology explains how the figures are built. If a card is blank, those two pages usually explain it faster than an email can.