Weekly Doubles

Privacy and data use

Privacy information for Weekly Doubles.

This page describes how the current service uses data.

Accounts and sign-in

Weekly Doubles uses the email address you enter to send a sign-in code and identify your account. A short-lived host-only session cookie is needed after sign-in. If you choose to stay signed in, a revocable host-only device credential can be kept by the browser for up to 400 days; the server does not set an automatic device expiry, and you can revoke devices from the account page. A separate CSRF cookie is used to protect form submissions. The independent admin console uses different host-only cookies and a separate authentication database.

Season and feedback data

Private season data can include roster display names, season settings, weekly schedules, scores, cancellations, memberships, invitations, and audit records needed to operate the season. Signed-in feedback can include the category, title, and details you submit, plus its public processing status. Internal handling notes are kept for restricted operations and are not shown in your feedback history. Do not submit passwords, invitation links, verification codes, or information you do not want stored. The current product does not expose self-service deletion or promise a fixed deletion deadline.

Service providers

Cloudflare Workers, Static Assets, and D1 provide the application runtime, asset delivery, and database storage. Resend processes the email messages needed for sign-in and season invitations, including the recipient address and message content. Bark sends the operator brief notifications after successful sign-in or season creation. These contain only the event type, time, and aggregate season settings such as player count; they exclude email addresses, roster names, scores, season names, and sign-in credentials. The current public application does not load analytics scripts.

Advertising status

Advertising is currently disabled. A real AdSense publisher ID is configured for public verification, but the site is not approved for advertising and the applicable consent experience is not ready. The product does not load Google advertising scripts or set advertising cookies. If advertising is later enabled, Google and its partners may use advertising cookies to serve ads based on visits to this or other sites. Non-personalized settings would not by themselves replace any consent requirement. Users can manage personalized advertising through Google Ads Settings or aboutads.info; the applicable consent experience and vendor notices would need to be configured before enabling ads.

Questions and feedback

When you can sign in, use the in-app sign-in flow and feedback page to report a product issue or question. This page does not publish an administrator email as a customer-support address.