Privacy
BrandApp Playground is a developer playground, not a product that accumulates a profile of you. This page lists everything it stores.
What this site stores
BrandApp credentials you enter on the connection page
Sealed with AES-256-GCM and written to the reopt-playground-config cookie — httpOnly, sameSite=strict, 30-day lifetime. Plaintext never reaches cookie storage, and the cookie is readable only by this deployment's server. Clearing it from the connection page removes it immediately.
Session state, if you sign in with Reopt
Better Auth issues a session cookie. The Reopt adapter keeps the session record in Reopt's backend rather than in a database owned by this app, so signing out ends it — and so does back-channel logout when the Reopt session is revoked somewhere else. Signing in is optional; every app-scoped demo works without it.
Theme preference
opt-preset and opt-mode in localStorage, read before first paint so the page does not flash. It never leaves your browser.
What it does not do
- No analytics, tracking pixels, or advertising identifiers. There is no measurement script on any page.
- No third-party scripts, fonts, or embeds. The site loads only its own assets.
- No credential is ever exposed to the browser. Every SDK call runs server-side behind a route handler.
- Public deployments never hand server environment credentials to anonymous visitors — each visitor connects their own BrandApp.
Data you create in a demo
Records, uploaded files, and AI generations are written to the BrandApp whose credentials are connected — yours, if you connected your own. That data is governed by that BrandApp and by Reopt's platform terms, not by this site. In dev mode everything lives in an in-memory server on your own machine and disappears when the process restarts. Uploads are capped before parsing at 10 MiB by default.
Questions
Write to contact@reopt.ai, or open an issue on GitHub. Reopt is 주식회사 리옵트, 천호대로101길 43, 1층 14호(중곡동), 광진구, 서울특별시, Republic of Korea.