Pinar
HomePlansWhat’s newHelp
Sign in
⌘ K

Get startedCaptures and pinsAI agentsProjects and collectionsCloud and plansPrivacy and data
Get started
Captures and pins
AI agents
Projects and collections
Cloud and plans
Privacy and data
Where your data livesAutomatic sanitizationLocal security and recoveryTelemetry, consent, and policies
Help/Privacy and data

Where your data lives

Separate local files, cloud persistence, browser preferences, and public projections.

5 min
Visual example: Local Server keeps history and screenshots on this computer and does not require hosted-service legal acceptance.

In this guide

  1. 1Local boundary
  2. 2Cloud boundary
  3. 3Confirm which store actually holds each capture
1

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.

2

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.

3

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.
Still need context?See all in category

On this page

Local boundaryCloud boundaryConfirm which store actually holds each capture
Support Fair Source development

Prefer supporting public source development directly? Sponsor on GitHub or buy a coffee.

Buy Me a CoffeeSponsor on GitHub
Pinar·© 2026·Pinar v0.3.6
Terms of ServicePrivacy Policy