Business profile data
The platform stores business, website, onboarding, audit, content, and publishing context needed to operate SEO workflows.
Privacy
This privacy page restores the public legal route in the new Turborepo and should be finalized with counsel before production launch.
Data
business context
LLM
usage tracking
AWS
runtime controls
Privacy surface
Business, content, and publishing data
Business profile data
Protected
Generated content
Tracked
Publishing credentials
Secret
Usage events
Audited
Restored from the old public navigation and aligned with the new V2 route system.
What this page covers
This route restores the previous seo-fe navigation surface while keeping the new Turborepo design consistent, brand-configured, and production-shaped.
The platform stores business, website, onboarding, audit, content, and publishing context needed to operate SEO workflows.
Publishing credentials should live behind secure runtime boundaries such as AWS Secrets Manager or SSM.
This route is a production placeholder and should be reviewed with final legal policy language before public launch.
Workflow
The public page should point buyers into working auth, onboarding, audit, pricing, and dashboard paths while deeper detail pages are built.
Keep data collection scoped to onboarding, content, publishing, billing, and operations requirements.
Load secrets from AWS-native boundaries instead of exposing them through client bundles.
Use audit trails and usage records to preserve operational visibility.
FAQ
No. This restores the route and page shell. Final privacy language should be approved before production launch.
No. Client pages should only use public runtime config. Sensitive config belongs in server or AWS runtime boundaries.
Yes. LLM usage tracking is part of the planned production data model and reliability layer.
Continue
Start with signup, audit the business, and let the dashboard guide the next production workflow.