Privacy.

Zaltt Ltd is responsible as controller for website enquiries and analytics, business contacts, account administration, allowances, security, usage records, terms acceptance and support. Unmesh Lele, the founder, handles enquiries personally.

Zaltt Ltd, registered in England and Wales, company no. 17240841, registered office 124–128 City Road, London EC1V 2NX.

For privacy questions or a request about your information, email hello@zaltt.com. This notice covers website visits and optional analytics, enquiries, business contacts we email about Bloooom, Google sign-in, the Revit plugin and the Free cloud rendering service. The service sections below explain the project information involved. Paid checkout and Local AI installations are outside this Free launch notice.

1. The studio form asks for your name, email address, project type and project details.
2. The Bloooom form asks for your name, email address, Revit version and confirmation that we may contact you about your interest. You can add a message, including the plan you are interested in.
3. The website records when an enquiry arrives. The forms use temporary signed tokens and identifiers derived from your email address to limit spam and repeated submissions. The identifiers used for submission limits are held in server memory, separate from enquiry records. The enquiry handler does not store your raw IP address.

We also receive anything you choose to send by email. Please leave out passwords, payment details and sensitive information about yourself or other people. Neither form asks for payment card details.

We use your details to understand your request, reply and discuss the service or trial you asked about. Where you ask us to take steps towards a contract with you, our lawful basis is taking those steps before entering a contract.

For general questions, enquiries on behalf of a business and website security, we rely on legitimate interests: answering relevant enquiries, discussing our services and protecting the website from abuse.

Submitting a form does not sign you up to a mailing list. The Bloooom contact confirmation applies to your enquiry, not unrelated marketing. The forms do not make automated decisions about you.

You choose whether to send an enquiry. We need the required fields to receive it through the form; email is also available.

Microsoft Azure hosts this website and stores form submissions as private records in Azure Table Storage in UK South. They are not published as website pages. Unmesh reviews them and replies personally. Azure also processes technical request information to deliver and protect the website.

Microsoft 365 processes the email messages we send and receive. Microsoft Azure and Microsoft 365 act as service providers for these purposes. Their data-protection terms describe how they handle personal information, including their safeguards for international transfers. You can contact us for details.

We keep unanswered enquiries from both the studio form and the Bloooom form for up to six months, unless you become a client, start a trial or keep the conversation going.

A monthly reminder identifies enquiries from both forms approaching or at six months. Unmesh reviews them and deletes records that are no longer needed. This is a manual review, not an automatic deletion timer. For clients, trials and ongoing conversations, we keep what is needed to handle the request, provide the service or meet a legal obligation.

Copies may also exist in email correspondence and backups. Deleting an active enquiry does not immediately erase every backup copy. Tell us if you want us to check the copies we hold as part of a deletion request; we will explain any legal reason to retain them.

You can ask about a particular record or request deletion at hello@zaltt.com.

The website stores your light or dark theme choice in your browser under zaltt-theme. You can remove it by clearing this site's browser data. The site still works without that preference.

Optional analytics is described below. Form security uses temporary request tokens, spam traps and submission limits. The forms do not use an external CAPTCHA service.

Depending on the circumstances, UK data protection law gives you the right to ask for a copy of your information, correct it, request erasure, restrict its use, object to processing based on legitimate interests, or receive certain information in a portable format.

Email hello@zaltt.com to make a request. Tell us which enquiry, business contact, account or service record it relates to. We may need to check your identity before sharing or changing personal information. We will explain if a legal exception limits what we can do.

You can also complain to the UK's Information Commissioner's Office at ico.org.uk/make-a-complaint.

We will date changes to this notice and explain material changes to how the website or Free service handles information. Updating this notice does not change an earlier agreement or replace any acceptance or consent that is required.

Start for Free opens a separate get-started page on the Bloooom by Zaltt website. Google and Auth0 verify your email before the installation guide. On first use, Auth0 may create an identity for you. The website does not grant the Free allowance. After sign-in, the website checks the published Windows installer and starts the download when it is available. Signing in does not grant renders, verify Student eligibility or take payment.

The website requests sign-in and email access. It shows your email only when the Auth0-validated identity marks it as verified. The protected sign-in transaction identifies the Free journey, without selecting a paid plan. Your email stays in page memory; the website does not submit it to an account or billing service or record legal acceptance. The terms and age check take place in the Revit plugin. It does not copy your name, photo or phone number into website records. Google and Auth0 handle your identity information under their own service arrangements. Auth0 can retain an identity after you close this page or change account.

After verified sign-in, the page checks Microsoft Azure Blob Storage for the Windows installer. When it is available, the download starts automatically. The page does not send your email or sign-in token with the availability check or download. Microsoft Azure receives the technical request information needed to deliver the file.

Website session tokens are held in page memory, not local storage. Reloading the get-started page begins signed out. Browsers may retain a page in memory when you navigate away and return with Back; the website checks the session again when the page returns. The SDK uses session storage for the security information needed to complete sign-in, then removes it when it handles the return. An abandoned attempt remains until the tab's session storage is cleared. A first-party sign-in marker cookie lasts up to one day and is removed when you change account or begin a fresh get-started page session. It contains no email or token. Ordinary landing-page visits do not initialise authentication.

Auth0 and Google may set their own sign-in cookies. Their observed cookie names and durations still need checking during the founder's real sign-in test.

Choosing another account clears this website's authenticated state. It leaves your Auth0 and Google browser sessions and any Revit sessions unchanged. You can still browse the site and enquire about a trial without signing in.

This section describes website sign-in. The Free service sections below cover the account service and Revit plugin. For a question about your identity or a deletion request, email hello@zaltt.com. Signing in on the website does not record acceptance of product terms.

We may contact people at architecture practices about Bloooom where it is relevant to their professional work. We use the practice's name and company details from Companies House, and information it publishes on its own website: business email addresses (which can include a named person's work address), published landline numbers, team size where stated, the kinds of work it does and whether it mentions Revit or BIM. We keep the source and collection date and a limited record of our contact and any reply. We do not use LinkedIn, bought lists or guessed email addresses, and we do not keep separate staff details. We also check whether the practice's domain receives email through Cloudflare's public DNS service. That check uses the domain name, not an email address.

Our basis for this processing is legitimate interests: introducing a relevant professional tool to architecture practices and managing those business conversations. We assess whether the contact is necessary, proportionate and reasonable for the person receiving it. A public business address is not, by itself, permission to send every kind of marketing message. We apply the email-marketing rules that apply to the recipient.

We send and manage email with Microsoft 365. We used Claude Pro, provided by Anthropic, to research practices and draft messages, with the account's "Help improve Claude" setting switched off. Prospect information passed through Anthropic's service. We keep the prospect list and a spreadsheet of sends and replies on the founder's computer. Apart from the service providers described in this notice, we have not shared the prospect list outside Zaltt. We do not use a separate marketing or contact-management service.

For UK contacts, Anthropic Ireland, Limited is a controller under Anthropic's Non-User Privacy Policy. Anthropic may process information in the US and other countries outside the UK. That policy explains its retention, privacy rights and international-transfer safeguards. Its model-training explanation describes the effect of the account setting and the exceptions for safety reviews and feedback.

If you do not reply and there is no ongoing business conversation, we keep prospect information for up to 12 months from the date we collected it. We then remove it from the active prospect list. A reply or continuing business relationship follows the applicable enquiry or customer retention schedule described in this notice.

You can object to direct marketing at any time, including processing carried out for that marketing. Reply to the message or contact hello@zaltt.com. You do not need to give a reason. We will stop using your information for that marketing and remove it from active outreach. We keep only the contact identifier needed to prevent another message, the scope of the objection and when it was received, for as long as needed to honour your choice. This minimal do-not-contact record is separate from the active prospect list.

If you would rather not hear from us about Bloooom, reply "no thanks" and we will stop contacting you about it.

Bloooom's Free cloud service is for people aged 18 or over. It includes Google sign-in, the Revit plugin and an allowance of 20 renders and five enlargements a month, with no daily cap. Paid checkout and a Local AI installation are outside this Free service notice.

We use the images you upload to make the render or enlargement you request. We do not use your images or outputs to improve or train models. The workflow sends your chosen view or enlargement input, not the complete Revit project file.

Do not submit client work covered by an NDA or another confidentiality agreement, or material that requires deletion by a fixed deadline. Use your own non-confidential test material. Leave out passwords, payment details and personal information that is not needed for the request.

Bloooom does not receive your Google password. The website does not copy your name, photograph or phone number into its records. Google and Auth0 may process further information under their own arrangements. We do not ask for an Autodesk token or licence file to check an allowance.

A signed-in device is one Windows user profile on one computer. Compatible Bloooom plugins in that profile share account and sign-in state. Signing out through one signs out the other Bloooom plugins in the same profile. Sign-in is not shared across Windows users, and each signed-in profile occupies a device slot.

An account can have two active devices. Signing in on a third signs out the one used longest ago, and the plugin shows which device was signed out. Contact us if you need help with a device or session.

The shared Free computer allowance is separate from the device limit. Accounts on the same physical computer share one Free allowance, including across different Windows profiles. A shared Autodesk allowance also applies when Revit supplies that identifier. Each account and each applicable shared allowance has 20 renders and five enlargements a month. The allowance with the least remaining use applies.

Each shared allowance renews on the monthly anniversary of its first Free sign-in. Your account has its own anniversary. Creating another account does not reset a shared date. There is no daily cap, and only one render can run at a time.

The raw Windows machine and Autodesk identifiers stay on your computer in this process. If the Autodesk identifier is unavailable, the plugin leaves it out rather than reading another Autodesk value. These identifiers do not prove hardware identity or ownership of an Autodesk account. Cloned computers can share an allowance.

The stored hashes and links to accounts are pseudonymous personal data, not anonymous data. We use them to apply the Free allowance and prevent extra free use through several accounts. They contain no Autodesk name or project content and are excluded from routine logs and support reports. Ordinary account and support records are separate.

When more than three accounts share a computer or Autodesk identifier, an operator sees an informational alert with aggregate counts. The alert does not itself block an account or render, or establish misuse. Allowance limits still apply. Email hello@zaltt.com if you believe an allowance has been applied incorrectly.

We process the information needed to provide your account and requested renders, administer allowances and device limits, and answer service support requests to perform our contract with you or take steps you ask for before it.

For service security and prevention of abuse, including shared-allowance checks and informational alerts, we rely on legitimate interests in protecting Bloooom and keeping the Free allowance fair. General enquiries and messages from business representatives follow the legitimate-interests basis described above. We retain terms-acceptance evidence for our legitimate interests in keeping a reliable contract record and handling claims. Where a specific legal obligation applies, we process the information needed to meet it.

Usage records help us answer support questions, operate allowances, prevent abuse and understand how Bloooom is used. The optional improvement uses below are separate from the processing needed to deliver your request.

Optional improvement and training

After a later update, only Zaltt may use recorded typed text, settings and usage to improve Bloooom and train or fine-tune models for Bloooom. This can include the words people type, their choices, repeated requests, timings, failures and actions in the plugin. Our basis is legitimate interests in understanding and improving the product. We keep this optional information for up to 24 months from collection, then delete it.

We do not keep your submitted images or outputs for product improvement and never train or fine-tune models on them. We do not sell your images, outputs, recorded typed text, settings or usage, or use them for advertising. This permission does not allow another business or customer to train on the records.

The launch software keeps its existing cleanup controls. The additional retention, behaviour collection and model training described here are future uses, not features already running. Website analytics follows the separate analytics consent choice.

You can object to optional improvement, including training and fine-tuning, at any time by emailing hello@zaltt.com. We will exclude your records from future optional analysis and training. This does not stop processing needed to deliver your requests, run your account and allowance, provide support or protect the service.

An opt-out does not reverse training already completed. Deleting a source record does not automatically remove its influence from an existing model. We will assess requests about records and models under the rights described in this notice; we do not promise that a trained model can be untrained.

A Settings switch for optional improvement and behaviour events will follow after launch. Until then, email is the opt-out route. Accepting product terms is not consent to website analytics or unrelated marketing, and these new terms do not change the agreement governing earlier work.

Automatic expiry and cleanup controls are intended to remove temporary job content after processing. We have not proved complete removal of every copy on a fixed schedule, including after errors or from older backups. Images, typed text and settings may remain after a job ends. We do not promise deletion within two hours or another fixed period for this temporary content. You can ask us to delete it at hello@zaltt.com.

Existing cleanup also removes typed text, style choices and job output dimensions from ordinary usage records, but complete removal within a fixed time has not been established. A separate usage or recognition record can still be personal data. Images and outputs are excluded from improvement retention and training; that is not a claim that every processing or historical copy has already disappeared.

The website enquiry and business-contact periods above remain separate: up to six months for unanswered enquiries and up to 12 months for unanswered outreach. Signing out, uninstalling or an image expiring is different from closing an account. Contact us to request closure or ask about a particular record.

If a legal obligation or a specific claim requires us to keep information beyond the ordinary period, we restrict it to that purpose and explain the reason when responding to a request. We do not treat a possible future dispute as permission to keep every record indefinitely. The handling of information submitted under an earlier agreement stays governed by that agreement.

The rendering and account service run on Microsoft Azure in Poland Central, in the EU. Azure also hosts the website. Website enquiry records are stored in UK South, and the limited Mattermost notification described above is hosted on Zaltt's Azure server in Sweden Central. Those are separate uses and locations.

Auth0 provides sign-in through Bloooom's UK-region tenant. Its support staff may access information from elsewhere under its contract. A UK tenant does not mean that every provider or support operation stays in the UK. Google verifies your Google account through Auth0. We do not receive your Google password.

Hosting and identity providers receive the technical request information needed to deliver and protect their services. This can include your IP address and browser information. The enquiry handler does not store a raw IP address in the enquiry record.

Microsoft 365 processes enquiry and support email. Provider processing and international transfers are covered by the applicable service arrangements and privacy information. For details, see Microsoft's privacy statement, Okta and Auth0's privacy information and Google's privacy policy. You can ask hello@zaltt.com for information about the safeguards relevant to your data.

Google Analytics, Microsoft Clarity and the outreach services are described in their own sections of this notice, including processing outside the UK. We do not claim that all information stays in the UK or that providers keep no records of their own.

No payment is taken for the Free plan. Paid prices displayed on the website do not start a subscription. Paid checkout and Company-plan processing will need their own updated information before those services are enabled.

On Windows, the plugin keeps its shared Bloooom session in the current Windows user's application data, protected by Windows user-scoped encryption. Compatible plugins in that profile can share sign-in. This storage is separate from browser cookies and the computer and Autodesk allowance hashes.

The service uses encrypted connections, and access is limited to what is needed for the purposes described here. We do not make a more specific security claim or say that every security task is complete.

Account eligibility, allowances and device limits are applied automatically. The shared-identifier alert is informational. These controls do not judge the quality of your work or establish fraud. You can contact us to question an incorrect result.

You can browse and enquire without Google sign-in. The Free cloud service requires an eligible signed-in account and the applicable allowance checks. If an essential computer identifier is unavailable, the plugin may ask you to update and sign in again; it does not substitute another Autodesk identifier.

Removal of file paths and Windows user names from problem reports is planned for an update. We do not claim that reports are already anonymous. Review a report before sending it and leave out unnecessary personal or confidential information.

Your access, correction, deletion, objection and other rights described above also apply to the Free service. Email hello@zaltt.com and identify the account or information involved. We may need to verify your identity, will respond within the applicable legal time limits and will explain any exception. Do not send a password or session token. Withdrawing consent does not affect processing already carried out with that consent.

With your consent, we use Google Analytics 4 to understand which pages people visit and which actions they take. We use Microsoft Clarity for heatmaps and masked session replays, which help us see how people move through the website.

These tools collect pages visited, clicks, scrolling, device and browser information and approximate location. Google and Microsoft process this information, including in the United States. Clarity masks form fields and the signed-in email. We do not include your name, email, sign-in tokens or enquiry text in analytics events.

With consent, we record Start for Free clicks (start_for_free_click), completed sign-ins (sign_in_completed), manual download clicks (download_click), confirmed enquiries (enquiry_sent) and views of the pricing section (pricing_view). A visit opened from Revit can send one revit_pricing_visit event. The page removes the visit marker from the address bar and keeps it in memory for that page only, without saving it in a cookie or browser storage. If you ask to hear when paid plans open, a confirmed enquiry can also send paid_plan_interest_sent with the plan you selected: Student, Individual or Company. Neither event is sent before consent, and neither contains your enquiry text or contact details. Page addresses sent to analytics contain no query strings.

GA4 event-level data retention is set to 14 months. Cookie lifetimes are listed below; they are separate from how long a provider holds the resulting analytics records.

Our lawful basis for this website analytics is your consent. Neither tool loads before you choose Accept. Reject lets you use the website, enquire and sign in. Advertising storage and advertising personalisation remain off.

You can withdraw consent at any time through Cookie settings in the footer, then choose Reject. This stops the tools and removes their analytics cookies from this website. If the tools have already loaded, the page reloads to stop them. Any unsent form text may be lost. Withdrawal does not affect processing already carried out with your consent.

We save your choice in this browser for up to 180 days using local storage. It contains only your choice and when you made it. It is not an analytics cookie. If local storage is unavailable, a rejection can be kept for this tab instead. Clearing this site's browser data removes the saved choice.