> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/native-integrations/overview-1/cache-policy.md).

# Cache Policy

Choose how your app reuses pages it has already loaded.

When your app loads a page, it can keep a copy on the device. The next time someone visits that page, the app can show the stored copy instead of fetching it again — which is faster and uses less data.

Cache Policy is where you decide how willing your app should be to do that.

## Set it

Open **Native Features → Cache Policy** and pick one of three modes.

<figure><img src="https://3731994945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlBy5z08zL1UoCwNqmg%2Fuploads%2Fgit-blob-00597d1dd6dbefaa412ce1e06ccaf23078270e1b%2Fnf-cache-policy.png?alt=media" alt="The Cache Policy screen showing Default mode, No cache policy and Cache else network"><figcaption></figcaption></figure>

| Mode                   | What it does                                                                                      |
| ---------------------- | ------------------------------------------------------------------------------------------------- |
| **Default mode**       | The device decides. Pages are reused from cache when they're still fresh.                         |
| **No cache policy**    | Going back can use the cache, but every new page loads fresh from the network.                    |
| **Cache else network** | Reuses cached pages for back and new navigation when available, otherwise loads from the network. |

Click **Save as draft** when you're done.

## Which to choose

**Default mode** suits most apps. It follows the caching rules your website already sends, so pages are reused while they are still considered fresh and fetched again when they are not. If you have not thought about caching, leave it here.

**No cache policy** is the choice when your content changes constantly and customers must never see a stale version — live stock levels, prices that move during the day, a dashboard of current figures. Going back still feels instant, but anything new is fetched fresh. The cost is more loading and more data.

**Cache else network** is the fastest and the most willing to show something slightly old. It suits content that rarely changes: a catalogue, articles, help pages.

{% hint style="info" %}
How long a cached page stays fresh is decided by your **website**, not by Twinr. Your server sends cache headers with each page, and the app respects them. If pages are going stale too slowly or too quickly, that is where to adjust it.
{% endhint %}

{% hint style="warning" %}
If customers report seeing old prices or outdated stock, check this setting before looking anywhere else. **Cache else network** will happily show a cached page even when a fresher one exists.
{% endhint %}

## Logged-in customers

Caching stores pages, not sessions. Someone signed in stays signed in whichever mode you choose.

That said, a page cached while signed in can briefly reappear after signing out. If your site shows account details on otherwise public pages, **No cache policy** avoids that entirely.
