Cookies & similar technologies

The short version: TripPortfolio’s marketing site at tripportfolio.ai does not set any cookies. We measure aggregate traffic with Plausible Analytics, a cookie-less, privacy-first analytics tool. That is why you do not see a cookie banner on this site — we do not need your consent because we are not setting cookies that would require it.

The authenticated TripPortfolio product (the advisor dashboard at app.tripportfolio.ai and the studio editor) uses one short-lived first-party session cookie to keep you signed in, plus browserlocalStoragefor client-side editor state. Those are described below in detail.

1. What “cookies” means here

For this page, “cookies and similar technologies” covers HTTP cookies set by the server, cookies set by JavaScript on a page, browserlocalStorageand sessionStorage, IndexedDB, and any tracking pixel or fingerprinting technique that tries to identify a browser across sessions. We are deliberate about which of these we use and why.

2. The marketing site (tripportfolio.ai)

The pages on this domain — the homepage, pricing, demo and trial sign-up forms, blog, legal pages, and the rest of the public site — do not set or read any cookies. The only third-party script we load is the Plausible analytics tag, which counts page views and a small set of clearly named custom events (for example “Trial CTA clicked” and “App download clicked”). Plausible does this without setting cookies and without storing any personal data, IP addresses, or device identifiers in a way that can be used to identify or track an individual. Plausible publishes the technical details of its data collection in its data policy.

If you submit the demo or trial form, the form posts to our API and we do not set a cookie as part of that flow. The redirect into the dashboard after a successful trial sign-up is what creates the session cookie described below.

3. The product (app.tripportfolio.ai and the studio)

When you sign in to the advisor dashboard or the content studio we set a single first-party session cookie named tripportfolio.session. It contains a signed identifier that maps to your session on our server, is markedSecure and HttpOnly, and is SameSite=Lax. The cookie is strictly necessary to keep you signed in; without it you would have to re-authenticate on every page load. We do not need consent for strictly necessary cookies under the GDPR e-Privacy framework.

The studio editor uses browser localStorage to remember which post you were last editing, your editor theme preference, and other local UI state. None of that information is sent to our servers and you can clear it at any time from your browser’s site settings.

4. The mobile app

The TripPortfolio traveler mobile app does not run in a browser and therefore does not set cookies in the traditional sense. It stores your authentication token in the operating system’s secure storage (Keychain on iOS, Keystore on Android) and caches trip data and documents for offline access in app-private storage. You can revoke that storage by signing out or by uninstalling the app.

5. What we do not use

We do not use third-party advertising cookies, cross-site tracking pixels, social-network re-targeting tags, session replay tools, or browser fingerprinting libraries on either the marketing site or the authenticated product. We do not load Google Analytics, Facebook Pixel, LinkedIn Insight, Hotjar, or similar tools. If a future product surface requires a new category of cookie or storage we will update this page and surface a clear consent flow before turning it on.

6. Managing cookies in your browser

You can block, delete, or restrict cookies and local storage from your browser’s settings. Blocking the session cookie described above will sign you out of the product and prevent you from signing back in until you re-enable it.

7. Questions

If you have a question about how we use cookies or similar technologies, email privacy@tripportfolio.ai. For the broader picture of how we collect and use data see our Privacy Policy.