What Vealth handles, where it goes, how to ask for deletion.

This page is for anyone using Vealth: it says what we keep, where it goes and how to ask for deletion. Vealth is run by EcoWealth Corporation, a Wyoming corporation based in Los Angeles. We write in plain English. There are no ad networks and no cookies set by us. One outside script does load on every page: a privacy-first page-view counter from Cloudflare, which counts visits without cookies and without following you across sites. Two more outside companies come in only if you press a button that needs them: Coinbase, for the face or fingerprint sign-in, and Stripe, only to connect a payout account to be paid by card. When you pay a worker with your own card or bank, that payment is between you and them: it does not go through Vealth, and Vealth loads nothing for it. One honest caveat up front: when work settles, a public, permanent onchain record of the settlement is written. That permanence is the point of a provable receipt, and it means some records cannot be deleted by anyone. This is operational guidance, not lawyer-reviewed legal advice.

Only what the work needs, and only when you act.

Vealth is a public board of jobs: you claim one, do it, and prove it. Here is every piece of information the site touches, and when.

  1. Wallet address and signature (claiming or bidding) When you claim or bid on a job, you approve a short message with your face or fingerprint sign-in (a Coinbase Smart Wallet, made for you in a small Coinbase window), or with a wallet app you already have. That approval is called a signature. We receive your wallet address and the signature, to prove the wallet is yours. We check the signature when it arrives and do not keep it. To stop it being used twice, we hold a one-time marker in memory for five minutes, then it is gone. So no signature of yours is on file here. We do keep the wallet address, because the record is about that wallet. Your wallet’s secret recovery words and private key never leave your wallet, and a signature cannot spend your money.
  2. Proof evidence (submitting a completed job) The proof a job names, usually photos with your phone’s location (GPS) and timestamp, plus short notes. It is not public: the public job page shows only that a photo exists and that a location was attached. Never the image, never the coordinate. The evidence itself opens only for the person reviewing that job, after they approve with their own signature. The person who submitted it cannot review their own work. On the jobs Vealth wrote from its own library, that reviewer is Vealth today; on a job a person posted, it is that person; and where a payer’s offer took the acceptor seat, it is that payer. Follow the safety rules: public spaces, or a private frontage only with the owner's written consent; no faces, no license plates, no photos into homes or cars.
  3. Founder-review email (the no-wallet path) If you claim by email instead of signing, your mail client sends the job ID and the wallet address you type to [email protected]. You choose exactly what to send; the Vealth server never sees the message.
  4. Emailed draft (/start.html) The place / problem / proof you type stay in your browser only. Nothing is sent or stored on a server until you press "Email for review" or "Copy draft job"; then it goes only where you send it.
  5. A stop signal (only when a post or a claim stops on your screen) If the sign-in or the signing step stops on your screen (the face or fingerprint sign-in times out, you close the window, a script does not load), the page sends one small signal to vealth.net so we can see where people get stuck. It carries exactly two things: the name of the step, from a fixed list of fifteen (for example signin_timeout or sign_cancelled), and the language the page is in (en, es, pt, fr or sw). It never carries anything you typed, your wallet address, your place, a photo or your name, and our server refuses a signal with anything else in it. What we keep is one line per signal: the day, the step and the language, nothing that says who sent it. It goes at most once per step per visit, and nothing is sent when you only read. Like every request to this site, it also passes through the web server’s ordinary request log, which the count we keep is not made from.

We do not ask for your name, phone number, or date of birth. The board stores no cookies of ours and needs no account or signup to read it.

One outside script on every page, and two outside companies only if you act.

  1. Typefaces: served by us, not by Google Inter, Fraunces and IBM Plex Mono are hosted by us at vealth.net/fonts/. Your browser does not contact Google or any other company to show them, so no one else sees which pages you open.
  2. Cloudflare (serving + Web Analytics beacon) vealth.net is served through Cloudflare, which adds its privacy-first Web Analytics page-view counter at the edge. Your browser loads that script from static.cloudflareinsights.com and sends a page-view count to cloudflareinsights.com. It counts page views without cookies and without tracking you across sites. No ad network, no session recording, no cross-site profile.
  3. Coinbase (only when you press a button that signs, and choose the face or fingerprint sign-in) Pressing Claim, Vote, Send proof, Post, Fund or the sign-in under My work loads Vealth’s own copy of Coinbase’s wallet code from vealth.net, and the sign-in opens in a small window from keys.coinbase.com. That window, and the wallet code’s own calls to other coinbase.com addresses, are Coinbase’s: what Coinbase receives is covered by Coinbase’s own privacy notice, not by this page. Vealth never sees or keeps the wallet’s key. If you use a wallet app you already have, none of this loads. A page where you only read loads nothing from Coinbase.
  4. Stripe (only to connect a payout account, or if paying Vealth by card reopens) Paying Vealth by card is closed. A card you use to pay a worker directly is your own card with your own bank: that payment never goes through Vealth, and no page here loads anything from Stripe for it. If paying Vealth by card reopens and you choose it, your browser leaves vealth.net and goes to Stripe’s own checkout page, where the card number is typed. Vealth never sees the card number. If you connect a payout account to receive card pay, you are sent to a Stripe page for that too. What Stripe keeps is covered by Stripe’s own privacy notice, not by this page. No page loads anything from Stripe unless you press to connect a payout account or, if it reopens, to pay Vealth.

That is the whole list. No Meta pixel, no Google Analytics, no marketing CRM, no third-party form host.

Onchain (public, permanent) or on our server.

  1. Public onchain receipts (Base) When a job settles, the settlement (your wallet address, the job, the payment, the proof reference) is written to the Base blockchain. This record is public and permanent: anyone can read it, and no one (not you, not us) can edit or delete it. Onchain records are permanent, and anyone can check that half without us. The evidence behind the receipt, the photos and the review, is kept in our own records, and those records are not permanent yet. Do not put anything you need kept private into a claim you intend to settle.
  2. Claim and proof records (our server) Claims, bids, and submitted proof bundles are held on the same single server that serves vealth.net, so they can be reviewed.
  3. Email (the founder's inbox) Anything you email lands in the founder's inbox at [email protected] and stays there until deleted. The Vealth server does not see or store it.

Onchain: everyone. On our server: the founder, and nobody else.

Onchain records are public by design; that is the point of a provable receipt. On our server, Brandon Kelly, EcoWealth's founder, is the only person with administrator access to the server and the only person reading [email protected]. There is no team, no contractor with backend access, no exported-to-spreadsheet pipeline.

We do not sell or share your data.

Wallet addresses, proof bundles, and emails are not sold, traded, rented, syndicated to a partner network, fed to a marketing automation tool, or used to train a public AI model. The only outbound use is the founder reviewing your work and replying from that inbox. If a future service ever changes this, the change will be written on this page first.

Data on our server: email to delete, the default answer is yes. Onchain: cannot be removed.

Email [email protected] with the wallet address or email you used. The default response is to delete the matching claim, proof, or email record from our server and confirm within one business day. What we cannot delete is a public onchain receipt: the blockchain is permanent and no one can edit it, which is exactly why an outside receipt is trustworthy. Correction of records on our server follows the same path.

Privacy questions go to the same inbox.

There is no privacy desk. Email [email protected] with a subject line that starts with "privacy" and the founder will reply within one business day. See also the Terms and Safety pages.

This page is operational guidance (what the site actually does, in plain English), not lawyer-reviewed legal advice. It is not a comprehensive privacy policy under GDPR, CCPA, or any other regulatory framework. If you need a formal legal review before submitting commercial data, ask first and the founder will reply about what the current practice can and cannot promise.