Where your data lives
Separate local files, cloud persistence, browser preferences, and public projections.
5 minIn this guide
Local boundary
Local screenshots and history stay on this computer. Browser preferences such as view, language, theme, and delivery settings stay in this browser unless a signed-in feature explicitly syncs them.
Cloud boundary
Cloud account records, capture metadata, and images are stored in the hosted service. Stripe processes billing, and the email service sends login codes. The Subprocessors page is the current list of external service roles.
Confirm which store actually holds each capture
Local screenshots are stored as PNG files, and session history stays on this computer. Theme is a browser-only preference on the Interface tab. Language and Capture delivery switches live in the same settings dialog; a signed-in cloud account can keep those delivery choices in the hosted workspace.
Hosted captures keep metadata and images in the cloud service. Unlisted viewers and Markdown copies are available without a workspace session. Email sign-in codes expire, and the form does not reveal whether an account exists. The Subprocessors page names the current hosted providers, and Pinar does not receive full card details. Current policy versions are published on the legal pages.
- If local history cannot open, Pinar recovers a usable catalog on this computer instead of crashing.
- Open a hosted screenshot from its share page or Markdown viewer; a missing image shows not found rather than account details.
- In settings, confirm Interface theme locally, then distinguish Capture delivery switches from cloud-synced delivery choices when signed in.