> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shieldhq.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Accessing Content

> How recipients can access content shared via SHIELD

# Accessing Content

When someone shares content with you via SHIELD, you'll receive a secure link. This guide explains how to access that content.

## What You'll Need

* A web3 wallet (MetaMask, Coinbase Wallet, Rainbow, etc.)
* The wallet address must match the one the sender authorized
* Some ETH on Base for the access transaction (usually under \$0.01)

## Access Process

### Step 1: Open the Link

Click or paste the secure link into your browser. It will look like:

```
https://app.shieldhq.xyz/r/policyId#def456
```

<Note>
  The decryption key after `#` is never sent to any server. It stays in your browser.
</Note>

### Step 2: Connect Your Wallet

1. Click "Connect Wallet"
2. Select your wallet
3. Approve the connection

### Step 3: Authenticate with SIWE

You'll be asked to sign a message like:

```
shieldhq.xyz wants you to sign in with your Ethereum account:
0x...

Sign this message to prove you own this wallet.
```

<Info>
  This is **not** a transaction. You're not spending ETH, just proving ownership of your address.
</Info>

### Step 4: Sign Access Transaction

If authentication succeeds, you'll need to sign a transaction to log your access on-chain:

<Warning>
  This **is** a transaction that costs a small amount of gas (usually under \$0.01 on Base).
</Warning>

### Step 5: View Content

Once the transaction confirms:

* **Files**: Click "Download" to save the decrypted file
* **Messages**: The decrypted text displays in the browser

## Troubleshooting

<AccordionGroup>
  <Accordion title="'Unauthorized wallet' error">
    This means your connected wallet address doesn't match the recipient address set by the sender.

    **Solution**: Switch to the correct wallet or ask the sender to create a new link for your current address.
  </Accordion>

  <Accordion title="'Policy expired' error">
    The link has passed its expiration time.

    **Solution**: Ask the sender to create a new link.
  </Accordion>

  <Accordion title="'Max attempts reached' error">
    The content has been accessed the maximum number of times allowed.

    **Solution**: Ask the sender to create a new link.
  </Accordion>

  <Accordion title="'Policy not found' error">
    The policy ID doesn't exist on-chain.

    **Solution**: The link may be malformed. Ask the sender to resend the complete link.
  </Accordion>

  <Accordion title="Transaction fails">
    Common causes:

    * Insufficient ETH for gas
    * Network congestion
    * Policy became invalid between check and transaction

    **Solution**: Ensure you have enough ETH for gas. If the problem persists, the policy may have just expired or reached max attempts.
  </Accordion>

  <Accordion title="Decryption fails">
    This is rare but can happen if:

    * The URL fragment was truncated (copy-paste error)
    * The IPFS content was unpinned

    **Solution**: Ensure you have the complete link including everything after `#`. If the issue persists, the content may no longer be available on IPFS.
  </Accordion>
</AccordionGroup>

## After Accessing

Once you've accessed the content:

1. **Save the file/message** - SHIELD doesn't store unencrypted content for you
2. **Check your access log** - Visit your profile to see all content you've accessed
3. **Rate the sender** - Optional feedback helps improve the ecosystem

## Privacy Notes

* Your access creates an **on-chain record** that cannot be deleted
* The **timestamp** of your access is permanently recorded
* The **success/failure** status is logged
* Your **wallet address** is visible on-chain

This transparency is by design—it creates an audit trail that benefits both senders and recipients.