Browsing
Public catalog access is lightweight
Public previews, catalog routes, and agent documentation are designed to be readable without a logged-in user profile.
Privacy
Minimal product surface, limited account data, transaction data where required.
Revenue Sleuth is designed to avoid account creation. Public browsing requires no user account, while purchase fulfillment necessarily involves payment and receipt data.
Transactions
Purchase metadata is retained for fulfillment
Purchase records, offer identifiers, receipt tokens, and fulfillment state are stored so Revenue Sleuth can grant and maintain access to purchased artifacts.
Analytics
Site analytics are enabled
Revenue Sleuth uses site analytics to understand catalog usage and improve the storefront. Analytics do not change the access model: purchased artifact retrieval still depends on the issued token, not a user account.
Contact
Privacy and data questions
Questions about purchase records, receipt-linked access, or data handling can be sent to support@fallsoft.co.