Waytale AI Home

Transparent by design

Data Handling

A practical summary of what Waytale AI processes, why it is needed, and how it should be protected.

1. Data handling principles

  • Use data for the trip: location and route context should support directions and story cues, not unrelated profiling.
  • Ask first: precise location requires device permission and can be revoked in iOS Settings.
  • Minimize prompts: AI narration should receive the context needed for a story, not unrelated personal information.
  • Protect keys: production AI, map, and routing credentials should be held server-side, not embedded in the mobile app.
  • Make silence easy: narration can be turned off while directions continue.

2. Data flow by feature

Feature Data involved Purpose Typical handling
Location permission Precise location and route progress Center map, start route, trigger nearby cues Processed during use; may be sent to routing/story services when needed
Destination search Typed query, selected place, approximate region Show address/place suggestions and plan a route Sent to geocoding/search providers; cached only as needed
Route planning Origin, destination, travel mode, route geometry Calculate distance, time, and steps Processed by routing services and the app
AI stories Route context, nearby places, interests, story settings Generate spoken narration Sent to AI provider through Waytale-controlled service layer in production
Diagnostics Crash logs, app version, device type, timestamps Fix bugs and improve reliability Retained only as reasonably needed for operations and debugging
Support Email, message, screenshots, issue details Respond to requests and resolve problems Stored in support systems until no longer needed

3. AI prompt boundaries

Waytale AI narration prompts should be limited to travel-relevant context, such as:

  • Origin and destination labels.
  • Route segment or nearby place context.
  • Selected interests such as history, food, culture, architecture, nature, or hidden gems.
  • Safety instructions telling the AI not to invent unverified facts or unsafe driving instructions.

Prompts should not include unrelated contacts, photos, payment details, private documents, account passwords, or other sensitive content that is not needed for narration.

4. Production service controls

For production release, Waytale AI should use a server-side service layer with:

  • Provider API keys stored outside the mobile app.
  • Rate limits and abuse monitoring.
  • Logging that avoids storing unnecessary precise trip histories.
  • Clear separation between support data, route operations, diagnostics, and AI narration.
  • Reviewable vendor list for AI, mapping, routing, hosting, and diagnostics providers.

5. User controls

  • Turn narration on or off.
  • Change story interests and depth.
  • Revoke location permission in iOS Settings.
  • Contact Waytale AI to request access, correction, or deletion of personal information.

Send data requests to privacy@waytale.stayatthea.com.