Data We Collect
Application forms may collect name, email, audience stage, creator revenue range, bottlenecks, and growth goals. Studio demo data may include content plans, sponsor records, offer models, and workspace settings.
Privacy
Influencera is currently a production SaaS shell and demo workspace. This page explains the intended privacy posture for creators, teams, and brand operators as the product moves into customer use.
Application forms may collect name, email, audience stage, creator revenue range, bottlenecks, and growth goals. Studio demo data may include content plans, sponsor records, offer models, and workspace settings.
Data is used to operate the product, qualify growth reviews, improve workflows, and prepare customer support, onboarding, analytics, and billing flows.
If Google AdSense, conversion analytics, or similar partners are enabled, third-party technologies may process cookies, device data, IP addresses, referral sources, or page activity to measure visits, prevent fraud, and serve or evaluate ads.
AI requests are routed through server-side endpoints. When no model key is configured, deterministic fallback output is returned so sensitive keys are not exposed to the browser.
The app uses strict security headers, API payload limits, typed data contracts, non-cacheable API responses, and a release audit loop before production deploys.
Account deletion, export, and privacy review requests can be submitted through the data request API and stored for operator review through the production persistence layer.
Before taking live payments or storing customer data at scale, connect production secrets, confirm retention policy with counsel, and test deletion/export fulfillment end to end.