Privacy policy

When you create or use an Inspora account, Clerk handles sign-in and account security. This can involve your email address, authentication identifiers, sessions and the profile information you provide. Optional authenticator verification and backup codes are managed through your account security settings.

If you choose to connect X, the permissions shown by X allow Clerk to obtain the account information needed for that connection, including your X account ID, username, profile information and email when available. Inspora uses X identity and public profile information for creator profiles and ownership claims. Inspora requests read access for these features; connecting X does not authorize Inspora to publish posts or send messages for you.

Creator account ownership is separate from work attribution. Profile and ownership information may be reviewed to resolve claims, corrections, abuse or account requests. Information you choose to publish on a creator profile or approved work entry is visible to other visitors.

You can review or revoke the X connection through X's connected-app settings. Account connection controls are also available where supported in your Inspora account. Removing a connection and correcting published work attribution are separate requests.

When payment features are available and you use them, Stripe processes checkout and billing. Inspora keeps the account, payment references, status and history needed to provide and reconcile sponsorship.

Clerk, X, Stripe and PostHog process information for their respective services. Their privacy notices are linked below. Contact information and material you send with a support, correction or removal request are used to handle that request.

Inspora measures public page views and sponsorship delivery with its own accepted-event records. PostHog provides a separate audience source where configured. Private account, sponsorship and administrator pages are excluded.

Analytics visitor identifiers are not stored in cookies or browser storage. Our monthly anonymous counting key uses transient trusted network and browser information; raw IP addresses, full browser identifiers, account identities and sensitive URLs are not retained in our event records. Shared networks can count together, and changing networks or browsers can count again. Monthly resets can count a returning visitor again in a range crossing months. Missing trustworthy identity contributes delivery, with no invented unique visitor.

A sponsor impression requires at least half the placement to be visible continuously for one foreground second. Clicks count actual outbound activations. Unique visitors counts qualifying impression identities for sponsors and page-view identities for site audience; it is an estimate, not an exact count of people. Video figures measure the displayed preview and exclude repeat loops. A click does not prove a destination visit, signup or sale.

Country uses trusted deployment network geolocation, with an Unknown bucket when unavailable. VPNs, relays and incomplete mapping affect it; this does not establish a visitor's physical location or nationality. We retain coarse devices and sanitized referring domains. PostHog resets anonymous identifiers daily, so their longer-range reach cannot replace our monthly sponsorship reach. Work opens use a tab-only session that resets on reload or after thirty minutes of inactivity.

Accepted raw events are proposed for ninety-day retention only after whole-range and closed-period summaries are finalized. Aggregate reports and history remain for up to twenty-four months. Operational monthly secrets are destroyed one hour after rollover; retained recovery backups may still contain encrypted copies until those backups expire. Backup access is restricted, and secret destruction does not erase those copies.

Separate minute-scoped abuse-control keys bound new event and retry receipts. They never supply reach figures and expire after one hour; raw network addresses are not retained.

We do not use this data for targeted advertising or cross-site tracking. Person profiles, session replay, heatmaps, and automatic interaction capture are disabled. Sponsors may receive aggregate delivery and audience figures; they do not receive browser identifiers or event-level analytics data.

Do Not Track, Global Privacy Control and the site's analytics control disable all analytics collectors. A functional preference cookie stores only this choice, not a visitor identifier. You can disable analytics for your browser using that control on Inspora. The preference remains until you enable analytics again or clear this site's browser data. PostHog's own data handling is described in its privacy notice.

Use your account settings where available, or contact Inspora, to request an account correction or deletion. Sign-in accounts, published creator attribution and billing or operational history have different purposes and are handled separately. Records needed to resolve a request, prevent abuse or meet applicable recordkeeping obligations may be retained. Recovery backups can contain earlier captured copies until those backups are removed.

For questions about your account or information, corrections, or a rights-holder removal request, contact the Inspora team using the email below. Include the relevant Inspora URL and the information needed to identify and review your request.