Appbase website analytics

Optional analytics helps us understand which guides are useful and whether people can set up Appbase. You can use the product with analytics declined.

What allowing analytics means

We store a random browser identifier and a limited acquisition source for up to 180 days. We send selected page paths, signup-button clicks and setup milestones to PostHog. After you sign in, we connect those events to an opaque Appbase account identifier. Setup milestones include creation of a verified workspace, creation of an app, first delivery of an explicit SDK event and a mapped RevenueCat connection.

We do not send form contents, email addresses, sign-in codes, setup tokens, API keys, customer mobile event properties, feedback messages or payment details as website analytics. Private app routes are reduced to a dashboard label. We do not record sessions or automatically capture clicks. Appbase does not forward your IP address for analytics, and IP-based location enrichment is disabled.

Change your choice

Use the preference controls on this page to allow or decline. Declining stops future browser events and, while signed in, disables queued and future account milestones. If saving the account preference fails, retry while signed in. It does not delete events already delivered. Contact Appbase for help with previously collected analytics.

We honor browser Global Privacy Control and Do Not Track signals. Signing out clears the browser analytics identity so another account is not linked to it. If you change a preference while signed out, sign in to apply that choice to your account’s future setup milestones.

This describes Appbase’s own website and SaaS telemetry. Events you deliberately send from your mobile app to your private Appbase workspace are a separate product dataset.