Where your decks go. Who sees them. What we built to keep it that way.
Manufacturers uploading line review decks are sharing pricing strategy, cost structures, and go-to-market plans. We treat that seriously. Here is exactly how the system works.
Your workspace. Nowhere else.
When you upload a deck, it goes to Firebase Storage, scoped to your workspace ID. No other customer can access your files. Firebase Storage rules and Firestore security rules enforce hard workspace boundaries at the infrastructure level, not just in application code.
To score your deck, our server retrieves the file and sends the content to Anthropic’s enterprise API for analysis. The response, scores, findings, recommendations, is written back to your workspace in Firestore. The original file remains in your private Storage bucket.
Your deck content does not go to ChatGPT, Claude.ai, or any consumer AI platform. It goes to Anthropic’s enterprise API, a server-to-server integration with enterprise data terms, operated separately from Anthropic’s consumer products.
The engine under the hood, and what it means for your data.
Auto SKUS uses Anthropic as a reasoning engine, the same way enterprise software companies use AWS as infrastructure. We built the scoring rubric, the retailer knowledge vault, the LRO memory system, and the optimization framework. Anthropic’s API provides the reasoning layer that runs them.
Under Anthropic’s enterprise API terms, Anthropic does not use your data to train its models by default. Content sent via the API is processed to generate a response and is not retained for training purposes.
This is a meaningful distinction from consumer AI products. When you use Claude.ai or ChatGPT directly, you are interacting with a public platform with different data handling terms. The enterprise API is a separate product with enterprise-grade privacy commitments.
Your intelligence does not bleed into anyone else’s.
Every piece of data in Auto SKUS, retailer scores, intelligence items, deck history, Margin Math programs, Grant conversations: is scoped to your workspace. Firebase security rules enforce these boundaries at the database level. There is no shared knowledge pool across customers.
Grant’s compounding intelligence (what he learns from your uploads) is specific to your workspace. A competitor uploading into Auto SKUS gets no benefit from your history, and you get no benefit from theirs. The intelligence is yours.
A purpose-built optimization engine. Not a wrapper.
Auto SKUS is not a chat interface wrapped around a public AI model. We built a proprietary scoring system calibrated to how retail buyers evaluate line reviews. We built retailer-specific knowledge profiles covering Walmart, Costco, AutoZone, O’Reilly, and Advance. We built a compounding memory layer that gets smarter with every deck you upload. We built the LRO Command Center to track scores, actions, and intelligence over time.
The AI provides the reasoning capacity. The product is everything built on top of it, and everything it learns about your business stays exclusively in your workspace.
Your team. Our CS team for support. No one else.
Workspace members you invite can access your workspace data based on the role you assign (owner, approver, commenter, viewer). You control who is on your team.
Our Customer Success team can access workspace metadata (plan, status, trial) for support purposes. CS access is role-gated, capability-scoped, and every CS action is audit-logged. CS team members are individually provisioned, there is no blanket admin access.
We do not sell your data. We do not share your data with third parties beyond the infrastructure providers listed here (Firebase/Google Cloud, Anthropic, Resend for transactional email, Vercel for hosting).
If your IT or legal team has questions about data handling, infrastructure, or our third-party providers, reach out directly. We’ll answer plainly.
sales@autoskus.com →