LyraAll legal documents

Draft, needs legal review. This is a structure for the entity's lawyers to complete; it is not legal advice and it is not yet in force.

Privacy policy

Version 2026-11-draft-2

This policy explains what personal data Lyra collects, why, where it goes and what rights you have. The controller is [LEGAL ENTITY NAME], registered in [JURISDICTION] under number [REGISTRATION NUMBER], at [REGISTERED ADDRESS]. Privacy questions go to [DPO OR PRIVACY CONTACT] or [LEGAL EMAIL].

It applies to the website, the desktop app and the design tool inside it, including the assistant, the web pages and servers that support them, and support (together, the Service), and takes effect on [EFFECTIVE DATE].

1. What we store

The Service stores the following. Each line names the kind of data, with the plain meaning of what it holds.

Account and company

  • Company: name, short name, country, plan, how the plan was given (at sign-up, by payment, as gifted access or by our staff), who assigned it and when, subscription status, branding you upload for proposals, the identifiers Stripe gives us for your customer and subscription (never card numbers).
  • User profile: email address, full name, role in the company (owner, member or staff), whether two-factor authentication is required, when you were last seen, and your sign-in credentials held by our authentication provider.
  • Invitations to join a company: the invited email address, the role, who invited, a one-time token and its expiry.
  • Gift invitations: the invited email address, name and company name, whether the invitation came from our staff or from a partner programme and, for a partner, its own reference for the person invited, a one-time sign-up code, the status (pending, accepted or revoked), the company it was accepted for, and when it was accepted or revoked and by whom.
  • Plan exceptions granted to your company, with a note and who set them.

Projects and media

  • Projects: name, number of floors, the design data (plans, areas, devices, settings and text you enter), its size, version number, who last saved, a thumbnail and when it was archived.
  • Project versions: the last 25 saved versions of each project, with who saved each.
  • Shares: a snapshot of the shared area, the kind of share (3D view or report), its link token, expiry, revocation, how many times it was opened and who made it.
  • Images: floor plans and photos you upload, as files in private storage, with their size and dimensions.

Your library

  • Private items: the products and brands your company adds, their data (for a brand, its name, website and logo), the source you gave (a URL, a datasheet, a photo or entered by hand), whether AI import produced them and who made them.
  • Promotion queue: when a product or brand is reviewed for the shared library, the reviewer's notes and corrections and the decision. The published entry never names your company.

Access and devices

  • Licences: a hash of the signed licence token, its plan, issue and expiry times and the device it was issued to.
  • Desktop devices: a device identifier, its name, the app version and when it last connected.
  • On your device: the desktop app keeps its signed licence, the device identifier, its settings and cached copies of your projects, your company's private library, the catalogue and the tool, so that it starts quickly and works offline. This is described in the cookie notice (legal/cookies.md).

AI usage

  • Metering: for each AI request, the company, the user, the feature, the model, the token counts and the cost, rolled up per month to apply your plan's allowance. The content of the request, including any file you dropped into the chat, is not kept in the metering record.

Support

  • Tickets and messages: the subject, status, channel, who opened it, who it is assigned to, and the transcript of the conversation, including messages written by the AI assistant and by our staff. When a conversation with the assistant is handed to a person on Studio, that conversation becomes part of the ticket.

Governance

  • Audit log: administrative actions on the Service, with the actor, the action, the target, the IP address and the time.
  • Staff project views: every time a staff member opens a customer project, with the staff member, the project, the reason and the time (section 7).
  • Legal acceptances: which version of which document each user accepted, when and from which IP address.

Newsletter

  • Subscribers: email address, the version of the consent sentence you agreed to, the page on which you subscribed, when you confirmed, when you unsubscribed, and an unsubscribe token.

Telemetry

  • Events: product events such as a feature being opened or an error, with the app version and, where you are signed in, the company and user. Telemetry is used to improve the Tool and to find faults; it does not include the content of your projects.

2. Why we process it, and on what basis

PurposeDataBasis
Providing the Service you signed up for: accounts, projects, library, shares, desktop licences, exportsaccount, company, projects, media, library, accessperformance of the contract
Billing and taxcompany, Stripe identifiers, invoicescontract; legal obligation
Applying your plan, including the AI allowancelicences, AI meteringcontract
Giving, recording and revoking gifted accessgift invitations, company planlegitimate interest in running the gifted access programme; contract once the invitation is accepted
The assistant, AI design and AI import, when you use themyour messages, the files you drop into the chat, the project data and the URL, document or photo the feature needsperformance of the contract
Support you ask for, by chat or email, including a conversation handed from the assistant to a person on Studiotickets, messages, the project you ask aboutcontract
Keeping the Service secure, preventing abuse and investigating incidentsaudit log, licences, telemetry, IP addresseslegitimate interest in a secure service
Improving the Tooltelemetry, anonymised usage statisticslegitimate interest
Reviewing items for the shared librarypromotion queuelegitimate interest; the published entry is anonymised
Sending account, gifted access, renewal and service emailsemail address, name, plan datescontract; legitimate interest
The newslettersubscriber recordconsent, which you can withdraw at any time
Recording acceptance of legal documentslegal acceptanceslegal obligation; legitimate interest

Where the law applying to you requires a lawful basis, the basis is as shown. Where it does not, we still process data only for these purposes.

3. AI processing

Some features send data to a large language model operated by Anthropic, acting as our processor. None of them is available on the Free plan.

  • The assistant: when you write to the assistant in the Tool, your messages, the files you drop into the chat (such as floor plans, spec sheets and pictures) and the parts of the open project it reads to answer you or to act are sent to produce the answer and the actions, which come back into your project. Files you drop into the chat are sent to Anthropic for processing. Nothing is sent until you write to the assistant or drop a file into the chat.
  • AI design and review: when you ask for a design or a review, the design data of the areas you chose (plan geometry, areas, heights, targets, devices and your instruction) is sent, and the proposal comes back into your project. Nothing is sent until you ask.
  • AI import: the URL, datasheet or photo you give, including a spec sheet you drop into the chat, is sent to extract product data for your review.
  • Hand-off to a person (Studio): if you ask for a person and confirm, the conversation is passed to our support staff and kept with your support ticket (section 1, Support).

We meter each request (section 1, AI usage). We do not use your content to train models. Anthropic processes it under its commercial terms and data processing addendum; see legal/subprocessors.md.

4. Who else receives data

We use a small number of providers (subprocessors) to run the Service: hosting, database and storage, email, payments and AI. They are listed with their purpose, the data each receives and their location in legal/subprocessors.md, which we keep current. We do not sell personal data and we do not use advertising networks.

When a partner programme invites a company to gifted access, the partner gives us the invited person's email address, name and company name and its own reference for them, and it can ask us whether the invitation was accepted and which plan the company is on. It receives nothing else about your account or your projects.

We may also disclose data when the law requires it, to protect the Service or others, or to a successor of the business with notice to you.

5. International transfers

Our providers operate in more than one country, so data may be processed outside [JURISDICTION]. Where that happens we rely on the provider's data processing addendum and the transfer mechanisms it contains. The region of each provider is stated in legal/subprocessors.md.

6. How long we keep data

DataKept for
Account, company, projects, library, mediawhile the account exists, then deleted [RETENTION PERIOD] after closure
Project versionsthe last 25 versions of each project
Sharesuntil they expire or are revoked; the snapshot is then deleted
Gift invitationswhile the invitation or the gifted access lasts, then [RETENTION PERIOD]
Licences and desktop devicesuntil expiry or sign-out, then [RETENTION PERIOD]
AI metering[RETENTION PERIOD], for billing and allowance disputes
Support tickets[RETENTION PERIOD] after closure
Audit log and staff project views[RETENTION PERIOD]
Legal acceptancesfor as long as the law requires us to show acceptance
Newsletteruntil you unsubscribe; the unsubscribed record is kept so we do not email you again
Telemetry[RETENTION PERIOD], then aggregated
Backupsrotated within [RETENTION PERIOD]

Nothing is deleted when a plan is downgraded or cancelled, or when gifted access ends.

7. Staff access to your projects

Our staff can open a customer's project only for support you asked for, for quality review of the Tool, or to investigate abuse or a security problem. Every such access is recorded with the staff member, the project, the reason and the time, and your company's owner can read the record.

8. Security

Data is held in access-controlled databases and private storage with row-level access rules, and travels over encrypted connections. Images are served through short-lived signed links. Staff use separate staff accounts. The security measures of each provider are described in its own documentation (legal/subprocessors.md). Please report a security problem to [LEGAL EMAIL].

9. Your rights

Depending on the law that applies to you, you may have the right to access the personal data we hold about you, to correct it, to have it deleted, to receive it in a portable form, to object to or restrict certain processing, and to withdraw consent where processing relies on it. You can save a copy of your projects as project files from the Tool, manage your team and branding in the app, and leave the newsletter through the link in every copy. For anything else, including a change to your name or email address, write to [DPO OR PRIVACY CONTACT] or [LEGAL EMAIL]. We answer within the time the law sets.

You may also complain to the data protection authority in [JURISDICTION] or where you live.

10. Cookies and storage on your device

What the website and our remaining web pages keep in your browser, and what the desktop app keeps on your device, is described in the cookie notice (legal/cookies.md).

11. Children

The Service is for business use and is not directed at children. We do not knowingly collect data from children.

12. Changes to this policy

Each version of this policy has a version number and a published date. We announce material changes by email to company owners and in the app before they take effect.

13. Contact

[LEGAL ENTITY NAME], [REGISTERED ADDRESS]. Privacy: [DPO OR PRIVACY CONTACT], [LEGAL EMAIL].

See also: Terms of service, Refund and cancellation policy, Acceptable use policy, Cookie notice, Subprocessors.