Option A
Anonymous Usage Metrics
For visitors who do not create an account or sign in.
-
✓
What: IP address (truncated), device type, browser version, pages visited, session duration.
-
✓
Why: To diagnose technical issues, understand feature usage trends, and improve site performance. No personal profiles are built.
-
⚠
Limitation: This data is aggregated and cannot be used to contact you or personalize your experience. It's purely for our internal analytics to build a better tool.
Best For...
Casual browsers, research-only visitors, or developers evaluating the platform without commitment. You get service, we get operational insight.
Option B
Account & Community Data
For users who create an account to save projects or join the community.
-
✓
What: Email address, password (hashed), username, project metadata (saved tool configurations, preferences), and optional profile information.
-
✓
Why: To authenticate you, sync your work across devices, provide a personalized workspace, and enable community features (like sharing prototypes).
-
⚠
Responsibility: You control your project visibility. We do not sell your project data. Your saved configurations are yours; we access them only for backup and restoration.
Best For...
Active developers, indie studios, and teams building real products. You get a persistent workspace, we get the ability to help you succeed.