Last updated November 15, 2026

Privacy Policy

BlindSight is a hackathon project running on NEAR testnet. This policy describes what data the app handles, where it goes and how long it is kept. It reflects how the code works today, including its limits.

Summary

  • There are no BlindSight accounts, no cookies, no analytics and no advertising trackers.
  • You are identified only by your NEAR account ID, which is public on the blockchain.
  • Questions are only ever sent encrypted to a verified AI enclave, and the question text isn't kept after your request finishes.
  • Published datasets are encrypted at rest and deleted when you unpublish. BlindSight's server can decrypt them to answer questions.
  • We don't sell or share your data for marketing.

Wallet and payments

When you connect a wallet, the app learns your NEAR account ID. It never sees or stores your private keys; signing happens in your wallet. Your browser reads your balance from a public NEAR RPC node.

Every payment is a transfer on the NEAR blockchain. Transactions, including the sender, receiver, amount and time, are public and permanent. Neither BlindSight nor anyone else can remove them.

To verify a payment, the server looks up the transaction on a public RPC node. It keeps the transaction hash in memory for up to 24 hours to stop the same payment being used twice. Publishing-fee transaction hashes are stored with the vault listing for as long as the vault exists.

Questions and answers

When you ask a question, BlindSight's server:

  1. Combines it with the vault's dataset into a prompt and sends it to NEAR AI Cloud, where the model runs inside an attested hardware enclave.
  2. Encrypts that prompt with Oblivious HTTP to a key held by the verified enclave, so NEAR AI's infrastructure outside the enclave can't read it. If the enclave can't be verified or the encrypted channel fails, the prompt is not sent at all. You get an error, and your payment stays valid for a retry.
  3. To detect attempts to reconstruct a dataset through many narrow questions, it keeps a short record for up to 10 minutes. The record holds keyed hashes of the question and of its words, and whether it looked like an extraction attempt. It is grouped by your account ID and the vault, and separately by a hash of your IP address and the vault. It never contains the question text. The hashing key is random, exists only in that server's memory, and changes whenever the server restarts.

Questions and answers are not written to a database or to logs, and the question text isn't kept after your request finishes. The answer is returned to your browser and not kept on the server.

The publisher of a vault does not see your questions. They can see the payments to their account on chain.

Published datasets

When you publish a vault:

  • Public: the title, description, price, your account ID, the payout account, the publishing-fee transaction and the publish date. These are shown to every visitor.
  • Encrypted: the dataset contents, including the names of the files you uploaded. They are encrypted with AES-256-GCM before being stored in a private Supabase storage bucket.

BlindSight's server holds the encryption key. To answer a question it decrypts the dataset in memory and may keep the prepared copy in memory for up to 30 minutes. The server itself is not an enclave, so you are trusting BlindSight with the contents. Parts of the dataset are sent to the model as described above, and answers are generated from it, so information from the dataset can appear in answers.

Don't publish real personal, medical, financial or otherwise confidential data. Use synthetic or non-sensitive data. By publishing, you confirm you have the right to share the data in this way.

Data in your browser

The app stores a few things in your browser's local and session storage. They are not sent to BlindSight:

  • Your wallet session, kept by the NEAR Wallet Selector so you stay connected.
  • Your recent activity in the marketplace (up to 50 entries: type, amount, vault name and transaction hash), stored per account.
  • A temporary flag that sends you to the marketplace after a wallet redirect.

Disconnecting your wallet ends the session but keeps the activity history. Clearing this site's data in your browser removes all of it.

Server logs

Our server logs record which step of a request ran and any error codes. They are written to exclude question text, dataset contents, file names and answers. Our hosting provider, Vercel, also keeps standard request logs such as IP address, user agent, URL and time, under its own policy.

Third parties

BlindSight relies on these services. Each handles data under its own privacy policy:

ServiceWhat it receives
VercelHosts the app; sees every request to it.
NEAR AI CloudThe prompt (your question plus dataset contents), always encrypted to its enclave.
SupabaseVault listings and encrypted dataset files.
FastNear RPCAccount and transaction lookups, from your browser and from our server.
MyNearWallet, MeteorWhatever you approve in the wallet you choose.
NEARBlocksOnly if you open a transaction or account link.

Retention

DataKept for
Question textOnly while your request is being answered
Anti-probing hashes (in memory, no question text)Up to 10 minutes, or until the server instance restarts
Prepared dataset copy (in memory)Up to 30 minutes, or until the server instance restarts
Used payment hashes (in memory)Up to 24 hours, or until the server instance restarts
Vault listing and encrypted datasetUntil you unpublish the vault
Blockchain transactionsPermanently, on the public NEAR testnet
Browser storageWallet session until you disconnect; activity history until you clear site data

Your choices

  • You can use the landing page and these docs without connecting a wallet.
  • You can unpublish your vaults at any time. Unpublishing deletes the listing and the encrypted file.
  • Because BlindSight has no accounts and stores no profile, there is nothing else tied to you to export or delete, beyond what is listed above. On-chain transactions can't be deleted by anyone.

BlindSight is not directed at children under 13.

Changes and contact

If how the app handles data changes, we'll update this page and its date. For questions or privacy requests, email prosperlinho@gmail.com or open an issue on GitHub.