FigpeaWhat We Collect
Figpea processes your design files entirely on your machine — files never leave it, so there is nothing file-shaped to send anywhere. The analytics we run on this website collect metadata only: event payloads carry no file names, no file contents, and no email addresses.
The two systems we run
- Google Analytics 4 records page views and the small set of behavior events listed below, so we can understand how visitors move through the site (for example, from the pricing page to checkout).
- Vercel Analytics records anonymous, cookieless page-view counts only — a raw traffic baseline. It never receives custom events.
Every event we send
This is the complete list of behavior events this website sends, together with every piece of data each one carries:
| Event | When it fires | Data it carries |
|-------|---------------|-----------------|
| editor_open_click | You click a link that opens the Figpea editor | source_path — the path of the page you clicked from (never the query string) |
| checkout_started | You start a checkout | billing — the billing interval (monthly or yearly) |
| checkout_completed | You return from a successful checkout (counted once per checkout) | billing — the billing interval |
| login_completed | You sign in (counted once per login) | nothing |
What is never collected
Our analytics never include file names, never include file contents, and never include email addresses or other personal details. Event parameters are checked against the allowlist above at runtime — anything outside it is dropped before an event is sent.