NYC Transit Bot ("the Service") is designed to store as little as possible. This page describes what data the Service handles and what happens to it.
Nothing, durably. The Service keeps a short rolling window of your recent messages in memory only, to support conversational follow-ups. This context is never written to disk or a database, and is discarded automatically as the conversation ages out or whenever the Service restarts. We do not build profiles, we do not use your data for advertising, and we do not sell or share your information with anyone.
To interpret natural-language requests, the content of your messages is sent to Anthropic's Claude API for processing, and is handled by Anthropic in accordance with its Privacy Policy and Commercial Terms, including Anthropic's own limited data-retention practices for API traffic. When you ask for directions, the origin and destination place names or addresses you type (and nothing else) are sent to Mapbox's Geocoding API to be resolved into map coordinates, and are handled by Mapbox under its Privacy Policy. Messages sent by SMS also pass through Twilio and your mobile carrier, which maintain their own message logs under their own privacy policies. No mobile information is shared with third parties for marketing purposes; text messaging originator opt-in data and consent are not shared with any third parties.
The Service uses no analytics, no advertising trackers, and no cookies beyond a random session identifier stored in your own browser for the web debug interface. Standard, short-lived web server logs (IP address, request path) may exist transiently for operational debugging.
Stop texting the Service and there is nothing left to delete — any in-memory context expires on its own. Text STOP to end replies at any time.
Any changes to this policy will be posted at this page.