refactor: rename SolaceScanScout to Solace and update related configurations
- Updated branding from "SolaceScanScout" to "Solace" across various files including deployment scripts, API responses, and documentation. - Changed default base URL for Playwright tests and updated security headers to reflect the new branding. - Enhanced README and API documentation to include new authentication endpoints and product access details. This refactor aligns the project branding and improves clarity in the API documentation.
This commit is contained in:
defiQUG
@@ -3,8 +3,8 @@
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Privacy Policy | SolaceScanScout</title>
|
||||
<meta name="description" content="Privacy policy for the SolaceScanScout explorer.">
|
||||
<title>Privacy Policy | SolaceScan</title>
|
||||
<meta name="description" content="Privacy policy for the SolaceScan Chain 138 explorer operated by DBIS / Defi Oracle.">
|
||||
<style>
|
||||
body { margin: 0; font-family: Arial, Helvetica, sans-serif; background: linear-gradient(180deg, #0f172a 0%, #111827 45%, #f8fafc 46%, #ffffff 100%); color: #0f172a; }
|
||||
.shell { max-width: 980px; margin: 0 auto; padding: 2rem 1rem 3rem; }
|
||||
@@ -19,19 +19,61 @@
|
||||
<body>
|
||||
<div class="shell">
|
||||
<div class="topbar">
|
||||
<div class="brand">SolaceScanScout Privacy Policy</div>
|
||||
<div class="brand">SolaceScan Privacy Policy</div>
|
||||
<a href="/">Back to explorer</a>
|
||||
</div>
|
||||
<div class="card">
|
||||
<h1 style="margin-top:0;">Privacy Policy</h1>
|
||||
<p class="muted">Last updated: 2026-03-25</p>
|
||||
<p>SolaceScanScout is a blockchain explorer. Most content you view comes from public blockchain data and public APIs. We do not ask for personal information to browse the explorer.</p>
|
||||
<p>SolaceScan is the public Chain 138 explorer surface operated by DBIS / Defi Oracle. Most content you view comes from public blockchain data, explorer indexers, route services, and public configuration endpoints. We do not ask for personal information to browse the public explorer.</p>
|
||||
<h2>What we store locally</h2>
|
||||
<ul>
|
||||
<li>We may store theme preference, locale, recent searches, and similar local UI settings in your browser.</li>
|
||||
<li>When you use wallet features or the Snap companion, the app may interact with your wallet provider to complete the request you initiate.</li>
|
||||
<li>Explorer queries are sent to the configured blockchain APIs and RPC endpoints so the site can display blocks, transactions, addresses, and related data.</li>
|
||||
<li>We do not sell personal data. We also do not intentionally track users with advertising cookies on this explorer.</li>
|
||||
<li>Watchlist entries, saved searches, and similar convenience features may also be stored in browser local storage on the device you use.</li>
|
||||
</ul>
|
||||
<h2>Wallet and account interactions</h2>
|
||||
<ul>
|
||||
<li>When you use wallet features, sign in with a wallet, or request wallet actions such as <code>wallet_addEthereumChain</code> or <code>wallet_watchAsset</code>, the explorer interacts with your wallet provider only for the action you initiate.</li>
|
||||
<li>Wallet requests are handled by your wallet software. We do not take custody of private keys through the public explorer.</li>
|
||||
<li>If you use authenticated access features, a session token may be stored locally in your browser to keep you signed in.</li>
|
||||
</ul>
|
||||
<h2>Explorer, RPC, and companion services</h2>
|
||||
<ul>
|
||||
<li>Explorer queries are sent to configured blockchain APIs, explorer APIs, route services, and RPC endpoints so the site can display blocks, transactions, addresses, tokens, routes, bridge monitoring, and related operational data.</li>
|
||||
<li>Some pages also link to companion resources such as the Chain 138 Snap site and machine-readable configuration endpoints.</li>
|
||||
<li>Operational services may record standard server logs for security, availability, abuse prevention, and troubleshooting.</li>
|
||||
<li>Operational logs may include timestamps, requested URLs, response codes, and similar service-health data. These records are used for security and service maintenance rather than advertising.</li>
|
||||
</ul>
|
||||
<h2>Cookies, analytics, and advertising</h2>
|
||||
<ul>
|
||||
<li>We do not intentionally use advertising cookies on this explorer.</li>
|
||||
<li>We do not sell personal data.</li>
|
||||
<li>If telemetry or monitoring is enabled for service health, it is used for product operations rather than targeted advertising.</li>
|
||||
</ul>
|
||||
<h2>Domains and operator identity</h2>
|
||||
<p>The explorer may be reached through <code>blockscout.defi-oracle.io</code> and companion DBIS domains such as <code>explorer.d-bis.org</code>. Those domains are part of the same Chain 138 explorer and companion tooling surface.</p>
|
||||
<h2>Third-party services</h2>
|
||||
<ul>
|
||||
<li>Wallet-provider software, RPC endpoints, Snap delivery, and related blockchain infrastructure may be operated by third parties or companion services with their own terms and availability posture.</li>
|
||||
<li>When you leave the public explorer for a companion site or third-party wallet flow, their policies and operational controls may differ from those of the explorer itself.</li>
|
||||
</ul>
|
||||
<h2>Retention and abuse prevention</h2>
|
||||
<ul>
|
||||
<li>We retain only the minimum service and security records needed to operate, troubleshoot, and protect the public explorer and related APIs.</li>
|
||||
<li>We may restrict, rate-limit, or block abusive traffic in order to preserve service integrity.</li>
|
||||
<li>Browser-local settings such as recent searches or watchlist entries remain under your browser profile until you clear them.</li>
|
||||
</ul>
|
||||
<h2>Operational subprocessors and infrastructure categories</h2>
|
||||
<ul>
|
||||
<li>The explorer may rely on infrastructure categories such as CDN delivery, DNS providers, reverse proxies, RPC endpoints, explorer indexers, and wallet-provider software.</li>
|
||||
<li>Those services process requests only to the extent needed to deliver explorer pages, static assets, blockchain data, wallet flows, and service-health monitoring.</li>
|
||||
</ul>
|
||||
<h2>Jurisdiction and service posture</h2>
|
||||
<ul>
|
||||
<li>This public explorer is an informational and operational infrastructure surface, not a consumer banking product.</li>
|
||||
<li>Questions about service operation, data handling, or policy notices should be directed to the support mailbox below so they can be routed to the correct operator team.</li>
|
||||
</ul>
|
||||
<h2>Contact</h2>
|
||||
<p>If you have privacy questions, contact <a href="mailto:support@d-bis.org">support@d-bis.org</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user