Inquiry and account information
Contact details, account identifiers, routes, dates, traveler counts, and customer communications support inquiry handling, quotes, account administration, and service coordination. Phoenix staff use the platform to review requests and follow up. Only provide information relevant to the service you need.
AI and communications
ElevenLabs supports Alex conversations. Twilio provides phone and SMS infrastructure. Postmark supports transactional email delivery. Depending on the channel, these services may process phone numbers, email addresses, messages, audio, transcripts, timestamps, and delivery events.
Phoenix stores conversation summaries and inquiry details in its platform to support follow-up. OpenAI integration supports platform AI features where enabled. Which information reaches an AI service depends on the feature used; confidential credentials and payment-card details should never be entered into a conversation.
Hosting, records, and measurement
Vercel supports the website and application deployment. Supabase/PostgreSQL supports platform records. Providers may process operational metadata as part of delivering, securing, and troubleshooting services.
The platform includes optional Google Analytics integration and first-party visit-attribution features. Measurement may include page activity and campaign identifiers when enabled. This notice does not claim that a cookie preference center is currently available or that analytics is disabled for every visitor.
Payments and future integrations
Production card-payment processing through the platform is not currently enabled. Do not submit card details through chat or SMS. If online payments are introduced, Phoenix will identify the payment flow and update relevant notices before using it.
Adding an integration to internal code does not mean it receives production customer data. Future marketing automation, payment tools, or new data uses require an operational review and appropriate notice and choices.
Retention and deletion
Different record categories need different retention decisions: conversations and recordings, account records, inquiries and quotes, delivery logs, consent and opt-out records, and security or audit records. Copies may also exist with providers or in backups.
Retention controls in software do not establish a guaranteed deletion period unless they are configured and operating. Phoenix will consider applicable recordkeeping duties, active requests, disputes, suppression requirements, and backup cycles when responding to deletion requests.
Third-party roles
This page identifies known operational services rather than promising a complete legal subprocessor register. Travel operators and other independently acting organizations may have their own notices and responsibilities. A provider reference is not a guarantee about certifications, storage region, or model-training practices. Ask Phoenix about the service relevant to your request.
Before adoption
- Verify production configuration and vendor contracts; do not infer zero retention or no model training from API usage.
- Set and verify retention periods and deletion jobs before publishing numerical promises.
A subsidiary of Phoenix Aviation Solutions, LLC
299 Ellsworth CtClarksville, TN 37043
(629) 206-5011 · Ask for privacy or policy assistance.
Use your browser’s print option to save a copy of this draft.