Privacy, in plain language.

No account, advertising, or analytics integrations are needed to explore the Senate and House record.

iOS app and website policy · Updated November 12, 2026

Using OpenVote

This policy covers the OpenVote iOS app, the openvote.dev website, and their shared API, operated by Devin Minnihan. The app and website do not ask you to create an account or include advertising trackers, session recording, or analytics SDKs. They do not request access to your contacts, camera, microphone, or precise location. The iOS app does not use an advertising identifier.

Searches, filters, and technical information

When you use the iOS app, it sends requests directly to the OpenVote API to load public Senate and House records. Requests include search terms, server-side filters, page numbers, and identifiers for votes or senators you open. The API passes relevant query values to Supabase to retrieve the requested records. These requests may appear in provider logs. Not every filter sends a request; some filtering happens only on your device.

On the website, searches, filters, page numbers, and record identifiers also appear in URLs and may remain in browser history or shared links. Vercel hosts the website and may process standard website request information, such as requested paths and search parameters, status codes, user-agent information, request identifiers, and processing regions. On the site’s current Hobby plan, Vercel retains runtime logs for up to 1 hour. This one-hour period applies only to runtime logs; Vercel may process other system data for different periods as described in its privacy notice.

When the app or website requests public records from the OpenVote API, Railway may process request timestamps, requested paths, IP addresses, user-agent information, response status codes, and edge-region information. Railway retains these operational logs for up to 7 days.

The API uses Supabase as its data service. Supabase retains API and database logs for up to 1 day. OpenVote and its service providers use operational information for security, reliability, troubleshooting, and abuse prevention. These logs are deleted according to each provider’s retention schedule.

These log-retention periods do not apply to the public Senate and House records stored in the service database. Those public records may be kept as part of OpenVote’s dataset. Operational requests are not used by OpenVote for advertising or cross-app tracking, and we do not sell personal information.

Preferences and on-device storage

The app and website follow your device’s light or dark appearance preference. The iOS app temporarily caches fetched records in memory for browsing. Website filters are represented in the URL. OpenVote does not use these preferences or caches to build an advertising profile and does not set tracking cookies.

Support messages

If you email us, we receive your email address, your message, and anything else you include. We use that information to respond to your request. Please avoid including sensitive information that is not needed to explain the issue.

Support messages are separate from provider logs and are not governed by the runtime or operational log-retention periods above. They may remain in our email system for as long as reasonably needed to respond, maintain a record of the request, protect the service, or comply with legal obligations. You may request deletion, subject to applicable legal or operational exceptions.

Other websites

Links to Senate.gov, the House Clerk’s website, and other external websites take you to services with their own privacy practices. Our service providers also maintain their own privacy policies: Vercel, Railway, and Supabase.

Questions and requests

For questions about information handled by OpenVote or to make a privacy request, email hello@openvote.dev. We will review your request and respond as applicable. This policy will be updated if the app’s or website’s data practices change.