Public beta
Fourlayer privacy notice
Last updated: 24 August 2026
What the beta handles
Fourlayer receives Google sign-in identity information needed for your account, including your email and basic profile details. It also stores the display name, role, and primary goal you choose as private account metadata.
Workspace content
Cloud workspaces include the architecture model, layout, name, description, icon, and sharing data required to provide editing and collaboration. Older browser-only drafts stay in the browser until you explicitly import them.
How data is used
Account and workspace data are used to authenticate you, save your work, enforce access controls, and provide the features you choose. Role and primary-goal metadata do not yet change the beta experience and are never shown in diagrams.
Storage and access
Fourlayer uses Supabase for authentication and cloud persistence. Workspace access follows the owner and collaborator permissions selected inside the product.
Account deletion
When account deletion is available in the running environment, the product asks you to confirm your email before permanently removing the account and associated data.
This public-beta draft describes the product as it is currently implemented and is pending legal review. Read the beta terms.