Effective: September 25, 2026
Revelation is designed to keep Poppy work local unless you deliberately connect ResiHub AI, attach/send context for connected reasoning, save a result, purchase/restore access, or enable anonymous usage/error sharing.
Revelation is provided by ResiHub AI. This policy covers the Revelation extension and Revelation-specific ResiHub AI services. Poppy AI, browser stores, Stripe, and other third parties have their own privacy practices.
Revelation stores journey state, goals, decisions, selected sources, attached results, preferences, and limited board observations in browser extension storage so work can continue. Removing the extension may remove local data.
Revelation may inspect the visible Poppy page to identify the current board, visible item labels/excerpts, selected text, and controls needed to guide the current workflow. It does not treat a visible card as proof that a source is connected, read, or analyzed. The current board name is displayed only when it can be identified reliably. Revelation does not intentionally scrape or transmit every Poppy creation.
Visible excerpts, links, or Poppy results become part of Revelation work only when you explicitly select/attach them or when a connected Resi response produces a draft/result. The Creations / Results shelf contains those explicit items. You control whether a selected item is included in connected reasoning or saved privately.
A standalone purchase may create or associate a free ResiHub AI identity using the verified purchase email. The identity is used for entitlement, restore, basic Resi allowance, fraud/security, and support. Payment processing is handled by Stripe or the marketplace shown at checkout; Revelation does not store full payment-card numbers.
When connected Resi guidance is enabled, Revelation sends the current goal, relevant journey state, selected Poppy operating records, and only the source/context authorized by product settings to the ResiHub AI service. Authentication credentials are used to authenticate requests but are not intentionally placed into prompts, exports, or product analytics.
For active qualifying members, ResiHub AI may retrieve relevant server-side CRM/GraphRAG context tied to the verified identity, such as goals, strategy, SWOT, online presence, and other context voluntarily supplied through ResiHub AI/Tell Resi. Revelation does not download the raw CRM or Neo4j graph into Chrome. If membership lapses, core Revelation can continue while this deeper member-only personalization is disabled.
Tell Resi is optional onboarding. If you choose it, information you submit there is governed by ResiHub AI’s applicable privacy terms and is stored server-side with your identity. Completing it is not required to unlock Revelation.
Revelation includes an optional setting to share anonymous product-usage and technical-error events to improve the product. When enabled, events may include extension version/channel, a random installation identifier, a random session identifier, session timing, and an allowlisted feature/event name such as Guide, Back, I’m Stuck, Show me where, result attachment, or normalized technical error code. This analytics channel is designed not to send prompts, board text, source excerpts, URLs, JWTs, email addresses, CRM content, or creation contents. You can turn the setting off at any time.
The mini Resi phone is another view of the same Revelation journey and uses the same connected Resi service when you submit a message. It does not create a separate hidden conversation. If you use Dictate, browser speech-recognition functionality may process audio under the browser/provider’s applicable terms; Revelation does not automatically start the microphone.
If private auto-save or an explicit Lily Pad save is enabled, attached results may be sent to ResiHub AI and stored with a durable server record. A local “saved” label is shown only after server confirmation.
After a successful entitlement verification, Revelation may cache entitlement state locally for a limited grace period (currently designed up to 72 hours) so a temporary service outage does not immediately lock out a verified customer. The server remains authoritative when connectivity returns.
Data may be processed by service providers necessary to operate Revelation and ResiHub AI, such as hosting, authentication, model/inference providers used by the connected Resi service, security/error services, and Stripe. We do not sell Revelation user data, provide it to data brokers, or use Poppy browsing/activity data for personalized advertising.
Local extension data remains until cleared, deleted by product controls where available, or removed with the extension. Server-side identity, entitlement, purchase, CRM, support, telemetry, security, and saved-artifact records follow ResiHub AI retention obligations. You may request access, correction, or deletion by contacting us; some transaction/security/legal records may be retained where required or permitted.
Connected traffic is designed to use HTTPS. Credentials are not intentionally embedded in exported work, and entitlement authority stays server-side. No security system is perfect.
Revelation is not designed as a medical/health-record product and is intended for adults and business users. Do not enter regulated sensitive information unless a future feature specifically requests it under updated terms and consent.
If Revelation’s data practices materially change, this policy will be updated before new practices are used where notice or consent is required. Contact: resihubai@gmail.com.