What this covers
This policy covers the Snapfall websites (snapfall.lol, www.snapfall.lol and app.snapfall.lol), the owner dashboards, and the customer links an operator sends for a job. It does not cover the Arc blockchain, Circle’s wallet services, or a wallet app you bring yourself. Those are run by others under their own policies.
What we do not collect
Visitors do not need an account. The sites run no analytics, advertising or tracking scripts and set no tracking cookies. We do not sell or rent personal information, and we do not build profiles of visitors.
Public blockchain data
Most of what the dashboard shows is read from the Snapfall contracts on Arc: wallet addresses, amounts, job ids, content hashes and transaction hashes. That data is public, anyone can read it, and it cannot be edited or deleted, by us or anyone else. If you fund, deliver or accept a job, your wallet address and the amounts become part of that public record. Work and job details stay off chain. Only their hashes are recorded.
Your browser
The sites keep a few small values in your own browser. Apart from the owner session cookie, none of them is sent to us.
| Theme | snapfall-theme: whether you chose light or dark. |
|---|---|
| Passkey wallet | The id of a passkey you created to pay for a job, so the page can find it again. The passkey itself stays on your device. |
| Bridge progress | If you bring USDC from another chain, the step a transfer has reached, so a reload can resume it. |
| Owner session | Only for the operator: an HttpOnly, same-site cookie set when they sign in to the owner dashboard. The browser sends it with each request to that dashboard so the server can recognise the owner. It expires on its own. |
You can clear all of these at any time from your browser’s settings.
Job records
When an operator takes a job, their own Snapfall daemon keeps the working record: the job’s description and terms, the customer’s wallet address, approvals, payment intents, delivery hashes and an event log. The daemon runs on the operator’s machine or on a private server the operator controls. A customer link opens one job and nothing else.
If the operator turns on the optional AI scoper, the text of a job request is sent to Anthropic, as written, to draft the scope. Anything typed into that text goes with it, so do not put private details in a request. Keys and stored job state are not sent. It is off unless the operator configures it.
Services we rely on
| Vercel and Render | Host the sites and the owner daemons. Like any web host, they log requests (IP address, browser, page) to run and secure the service. |
|---|---|
| Arc RPC providers | Answer the chain reads the dashboard makes, such as Alchemy or Arc’s public endpoint. |
| Circle | Provides the passkey wallet you can pay with, and the operator’s developer-controlled wallet. Circle’s privacy policy applies to those services. |
| Anthropic | Only if the operator turns on the AI scoper, as above. |
How long it is kept
Chain data is permanent. Hosting logs are kept for as long as each host’s own retention allows. A job record is kept by the operator’s daemon for as long as the operator needs it to account for the job, and can be deleted by the operator at any time.
Your choices
To ask what we hold about you, or to have a job record corrected or deleted, write to support@snapfall.lol. We will tell you what we can and cannot do. Chain data is outside anyone’s control. The service is not meant for anyone under 18.
Changes and contact
If this policy changes, the date at the top changes with it, and the history is public in the source repository. Questions go to support@snapfall.lol. See also the terms.