Privacy information

This app is a development preview. A complete operator-specific privacy policy must be published before public launch.

Account and billing data

When connected, Supabase processes sign-in and stores saved references, collections, workflow unlocks with their grant date and month, and subscription status. Unlocks are linked to your account to enforce the monthly allowance and retain access; they are deleted with your account. Stripe processes payments and billing details. The app stores Stripe customer and subscription identifiers, rather than payment-card details. GitHub provides repository-hosted images through the app's server.

Product feedback

Signed-in users can send private feedback to the Mobitech owner. We retain the message, category, language, date and account ID. A reply email and page path are included only when you provide or select them. Search terms and private collection links are not attached. Messages stay in Supabase, are separate from visitor analytics and are deleted with the account. A per-account counter limits submissions to five per hour.

Optional audience measurement

With your permission, Mobitech stores random browser identifiers (30 days), session identifiers (30 minutes of inactivity), public page paths, referring domains and allowed campaign labels. The first landing visit can be linked to a new account within 30 days, its first saved reference, its free workflow unlocks and its first confirmed Pro activation. IP addresses, form contents, search queries and full referring URLs are not stored in these statistics. Data stays in our Supabase project; no third-party advertising tracker is loaded.

Your choice is remembered for six months in browser storage and a preference cookie containing no visitor identifier. This cookie only controls the consent prompt; it never enables tracking. Use Analytics preferences at the bottom of the site to decline or withdraw consent without restricting catalog access. Visits and page views older than 90 days are removed by daily cleanup when collection runs. Withdrawal stops new tracking and clears browser identifiers; it does not erase previously recorded measurements. Only the account ID, first-save date and free-unlock dates are retained to measure product activation, without copying workflow IDs, references or notes into analytics. This history and first Pro activation history remain with account and billing records.

The operator's identity, contact details, retention policy, account-deletion process, and applicable privacy rights have not yet been configured. Don't collect production customer information until this policy and those processes are finalized.