Contact
Last updated 2026-05-13
AprScope is operated by Vladimir Kayzumov as an individual project. There is no support team, no ticketing system, and no SLA. Reasonable inquiries get a personal reply within a few days.
When to contact us
Things that are worth writing about:
- Data errors. A pool tagged with the wrong protocol or chain. An APY value that obviously contradicts the source. A page that loads but displays nothing.
- Privacy requests. Questions about what data we hold about you (probably none), or requests under GDPR / CCPA / equivalent legislation.
- Editorial corrections. Factual errors in a blog post or hand-written protocol description.
- Partnership inquiries. If you operate a DeFi protocol and would like to discuss correctly representing your pools, contact us. The answer to “can we pay for better placement” remains no, but corrections to factual data are welcome.
- Press inquiries. Quotes, comments, interviews. Quick replies depend on your deadline and how interesting the story is.
Things that probably won’t get a reply:
- Requests for personalized investment advice. We don’t provide it (see Terms).
- Generic SEO/content/marketing pitches. They go straight to spam.
- Cold outreach from agencies offering “guest post” placements.
How to reach us
Email is the primary channel. The address has been intentionally omitted from this page in raw text to reduce spam scraping; please assemble it from the parts below:
- The mailbox is
contact. - The domain is the domain of this site (whatever URL you’re reading this on).
So, on a site published at defi-yields.com, the address would be [email protected]. We’ll set up the mailbox once we register the production domain.
For privacy-related requests specifically (GDPR access requests, deletion requests, etc.), please put “Privacy” in the subject line so it routes correctly.
Response time
There is no committed response time. In practice, urgent issues (a serious data error visible on the homepage, a privacy request) get same-day attention. Everything else may take up to a week.
If your question is something other readers would benefit from, we may answer it on the blog rather than (or in addition to) replying directly. We’ll let you know if we plan to do that.
Last updated
This contact page was last reviewed on 2026-05-13.