Privacy notice

Version 2026-09-15. This notice covers the Planzoa website and application.

What we process and why

We use your name, email address, protected password record and session information to provide and secure your account. We process cloud projects, revisions, uploaded assets, comments and sharing decisions when you use those features. Support messages and account requests let us respond to you. These uses support our contract with you, our legitimate interests in providing a secure service, and applicable legal obligations.

Local and cloud work

Local evaluation stores projects in browser storage on your device. Importing and analysing a floor plan locally does not send it to an AI service. Choosing cloud saving, collaboration, provider lookup or another connected feature sends the information required for that feature. Property-data lookups may send location or site details to the selected data provider. Only use material you are entitled to share.

Connected sign-in providers

When you choose a connected sign-in provider, Google Firebase Authentication verifies that sign-in. We use the provider identifier, verified email address and display name to open or connect your Planzoa account. We do not receive your provider password or store provider access or refresh tokens. Connected methods open the same saved projects and subscription. Connecting to an existing account requires proof of ownership; you can manage connected methods from Your account. Signing in does not upload local models automatically.

Payments and service providers

Stripe processes payments and retains payment records. Planzoa stores subscription identifiers, status and billing dates, but does not store full card details. Where configured, Google Firebase processes password-reset email instructions and stores encrypted off-server backups. The email delivery provider configured for Firebase processes the email recipient and message. Service providers may process data outside your country; the operator must establish the appropriate safeguards for the deployment.

Cookies, browser storage and activity

A secure, HTTP-only session cookie keeps you signed in. Browser storage saves local projects and preferences. We collect bounded performance and error reports to diagnose reliability problems. With your consent, optional product activity records events such as opening the editor, creating a project, exporting and viewing pricing.

Optional Google Analytics helps us understand referring websites, campaign sources, approximate location, device categories and use of the app. It loads only after you allow analytics and uses first-party cookies for up to 90 days. We send known page names and limited campaign labels, not full query strings, drawing contents, project names, account identifiers or email addresses. If you allow analytics before opening checkout or the billing portal, we can associate your Google Analytics browser identifier with verified subscription payments and refunds for up to 90 days from that consent. Google receives the plan, currency, amount excluding tax, tax amount and a hashed transaction reference. It does not receive your card details, name, email address or Planzoa account identifier. Renewals may be reported without a browser session; attribution is therefore incomplete and Stripe remains the financial source of truth. Rejecting analytics removes this optional server association and queued reporting for it. Advertising personalisation and Google signals are disabled. Google may process this data outside the UK. See Google’s privacy policy and change your analytics choice at any time.

Our internal product records contain an event name and date; signed-in activity is associated with your account. They do not contain drawing contents, project names or free-text messages. Anonymous internal activity is counted without a tracking identifier. Browser Do Not Track and Global Privacy Control signals suppress optional client events and Google Analytics, including after an earlier opt-in. Essential account and billing records are still retained.

Retention

Product-event records expire after 90 days. Password-reset links expire after 30 minutes and stop working after use; previous sessions are revoked when you reset your password. The Firebase email queue is configured for short-lived message retention. Projects and account data remain available while the account is maintained, subject to an approved deletion request. Support and billing records may be retained where necessary to resolve issues or satisfy legal obligations. Backups expire according to the deployment retention schedule and are protected from ordinary user access.

Your choices and rights

You can download local project files, manage sharing and request access, correction, deletion or an account-data export through support. You may also have rights to restrict or object to processing, transfer your data and complain to your relevant data protection authority, including the UK Information Commissioner. We verify ownership before releasing or deleting account data and explain any legal reason for retaining records.