Privacy & local storage

1. Data controller and applicable rights

The VOIDS team is the controller for the website processing it determines. Applicable rights may include information, access, correction, portability, objection and deletion, subject to legal retention. Reasonable verification may be needed without collecting a private key. You may also contact the competent data-protection authority.

2. Data and purposes

Wallet addresses, network and transaction references are used to display ownership, activity and payment history. Deed names, app names and HTTPS links, their versions, updating wallet and update time are stored for public profiles. Profile and activation signatures are received to verify requested actions; receiving a signature does not mean every signature is retained in a profile table.

The website no longer collects new terms acknowledgments. Previously saved records may contain the wallet, collection, scope, release, document hash, signature and recorded time as evidence of that earlier acknowledgment. Infrastructure may process IP addresses and request/error logs for delivery, security and troubleshooting. Do not put sensitive or unnecessary personal information in public names, links or on-chain content.

The receipt index copies public contract events and block references into website storage to calculate activity and payment totals, detect reorganizations and avoid counting duplicates. Public directory fields include the subject, name, website link, profile version, signer and update time. Submitted profile signatures verify the update; they are not retained as signature fields in the profile table.

Historical acknowledgment storage is separate from directory profiles. Its fields identify the earlier signed message and document release. No acknowledgment record is required for current website actions. The website does not collect seed phrases, private keys or identity documents through this workflow.

3. Legal bases and visibility

Where applicable, processing is grounded in steps requested by the user and performance of the service, legal obligations, exercise of rights, and proportionate legitimate interests in security and operation. Consent is requested separately if a purpose requires it. A wallet signature authorizing a profile or terms is not consent for advertising. Public blockchain records and public website profiles can be viewed by others; a wallet address can identify a person when combined with other information.

We use the wallet and requested public changes to provide the action you ask for. Historical acknowledgment records may support evidence of the earlier release and the handling of disputes; operational logs support delivery, security and diagnosis. A legal duty can require retaining or disclosing particular records. Where a lawful basis or right depends on your location and circumstances, it is assessed under applicable law rather than inferred from a signature.

The retired acknowledgment endpoint no longer publishes wallet status or accepts new signatures. Historical signatures are not exposed through public reading pages. Blockchain events, profiles and links are public, may be indexed by third parties and can link activity across services. Public does not mean anonymous.

4. Service providers

Hosting (Vercel), database infrastructure (Supabase PostgreSQL), configured blockchain RPC providers and your wallet may process data necessary for their functions. RPC requests can disclose an IP address and requested addresses or transactions to the chosen provider. Providers may process data in different countries.

The website runs on Vercel; its directory and historical acknowledgment records use a private PostgreSQL schema in the project's Supabase infrastructure. Public RPC endpoints listed in the network configuration, and any configured server RPC endpoint, receive the blockchain queries they handle. Wallet software receives the selected account, network and messages you ask it to sign. Visiting an explorer or an application link brings you under that service's processing practices.

Repository and deployment infrastructure also support source delivery and operations. A private GitHub workflow keeps daily directory-profile exports for 30 days. That export is a directory recovery mechanism; it is not a backup of legal acknowledgments. We do not represent that all providers process data in one location or that this notice alone supplies a legal mechanism for an international transfer. Mandatory transfer requirements remain applicable.

5. Retention and security

Profiles remain associated with their Deed or app while used by the directory; a new holder can change the website Deed name. Historical acknowledgments are retained as needed to establish the earlier accepted release and exercise or defend rights. Legal retention and third-party blockchain records may limit what can be corrected or erased. We do not promise deletion from immutable blockchains.

Access controls, signature verification and bounded requests protect the service, but no system is risk-free. Independent app operators and wallet/RPC providers determine their own processing and should publish their own notices.

Historical acknowledgments have no automatic time-based deletion in the current implementation. Retention remains subject to the record’s evidential purpose and any applicable legal duty. A replacement profile updates the current directory record, but copies may remain in the 30-day directory exports and third-party caches. Provider request-log retention is controlled by the provider’s settings and policies; no universal log deletion period is promised.

Applicable privacy rights can include access, correction, erasure, restriction, objection and portability. Legal retention limits, verification requirements and response periods remain governed by applicable law. A wallet signature does not waive these rights. You may complain to the competent authority.

Deleting browser data or requesting removal from website storage cannot erase a signed transaction, event or copy held independently by another party. Do not place sensitive information on-chain on the assumption that the website can later remove it.

6. Browser storage and tracking

This website uses localStorage for the theme (voiddeeds-theme), display currency (voiddeeds-currency), wallet transaction history scoped to the release (voiddeeds:<release>:transactions), and cached revenue receipt snapshots (voiddeeds:receipts:<release>:<query>). Local history retains the latest 20 completed transactions and pending transactions. Cached receipt snapshots may be used for up to seven days. Clearing site data resets these preferences and local history, not blockchain transactions. Historical acknowledgment records are retained by the service and are not required for current actions.

Theme and display-currency preferences have no automatic expiry and remain until replaced or cleared. The transaction list includes network, public account, hash, label, status and timing, with transaction details used to recover pending submissions. Revenue snapshots contain public display data, not spending authority. An older snapshot can remain physically in browser storage even after its seven-day reuse window; clearing site data removes it.

The application code does not integrate advertising trackers or an analytics SDK and does not set an application tracking cookie. Hosting, wallet extensions, RPC services and linked websites may have their own logs or storage. Optional browser storage is not a terms-acceptance mechanism; website actions have no acknowledgment requirement.