What We Collect
When you sign in via GitHub OAuth, we store:
- Your GitHub user ID and login (username)
- Your avatar URL
- Your email address (if provided by GitHub)
- Your display name (if provided by GitHub)
When you use Pro apps, we store:
- Data you explicitly save in your apps (KV entries, database rows, uploaded files)
- Subscription status and Stripe customer ID (for billing)
- Per-(app, day) usage counts: session-minutes spent in each app and API calls made on your behalf. Used for platform operations and future creator reporting. See Usage analytics.
What We Don't Collect
- No analytics or tracking cookies
- No third-party trackers (Google Analytics, Facebook Pixel, etc.)
- No advertising IDs or fingerprinting
- No event-by-event logs, no IP-address profiling, no usage data sold or shared with advertisers
How We Use Your Data
- Authentication — Your GitHub identity lets you sign in across all apps.
- App data — Your KV entries, database rows, and files are stored so your apps work. Each app's data is isolated.
- Billing — Stripe handles payment processing. We store your Stripe customer ID to manage your subscription.
- Usage reporting — Coarse usage counts (session-minutes, API calls per app per day) help operate the platform and may support creator reporting. See below.
Usage Analytics
ProAppStore is a single subscription that unlocks every Pro app. We keep coarse per-app usage counts so the platform can operate, debug capacity, and support creator-facing reporting without tracking detailed behavior.
What we record, while you're signed in and a Pro app is the focused tab:
- A heartbeat every 60 seconds from
@proappstore/sdk, bumping a counter on (app, your user id, day in UTC). - Optional API-call counts that an app increments when it does work on your behalf.
What we do not record:
- Event-by-event session timelines — only daily totals.
- What you did inside the app (clicks, scrolls, content viewed).
- Your IP address or user-agent in these usage rows.
- Anything when the tab is hidden, backgrounded, or you're signed out.
Who sees what:
- You can see your own per-app usage on the Account page.
- Creators see daily aggregates for their own apps (active users, session-minutes, API calls). They cannot see per-user data.
- Stripe receives the payout amount, not the underlying usage data, when the monthly payout runs.
- No one else. We don't sell, share, or use usage data for advertising.
To opt out: don't sign in (the apps still work for free where applicable on FreeAppStore), or delete your account from the Dashboard — usage rows are removed with the rest of your account data.
Data Storage
All data is stored on Cloudflare's global network (D1 databases, R2 storage, KV). Data is encrypted at rest by Cloudflare. We do not transfer your data to any third parties except Stripe for payment processing.
Data Deletion
You can delete your account at any time from the Dashboard. Account deletion removes all your KV data, database entries, uploaded files, and subscription records. This action is irreversible.
Cookies
We use a single session cookie for authentication. No tracking cookies, no analytics cookies, no third-party cookies.
Third-Party Services
- GitHub — OAuth identity provider. GitHub Privacy Statement
- Stripe — Payment processing. Stripe Privacy Policy
- Cloudflare — Hosting and data storage. Cloudflare Privacy Policy
Changes
We'll update this page if our practices change. No email notifications — check back here.
For developers
Most Pro apps don't need their own privacy policy — this page already covers sign-in, billing, storage, usage analytics, and account deletion. If your app does something app-specific that this page doesn't already describe, copy the app privacy policy template, fill in the blanks, and link the result from your app's listing in the Creator Console.
Contact
Questions about privacy: open an issue on GitHub.