Your control. The full picture.

History is off by default.

Until you turn on saving, Redaq keeps conversation text in the current page’s memory. It is cleared when the page reloads, closes, or you clear the session. The chat endpoint does not write prompts or answers to the conversation database. You can export a conversation manually.

We store access metadata: a random visitor identifier in a signed, secure cookie, prompt counts, keyed hashes of network IP addresses for abuse limits, wallet verification challenges, and a verified wallet address. Raw IP addresses are not stored in Redaq’s application database. These records enforce access and prevent signature replay. Usage counts are separate from chat history. Wallet verification lasts up to 24 hours; challenges expire after five minutes. Expiry prevents use of a record; it does not promise that all expired metadata has been physically erased.

Optional history is server-stored.

When you enable saving, Redaq stores conversation text, mode, source links, analysis addresses and fact cards, title, and update time. Saved chats are linked to your browser session and verified wallet. Only that session with the corresponding verified wallet can retrieve them through the app. Connecting a different wallet switches the history you can access. Clearing cookies or using another browser does not restore saved history automatically; export chats you want to keep.

You can delete individual conversations or all saved conversations for the current wallet. Delete operations remove the live database records. Infrastructure backups and provider retention may follow separate schedules. Turning saving off does not delete chats that were already saved. Uploaded PDF files are not included in saved history.

You’re talking to Redaq.

The assistant and AI experience are presented as Redaq. Your prompts and conversation context are securely processed through Redaq’s infrastructure to generate responses. Redaq prioritizes privacy, confidentiality, and user control. Conversations are not saved by Redaq unless you explicitly enable saving. External processing services may handle requests, and inference is not end-to-end encrypted.

Never share wallet seed phrases, private keys, or highly sensitive credentials. Redaq is designed to minimize data retention and give you control over saved conversations. External processing services may have independent privacy and retention policies.

Private research and web searches.

Redaq provides private, uncensored AI-powered research through its integrated search infrastructure. Your questions are processed to generate relevant responses without saving conversation history unless you explicitly enable it. Web searches may interact with external search services and websites.

External search and processing services may have their own privacy and retention policies.

Public wallets stay public.

Wallet research reads Robinhood Chain through server-side RPC and blockchain data providers. Holder checks read your token balance and obtain market estimates from DEX Screener. Those providers receive the wallet or token addresses needed for the request. Public activity can identify patterns and link an address to other public information.

Verification uses a time-limited, one-time ownership signature. It does not request transfers or token approvals. No wallet transactions are available in Redaq. The displayed holdings snapshot may cover only part of an address’s activity; coverage and lookup times are provided with the data.

Privacy is built in.

Redaq delivers private, uncensored AI interactions through a securely integrated private AI model. Conversation history is disabled by default, and saved conversations remain under user control. Redaq does not require an account, and deleting saved history removes the corresponding records from Redaq’s database. External infrastructure may independently retain connection metadata or security logs according to its policies.

A secure, HTTP-only visitor cookie remembers free-access usage for up to one year. Shared network limits help prevent abuse, and expired usage counters are periodically removed. Session preferences remain in browser memory, while the landing-page entrance flag is stored in session storage. Redaq does not add advertising trackers.

Research supports your judgment.

AI answers and third-party data can be inaccurate or incomplete. Review primary sources and actual onchain evidence. Holding $REDAQ provides access under the stated usage policy; it does not guarantee returns or outcomes.