Privacy policy

Viamente is an AI travel planner built by Lygge Studios ApS, based in Copenhagen, Denmark. Questions about this policy or your data: write to peter@viamente.ai.

Viamente is currently in early access. Today it stores the travel plans you create and the messages you exchange with the planning assistant. Additional capabilities — collaborative planning, bookings, mobile companion — are on the roadmap. This policy covers all of them as they ship.

• Account — your email address, an optional display name, and the identifiers we receive when you sign in via magic link or Google. A session cookie (viamente_session, HttpOnly) keeps you logged in.
• Plans and conversations — the trip plans you create (destinations, dates, accommodation choices, notes) and the messages you send to the planning assistant. Your messages are transmitted to Anthropic to generate replies (see §4).
• Profile context — preferences that the assistant infers from your conversations (e.g. "travels with kids", "prefers boutique stays") are stored in a private ledger so subsequent plans get smarter for you specifically. You can ask for the contents of this ledger or its deletion at any time (see §8).
• Diagnostics — server logs (HTTP method, path, status code) are retained for roughly 30 days for debugging and abuse prevention.

• Cloudflare, Inc. — Workers, D1 (SQLite), and Email Sending (outbound transactional email such as magic links). Cloudflare is our primary processor; data is stored in EU regions where Cloudflare supports it.
• PostHog Cloud EU (eu.i.posthog.com) — product analytics. Pageviews and autocaptured clicks only; session recording is disabled. PostHog cookies (prefixedph_) are first-party and used to stitch a single visitor's session together. Your distinct ID is bound to your Viamente user ID only after you sign in.
• Anthropic, PBC — large-language-model inference for the planning assistant. Your conversation messages are transmitted to Anthropic's API to generate replies. Anthropic's API platform does not use API inputs or outputs to train its models.
• Google LLC — only if you choose "Continue with Google" to sign in. We request theopenid email profile scopes solely to look up or create your Viamente account and to show your name and email in the app. We do not request any other Google scopes (no Contacts, no Calendar, no Tasks).

• viamente_session — essential, HttpOnly, keeps you signed in.
• ph_* — set by PostHog for analytics (see §4).

We do not set advertising cookies and do not embed third-party trackers beyond PostHog. Visitors in the EU / EEA / UK / Switzerland see a banner the first time they arrive explaining this; dismissing it stores a single flag in your browser's local storage so the banner doesn't reappear.

Your plans persist until you delete them. You can delete a plan from your dashboard at any time. To erase your entire account and all associated data, email peter@viamente.ai — we process account erasures within 30 days and confirm in writing once complete. Erasure removes:

• Your plans, messages, and profile context from our database;
• Your PostHog person profile and all associated events;
• Any session, magic-link, or API tokens tied to your account;
• Your users row, after the cascading deletes above.

Logging out calls posthog.reset() so subsequent activity on the same browser is not associated with your identity even before account deletion.

Under the GDPR and equivalent data-protection laws, you have the right to access, rectify, erase, restrict the processing of, port, and object to the processing of your personal data. Write to peter@viamente.ai and we will respond within 30 days. You also have the right to lodge a complaint with your local data-protection supervisory authority.

Viamente is not directed at children under 16 and we do not knowingly collect personal data from them.

Cloudflare and PostHog are US-headquartered companies whose EU infrastructure we use to keep data in the European Union where possible. Anthropic processes API inputs in the United States. Where transfers outside the EEA occur, they rely on the EU Standard Contractual Clauses or an equivalent transfer mechanism.

We will update this page when our practices change. Material changes will re-prompt the cookie notice in your browser so you see them on your next visit.