Privacy policy

Scope and responsibility

This draft describes the current Serevin interface and its intended privacy practices for an international audience. A wallet address can be personal information when it identifies, or can be linked to, a person. Public blockchain data is not necessarily anonymous.

The legal operator, business contact details and designated privacy contact must be identified before this policy takes effect. Hosting locations, provider arrangements and log-retention settings also require confirmation. These pending details are not a claim that no personal information is processed.

Information used by the interface

When you connect a wallet, Serevin receives the public address and network information your wallet makes available. Wallet discovery may provide an extension name, identifier and icon. Serevin does not ask for or store your wallet signing private key or seed phrase.

For account views, Serevin processes the public address you connect or enter, together with returned balances, position shares and blockchain observations. For quotes, it processes the selected token addresses, input amount and the Uniswap slippage setting. The Route quote request uses its own fixed tolerance. Account or token addresses sent as query parameters can appear in network or infrastructure logs.

Browsing the public workspace does not create a saved portfolio. When the separate portfolio service is configured, explicit signed requests can store your public address, request parameters, challenge message and signature-related records, saved balance and position reports, alert rules and private inbox entries in PostgreSQL. These records can link an address to its service activity. Infrastructure providers may independently process IP addresses, timestamps, request URLs, device information and diagnostic records.

Market proposal drafts remain in the page until downloaded or submitted. The separate proposal service stores the submitting address, proposal contents, evidence URL, signature and request message in Cloudflare D1. Administrator review decisions and their signatures are also retained. Owner amendments additionally retain the source and replacement identifiers, owner signature and message, reviewer-policy snapshot, request expiry and server-recorded time. Replacing a proposal preserves its original contents and history. Owners can retrieve their own proposals; the two configured reviewers can access the review queue. Private feedback records include the note text, author wallet, signature, signing message, reviewer-policy snapshot and server-recorded time. The proposing wallet and current configured reviewers can read and add notes. Submitted evidence URLs and URLs in feedback are not fetched automatically. Do not include private keys, personal contact details or confidential material in a proposal or note. This metadata database does not hold tokens, lending balances or financial credits.

Why this information is used

Account and network information is used to show the requested balances and positions, distinguish a connected wallet from a watched address, manage the connection and check the selected network. Quote inputs are used to calculate routes for the requested trade size.

Appearance and connector preferences support your selected presentation and optional connection restoration. Providers may process operational information to deliver, protect and troubleshoot their services. If additional purposes or optional uses are introduced, the notice and any required choices must be updated before that processing begins.

Providers and public networks

A connected or watched address is sent to Serevin’s data endpoint and included in calls to the configured Robinhood Chain RPC service. Balances and recorded positions are read from public contracts, including the reviewed Morpho markets. Displaying a public address does not verify that you own it.

The hosted data service uses Alchemy as its primary blockchain RPC provider and Robinhood’s public RPC as a backup. These services receive the requested public addresses, contract calls and server connection metadata. The dedicated provider credential remains on Serevin’s server and is not sent to your browser or wallet.

Selecting Compare quotes also requests a quote from Route through Serevin’s server. That request sends chain ID 4663, the input and output token contract addresses and the input amount. Serevin does not forward your connected or watched wallet address, browser IP address, wallet credentials or transaction payload to Route. Route receives the server’s IP address and can process quote inputs, timestamps and other request metadata. This server-mediated request does not establish zero logging or retention by either provider.

If WalletConnect is enabled and selected, Reown/WalletConnect infrastructure and your chosen wallet help establish and maintain the session. The integration disables optional WalletConnect core telemetry. Connection metadata, QR-modal diagnostics and other provider processing can still occur; the setting does not establish zero tracking or zero retention.

The external Route link opens its homepage without a prefilled trade or wallet address. Once you follow that link, your browser connects directly to Route and can expose its IP address and browser information. Any wallet connection or trade there follows Route’s own interface, privacy practices and terms. Serevin does not embed that trading interface or forward a signing request.

Wallet providers, RPC services, hosting/CDN providers and external sites have their own privacy practices. Following an external link or authorizing a wallet connection can expose information to those providers. Processing may occur outside your country. The deployed provider list, locations, safeguards and retention arrangements must be confirmed before public release.

Browser storage and session data

The interface uses localStorage entries named serevin-appearance and serevin-wallet-connector for appearance and connector preference. A remembered connector can be used to request an already-authorized account silently. These preferences remain until replaced or removed through the application or your browser.

When used, the WalletConnect SDK can store pairings, sessions, client identifiers, deep-link preferences and transport-session cryptographic material in IndexedDB or browser-storage fallbacks. These connection keys are different from your wallet signing key or seed phrase.

The interface keeps local records of unfinished wallet requests so an interrupted request can be reconciled before another send. SVRN staking uses localStorage under a serevin-staking-request key scoped to the chain and campaign, with a browser Web Lock coordinating current-release tabs. Recent completed staking checks are also retained in a history key, limited to the latest 50 records across wallets for the campaign. They contain the account, action, token, observed amount, transaction references, block identity, outcome and check time. This historical notebook is stored in this browser and is removed when site storage is cleared. It does not establish current holdings or finality. Registration and activation use their own localStorage records. The separate service transaction journal uses IndexedDB under serevin-transaction-journal-v1. These records can include the public account, network, action, reviewed terms or deployment, destination, amount, calldata, transaction hash and timestamps. They contain no wallet signing key and are not authoritative balance ledgers.

A confirmed operation removes its pending record. An interrupted record remains until its onchain outcome is reconciled, or the user checks wallet activity and explicitly clears an eligible unresolved request. Connecting or disconnecting a wallet does not delete it. Clearing site storage or using another device removes or bypasses this local tracking, so reconcile your wallet history before starting another operation. Additional financial releases require their own release notice and verified wallet flow.

The current application does not include an active first-party advertising or analytics integration. That statement does not describe every dependency or provider. Browser privacy settings may prevent storage or connection restoration.

Retention and deletion

The current data endpoints request no-store handling for responses and do not maintain an application wallet-history database. This does not prevent separate infrastructure logging. Specific hosting and provider retention periods have not yet been finalized and must not be assumed to be zero.

Disconnecting clears the application’s active wallet state and attempts to terminate a WalletConnect session when one exists. It does not necessarily revoke an extension’s site permissions, remove every SDK storage entry or delete provider logs. You can revoke permissions in your wallet and clear this site’s browser storage.

The separately configured portfolio service retains saved reports and member inbox entries for 30 days. Its expired request challenges are removed after one day. Alert rules persist until the operator removes them under its approved retention policy; disabling an alert stops future checks but does not itself delete the record. Operator incidents and notification records persist for reconciliation. The proposal service retains submitted proposals, original signed submissions, review events, signed amendment relationships and signed feedback without automatic expiry so release decisions can be checked. Notes cannot be edited or deleted through the interface; disconnecting does not remove them. A request-handling process and provider backup and log-retention details remain pending.

Private contract inspections retain the exact proposal, RPC observations, recorded block, report digest, collection and receipt times, requesting wallet, authorizing signature and reviewer-policy snapshot without automatic expiry. Newer reports also retain oracle reference comparisons and supported feed publication times against an identified historical catalogue. The signature requests collection and does not endorse the future report contents. The proposing wallet and current reviewers can retrieve these records. Downloads contain those details. RPC providers receive read requests for the proposed contracts and configured oracle dependencies; submitted evidence URLs are not fetched.

An optional review-packet request assembles retained proposal, amendment, review and evidence records for the proposing wallet or current reviewers. The packet includes wallet addresses, original action signatures, policy metadata, request identifiers and report contents. Serevin assembles it when requested without saving an additional durable packet record; the underlying records and request challenge retain their existing retention rules. Choosing Download private packet saves a local file. Disconnecting does not delete a downloaded file or copies you share.

Choosing an admission request file checks it in browser memory without uploading it. An explicit signed submission sends the exact artifact to Serevin. The admission view clears its imported and loaded private records when the connected wallet identity changes or you choose Clear view. It does not save those records or signatures in browser storage. Downloaded files and the server records described below are not removed by clearing the view or disconnecting.

A separate admin-signed admission submission stores the uploaded original packet and dossier, complete candidate configuration, supporting decision statements and evidence references, the submitting admin signature, and later admission approval or revocation signatures. These private records have no automatic expiry and are accessible through the admission service only to current configured admins. They preserve what was considered for an exact release, including historical wallet addresses and signatures. Submitting a proposal or downloading its packet does not itself create this additional admission record. Admission request challenges become eligible for bounded deletion 24 hours after expiry when admission traffic runs cleanup; retained request and decision records are not deleted by that cleanup.

Proposal, feedback, amendment-history and evidence request challenges become eligible for deletion 24 hours after their two-minute expiry. Inspection attempts retain the requesting wallet and timing for usage limits; they become eligible 24 hours after their 25-second lease expires, including failed attempts. Old rate-limit counters are also eligible after one day. Bounded cleanup runs opportunistically on proposal traffic, so this is not a promise of deletion at an exact time. Cleanup does not delete proposals, reviews, signed replacement relationships, signed feedback or saved inspection reports.

Serevin cannot erase records from a public blockchain or delete records controlled independently by third parties. Onchain report hashes and credit-use events are public. The intended operator must provide an actual contact and process for applicable access and deletion requests; disconnecting a wallet does not delete a saved report or alert.

Your choices and applicable rights

You can browse general market information without connecting a wallet. Looking up a public address still sends that address to the data service. You can stop connection restoration by disconnecting, remove stored preferences and revoke permissions through your wallet.

You can browse the quote interface without requesting a Route quote. Route is contacted when you select Compare quotes, not merely when you edit an amount or token. Following the external Route link is a separate choice and opens that service directly.

Depending on applicable law, you may have rights to information, access, correction, deletion, objection, restriction, portability, withdrawal of consent or a complaint to a privacy regulator. These rights have conditions and exceptions. A public blockchain or independently controlled provider record may not be editable by Serevin.

Privacy choices and consent to personal-information processing are separate from agreement to service terms or acknowledgement of financial risk. Connecting a wallet is not consent to move funds or surrender legal rights.

Privacy requests and policy changes

The monitored privacy contact and responsible operator remain pending confirmation. No unverified email address is provided in this draft. A real contact and request-handling process must be published before the policy is put into effect.

Do not send a private key or seed phrase with a support request. Material changes should be identified with an updated version and effective date, and new consent obtained where required. Nothing in this policy removes privacy rights or duties that applicable law preserves.