COURT SPRINT

Privacy policy

Effective November 1, 2026

Court Sprint is a private court reservation helper. This policy describes what the application processes when its owner connects REC and Gmail, schedules a reservation, or uses checkout.

Information the app uses

The owner may save a REC email address and password as a connection. The app encrypts saved connection credentials. It uses them to sign in to REC, obtain a short-lived access token and participant ID, and act on the selected court reservation. Access tokens, participant IDs used for authentication, and SMS codes are handled in memory during a request; they are not saved in job records or application logs.

If the owner connects Gmail, the app stores an encrypted Google refresh credential and the chosen sender, subject, and enablement setting. It requests Gmail read-only access to search the Inbox for a recent forwarded REC verification email and read its code. It does not send, change, or delete Gmail messages. Email bodies and verification codes are not saved by Court Sprint.

Reservation records may contain the selected court, date and time, connection reference, REC cart or order ID, status, and non-secret diagnostic information. A checkout claim stores the cart ID to prevent a second automatic payment attempt for the same cart.

Payments and browser sessions

When automatic checkout is enabled by the owner, Court Sprint uses a temporary Browserbase browser to sign in to REC, compare the pending cart and total with the requested booking, and use REC's already-selected default saved card. REC and its payment provider process the payment. Court Sprint does not ask for or store full card numbers or card security codes. A checkout with an unclear result is not automatically retried.

Storage, logs, and service providers

Hosted encrypted connections and reservation records are stored in Neon. The app runs on Vercel and uses Browserbase for temporary REC browser sessions. Google provides Gmail authorization and Inbox access. REC processes reservations and checkout. These services may process information needed to provide their functions under their own privacy terms.

Court Sprint keeps limited operational logs such as request stages, status codes, timing, and outcomes. It is designed to omit passwords, bearer tokens, SMS codes, mail bodies, payment details, and raw provider responses. It does not include a third-party analytics tracker.

Access and retention

The reservation app and its data endpoints require the owner's Court Sprint sign-in. The privacy policy is public. The sign-in uses an HTTP-only session cookie that expires after 12 hours; hosted HTTPS sessions also set the Secure cookie attribute. Saved connections remain until the owner removes them. Reservation records and checkout claims remain in the owner's database until the owner removes them. Local development may use encrypted files instead of Neon.

The owner can disconnect Gmail or remove REC connections in the app. The owner controls the hosting and database and can remove retained records there. For questions about this private installation, contact its owner through the same channel used to obtain access.

Changes

This policy may be updated as the application changes. The effective date above shows when this version began.