Privacy
Privacy while your creator workspace takes shape.
This is the plain-language privacy policy. The working rule is simple: collect what is needed to manage access, support creators, improve the product, and run checkout safely.
Trust signals
No sale of signup data
Account emails are for access, updates, and support.
Creator workspace content
Ideas and saved systems are treated as your creator workflow material.
No public model training promise
Private saved packets are not sold or intentionally pooled into cross-user training.
Browser storage explained
Login, checkout, saved state, referrals, and analytics can use browser storage.
No retargeting pixels today
Advertising tools should be disclosed before they are added.
Delete route
Support can remove signup data or saved creator workspace content while self-serve controls are still maturing.
Optional media paths later
Media tools can use user-connected paths when those features open.
Removal requests
Use contact routing for privacy questions or signup removal.
01
Privacy ticket
What we collect
Creator Factory may collect your email address, creator type, channel size, and access preference so we can manage your account and send product updates.
02
Privacy ticket
How it is used
Account information is used for access, product updates, onboarding, support, fraud prevention, and improving the product experience. We do not sell signup data.
03
Privacy ticket
Creator content
Ideas, generated packets, and saved systems are treated as creator workspace content. Features may change as saving, exporting, accounts, and collaboration tools develop.
04
Privacy ticket
What happens to ideas
Ideas you enter are used to build your packet, save your workspace state when you choose to save it, provide support, prevent abuse, and improve product quality. Keep private information out of prompts unless you are comfortable using it inside the product.
05
Privacy ticket
Cookies and browser storage
Creator Factory uses necessary browser storage for login, checkout, saved workspace state, referral credit, and basic product analytics. This may include local storage, session storage, first-party fallback cookies, and third-party storage used by services such as Supabase, Stripe, Google Analytics, or connected tools.
06
Privacy ticket
Advertising
Creator Factory does not currently run ad retargeting pixels. If advertising or retargeting tools are added later, this policy should be updated before those tools are used so visitors know what is collected and why.
07
Privacy ticket
Training
Creator Factory does not sell your packets or intentionally use your private saved work to train a public cross-user model. If a third-party generation service processes a request, its terms and data handling may also apply to that call.
08
Privacy ticket
Deleting saved work
Account deletion and saved-work deletion may require support routing while self-serve controls mature. Email support with the account email and what you want removed.
09
Privacy ticket
Payments
Payments are processed by Stripe. Creator Factory does not store full card numbers.
10
Privacy ticket
Contact
For privacy questions or removal requests, email support@creatorfactoryos.com or use the contact page.