Accompany, on!Back to home

Privacy policy

Accompany, on! uses your signed-in session and trip membership to control access to your planning data. Places, outings, bookings and other entries you save follow the application’s existing trip and visibility controls.

Sign-in options

You can use available Google, email or ChatGPT sign-in options. Firebase Authentication handles Google and passwordless email sign-in. We store your verified account identifier, email address and display name to recognize your account. Google and email methods linked to the same Firebase account share that account. ChatGPT remains a separate identity. Matching email addresses alone never grant access to another traveler’s trips; restoring a traveler profile requires its valid invitation or personal code.

Email sign-in sends a single-use link through Firebase to the address you enter. You must confirm that email when opening the link on another device. Essential cookies and Firebase browser storage keep you signed in; the requesting browser also remembers the email and return page so you can continue your draft or invitation. Our server stores hashed session tokens and checks verified Firebase proof when renewing a session. Signing out clears this browser’s sign-in. Sign-in pages are excluded from usage analytics.

ChatGPT plugin

Connecting the Accompany, on! plugin uses Sites OAuth and your verified ChatGPT identity. Tool calls follow the same trip membership and visibility controls as the website. OpenAI receives the tool results needed for your request, which can include accessible saved places, itineraries, tasks, booking records and expense details. Changes you approve are saved through Accompany, on!’s existing services. Disconnecting the plugin stops that connection; it does not delete previously saved planning records.

Site administrators can stage catalog photos with their source, attribution and reuse permission, and review catalog import plans before committing or publishing. We store the reviewed plans, source identities, image provenance and per-item job receipts to reconcile retries and report progress. Staging alone does not publish a new catalog photo. Public catalog records include the published photo and attribution. These catalog operations do not rewrite travelers’ saved itineraries.

Website AI and live collaboration

Website AI features send your request and the context used by that feature to OpenAI. Depending on the feature, this can include search text and place details, selected planning cards, or shared trip details, traveler names, requirements, proposals, comments and cost records. OpenAI’s processing is described in its Privacy Policy.

Hosting and storage providers process account and planning records needed to operate the service. When live collaboration is enabled, Ably receives account and trip identifiers, presence and update messages needed to deliver it.

Retention and deletion

Saved account, trip and shared planning records have no scheduled age-based deletion. Completing or archiving a trip, signing out or disconnecting the plugin does not erase them. Available removal controls depend on the record and your permissions. Some removals retain hidden records, revision history or recovery copies. An organizer can permanently delete a trip and its scoped database records; associated file cleanup can remain pending if storage cleanup fails.

Catalog drafts, publication history, source and photo provenance, staged assets and import receipts have no fixed automatic deletion period. They support recovery and prevent duplicate or stale writes. Archiving a catalog entry removes its current publication, but an image published previously can remain available to keep existing saved copies working. Uncommitted catalog import previews expire after 24 hours; expiry does not delete the stored preview, and already admitted jobs can still resume.

Website sample-account access and plugin test mode last 24 hours. Expired plugin test-mode selections remain recorded until you explicitly renew, replace or disable them, so expiry cannot silently switch to your personal account. These access limits do not delete the shared sample records. Contact Support to ask about retained records or request deletion of your account data.

Usage analytics

Usage analytics is enabled by default. We use Microsoft Clarity to understand how people use Accompany, on! through clicks, scrolling, heatmaps and session replays, including public pages and signed-in planning screens. Clarity receives page URLs and titles, referring pages, browser and device information, and interaction data. Analytics cookies can connect visits into sessions. We send a denied consent signal for advertising storage.

Page content is masked for recordings, including text and form input. Masking does not hide all metadata: URLs and page titles may contain trip names or other information. We do not send account names, email addresses or custom user identifiers to Clarity’s identity API. Microsoft’s processing is described in the Microsoft Privacy Statement.

We also record a small set of first-party events when a journey form or public plan is opened, submitted or saved. These events use a random browser-tab session identifier and contain no account, trip or place identifiers, names, URLs or form content. The session expires after 30 minutes without a recorded event and is cleared when analytics is turned off or a private area is opened. We use these events to understand activity and the steps people take in the admin analytics dashboard. A short-lived, hourly network-address hash is used separately to limit abusive requests and is not attached to events.

First-party events older than 90 days are excluded from reports. Older events are removed in batches when new events arrive or an administrator opens analytics, so removal may occur later if the service is inactive. Expired request-limit records are removed when subsequent events arrive.

Admin pages, private support conversations, sign-in pages, and invitation entry pages are excluded from Clarity collection. The analytics setting for other pages stays unchanged when you use these private areas.

Use Analytics privacy at the bottom of the page to turn analytics off or back on. A saved opt-out is always respected. Turning analytics off stops first-party event collection, clears the tab’s analytics session and Clarity’s first-party cookies, and reloads the page to stop collection. Your choice is saved in this browser; changing it also updates other open tabs. Local development and preview domains are excluded.

Google place search

When you request a Google place search, Accompany, on! sends the search text, city or area and trip destination to Google Maps Platform. Selecting a result sends its Google place ID to retrieve details and an available photo. Google does not receive your session cookie or other trip records through these requests.

Place searches and details may reuse cached Google information. The displayed checked date records when that information was retrieved, and you can explicitly refresh it. Photos use temporary references and media links. Inspecting a place does not add it to your trip. When you explicitly add a place, its identity, name, location, source and checked details are saved with your trip. Booking locations remain drafts until you save the booking. Loading photos and contributor avatars makes requests to Google image services. Opening a source or venue link takes you to that provider’s website.

The Google Privacy Policy applies to Google’s processing of this information and is incorporated into this policy. Avoid entering private booking references, document contents or other sensitive information in a place search.

Terms of use