Trust Center
Trust, security & privacy
This page is maintained by the Wandering Lens team to answer common security and privacy questions about the site. It describes the controls in place today and how we handle the small amount of information visitors share with us. It is not an independent certification or audit report.
What this site is
Wandering Lens is a personal travel journal — long-form trip stories, route guides, and a couple of lightweight planning tools. There are no user accounts, no comments, and no public profiles.
What we collect
The only personal information we store is the email address of visitors who choose to subscribe to the newsletter. We do not ask for a name, phone number, location, or any other detail.
The planning tools (trip cost calculator, itinerary builder) run entirely in your browser. The inputs you type there are not sent to or stored on our servers.
How newsletter signups are handled
When you subscribe, your email is validated and stored in our managed database. Writes go through a single validated server function — direct public write access to the underlying table is disabled. The subscriber list is not readable by visitors and is not shared with third parties.
You can ask us to remove your email at any time using the contact address below; we will delete it from the list.
Hosting & infrastructure
The site is built and deployed on Lovable, with a managed Postgres database and serverless functions provided by the platform. Data is transmitted over HTTPS. We rely on the platform's standard security controls for infrastructure-level concerns (patching, network isolation, encryption at rest).
Cookies & analytics
The site uses only the cookies strictly required for it to function (for example, remembering your light/dark theme preference). We do not run third-party advertising trackers.
Reporting a security issue
If you believe you've found a security or privacy issue, please email xenon.ivybridge@gmail.com with a description and steps to reproduce. We'll acknowledge the report and work on a fix.
Changes to this page
This page is editable content and will be updated when our practices change. Last reviewed: June 2026.