Privacy policy

Contact requests and form security

When you submit a contact form, we process your name, email address and message to answer your request. Messages are delivered to info@build3dfloorplans.com through our transactional mail service. Do not include passwords, payment details or unnecessary personal information. Contact messages may remain in the support mailbox while needed to handle the request and associated service or legal obligations; you may request deletion using info@build3dfloorplans.com.

When enabled, Google reCAPTCHA protects form submissions against automated abuse. It processes browser, device and interaction signals and technical connection information, including your IP address, to assess whether a request is legitimate. We submit a verification token to Google and evaluate the result on our server. We do not send your form fields, message, password or floorplan content in that verification request. This security service is separate from optional Google Analytics and is not enabled by accepting analytics cookies. Our purpose and legal basis are the legitimate interest in protecting accounts and the service against spam, fraud and abuse. Google processes information under its Privacy Policy and Terms of Service. If verification prevents a contact request, you can email us directly.

About this policy

This policy explains how Build3D Floorplans processes personal information when you visit build3dfloorplans.com, create an account, sign in with Google or LinkedIn, upload and edit floorplans, collaborate, publish plans or purchase a subscription. Google sign-in is optional; email-and-password registration is also available. Agreeing to Google sign-in does not grant consent to audience analytics or advertising.

Google sign-in: information we access and collect

When you choose Sign in with Google, we request the OpenID Connect permissions openid, email and profile. Google supplies a unique account identifier, your email address and its verification status, and basic profile information such as your name. The profile response may also include a profile-picture URL or other basic profile fields; our sign-in integration does not save or display those additional fields. We save the Google account identifier as a linked sign-in identity and, when creating an account, your email address and name. We require a verified email address.

We do not request access to Gmail messages, Google Drive files, Google Calendar, Google Contacts or any other Google account content. Uploading a drawing to our service does not give us access to your Google Drive. Your Google password is entered on Google’s own sign-in page and is never provided to us.

How we use Google user data

We use the identifier to recognize your linked account and sign you in, your email address to create and administer your account and send essential account, security and service messages, and your name to identify your account within the service. The verified-email result helps prevent unverified account creation. If you link Google to an existing account while signed in, we store the linked identifier for future authentication; matching email addresses alone do not automatically merge accounts.

Google user data is used to provide the sign-in and account features you request, on the contractual basis described below. We do not sell Google user data, use it for targeted advertising, provide it to data brokers, or use it to train generalized artificial-intelligence or machine-learning models. Our analytics integration does not receive Google sign-in identifiers, names or email addresses.

Google user data: storage, access and sharing

Account names, emails and linked Google identifiers are stored in our service database on OVHcloud infrastructure and may be included in encrypted operational backups. The sign-in code uses Google-issued tokens to authenticate the sign-in response and retrieve basic identity information; it does not save those tokens in our account database or request offline access for background Google API activity.

Access to stored account information is limited by application permissions and operational access controls. Authorized service operators and infrastructure providers may process it to operate, support and secure the service. Our transactional email provider processes recipient addresses when delivering account messages. Workspace collaborators may see account information exposed by the collaboration features; Google account identifiers and authentication tokens are not included in public floorplans. Google receives the authentication requests you initiate and processes them under Google’s privacy policy. We may disclose relevant records when legally required. We do not otherwise transfer Google user data for purposes unrelated to these disclosed service functions.

Build3D Floorplans’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google access, retention and deletion requests

We keep the linked Google identifier while the sign-in connection is associated with your account, and account information while needed to provide the service. You can remove our connection from your Google Account connections. Removing access prevents further use of that authorization but does not itself erase the account information we already hold, delete your projects, or cancel a paid subscription.

To request removal of the Google sign-in connection, deletion of Google-derived account information, or deletion of your service account, email info@build3dfloorplans.com from your account email and describe the request. We verify your identity proportionately and explain any information that must be retained for a legal obligation or a specific security need. Arrange another sign-in method before requesting removal of your only sign-in connection. We normally respond within one month. Backup copies are handled separately from the active database; we will explain applicable backup retention and any deletion limits in our response. Do not send us your Google password or authentication tokens.

Optional audience analytics

With your consent, we use Google Analytics to understand visits to public pages. Analytics is blocked until you accept it. It can process browser and device information, technical connection information and public-page visits associated with cookie identifiers. Our integration excludes private account, editor, shared-plan, embedded-plan and authentication pages, strips URL queries and fragments, and does not send account names, emails or floorplan content. Google signals and advertising personalization are disabled.

The legal basis is your consent. Open Cookie settings to change or withdraw it. Consent choices and our analytics cookies last up to 180 days; Google’s server-side retention is controlled separately in the Analytics property; the 180-day browser-cookie lifetime is not a promise that Google deletes server-side data at that time. Contact us for the current property retention setting. See the cookie policy and Google’s privacy policy for details, including international processing. Withdrawing consent does not automatically delete data already collected.

Who is responsible?

Ali Ghaith, operating Build 3D Floorplans is responsible for the personal data processed to operate Build3D Floorplans, including account, billing and service-administration data. Contact info@build3dfloorplans.com about privacy or to request operator contact details. For personal data that a customer puts in floorplans, contacts or reservations, that customer decides how the information is used; contact them first about their records.

Information we process

We process your name, email, password hash or linked sign-in identity; workspace membership; profile and invoice details you provide; subscription, payment and invoice references; uploaded drawings and images; floorplans, contacts, reservations and activity records. Service requests can also include IP addresses, browser information, timestamps and security logs.

Stripe hosts payment checkout and billing management. PayPal, when available, is processed through Stripe. We receive payment status and billing references, not your PayPal password or full card number.

Why we use it

• To create accounts, convert and store drawings, collaborate, publish plans and administer subscriptions: performance of our contract.
• To prevent abuse, secure accounts and investigate faults: our legitimate interests in protecting the service and its users.
• To retain required invoice and accounting records: legal obligations.
• For optional advertising or other consent-based tracking: your consent, where required, before it is enabled.

Account and service messages include verification, security and billing notifications. Required form fields are necessary for the requested service; without them we may be unable to create an account or process an order.

Sharing and service providers

Authorized workspace members can access information according to their permissions. Publishing a plan makes its published content accessible to people with the shared link, including through an embed. Links can be forwarded; do not publish confidential or personal information without permission. Unpublishing cannot recall copies already made by others.

Hosting: OVHcloud. The service runs on an OVHcloud VPS. Encrypted backups are held on that server, with restricted recovery copies on an operator-managed computer.. Email: OVHcloud transactional email. Payment processing: Stripe and, when chosen, PayPal. If you choose Google or LinkedIn sign-in, that provider supplies the identity information needed for authentication and applies its own privacy notice. Data may also be disclosed where legally required.

Retention and international transfers

Account and saved project data remain until deleted or no longer needed to provide the service; there is currently no automatic expiry for inactive accounts. We review deletion requests individually and explain any records retained for accounting, legal claims or a specific security need. Operational logs rotate according to configured size limits rather than a fixed number of days. Encrypted backups currently have no automatic expiry schedule, so removal from the active service does not immediately erase historical backup copies. Contact us for deletion and retention questions.

Temporary import uploads are scheduled for removal after their configured expiry, normally 24 hours. This does not delete saved library files or resulting plans. Billing cancellation does not automatically delete your account or its records.

Google, Stripe, PayPal and other providers may process information in countries outside your country of residence, including outside the European Economic Area. Their privacy notices explain their processing locations and transfer arrangements. Contact us for information about the arrangements applicable to your data. This notice does not imply that every provider or backup is located in France.

Your choices and rights

You can request access, correction, deletion, restriction or portability of your personal data, and object to processing based on legitimate interests where applicable. You can withdraw consent without affecting earlier lawful processing. Send requests to info@build3dfloorplans.com; we may need proportionate information to verify your identity. We normally respond within one month, with any lawful extension explained to you.

You may complain to your local data protection authority. In France, contact the CNIL. Our service is intended for adults and authorized organizational users. Contact us if a child has supplied personal data.

Security and updates

Access controls, password hashing and other technical measures help protect information, but no system is risk-free. Keep your credentials and private sharing links secure. We update this notice when the service or its processing changes; the date above identifies this version. See our cookie policy for browser storage.