FoxPlot Admin
Track production hardening, legal review, global compliance, Play Store readiness, payment safety, content moderation, route protection, and final pre-launch tasks.
Launch readiness
14%
Demo readiness estimate
Critical
5
Must resolve before launch
Needs backend
6
Requires server/database work
Legal review
2
Attorney review needed
Important launch reminder
This page is a planning tracker, not a legal approval. Before FoxPlot goes public globally or is submitted to the Google Play Store, the legal pages, age-safety rules, user-generated content moderation, payment flows, ads, privacy disclosures, and account deletion process should be reviewed and enforced in production.
Production Hardening
This is where the late-stage hardening work should be tracked before launch.
Admin, payout, author, advertiser, account, and reporting pages must be protected by server-side authentication and authorization.
Disable unnecessary production source maps, avoid leaking internal structure, and make sure private data cannot be inferred from public pages or metadata.
Enforce file limits, supported file types, malware scanning where possible, media moderation, storage permissions, and safe delivery.
Legal
The draft Privacy Policy exists, but production launch requires legal review for data collection, analytics, ads, age-safety settings, user accounts, uploads, payments, and international users.
Launch risk
Launching with unreviewed privacy terms may create legal and app-store compliance risk.
Next step
Have a qualified attorney review the policy before public launch and mobile app submission.
Terms and Conditions are drafted but must be reviewed for author submissions, advertiser campaigns, payouts, user-generated content, AI-assisted content, and platform account rules.
Launch risk
Weak terms may create disputes around content ownership, payouts, ads, removals, and account suspensions.
Next step
Review final platform terms with legal counsel before launch.
Safety
Frontend safety models exist for ratings, flags, mature content, youth filtering, and account settings. Production needs server-side enforcement so restricted content cannot be accessed by URL or API calls.
Launch risk
Children or underage users could bypass frontend filters if backend enforcement is missing.
Next step
Enforce age/rating checks in server components, API routes, database queries, and media delivery.
Auth & Security
Role and permission models exist. Production must connect Clerk/database roles and enforce authorization server-side.
Launch risk
Private admin, payout, author, advertiser, and campaign pages could be exposed without route protection.
Next step
Add middleware/server guards for all protected routes and verify every sensitive action checks role permissions.
Near final launch, reduce exposure of obvious internal route names, private page structure, source maps, file names, and implementation details where practical.
Launch risk
Attackers may use exposed routes, source maps, or predictable internal paths to target private areas.
Next step
Disable production source maps when appropriate, protect private pages, review metadata, and avoid leaking internal structure.
Payments
Payout UI exists, but production payouts should use Stripe Connect or another compliant payout provider with tax, identity, fraud, and payout audit controls.
Launch risk
Improper payout handling can create tax, fraud, banking, and compliance problems.
Next step
Connect provider-managed onboarding, payout status, admin approval, tax forms, and audit logs.
Advertiser campaign dashboards and budgets exist in demo form. Production needs billing, funded balances, spend caps, refunds, campaign pausing, and invoice records.
Launch risk
Campaigns could overspend, run unfunded, or create billing disputes if spend enforcement is missing.
Next step
Connect Stripe billing, campaign funding, spend limits, invoices, refunds, and billing status webhooks.
Content Moderation
Moderation decisions are currently frontend demos. Production needs permanent audit logs for content approvals, rejections, author actions, ad decisions, payout changes, and safety overrides.
Launch risk
Without audit logs, FoxPlot may not be able to prove why content, ads, payouts, or accounts were approved or blocked.
Next step
Create database audit tables and write audit records for all sensitive admin actions.
Public platforms with user content should support reporting content, reviewing reports, taking action, and handling author/advertiser appeals.
Launch risk
Illegal, abusive, adult, unsafe, or policy-breaking content may remain live without a reporting workflow.
Next step
Add report buttons, admin report queue, enforcement actions, appeal statuses, and abuse monitoring.
Mobile App
FoxPlot needs Play Store readiness for content ratings, user-generated content, reporting tools, mature content handling, privacy disclosures, ads disclosures, and account deletion requirements.
Launch risk
The mobile app could be rejected if content rating, UGC moderation, safety, ads, or privacy requirements are incomplete.
Next step
Prepare Play Console disclosures, content rating questionnaire answers, privacy/data safety form, and user reporting/blocking features.
Performance
Before launch, uploads, media previews, library grids, images, and dashboards should be tested for performance and reasonable file-size limits.
Launch risk
Large files or unoptimized media can slow the app, increase cost, or cause crashes.
Next step
Add upload limits, compression rules, lazy loading, caching, and production performance testing.
Operations
FoxPlot needs a basic process for user support, author questions, advertiser disputes, payout issues, refunds, and moderation concerns.
Launch risk
Users, authors, and advertisers may not know how to get help or dispute decisions.
Next step
Add support contact methods, admin response workflow, support categories, and internal escalation rules.