Privacy Policy

Signing in sends authentication information to Bilig's account service and the sign-in provider you choose, such as Google or Apple. We retain your account identifier, email address and provider-supplied name where available. Existing email/password accounts can also sign in. Authentication credentials are used to authenticate you; never send your password to our support address.

Account records include sign-in and last-active times, platform, provider, locale, app version and consent choices. We use them to provide and secure accounts, apply your choices and understand account activity. An account-linked record prevents duplicate signup conversion claims. If you contact support, we receive your email and the information you choose to include so that we can handle your request.

You can enter trip names, dates, destinations, itinerary events, saved places, document details and travel preferences. Local features keep these on your device or in your browser. Account-backed sync and publishing features send the data needed for the feature to Bilig's backend.

In the current Android app, general trip plans, events, reminders, saved pins, document details and selected-photo metadata stay on the device. Selecting photos can read their embedded location to suggest places; the photos are not uploaded by this feature.

Publishing a trip is optional. On Android, publishing sends a minimal source trip with its title, dates, city and country, plus the public snapshot you choose to share. A public snapshot can contain the trip title and dates, stop names, rounded place coordinates, transport information and an optional author display name. Rounded coordinates can still identify a place. Private notes, booking references, costs, document images and photos are excluded from the public snapshot.

Published trips are visible to other people and may appear on bilig.app and in search engines. You can withdraw a publication. Withdrawing or deleting your account removes the publication from Bilig; copies already saved by others or cached by search engines may remain outside our control.

Location features use your device or browser permission. You can deny or revoke it and choose places manually. A selected place, trip stop or photo location may be precise even when it is not your current location. Map views and location searches can send coordinates, search text and request information to the mapping or geocoding provider needed to show the requested result.

Android uses Google Maps and the platform geocoder. Google Maps processes information including IP addresses, device or app identifiers, map interactions, camera coordinates and diagnostic or crash data. This processing supports the map service and is separate from Bilig's optional analytics switch. Google may also use Maps information to improve its services under its own terms. See the Google Privacy Policy and the Google Maps terms.

iOS and web map features may use Apple Maps or MapKit. Third-party maps, carrier sites and other services you open have their own privacy practices. The Apple Privacy Policyapplies to Apple's processing.

Bilig's optional Google Analytics/Firebase Analytics collection is off until you opt in. It helps us understand screen and feature use, sign-in, genuine new-account creation and verified purchase activity when available. The service can process app-instance or browser identifiers, device and app details, interaction events and approximate geography derived from IP addresses.

The current native apps disable Analytics advertising identifiers, advertising storage and ad personalization, and do not set the Bilig account ID as a Firebase Analytics user ID. Trip text, passwords, email addresses, photos and document contents are not included in Bilig's analytics events. Analytics consent does not enable Google Maps or control its separate service processing.

Website analytics, advertising and optional functionality have separate choices in the privacy panel. Google Analytics and, when enabled with the relevant permission, Google AdSense can receive online identifiers, device/request information and usage or advertising events. See our Cookie Policyand Your Privacy Choices. Refusing optional analytics does not block core planning features. You can withdraw consent in the app or website settings.

When an app-store purchase is available and you choose to make one, Apple or Google processes payment. Bilig can receive product identifiers, purchase status and transaction verification information to check access to paid features. We do not receive your full payment-card details. Store subscriptions must be managed separately in the store; deleting a Bilig account does not cancel them.

Bilig uses its own backend and hosting, Cloudflare delivery, authentication services and the mapping, analytics and payment providers described above. Network services receive IP addresses and technical request information to deliver, secure and troubleshoot the service. Connections to Bilig's public services use HTTPS. We do not sell your personal information.

Providers may process information in countries other than yours. Their roles and terms differ; Google Maps, sign-in providers and app stores also process information under their own policies. Contact us with questions about providers, international processing or safeguards relevant to your data.

Local planning data remains until you remove it, clear site/app data or delete the app. Server-backed account and associated data remain until removed through the feature or account deletion. Account deletion removes the account, profile, linked login and consent records, signup-claim record, synchronized private travel records and public trip publications from Bilig's active account database.

Operational security logs, backups, support correspondence and provider-held records may have separate retention. Deleting the active account does not instantly erase every backup or earlier provider event. Any necessary retention for security, fraud prevention or legal obligations is limited to that purpose; contact us for details or a provider-data deletion request. We do not promise a fixed deletion period for records outside the active account database.

You can request deletion without reinstalling the app. You may also request access, correction, restriction or portability, object to processing, withdraw consent and raise concerns with the relevant data protection authority where applicable. Turkish users can review the KVKK Notice.

We process information to provide requested services, protect their security, comply with applicable obligations and, for optional analytics or advertising, apply your consent choices. Passport and visa content is planning information: check current requirements with official authorities before travel.