Privacy Policy

This is a testnet demo

GoHealthMe runs on the Arc testnet. All USDC here is test USDC with no real monetary value. Nothing on this site can pay you real money or cost you real money.

Signing in creates a wallet

When you sign in with your email, Dynamic (a Fireblocks company) creates an embedded wallet for you on Arc. From that step we hold your email address and your wallet address.

Your handle is public on purpose

Claiming a handle is optional. If you do, your @handle, the emoji you pick, and your public page at /u/your-handle become visible to anyone. That page shows your verified wins and payouts, never the health category behind them. Handles are stored in our database (Supabase) and are public by design.

Challenges and feedback

If you create or accept a challenge, we store its metadata in Supabase: an invite token, the pool id, an optional label for who the challenge is for, and an optional message. If you leave feedback, we store your rating and your message.

One thing to be clear about: the health goal text you write when you create a pool or a challenge (for example, "lose 10 lbs") is written on-chain in the pool's goal description, not just in our database. See the on-chain section below.

The Ask helper sends your question to Google

When you type a question into the in-app helper, that question is sent to Google's Gemini model (via Vertex AI on Google Cloud) so it can answer questions about how the app works. Only the text you type is sent. We do not send your health data, your pool activity, or your wallet address.

Document proof stays inside a secure enclave

When you verify a goal by uploading a document (a lab result, a flu-shot record, a screening result), the file is sent to a confidential trusted execution environment (a secure enclave) so the verification model can read it. Only the signed yes-or-no verdict leaves the enclave. The document itself is not written to our database or to the blockchain.

Wearable data is handled differently, and we want to be straight about it

If you connect a wearable through Junction (WHOOP, Oura, Fitbit, or Garmin), the health summary we pull to check a streak passes through our own server (hosted on Vercel) before we compute the result. It does not go through the secure enclave.

So the "nobody ever sees your health data" claim is true for the document path and not for the wearable path. We do not write wearable summaries to the blockchain, but our server does handle them to run the check. If that matters to you, use the document path instead of connecting a wearable.

Some things are public and permanent by design

GoHealthMe settles on the Arc testnet blockchain. Wallet addresses, pool activity, payouts, and the goal text you write when you create a pool are recorded on-chain. Blockchain records are public and, by their nature, permanent. We cannot edit or delete them. Do not put anything in a goal description that you would not want to be public forever.

Who processes your data

We rely on the following third parties to run the demo. Each is named so you can read their own policies:

• Dynamic (a Fireblocks company) - email sign-in and embedded wallets
• Circle - the agent wallet and USDC settlement
• Supabase - our database (handles, challenge metadata, feedback)
• Google Cloud / Vertex AI - the Gemini model that answers helper questions
• Vercel - hosting for the app and its server
• Arc testnet - the public blockchain where pools settle
• Junction - wearable summaries, only if you connect a device

How long we keep it

We keep off-chain data (handles, challenge metadata, feedback) until you ask us to delete it, or until we reset the testnet. Testnet data may be wiped at any time. On-chain data is permanent and outside our control to delete.

Contact

This demo is operated by Meowteam6. To ask a question or request deletion of your off-chain data, email andre102599@gmail.com (contact address to be confirmed).