Yog-Scope is a read-only public dashboard. It does not require an account, does not use analytics, and does not track visitors. This page explains in plain terms the very limited data the platform handles.
In short
Yog-Scope does not require an account, uses no analytics, shows no advertising, and sets no cookie that requires consent. Our servers do not record your IP address. We only see personal data about you if you write to us, support the project, or use an API key we issued you. Two exceptions worth knowing: Cloudflare, which protects the site, sees the IP address of every visit (see "When you browse the site"), and token logos are loaded directly from third-party servers, which therefore see your IP address too (see "Token logos" below). No data is subject to automated decision-making or profiling.
Who is responsible
The data controller is AWSD, a SASU registered with the Paris Trade and Companies Register (RCS) under number 100 091 446, whose registered office is at 60 rue François Ier, 75008 Paris, France, reachable at +33 9 82 75 14 25. For any question about your data, write to [email protected]. AWSD has not appointed a data protection officer.
When you browse the site
To send you a page or answer an API call, our servers, hosted by Scaleway in the European Union, receive your IP address, passed on to them by Cloudflare (see below). They do not write it to any log. Our technical logs only contain the method and the address requested, a request identifier — yours if you send one in an x-request-id header, a random one otherwise —, the response status and the processing time, and nothing else that identifies you. Before reaching our servers, every request goes through Cloudflare (Cloudflare, Inc., United States), which protects the site against attacks and bots. Cloudflare is the one that sets up the encrypted connection with your browser, so it sees everything exchanged between your browser and our servers, including your IP address, the headers your browser sends and the full address of the pages and API calls requested. It processes them as a processor, on our behalf and under its data processing agreement. It keeps them for as long as that service requires, and no later than the end of our contract with it. The legal basis is our legitimate interest in protecting the site and keeping it available (GDPR, article 6(1)(f)). This data may be transferred outside the European Union, in particular to the United States. Transfers to the United States are covered by the EU–US Data Privacy Framework, the subject of a European Commission adequacy decision of 10 July 2023; transfers to other countries by the European Commission's standard contractual clauses, provided for in Cloudflare's data processing agreement. There is no account system, no tracking pixel, and no third-party analytics.
When you write to us
If you write to the contact address, we process your email address and the content of your message in order to reply. The legal basis is our legitimate interest in handling the requests sent to us (GDPR, article 6(1)(f)). Writing to us is optional: the site works exactly the same without it. Your messages are kept for as long as it takes to handle your request, then deleted. They go through our mailbox, provided by Google (Gmail), and may therefore be transferred to the United States. That transfer is covered by the EU–US Data Privacy Framework, the subject of a European Commission adequacy decision of 10 July 2023.
When you use an API key
If we issue you an API key, we keep the name we gave your client, the key's prefix and a hash of it — never the key itself — and the dates the key and your client were created and revoked, in order to check each call and to revoke the key. Each call made with a key is counted by client and by route, in counters that are not stored and reset whenever the service restarts, of which we only copy readings to watch the service; the API's logs do not name the client. The legal basis is our legitimate interest in controlling access to the API (GDPR, article 6(1)(f)). A revoked key stays recorded, without the key, until you ask us to erase it; our backups, kept for up to 28 days, hold it until they expire.
When you support the project
If you donate SOL to the address shown on the "Support us" page, the Solana blockchain makes the sending wallet's address, the amount and the date public and permanent. We see them like everyone else, so that we know who supports the project, on the basis of our legitimate interest (GDPR, article 6(1)(f)). Neither we nor anyone else can erase them: the right to erasure cannot be exercised on an on-chain transaction. We make no attempt to link a wallet address to a person.
Token logos
The dashboard pages show each token's logo. That logo is not served by Yog-Scope: your browser downloads it directly from the address the token's creator wrote into its on-chain metadata. As with any image loaded on the web, each of these servers receives your IP address, your browser's identifier (user agent) and our site's name, without the path of the page you are viewing. We do not choose these servers and do not know them in advance. They may be located outside the European Union, including in countries not covered by any adequacy decision. We send them nothing else and receive nothing from them. The legal basis is our legitimate interest in showing the tokens' visual identity (GDPR, article 6(1)(f)). To avoid it, block third-party images in your browser: the site remains fully usable, only the logos stay blank.
Your rights
Under the GDPR you have the right to access, rectify, erase, restrict, port, or object to the processing of your personal data, and to define directives about your data after your death. To exercise any of these rights, write to [email protected]. You also have the right to lodge a complaint with the French data protection authority (CNIL, www.cnil.fr) if you believe your rights are not respected.
Changes to this policy
This policy may evolve, for instance if the platform starts using analytics or introduces an account system. When it changes, the "last updated" date at the top of the page is revised; substantive changes will be highlighted on the site.
A question about this document?
Write to us