BentoBack to Bento
Public policy

Privacy Policy

Version2026-10-25
Effective2026-10-25
Contacthello@usebento.co

This Privacy Policy explains what Bento Labs may receive and why when you use the private beta. Bento is a private creative studio; customer media is private by default and is not published to a public feed. Questions, export requests, and deletion requests can be sent to hello@usebento.co.

Information we may handle

  • Account and contact data, including an email address and account security details.
  • Waitlist qualification answers, such as creative interests, provider use, frustrations, and contact handles you choose to share.
  • Prompts, uploads, references, outputs, thumbnails, and other media you ask Bento to store or process.
  • Connected-provider credentials and metadata needed to connect a service such as Grok. Provider secrets are handled through the account connection flow.
  • Job, usage, security, reliability, and audit records needed to operate and support the service.
  • Support conversations and manual-payment evidence when you provide it during the beta.
  • How you found Bento. If you open a Bento link (for example one in a creator’s bio), a cookie remembers that link for 90 days so we can see which link led to your waitlist signup. For each link click we record the app it came from, the kind of device, and the browser. We do not store your IP address for this.
  • How the site is used. Bento uses PostHog to count page visits and feature use. PostHog receives an internal account number, a random device ID stored in your browser, what was clicked, your browser and device type, and an approximate location based on your IP address. It never receives your email, name, prompts, or media.
  • Fraud and security signals. To prevent abuse and enforce bans, Bento keeps a small set of signals, described in “Fraud prevention and security” below.

Why and with whom

Bento uses this information to provide the service you request, operate accounts and the waitlist, deliver media, respond to support, protect security, enforce policies, reconcile manual beta operations, and meet legal obligations. Service providers may process information only as needed for those purposes. Connected providers process requests under their own terms and policies, and their moderation may occur now.

Payments are handled by Stripe, which receives your payment details directly and uses them under its own privacy policy, including for its own fraud screening. Bento never receives your full card number.

Bento does not currently use customer prompts or media to train models. Any future general training use would require explicit opt-in. Suspected-illegal material is never used for training.

Fraud prevention and security

Bento uses a few signals to spot fraud, payment abuse, and people who try to return after a ban. We use them only to detect and prevent fraud and payment abuse, to find accounts that break the Acceptable Use Policy or try to get around a ban, and to enforce bans and keep the service secure.

The signals are:

  • a one-way fingerprint of your IP address, recorded when you sign in or join the waitlist. It can be compared with another fingerprint but cannot be turned back into the address.
  • a one-way fingerprint of the device ID PostHog stores in your browser, recorded at the same moments
  • your email address in a normalized form, so Bento can tell when two addresses reach the same inbox or look alike across providers (for example when dots or a “+” tag are added to a Gmail address), and whether its domain is a throwaway email service
  • a card fingerprint from Stripe, a code that identifies a payment card without revealing its number

Bento compares these signals in its own database. It never sends your email or name to PostHog for this, and these checks don’t read your prompts, uploads, or outputs.

When an account is banned, Bento keeps its signals on a block list and checks new waitlist signups and invites against it. Bento will also add the banned account’s card fingerprints to a Stripe Radar block list, so Stripe declines those cards on Bento for any account. A matching signal only flags a signup for review: its invite is held until a person on the Bento team looks at it. A person makes every ban decision, and no one is banned or blocked automatically because a signal matched.

If you think we flagged or banned you by mistake, email hello@usebento.co and we’ll review it.

Legal basis. If you’re in the European Economic Area, the United Kingdom, or another place with similar laws, Bento relies on legitimate interests to process these signals: protecting the service, its members, and its payments from fraud and abuse. You can object to this processing by emailing hello@usebento.co. We’ll weigh your objection against the fraud and safety need, and we may still keep signals tied to a ban.

Retention. Bento deletes the IP and device fingerprints 90 days after it last records them for an account in good standing, and 90 days after a waitlist signup. For a banned account, Bento keeps its signals and card fingerprints for 3 years after the ban, and deletes them sooner if the ban is lifted. A waitlist signup’s fingerprints that match a banned account’s are kept as long as the banned account’s are. Card fingerprints on Stripe’s block list stay there until Bento removes them.

Media access and planned safety controls

Bento and its service providers may process or access customer media for service delivery, support, security, policy enforcement, or legal obligations. Bento does not promise zero human access, zero logs, or end-to-end encryption. Bento’s planned local fail-closed safety scanning and limited audited human review of flagged material are not active in production; they will be disclosed and activated only with the corresponding runtime controls and policy gates.

Requests, age, and retention

You may email hello@usebento.co to ask about access, correction, export, or deletion, or to object to how we use your information. Requests are handled manually during the beta and may be limited by security, fraud prevention, accounting, service records, legal obligations, or a restricted preservation requirement. For example, Bento keeps a banned account’s signals for the period described in “Fraud prevention and security”. If you’re in the EEA or UK, you can also complain to your local data protection authority. General account eligibility is 13 or the higher local minimum; future Mature Content would be 18+ with separate controls. See the Retention and Preservation Policy for the categories and boundaries Bento currently describes.

Bento

Bento Labs · Private creative studio

TermsAcceptable UsePrivacy

Public information for the current private beta. Questions about rights, privacy, or these policies can be sent to hello@usebento.co.