Privacy Policy

1. Who is responsible

This policy covers the my3dhouse website, iPhone and iPad app, private house viewers and published house pages. The controller responsible for the personal information described here is Marcus Greenwood trading as my3dhouse, an individual sole trader. “We”, “us” and “our” refer to that operator.

Contact mg3d@ub.io or write to Leigh Park Road, Leigh-on-Sea, SS9 2DU, United Kingdom for privacy questions or requests.

2. Information we collect

• Your references and instructions: photographs, plans, elevations, PDFs, filenames, descriptions, edit requests and house names. Files may contain addresses, people, location metadata or other embedded information. Please remove details that are not needed for the model.
• Your house: generated scenes, models, previews, versions, build progress, publishing choices and public descriptions.
• Contact information: the email address you provide for completion notifications, your notification preferences and any support correspondence.
• Library access: a random credential stored in your browser or app, with a corresponding hashed identifier on our server. This connects your houses and purchases to your device’s library without a conventional sign-in.
• Orders: purchase identifiers, amounts, currency, discounts, payment status and edit balances. Stripe handles web payment details; Apple handles in-app payments where available. We do not receive your full card number or card security code.
• Technical records: IP addresses and request information used by our hosting and security systems, errors, build activity, timings, resource and model usage counters, and email delivery status. Operational usage records are private.
• Website analytics: Google Analytics receives information about visits to our website pages, including cookie identifiers, page views, browser and device information, and general referral sources. We do not send your uploads, prompts, notification email or library credential to Google Analytics.

The app only imports photos or files you select. We do not request access to your entire photo library, contacts or device location. The iOS photo picker re-encodes selected photos, but we do not promise to remove metadata from every uploaded file.

3. How a house is made

Your uploads, house records and generated files are stored using Cloudflare’s database and private object storage. An external rendering server downloads the references, prepares images and pages from plans, and uses Blender to build and export the model.

Reference images, pages from documents and your instructions are also sent to OpenAI through ChatGPT/Codex using the operator’s account. AI inference happens in OpenAI’s cloud. This processing takes place on external servers; it does not stay on your device or happen offline.

OpenAI’s retention and any use of content to improve its models depend on the service and the operator’s account settings. We do not offer a guarantee that submissions are excluded from OpenAI model training or immediately deleted by OpenAI. See OpenAI’s Privacy Policy and its explanation of model improvement. Your personal ChatGPT settings do not control the operator’s account.

The operator may review references and builds to provide support, fix errors and check reconstruction quality. Do not upload passwords, financial documents, security codes or other sensitive information unrelated to the house.

4. Why we use information

Under UK data protection law, we rely on the following bases where personal information is involved:

• Contract: to prepare and perform the service you request, including receiving references, generating and editing models, keeping your library, processing orders, hosting a publication you request and sending requested service updates.
• Legitimate interests: to keep the service secure, prevent fraud and abuse, diagnose failures, handle support and disputes, and understand the resources needed to run the studio. We balance these interests against your privacy and do not use these records for advertising.
• Legal obligations: to maintain necessary financial records and respond to lawful requests.
• Consent, where required: for processing that requires your permission. If we rely on consent, you may withdraw it by contacting us; withdrawal does not affect processing already carried out lawfully.

References and instructions are needed to build a house. The creation form asks for an email so we can notify you when it is ready. You can change the address or switch off future completion emails in your house’s Details. We do not use completion addresses for newsletters or promotional messages.

We generate architectural visualisations, not decisions about people with legal or similarly significant effects.

5. Private houses, public houses and email links

Uploads and unpublished models are not publicly listed. Owner access requires the library credential stored on your device. Anyone able to use that browser or app may access its library, so use your device’s own security controls.

If you publish, your chosen title, description, model and a rendered social preview become public at a shareable address. They may be indexed by search engines or copied by visitors and social platforms. Reference photos and plans are not included on the published house page. Later edits remain private until you publish an updated snapshot.

Completion emails contain a private viewing link to that completed version, valid for 30 days. Anyone with the link can view the model, including someone you forward it to. The link does not grant editing access or access to your references. Its expiry does not delete the house.

To request removal of a public house or revoke access to an email link, contact mg3d@ub.io. We may need to verify your connection to the house. Copies already saved by other people or platforms may remain outside our control.

6. Providers and international processing

Our principal providers are Cloudflare for hosting, storage, security and email delivery; OpenAI for interpreting references and generating model instructions; Stripe for web payments; and Apple for app distribution and in-app purchases where available. Your email provider also processes messages sent to you. Payment providers use some information for their own fraud prevention and legal responsibilities under their policies.

Google provides website usage measurement through Google Analytics. See Google’s Privacy Policy and how Google uses information from sites that use its services.

These providers operate internationally, including in the United States. Information may therefore be processed outside the UK. Applicable protections depend on the provider, destination and service, and may include adequacy decisions or contractual transfer safeguards. You can contact us for details of the arrangements relevant to your information; providers also describe their transfers in the policies linked above.

We do not sell your personal information or share it for targeted advertising. We may disclose information where required by law or reasonably necessary to protect people, resolve a dispute or prevent misuse.

7. Device storage and cookies

The website uses essential browser local storage to remember your library credential. The iOS app stores its own credential in its private app data. These libraries are separate; clearing website data or removing app data may permanently remove your owner access. An email viewing link is not an account recovery link.

The website uses Google Analytics to understand visits and improve the service. The Google tag loads automatically on website pages and may set analytics cookies. You can use browser controls or tracking-blocking tools to limit analytics cookies and requests.

Private email viewing links are counted under a generic page address without their access tokens or private house titles. Query strings and URL fragments are omitted from our page configuration, and referral information is limited to the referring site’s origin. Google advertising signals and ad personalisation are disabled. The native iOS app does not include this Google Analytics tag.

Hosting security features and payment providers may use essential cookies or similar technology when you use their services. You can control website storage in your browser, but blocking or deleting the library credential prevents normal library access.

8. Retention and deletion

We keep references, instructions, models and versions while needed to provide your saved house, further edits and requested hosting. Build files and diagnostic records also remain on the rendering server. There is currently no automatic expiry for house projects or rendering job folders; deleting your browser or app data does not delete these server copies.

Contact mg3d@ub.io to request deletion of a house, its references or associated personal information. We review whether anything must be retained for a legal obligation, unresolved payment issue, dispute or security investigation, and explain any applicable exception. Otherwise, the request covers our cloud storage, rendering files and copies under our control. Deletion and unpublishing are currently handled by the operator, rather than a self-service button.

Retention of order and financial records depends on applicable tax and accounting duties. Support, email delivery and security records are kept for as long as reasonably needed to resolve the issue or meet those duties. Restricted backups may retain copies while needed for recovery; we consider these in deletion requests and avoid reintroducing deleted records if restoring a backup. Providers may retain records under their own applicable obligations and policies. We cannot erase copies independently saved by public viewers.

9. Your choices and rights

Depending on the circumstances, you can ask to access, correct or erase your personal information, restrict its use, or receive a portable copy. Where we rely on consent, you can withdraw it.

You have the right to object to processing based on our legitimate interests. Tell us about your circumstances so we can consider your request.

Email mg3d@ub.io with your request and, if relevant, the house address or order reference. Do not send your library credential or card details. We may ask for proportionate evidence of ownership to protect other people’s information. We normally respond within one month, subject to the extensions and exceptions permitted by law.

You can complain to the Information Commissioner’s Office (ICO) in the UK, or your local data protection authority. You do not have to contact us first, although we welcome the chance to help.

10. Children, security and updates

The house-creation and purchasing service is intended for adults aged 18 or over. We do not knowingly collect children’s information for their own use of that service. If you believe a child has submitted personal information, contact us.

We use HTTPS, private storage and access checks to protect information, but no system or shared link is completely secure. We update this policy when our practices change and show the effective date above. For material changes affecting existing information, we will provide an appropriate notice.