1. Operator and contact
VIP Taxi Port is operated by atamantravel lcc. Contact us at atamanviptaxiport@gmail.com or +90 530 596 77 52 for privacy questions, corrections or deletion requests.
This notice covers the booking information used by the operations system and its Google Calendar, Gmail and Maps connections. Only authorized staff connect an operator Google account. Customers do not grant Google account permissions to make or manage a booking.
2. Information used
Booking and customer management
The booking system stores the details supplied for a transfer, such as customer contact details, passenger information, routes, stops, pickup times, vehicle selection, flight details, meeting instructions and booking requests. Staff use these records, status history and approved decisions to manage the booking. A private customer-management link provides access to the associated booking; anyone holding that link should treat it as confidential.
Operator identity and Calendar authorization
The Calendar connection requests openid and email to identify the authorizing operator, and https://www.googleapis.com/auth/calendar.app.created to manage calendars and events created by this app. The site stores the authorized account identity, connection identifiers and credentials needed to maintain that connection. This scope does not provide access to the operator's personal calendars.
For each journey leg, a Calendar event can contain:
- The booking reference and booking status.
- Pickup and drop-off locations, stops and selected stop waiting times.
- Pickup time, estimated journey duration, vehicle type and passenger count.
- A link to the booking in WordPress administration, which requires an authorized administrator login.
The app does not put customer names, email addresses, phone numbers, passenger rosters, prices or private customer-management links in Calendar events. It does not add guests, send customer invitations or create video meetings. The app reads back its own events to verify creation, approved changes and removal. Local sync records include calendar and event identifiers, booking versions, timestamps and sync outcomes.
Gmail sending authorization
The separate Gmail connection requests https://www.googleapis.com/auth/gmail.send to send mail on behalf of the operator's authorized mailbox. It does not request permission to read or search the inbox.
Messages may include booking and contact details, itineraries, flight or meeting instructions, approved changes, status decisions and a private booking-management link. Messages go to the relevant customer and administration recipients configured for the booking. The mail connector can retain delivery records and message content in restricted WordPress mail logs.
Maps and location requests
Google Maps Platform receives location-search text, selected places, route locations and routing parameters needed for location search, maps, distances and journey estimates. These services use website API keys, not a customer's Google OAuth authorization. Browser-based Maps requests can also send technical request information to Google.
3. Purpose and sharing
We use this information to manage transfers, communicate booking decisions, maintain the operator's schedule and investigate delivery or synchronization problems. WordPress remains the source of truth. A customer's requested change does not alter the confirmed itinerary until an authorized operator approves it.
Information is shared with service providers only as needed for these connected features:
- Google: the information needed for the authorized Calendar events, Gmail messages and Maps requests.
- Hostinger: hosting of the WordPress website and its stored records and backups.
- FluentSMTP: the configured WordPress mail connector. Its
fluentsmtp.com/gapi/authorization-code relay is used in the Gmail authorization process; the sending connection is saved in the private WordPress administration settings. - Authorized staff and message recipients: access needed to administer bookings or receive the relevant communications. Mail services and recipients may retain their own copies.
These providers may process information in countries other than the customer's country. Their own privacy and service terms also apply to the services they provide.
Google API Limited Use
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use Google API information for the user-facing features described here, not to sell it, target advertising, determine creditworthiness or train generalized artificial-intelligence models. Human access is limited to the permitted purposes under that policy, such as authorized support and security work.
See also the Google Privacy Policy and Google Maps Platform terms.
4. Safeguards
Administrative access is restricted to authorized WordPress users. Calendar credentials are stored with authenticated encryption in the WordPress database and used over HTTPS for Google requests. The Calendar connection is restricted to the app-created calendar and verifies its own event identifiers and ownership before changing events.
Mail credentials are maintained separately by the configured mail connector in its protected administration settings. Mail logs and booking records are restricted to authorized staff. Customer-management links are private, revocable access links and should not be forwarded or published.
No online service can promise absolute security. Please do not send passwords, verification codes, payment-card details or identity documents in a support request.
5. Retention and deletion
Booking records, customer requests, status history, audit records and mail records in the current workflow remain stored until an actual authorized deletion is carried out. They are not automatically erased by completing or cancelling a booking. We use these records to manage the service, resolve questions and maintain the booking history.
An approved cancellation removes the app's related active Calendar events when synchronization succeeds. It does not erase the WordPress booking, previously sent messages, recipient copies or backups. Calendar provider records may also remain according to Google's handling of deleted events.
Disconnecting Calendar removes the local Calendar connection credentials and stops future synchronization. It does not itself delete the Google calendar or its existing events, erase booking records or revoke the grant in the Google account. Revoking a Google permission stops future authorized access but does not erase previously stored information. Disconnecting the mail connector likewise does not recall messages or erase booking and mail records.
To request deletion or correction, contact atamanviptaxiport@gmail.com and identify the relevant booking or connection. We will verify the requester's authority, assess the records concerned and explain any records that must be retained for service, dispute or recordkeeping reasons. We will explain the scope of any deletion performed rather than treating a cancellation or disconnection as complete erasure.
Copies held by Google, mail recipients, hosting providers and backups may remain under their own retention and backup processes. A deletion from the active website does not guarantee immediate removal from every provider or backup copy.
6. Your choices and questions
An authorized operator can pause Calendar synchronization or disconnect the local connection from WordPress administration. Google permissions can be reviewed or removed in Google Account connections. Gmail and Calendar are separate connections; disconnecting one does not disconnect the other.
Customers can use their private booking-management link to view their booking and submit a request, or contact us for help. For access, correction, deletion or privacy questions, use the contact details above. Share only the information needed to locate the booking; never send a password or verification code.
We will update this notice if the connected features or information handling change materially, and obtain additional authorization where required for new Google permissions.