Privacy Policy

Information we handle

We process the account identity used to sign in, profile settings, customer and trip records entered into the CRM, reminders, invoices, itinerary details, and technical information needed to keep the service secure and reliable.

How we use information

Information is used only to provide CRM features, prepare travel documents, organize customer work, secure the service, diagnose problems, and support requested integrations. We do not sell personal information or use CRM records for advertising.

Google and Gmail data

If you connect Gmail, TravelDeskApp accesses your verified Google account email address, Google OAuth authorization tokens, and the Gmail send-only permission. When you explicitly confirm a send, the application submits the recipient address, subject, message body, and itinerary PDF attachment you reviewed to the Gmail API so Google can send that message from your connected account.

TravelDeskApp does not request or access your Gmail inbox, existing sent messages, contacts, or drafts. It cannot read, modify, or delete existing Gmail content. Google OAuth tokens are stored encrypted and are used only to maintain the Gmail connection and authorize messages you explicitly initiate.

TravelDeskApp's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google data and artificial intelligence

TravelDeskApp does not provide Google Workspace API user data—including Google account information, OAuth tokens, or Gmail message data—to OpenAI or any other artificial intelligence or machine-learning model.

TravelDeskApp does not use or transfer raw, aggregated, or derived Google Workspace API user data to create, train, develop, or improve generalized artificial intelligence or machine-learning models. Any separate AI-assisted CRM feature operates independently of the connected Gmail integration and does not receive data obtained from Google Workspace APIs.

Document uploads and extraction

When you select Extract details, the uploaded passport identity page or booking confirmation is sent to OpenAI to read the supported fields. The CRM does not retain the original file. Extraction results remain a draft until you review and save them; saved passport numbers are encrypted. Passport extraction is restricted to the CRM owner. OpenAI response storage is disabled for these requests; the provider's data retention policies still apply. This feature uses files you choose, independently of the Gmail connection.

Storage and security

Access to the CRM is restricted to approved accounts. Sensitive integration credentials and tokens are encrypted or stored as protected service secrets. Reasonable administrative and technical safeguards are used, but no online service can guarantee absolute security.

Retention and deletion

CRM records are retained while they are needed for the service or the account owner's business records. A connected Gmail account can be disconnected from TravelDeskApp, and access can also be revoked from the Google Account connections page. Contact us to request access, correction, or deletion of information associated with your account.

Service providers

TravelDeskApp relies on infrastructure and integration providers, including Cloudflare, Google, and OpenAI, only as needed to operate requested features. These providers process data under their own terms and security commitments.

Contact

Questions or privacy requests can be sent to theeagletrvl@gmail.com.