Browsing Peria never needs an account — no tracking cookies, no ad networks, and the places you collect stay in your own browser. If you choose to create a free account (to keep trips across devices), we store only what you explicitly save: your email, an optional name, an optional home country/region and travel style, and your saved trips and places. Deleting your account erases all of it.
Peria uses your browser's local storage for your theme choice and the spots you collect while browsing a city. Signed out, that data never leaves your device unless you share a plan link yourself. Clearing your browser storage removes it.
Sign-in is by email link or Google, and is only ever offered — never required — when you reach for something that needs it, like saving a trip. With an account we store: your email address, an optional display name, an optional home country/region and travel style (asked once after sign-in, always skippable, and editable or removable any time from the account menu), and the trips and places you choose to save. Sign-in sets one strictly-necessary session cookie (it identifies your session and nothing else — it is not used for tracking or advertising). Sign-in emails are delivered by Resend, our email processor, which handles your address solely to deliver that message. You can delete your account from the account menu at any time; this permanently erases your profile, sessions, saved trips and saved places from our server.
If you subscribe to Peria Pro, payment is handled entirely by Stripe on Stripe-hosted pages — we never see or store your card details, only your subscription's status. The optional "wall tuned to you" setting (off by default, Pro only) reorders the photo wall using nothing but the trips and places you have saved to your own account; that taste signal is computed on the fly, never stored, never shared, and disappears when you turn the setting off or delete your account.
Like any website, our server processes the technical basics of each request (the page asked for, an IP address) to deliver pages and apply per-visitor rate limits. We don't build profiles from this or sell it.
If you use the chat assistant, the messages you type (plus the relevant city context) are sent to our AI provider — currently Google's Gemini API — to generate the answer. Don't put personal details you wouldn't want processed there into the chat. Conversations aren't linked to any identity, and we don't store them after answering.
We use GoatCounter, a privacy-respecting counter, to see aggregate page views (which pages, which countries, roughly). It sets no cookies and doesn't identify or follow you across sites. We also record a handful of anonymous product events on our own server (for example "a wall was viewed" or "a plan was built") — each is just a timestamp, the event name and the city. To understand which communities our visitors come from, when you first arrive we also note the referring site's hostname and any campaign tag in the link you followed, together with a random id that lives only in your browser tab and disappears when you close it. That id is not a cookie, it doesn't follow you across visits or sites, and it is never connected to an account — signed in or out, these events contain nothing that identifies you.
Pages load fonts from Google Fonts, maps from OpenStreetMap/CARTO, and some venue photos from their providers (for example Hot Pepper or Tripadvisor). When you follow an outbound link — to Google Maps, a restaurant page, or a booking site — that site's own privacy policy applies. Some outbound links may be affiliate links, described in our disclosure.
Signed out, we hold essentially nothing about you. With an account, everything we hold is visible in the product itself (your profile, your trips and saved places) and is erased by deleting your account. For any privacy question or request, write to [email protected].
© 2026 Peria · All rights reserved. The site, its design, code, text and curated data are protected; please don’t copy or scrape them.