Frequently asked questions
Answers grounded in the current repo, not in guessed policy text.
This FAQ explains what the new portal pages cover, what is still placeholder-only, and why the implementation avoids unsupported enterprise, compliance, and legal promises.
FAQ
Current questions and current answers.
The details pattern keeps the page keyboard accessible without introducing client-side state.
What does this FAQ cover today?
It covers the current portal implementation, route intent, and areas where legal, compliance, or enterprise details were not provided in the repo.
Does the repo provide enterprise compliance claims?
No. Certifications, security standards, contractual terms, and admin-control claims were not provided, so this implementation leaves them out.
Is there a final privacy policy in this repo?
No. The privacy page is a placeholder structure only and should not be treated as binding legal text.
Why are some links and promises intentionally limited?
The implementation follows a no-guessing rule: unsupported claims, unconfirmed links, and future capabilities remain clearly marked instead of being implied.
How do these routes interact with the storefront?
They are static App Router pages that sit alongside the commerce storefront. Product, catalog, cart, and checkout behavior remain untouched.
Related pages