Legal
Privacy Policy
Plain-English starting privacy policy for FanaticFactory. Replace this source with counsel-reviewed policy language before public launch if required.
Contact us01
Information we use
FanaticFactory may use account, member, factory, and activity information to provide the app experience, support communities, improve the product, and understand which public pages help visitors choose a next step.
02
Public and private content
Public marketing pages are intended to be crawlable. Private Factory content, member-only content, and prospect-specific previews should not be indexed unless deliberately published.
03
Analytics on public pages
FanaticFactory may use privacy-conscious product analytics on public marketing pages to understand visits, page paths, referrers, button clicks, form submissions, guide interest, pricing interest, and private-preview interest. These events help us improve the public site and decide which owner education or setup paths are useful.
- Analytics events are intended to describe page and product behavior, not sensitive Factory content.
- Public analytics may include browser, device, approximate location, referrer, page URL, and clicked link context supplied by the browser or analytics provider.
- FanaticFactory does not intentionally send private Factory posts, DMs, payment details, passwords, or member-only content through public-page analytics events.
04
Cookies and local storage
Analytics tools may use cookies, local storage, or similar browser storage to distinguish repeat visits, avoid counting the same visit as unrelated traffic, and connect anonymous public-page behavior into a useful funnel.
05
Analytics provider
The public site is prepared to use PostHog for product analytics. PostHog may process analytics events for FanaticFactory according to its own infrastructure, retention, and security practices. If analytics is enabled, FanaticFactory should keep this page aligned with the live provider configuration.
06
Opt-out and controls
Visitors can use browser privacy controls, tracker blockers, cookie controls, or similar tools to limit analytics collection. Account-specific privacy questions should go through the contact path.
07
Contact
Questions about privacy, account data, or community data should go through the contact path.