What we collect on rumblebuilt.com, how Signal and optional analytics fit in, how the cookie banner works, and how optional AI assist in our products handles your content.
These pages are mostly static HTML. Every page loads assets/cookie-consent.js, which asks for consent before loading non-essential scripts.
If you accept analytics (or accept all), we load assets/analytics.js, which in turn loads Vercel’s first-party script (/_vercel/insights/script.js) when the site is deployed on Vercel and Web Analytics is enabled for that project. If Analytics is off or the script cannot load, you may see nothing collected — that is expected.
We also load assets/product-analytics.js, which sends the anonymous page path (for example /pricing) to Rumble-operated Product 360 analytics via our server — no email, account id, or Supabase user id. Query strings and dynamic id segments are stripped or normalized before send.
Vercel Web Analytics provides aggregated traffic and performance insight; see
Vercel’s Web Analytics privacy documentation.
If you choose essential only, we do not load that analytics bundle on that browser.
We do not embed ad pixels or remarketing tags in our pages by default; consent for optional third-party advertising tags is reserved for future tags wired in code (for example __rbsLoadMarketingTags in cookie-consent.js) and only runs after opt-in.
Pages load Google Fonts from Google’s network (stylesheet and font files). When you submit Signal, a Support ticket, or the investors form, your browser sends the data to Rumble Built systems on this site, which may draft an acknowledgment with AI assistance (OpenAI) and email you via our mail provider (Postmark). Submissions, chat turns, and related emails are stored in our first-party database so our team can follow up with context.
The optional Ask chat on some pages stores a short conversation history, session id, and optional name/email in your browser localStorage (keys prefixed rbs-chat-) so the panel can resume on this device; use Clear chat in the panel to delete that data locally. Chat messages you send are processed by the same OpenAI-assisted pipeline, may trigger Postmark email, and are retained in our systems with your case/session.
We also keep an anonymous first-party rbs-visitor-id in localStorage so that if you later contact us, our team can (when you have accepted analytics) see the pages and key CTAs you used on this site. Journey events (page views and selected clicks) are recorded only after you opt into analytics via the cookie banner; they are not sold and are used for support and product improvement. See How site agents work.
Production responses also send security headers (HSTS, CSP, and related controls); see Security for a summary aligned with our deployment.
Use of the site is subject to our Terms of use.
Paid subscriptions and in-app purchases for our products are additionally governed by Product terms.
Signal, the Support form, and the investors inquiry are processed by Rumble Built systems on this site (AI-assisted drafting and email via Postmark). Use https:// in production so submissions are encrypted in transit.
Light/dark mode toggles store a theme key in localStorage in your browser only — not on our servers.
Memory is the product. Capture, organize, search, and retrieve in products such as CapturedIt work without turning on AI. Enrichment (for example summaries or transcription) and connections to external assistants are optional and configured by you — or by your team’s admins where applicable.
When you enable an AI assist feature, the content needed for that job may be sent to a model provider you (or we, under your configuration) select for that feature. Providers process that content to return a result; their retention and subprocessors are governed by their policies and our contracts with them. We do not use your product library to train Rumble Built’s own foundation models. You can leave enrichment off and still use capture and retrieval. For paid plans and checkout, see also Product terms; for CapturedIt licensing, see the CapturedIt EULA.
Studio engagements where we deploy AI features for a customer follow the same production bar as our homepage: tested, bounded, owned by a named owner on your team, with human review where stakes are high. Ask in Signal if you need a written data-flow summary for a specific engagement.
A cookie preferences banner appears when you have not yet saved a choice. Your choice is stored in browser localStorage under the key
rbs-cookie-prefs-v1 (versioned JSON: analytics and optional-advertising flags). That is separate from the theme key above.
Essential only keeps appearance storage and does not load Vercel Web Analytics or optional advertising hooks.
Accept analytics loads Vercel Web Analytics and anonymous Product 360 page-path reporting. Accept all also allows optional third-party advertising scripts once they are wired to the documented hook.
You can reopen the panel anytime via Cookie settings in the site footer.
We may revise this page when our site, subprocessors, or practices change. The canonical URL for this policy is in the page <head>. Material changes are reflected here; continued use of the site after updates means you acknowledge the revised description (see also our Terms of use).
Questions about a project or engagement?
Contact