Updated 3 October 2026. This notice covers seferiptal.com and Sefer İptal’s read-only assistant integration, where available. Privacy contact: contact@seferiptal.com.
When you use Sefer İptal through ChatGPT
When you ask an assistant to check a route, sailing, cancellation or prediction using our integration, the assistant sends the selected tool and its query parameters to our service. These can include a short terminal or route-name search, terminal or route identifiers, travel dates, a sailing identifier, a status filter and result pagination. We use them to retrieve public sailing information and return it to the assistant. The integration does not require an account, booking reference, passenger name, payment details, precise device location or access to your saved browser follow list. Do not put those details into a query or contact message. Our tools do not request your full conversation. The transport connection and request metadata still pass through our hosting infrastructure. Tool results go back to OpenAI so ChatGPT can answer; OpenAI processes your conversation under its own privacy policy and your account controls. Disconnecting the integration prevents further use through that connection; deleting a ChatGPT conversation does not itself request deletion of our infrastructure or support records.
Why information is processed
We process route/date requests to supply the information you ask for; necessary technical connection records protect and operate the service. In jurisdictions applying GDPR, service delivery relies on the necessity of fulfilling your request and security processing on the legitimate interest in reliable, abuse-resistant operation. Where KVKK applies, the corresponding grounds are processing directly necessary for performing the service and necessary legitimate interests without harming fundamental rights (Article 5(2)(c) and (f)), as applicable. Optional PostHog analysis uses your separate consent (GDPR Article 6(1)(a); KVKK Article 5(1)); visiting this notice or using the service is not analytics consent. A message you send supplies your email address, message and any attachments to respond to your inquiry. If you request ferry alerts, we process your email address, selected sailings and alert settings to verify the address and deliver the alerts you chose. Cancellation estimates concern sailings and weather, not a personal credit, eligibility or legal decision about you.
Recipients and international processing
Cloudflare processes requests to host, deliver and protect the service and to provide its website measurements. PostHog processes optional usage events only after consent; our project uses the United States region. Email providers also process the confirmation, access and ferry-alert messages you request. OpenAI processes assistant requests and returned results when you use ChatGPT. These providers can process information outside your country, including the United States. The terms and privacy notices of external operators apply when you leave this site. We do not send browser follow lists or ChatGPT queries to PostHog as event payloads. Our integration does not request advertising identifiers or use your queries for personalized advertising.
Your privacy choices and requests
Email contact@seferiptal.com for access, correction, deletion, objection, restriction, portability or consent-withdrawal requests where applicable. Include the page or service, approximate time and enough information to identify your request; do not send identity documents or tickets in an initial email. We may ask for proportionate verification when needed to prevent disclosure to another person. Email-alert settings are tied to your verified email address. There is no general visitor account; we may need additional information to identify unrelated technical records. Your rights and exceptions depend on applicable law. Under KVKK Article 11, rights include learning whether data is processed, its purpose and recipients, correction or deletion where conditions are met, notification of those changes to recipients, objection to adverse results solely from automated analysis and compensation for unlawful processing. Under GDPR you may also complain to the supervisory authority where you live, work or believe an infringement occurred; in Türkiye the authority is KVKK. Nothing in our terms removes mandatory statutory rights.
Retention and changes
The sections below describe browser storage and the verified scope of infrastructure records. Support messages and provider-held records have different retention settings; we do not currently publish a verified deletion period covering every provider, export and backup. Contact us for the applicable record and a deletion request. Email-alert recipient records, alert settings and delivery history, plus completed-sailing and outcome records, are retained without an automatic deletion period. Completed sailing outcomes may support future forecast-model improvement. Email addresses and delivery records support alert operation and auditing. Provider-held records, exports and backups can have separate settings; we do not publish one deletion period covering every provider and copy. We will update this notice when data practices change; new optional processing that requires consent will require a new choice. See our terms of use.
We also record aggregate connector tool-use diagnostics: the tool name, success or error category, elapsed time, result-count bucket and an explicit test marker. These added diagnostic records do not include tool arguments, exact travel dates, sailing identifiers or a connected-account identifier. Hosting request logs are separate, as described above.
This page explains how Sefer İptal’s browser follow list, optional email alerts and requests to the site work. Following a sailing needs no account, password, ticket or payment details. Email alerts use a verified address and a private emailed link for settings; there is no full account or password.
My trips is saved in this browser
Your browser follow list is saved in local storage (localStorage). It includes selected sailing details and a limited history, is not synchronized across devices, and may be visible to someone using the same browser profile. Optional email alerts are separate: when you request one, the selected sailing and settings are stored on the server while verification is pending. After you verify your address, alerts can be sent while this page is closed when email delivery is enabled. A private session cookie keeps your settings available on the device after you open a one-time emailed link. Pending sailing keys are kept in browser session storage so unfollowing can show the correct warning; they are ignored after one day. If browser storage is blocked, the local follow list may not persist; the page displays a storage warning.
Terminal and route catalogue
The application also caches a terminal and route catalogue from a successful request in this browser. This reference information is not a ticket or personal trip record. If a network request fails, the cached catalogue may be used with its freshness considered separately. Clearing browser site data removes this cache as well.
Removing saved records
Unfollowing a sailing removes it from the browser list. If your address is verified and that sailing has an active email alert, you are asked whether to turn it off too. Unfollowing does not cancel an email request awaiting verification; review the listed sailings before confirming the email. Turning off an alert stops future alert emails; its recipient, sailing and delivery records remain stored. Clearing seferiptal.com site data resets only the browser follow list and does not delete server-side alert or completed-sailing records. Alert recipient records and completed sailing outcomes are not automatically deleted; outcomes may be used to improve future forecasts. Browser settings can affect how long the local list persists.
Requests used to retrieve sailing information
Local storage does not mean that refreshing a sailing makes no network requests. Searches and refreshes send the relevant route and date range to Sefer İptal. The browser follow list and its local status history are not uploaded as a full account profile. If you request email alerts, the server receives the selected sailing identifiers and settings so it can evaluate them after the page closes. We send no sailing alerts before email verification; after verification, alert emails are sent when your selected conditions occur and email delivery is enabled.
The address bar, shared links and language
Selected departure, arrival and date can appear in the page URL. A person receiving a shared link can see that selection; the URL may also appear in browser history and is sent to the server when the page is requested. Language is determined by the Turkish or English page URL; the current language choice is not saved in a preference cookie.
Hosting, technical records and analytics
Cloudflare delivers this website. Page and sailing-information requests are processed by the hosting infrastructure to operate and protect the service; this network activity includes connection and request information. Server observability is enabled, so we do not claim that no technical records are kept. Cloudflare Web Analytics is enabled; pages may load a measurement script for visits and page performance. Cloudflare’s analytics documentation describes these measurements. This page does not claim that all infrastructure and analytics data is anonymous or deleted after a specific period.
Analytics and technical logs are different
The 20 September 2026 configuration check found request logging enabled and URL query-string redaction disabled. Route and date selections in URLs may therefore appear in technical logs. The application has no code that sends the follow list as advertising or custom analytics events. Cloudflare’s Web Analytics documentation says analytics omit URL query strings and measurements from the previous six months are accessible; that statement does not apply to server logs. Analytics data scope and Workers Logs describe different services. The service uses the verified Workers Paid plan, for which Cloudflare documents seven days of Workers Logs retention. We have not verified a single deletion period for every infrastructure log or export. Infrastructure measurements are accessed through the Cloudflare account operating the service; we do not publish a public visitor-log archive.
Cookies and external links
The browser follow list is stored in localStorage, and the site does not use cookies for that list or for the language preference. Verified email-alert settings use a necessary Secure, HttpOnly session cookie after you open a private settings link; it is not used for analytics. Hosting and security services may use their own cookies. When you follow links to IDO or other sources, those services’ practices apply. Email providers deliver confirmation, access and ferry-alert messages.
Questions
Use the contact page for storage or privacy questions. You do not need to include tickets, booking codes, identity documents or payment details in your message. See About Sefer İptal and data sources for our publishing scope.
Optional PostHog usage analytics
Optional analytics is off until you press “Allow optional usage analytics” below. You can use the entire service without allowing it. Consent applies to this browser for 180 days; you can withdraw it here at any time. Existing opt-out preferences or older analytics settings do not count as consent. Do Not Track and Global Privacy Control prevent loading PostHog even if you previously allowed it. If browser storage is unavailable, optional analytics stays off.
If you allow it, PostHog receives page views, valid route searches with result counts capped at 50, empty results or coarse search errors, opening sailing details, follow/unfollow actions, language changes, selected button clicks and approximate active time. Events can include route codes, a past/today/future date category, browser/device information, page path and referring domain. A random browser identifier and session information link events in browser storage. The US-region PostHog service receives network connection information including the IP address. We exclude exact travel dates, URL queries and fragments, full referring URLs, saved sailing lists, form text and person-profile updates from event payloads. For shared-link visits, we include only the fixed campaign values source=share, medium=referral and campaign=sailing_share with events on that page; we do not collect a sharer identifier. A shared link itself contains the selected route and date plus a sailing reference in its fragment, which analytics excludes. Session recording, heatmaps, advertising tracking and automatic DOM capture are disabled.
Withdrawal stops future PostHog collection and removes PostHog browser identifiers where storage is accessible. Other open tabs also stop when the preference changes. Withdrawal does not automatically delete events already received; contact us about those. Your consent choice and date stay in browser storage until you clear site data or change the choice. This control does not change Cloudflare Web Analytics, hosting/security records, email or OpenAI’s own processing. PostHog event retention is separate from browser storage: the project’s effective event-deletion period has not been verified, so we do not promise that past events expire after 180 days. See PostHog’s privacy notice.