Trust and data use
Privacy Policy
Last updated: October 30, 2026
Bento Sprint is built for club and team coordination. This policy explains what the application is designed to collect, how configured service providers may process it, and the choices available in the product.
What we collect
- OAuth profile basics from GitHub or Google, whichever you sign in with, including name, email address when available, and profile picture, plus provider account identifiers and OAuth access, refresh, or ID tokens that Auth.js stores when supplied so sign-in and account linking can work.
- Club content created in the app, including teams, boards, tasks, comments, announcements, memberships, and review history.
- Billing identifiers for paid clubs, such as Stripe customer and subscription IDs. When a club owner or admin first starts an upgrade, Bento Sprint gives Stripe the club's name and ID and that person's email address. Stripe's checkout page collects the payment details and Stripe processes them; Bento Sprint does not store full card numbers.
- When outbound integrations are configured, encrypted provider credentials and destination settings such as channel IDs, webhook URLs, or database IDs, along with delivery records, retry/error details, and event payloads. Payloads can contain actor, club, team, source-record, card, or announcement context needed for the selected delivery.
- Security and operational logs used to investigate failures, enforce rate limits, and protect access.
- Your time zone name, such as America/Chicago, in a functional cookie named tz that the sign-in pages and the app set so due dates follow your calendar day; it is not used for tracking.
- If a deployment configures PostHog, an analytics cookie whose name starts with ph_ and ends with _posthog, which every visitor, signed in or not, gets on the first page they open. It lasts a year after your last visit and holds a random ID for your browser, your account ID once you sign in, the current session's ID, and the address and referrer of the first page you opened, with invite and join tokens removed. PostHog keeps a fuller copy in your browser's local storage.
Analytics and reliability tools
When a deployment configures PostHog, the browser sends page views, page exits, errors, and named product events, such as moving a card or finishing the sample board on the home page or the demo page. The sample board never writes to a Bento Sprint workspace, and its events carry no card text. Signed-in users are identified by their account ID only, not by name or email. Session replay, autocaptured clicks, heatmaps, and performance capture are off by default; an operator has to turn each one on, and replay then masks all text and inputs. Invite and join tokens are removed from page addresses before they are sent.
When Sentry is configured, it can receive errors, a sample of performance traces, application logs, captured console warnings and errors, request details such as the page address, browser, and referring page, and the signed-in user's ID, name, and email. Before anything is sent, the application removes common tokens, cookies, authorization values, IP addresses and location headers, email addresses in logs, and invite and join tokens. Sentry can also record a session replay, which masks all text and inputs, blocks media, and never runs on invite or join pages. Unless the deployment changes the rates, replay records 1 in 10 sessions; in every other session it keeps about the last minute in the browser and sends it only if an error happens or you open the Report issue form, even if you close it without sending, and then records the rest of that session. The Report issue form sends a name, a required email, a description, and an optional screenshot.
How we use data
- Authenticate accounts and manage invites, memberships, and roles.
- Provide the workflow, communication, review, billing, and export features requested by users.
- Process upgrades and subscription changes through Stripe checkout and the Stripe billing portal.
- Measure product use, diagnose failures, prevent abuse, and improve reliability when analytics or monitoring is configured.
Sharing and visibility
We do not sell personal data. Data may be processed by configured hosting, database, authentication, analytics, monitoring, and payment providers, or disclosed when required by law. When an authorized admin configures outbound delivery, the selected Slack, Discord, or Notion destination receives the event payload described above. Activity inside a club is visible to members and leaders according to the product's club, team, and role scopes.
Your choices
Club owners and admins can manage memberships and billing from the product. Browser privacy controls may limit analytics storage. You can revoke Bento Sprint's access to your GitHub or Google account at any time, in your GitHub settings under Applications or on your Google Account's linked apps page.
We update this policy when the providers we use, the data we collect, or the controls available to you change.