1. Who handles your data
Compass is operated by VLADISLAV PIDGIRNER, an individual based in Kyrgyzstan. Compass is a travel planning service. This policy covers the Compass mobile application, web experience, and related cloud features.
For privacy questions, contact support@compath.world.
2. Data we handle
Reviews, when you use this feature: your public display name, rating, text, self-reported visit date and selected photos; internally, account linkage, reports, blocked authors and moderation decisions. Your email and internal account ID are not shown with reviews. Photo metadata, including GPS, is removed before upload. Approved contributions are visible to other users. You may delete a review; account deletion removes linked reviews and photos. Previously issued photo links may remain valid for up to five minutes. File deletion is retried after failures; backups follow this policy’s retention schedule. For anti-spam protection, action type, time and account linkage are retained for up to 48 hours while cleanup is operating normally, not for advertising analytics. During an outage, these records remain until the next successful cleanup.
- Account data: user identifier, name, and email received when you sign in with Apple, Google, or another available provider. The profile editor lets you change your name and optionally choose an avatar. We store a resized photo without GPS or camera metadata, not the original library file. Your avatar is private to your account, is not published with reviews, and is not sent to partners. Removing the photo or account deletes the current avatar; backups follow this policy’s retention schedule.
- Trip content: cities, dates, itineraries, saved and visited places, accommodation, transport, and eSIM preferences.
- Location: used with your permission for nearby discovery, routing, city selection, and emergency coordinates.
- Preferences: language, selected city, permissions, and notification settings.
- Technical data: error and security logs required to protect and operate the service. Server authentication sessions contain an IP address and client information (user agent).
- Web analytics: aggregated page views, referrer, country or region, device type, browser, and performance measurements. Compass uses Vercel Web Analytics and Speed Insights without third-party advertising cookies. Compass removes query parameters and URL fragments before sending events; email, account identifiers, and trip content are not added to analytics events.
- Partner handoffs: selected provider, platform, category, city, and time. A shared source label is the same for handoffs from the same category, city, and platform to the same provider; it does not identify a person or device. Compass partner analytics does not store account, installation or trip identifiers, search dates, or precise coordinates. Partners may return booking status and commission records for source-level revenue reconciliation.
Compass web maps use OpenFreeMap and OpenStreetMap data. Viewing maps sends map tile requests and your IP address to the provider; walking/driving route requests send the selected coordinates to OSRM/FOSSGIS. Downloaded city photos and maps stay in browser storage, which the browser may reclaim if storage is low. OpenFreeMap · OSRM/FOSSGIS
Web maps and weather: optional provider-backed place search uses Apple Maps; selected-city weather uses WeatherKit. In Norway, selected coordinates and departure time are sent to Entur; in Switzerland, to Opendata.ch. Responses include timetables and available real-time updates. Itineraries appear on an OpenStreetMap map; Swiss connections are schematic stop-to-stop lines. Transit responses are not saved for offline access. Entur terms and data · Opendata.ch privacy.
Web notifications: after permission, we keep a private browser subscription, installation identifier, language, time zone and association with the current account session. The server sends requested reminders through the browser push service. Signing out disables the device subscription; account deletion removes related server subscriptions and reminders. Browser drafts and personal records are separated by account. Shared editorial city downloads contain no personal trips or account records.
3. How we use data
We use data for authentication, device sync, personal trip plans, offline access, routing, notifications, support, and account security. Partner analytics helps reconcile handoffs, bookings, and commissions earned by Compass.
Compass does not sell personal data. A partner’s own data processing rules also apply when you continue to its service.
4. Location
Your current location is not a Compass profile field. It is used for requested features such as directions, nearby discovery, and city selection. Weather requests use the selected city centre coordinates from the catalogue, not the current GPS position of your device. When you open a taxi service, pickup and destination coordinates may be sent to the Compass server and selected partner to fulfill your request, but are not retained in Compass partner analytics. The pickup may be your current location when you are in the selected city. You can disable location access in iOS Settings.
5. Cloud sync and providers
Editorial photos of places, walks and cities, and banner images, are delivered from private Beget object storage in region ru1, Russia. The Compass server checks publication and issues a temporary signed link; your device then downloads the image directly from Beget over HTTPS. For this download, Compass does not forward your email, account identifier or session token to Beget. The network request reveals your IP address and technical request information to the provider; private storage does not mean an anonymous download. Avatars and user review photos remain in separate protected Supabase storage, not this editorial storage. See Beget's privacy policy.
Compass uses Supabase for accounts and synchronization. Features may contact Apple MapKit, Apple WeatherKit, Open-Meteo, Apple, Google, Yandex ID, Nexus, Travelpayouts, and partner services you choose. Necessary search parameters, such as city, dates, passenger counts, or taxi pickup points, and a shared source label are sent when you open an offer. Your account and trip content are not used to associate partner purchases with you.
When creating a partner link, the server sends the link service the selected offer URL, the Compass affiliate label and a shared source label. This request does not forward account, installation or trip identifiers, or the Compass session token. Requested search parameters may be included in the offer URL; the absence of an account identifier does not make those parameters anonymous.
For Google sign-in on iPhone, Google's component declares possible processing of name, email, phone number, account/device identifiers, approximate location, usage information and other data for sign-in functionality and analytics. It declares no tracking. Compass requests no additional phone-number access and has no phone-number sign-in form. This declaration does not mean Compass receives every listed data type. See Google's privacy policy and sign-in data disclosure.
When Yandex ID sign-in is available in your version, it requests access to email and your profile picture. The server verifies the token with Yandex and receives a user identifier, email and, when permission is granted and a photo exists, an avatar URL. This flow does not request your name, phone number or date of birth. Older grants may include only email until you sign in again. Yandex's own processing is described in its privacy policy.
If Google or Yandex provides a photo, Compass may use it as your initial avatar when you have not selected or removed a photo in Compass. The app downloads the photo from the provider without sending a Compass token and stores a resized copy without GPS or camera metadata in your private profile. Signing in again does not overwrite your chosen avatar or restore a removed one. Apple does not provide a profile photo through Sign in with Apple.
From build 30, weather requests use only Apple WeatherKit with a local cache. Earlier app versions may use Open-Meteo as a fallback. From build 38, Nexus sign-in is temporarily hidden in the production app; this does not delete existing accounts or data.
The automatic Travelpayouts Drive script is disabled on the website. Partner offers open through your explicit action. Partner websites may use their own cookies and data processing practices, governed by their policies.
According to Travelpayouts documentation, the affiliate label is normally stored in a cookie for 30 days unless the individual program specifies a different period. This label identifies Compass as the affiliate, not your Compass account. The attribution window does not mean all technical data, cookies or booking information are erased after 30 days.
Opening a website in the app's embedded browser does not mean anonymous browsing. A partner website may receive your IP address, browser information, cookies and information you enter there, such as booking contact details. The relevant service processes this information under its own rules; Compass's shared source label does not prevent that processing. Before continuing, review the selected service's privacy policy and privacy settings.
The app stores its sign-in session in the system Keychain. Compass does not receive your Apple, Google, or Yandex account password or collect card details. Purchases and bookings are completed by the partner.
6. Retention and security
Synced data remains while your account exists. Server-confirmed account deletion removes synchronized account data; the app clears that account's local data. Guest data is stored separately. Audit events are detached from the account and their personal metadata is cleared. Other devices that were offline need to reconnect to complete cleanup. The system Keychain is managed separately from app removal.
To safely complete deletion, the app keeps a retry secret in Keychain; the server stores only its hash and the operation status. An unfinished server request record lasts seven days. A completed deletion receipt is retained until the app acknowledges local cleanup: a lost connection or a device reopened later must not restore a deleted account. These records contain no trip content; completed receipts have no fixed expiry before that acknowledgment.
When an individual synced object is deleted, its content is scrubbed. A minimal deletion marker with its identifier and revision remains for devices that were offline. A separate protected journal retains identifier hashes and deletion times, without names, emails or trip content, to prevent deleted data from returning after a backup restore. These hashes are not treated as fully anonymous data.
New partner handoff records without account, installation, trip or search-context associations are retained for 90 days, then replaced with daily source totals for up to 13 months. Financially linked records and minimal historical attribution keys needed for late commissions are retained separately for reconciliation and legal obligations; they are not automatically deleted after 90 days. Successful partner synchronization diagnostics are removed after 30 days. Errors, unfinished operations and financial records are excluded from that cleanup.
To reconcile affiliate commissions, the server receives the partner's transaction identifier, purchase amount and currency, commission, status and transaction time. These financial records contain no card details and do not form a purchase history linked to your Compass account. However, an external transaction identifier is not automatically considered anonymous.
These periods apply to the specified Compass records, not to cookies, search data or bookings on partner websites. A partner's retention periods depend on its policy, processing purposes and legal obligations. Deleting your Compass account does not itself delete a partner's data or bookings. Direct a deletion request to the relevant service; Compass support can help identify the partner you continued to.
Authentication sessions and security logs have a separate lifecycle: partner analytics retention does not apply to active sessions. Sign-out or account deletion terminates the relevant session. A cloud provider's limited log visibility window does not guarantee erasure of all of its technical records.
The 90-day, 13-month and 30-day periods for the specified Compass records are not deletion deadlines for Beget's technical logs. A signed link's expiry limits access through that link, not the retention of the provider's network records. Contact Compass support regarding those records; we will clarify the applicable conditions with the provider without promising an unverified deletion deadline.
Backups may contain data from their creation time. New operational copies are encrypted, with the key stored separately. Operational backups have a 30-day policy, with removal only after a verified replacement; if the replacement is not verified, the last usable copy remains until verification is complete. Subsequent deletions must be applied before a restored service is opened to clients. Historical copies made before the deletion journal was introduced are isolated and must not be opened to users without separately checking that deleted data is absent. Contact support regarding access to or removal of data from backups.
We use access controls, encrypted connections, and server policies that prevent users from reading each other’s private data.
7. Your choices and rights
You may browse local city content without an account, disable iOS permissions, change notifications, sign out, or delete your account and synchronized data.
See the account deletion instructions. Contact support to request access, correction, or deletion.
8. Children and policy changes
Compass is not intended for children under 13. We may update this policy when features or legal requirements change. The latest version and effective date will remain available here.