Roadrunner Privacy Policy
Roadrunner is operated for its owner’s personal use. This policy describes its Google connection and the records that connection creates.
Google data accessed.
Roadrunner requests gmail.readonly, which permits read access across the authorized mailbox, and calendar.events.readonly, which permits reading events on calendars the account can access. Its current importer uses those grants more narrowly. It reads the Gmail profile to confirm the account, then imports sent-mail metadata and changes to sent-mail history. It requests the From, To, and Subject headers and receives Gmail’s snippet, which may include a fragment of the message body. It does not fetch full message bodies or attachments. It imports events from one configured calendar, including event titles, times, organizers, attendees, and locations where available.
How the data is used.
Roadrunner adds those records to the owner’s private timeline for review and task planning. It uses account-specific identifiers and sync positions to avoid mixing records from different Google accounts. It does not sell Google data or use it for advertising. The Google importer does not send mail or edit a calendar.
Where the data goes.
Roadrunner currently stores imported records in a local database on the owner’s computer, which also holds connection credentials and runs the import process. When the hosted setup is enabled, Neon will store database records, and Cloudflare will process private API traffic and store uploaded media. Full Google mail bodies and attachments are not copied into Roadrunner by this importer. If a Google response cannot be processed, Roadrunner may keep the rejected source response as private diagnostic evidence.
Roadrunner agent workflows may send relevant stored information to OpenAI through Codex to perform the owner’s requested or scheduled work. Routine Gmail and Calendar import runs do not call an AI model. This policy does not make a claim about any provider’s retention or model-training practices.
Access, retention, and removal.
Only the owner is meant to access the app and its records. Roadrunner keeps an append-only history by default. Disconnecting or revoking a Google account stops future authorized reads, but it does not erase records already imported. The owner must arrange a manual removal of stored records or credentials. There is no automatic deletion period or self-service deletion control.
For privacy or access questions, use the support email shown on the Google authorization screen.