Privacy Policy

Updated 18 September 2026

This page describes how the current private plotpace.com planner handles your information.

Information we store

When you sign in, we store your provider's account identifier and any name or email it supplies. Linked accounts point to the same plotpace.com profile. We never receive or store your provider password, and do not keep provider access or refresh tokens in your session.

We also store the personal details and travel preferences you choose to save, trip plans, traveler details, uploaded trip images and your per-trip panel preferences. Profile email addresses do not automatically link accounts or grant trip access.

How information is used and shared

We use account identifiers to sign you in, link accounts you explicitly authorize and apply trip permissions. Profile details and preferences are stored for your use in the planner. They are not automatically copied into a trip.

Linked travelers can see information shared in their trips according to their role. System administrators can view registered account names, emails and identifiers and manage access; administrator status alone does not grant access to private trip details. The person operating the service can access its database, logs and backups for maintenance.

Sign-in providers

Your chosen provider receives your sign-in request and handles authentication under its own privacy policy. Only configured providers are offered. Google, Apple and Microsoft use OpenID Connect; Facebook uses OAuth and its profile API. Each linked provider supplies a separate identifier.

Place search and trip maps

When Google Maps lookup is configured, stop searches, route endpoint place identifiers and selected place identifiers are sent to Google through this server. We store the stop name and region you confirm and its Google place ID. Google processes lookup requests under its Privacy Policy.

When you display a trip map, Google receives the mapped coordinates and an image request from your browser. We temporarily cache place coordinates for less than 30 days to reduce repeated lookups. Map images are served by Google under its terms and privacy policy.

Accommodation searches send your destination or selected map area and lodging query to Google. Comparing shortlisted Google properties requests their current details. These searches do not send trip dates or check availability. The interactive map loads Google Maps in your browser. We retain your authored shortlist names, notes, public property links and Google place IDs, not provider rating or photo snapshots. Shortlists are shared within their trip and included in exports; your personal search defaults are not exported. Manual property links are opened only when you choose them.

Cookies and diagnostics

When leaving the editor for accommodation research, unsaved core holiday fields can be retained in this browser tab’s session storage for up to 24 hours so they can be restored on return. Closing the tab clears its session storage.

Essential cookies maintain your sign-in session, protect forms and verify sign-in callbacks. This application does not include advertising or third-party analytics tracking.

Operational logs record requests, sign-in outcomes, interface actions, validation outcomes and browser failures to help diagnose problems. Interface diagnostics do not include typed values, trip names, notes or image contents. Normal authentication logs omit email addresses; when authentication debug logging is enabled, logs can include account identifiers and email addresses. Logs and database backups are stored by the service operator.

Storage and retention

Data is stored in the PostgreSQL database of this instance. Records remain until removed by the relevant application tools or operator. Deleted records can remain in retained backups until those backups expire. Backup retention is configurable; no fixed deletion period is promised here.

Your choices

You can review and update your personal information in About Me. Contact the person who provided your access to request a copy of your information, correction, account removal or assistance with a privacy concern. Shared trip data may also concern other travelers and needs to be considered with the trip owner.

Only provide information needed for your planning. Avoid putting sensitive personal information in free-text travel notes.