Privacy Policy
Effective 23 October 2026. What MeloAI Inc. does with personal data across every Melo product, its websites, its apps and the links and forms our customers send out.
1. Who We Are and What This Covers
The Melo products are operated by MeloAI Inc. (“Melo”, “we”, “us”), a company in the United States. Where this policy says we are the controller, MeloAI Inc. is the entity that decides why and how the data is processed. One account serves every product, and this one policy covers all of them:
| Product | Site | What it is |
|---|---|---|
| MeloDocs | melodocs.ai | the document builder — quotes, contracts, invoices, share links, e-signature |
| MeloJobs | melojobs.ai | the CRM — leads, pipeline, appointments, crews, client portals, lead-intake forms |
| MeloBooks | melobooks.ai | accounting — the ledger, job costing, bank-file import |
| MeloBids | melobids.ai | the takeoff engine — plan sets, measured quantities, pricing |
| MeloScan | meloscan.ai | the iOS room scanner and MeloScan Desktop — captures, plans, designs, renders |
| MeloPay | melopay.ai | payments — deposits and invoices collected on a document, payouts to your account |
It also covers:
- the marketing website on each of those domains, and the suite page;
- the MeloScan app for iPhone and iPad, and MeloScan Desktop in the browser;
- share links — the pages where a client of one of our customers reads, signs or pays a document;
- client portals and lead-intake forms — the pages a customer gives their own clients and prospects;
- emails, support conversations and feedback connected to the above.
It does not cover any third-party site we link to, or Stripe’s, Apple’s or your bank’s own handling of your data under their terms. Where you connect one Melo product to another, data moves between them on your instruction and this policy continues to govern all of it.
2. Our Two Roles: Controller and Processor
This distinction decides who you should contact about what, so it is worth two paragraphs.
We Are the Controller of Your Account
If you sign up, we decide how your name, email, billing record and use of the products are handled. Requests about that come to us, and section 12 explains how to make one.
We Are a Processor for What You Put Into the Products
The contents of your documents, your client and lead records, your plan sets, your scans and your books — your client’s name and address, the price of their job, the amount they paid, the drawings an architect sent you, the geometry of a room you scanned, the rows in your bank’s export file — are yours. You decide what goes in and who it goes to; we process it on your instruction to render, store, measure, share and collect on it. If you are one of our customers’ clients and want your details corrected or removed, the business that holds them is the right first contact. We help them do it, and we respond directly where the law requires.
Customers who need a written data processing agreement, including the standard contractual clauses, can request one at privacy@melodocs.ai.
3. Information We Collect
The categories below are the whole of it. Which ones apply to you depends on which products you use; a MeloDocs-only customer never gives us a plan set or a bank file.
| Category | What it includes | Products |
|---|---|---|
| Account | Your name, email address, password hash or identity-provider subject, the second-factor secret if you enable one, workspace name and role, and the appearance and language preferences you set. | All |
| Business profile | Company name, contact details, logo, addresses, licence numbers you choose to print, tax registration, default rates and payment terms — the things that appear on your documents. | All |
| Document content | Everything you or MeloAI put in a document: line items, quantities, rates, totals, scope and exclusions, clauses, notes, schedules, and any photos, plan sheets or files you attach. | MeloDocs, MeloJobs, MeloBids, MeloScan |
| Your clients' and leads' details | Names, email addresses, phone numbers, postal and job-site addresses, property details, appointment times, notes, the photos you take on the job, and messages exchanged through a client portal — entered by you, imported, or submitted by the person themselves through a lead-intake form or portal. | MeloDocs, MeloJobs |
| Share-link and signature activity | That a document was opened, how many times and when it was last opened, and when it was accepted — with the typed name of the person who accepted it. That record is what makes an acceptance evidentially useful. | MeloDocs, MeloJobs, MeloPay |
| Payments and payouts | Amounts, currency, status, due dates and the deposit or balance a document calls for; the brand and last four digits of a card; our payment processor's identifiers; and, for payouts, the status of the Stripe account you connect. Full card numbers, bank account numbers and the identity documents Stripe may ask for never reach our servers. | MeloPay, MeloDocs, MeloJobs, MeloBooks |
| Plan sets and takeoffs | The PDF, DXF or DWG files you upload, the text read off their sheets (title blocks, schedules, dimension strings), the marks and quantities measured from them, your unit rates and the quotes you record from subcontractors. A plan set is usually a third party's document, often under a non-disclosure agreement; see section 16. | MeloBids |
| Room scans and designs | The geometry of a room captured by the app — walls, openings, dimensions, a mesh or 3D model — the floor plans and elevations drawn from it, pins with notes and photos you add, the design options and renders you make, and the project name and address you give it. Captures are processed on the device; only what you choose to send reaches us (section 16). | MeloScan |
| Bank and ledger data | The transaction rows in the CSV, OFX or QFX file you export from your bank and import — dates, amounts, payee descriptions, balances — and the journal, budgets, job costs and periods you keep. We never hold your online-banking credentials: there is no live bank connection, by design. | MeloBooks |
| Usage and technical | Features used, AI generations and render credits against your plan limit, error and performance traces, IP address, browser and operating system, and the device model and OS version the app reports. | All |
| Communications | Support emails, feedback you send in the product, notes sent through a product's contact form, and the messages — and any files — you exchange with MeloAI. | All |
What We Deliberately Do Not Collect
- Full card numbers, CVCs, bank account numbers or online-banking credentials — card and bank details go directly to our payment processor; a bank file is one you export yourself.
- A location trail. We do not look up where you are from your IP address; it sits in request logs for security and nothing more. The MeloScan app asks for your location once, with your permission, to suggest the address of a new project; we store the address you keep, not your position.
- Faces, bodies or voices. A room scan measures walls, floors and openings; it is not a biometric and we do not process biometric identifiers. The microphone in the MeloAI composer uses your browser’s own speech recognition, so the audio is handled by your browser or operating-system vendor under their terms; we receive only the text.
- Special-category data (health, biometrics, race, religion, politics, sexuality) or government identifiers. If you type such information into a document or a client note you do so as its controller, and should consider whether you have a lawful basis.
4. Where It Comes From
- You. Almost all of it — what you type, upload, import, scan and configure.
- Your devices. Technical data your browser sends when it requests a page, and what the MeloScan app sends when you tap Send to Melo.
- Your clients and prospects. When someone opens, signs or pays a document you sent, that activity is recorded against the document. When someone fills in your lead-intake form or writes to you through their portal, what they submit lands in your workspace.
- Third parties you work with. The architect’s plan set you upload to MeloBids; the subcontractor’s quote you record against it.
- Your bank — through you. A file you downloaded from your bank and imported into MeloBooks. We never contact your bank.
- Our processors. Payment and payout status from Stripe, and the error reports our monitoring sends when something breaks.
- Other Melo products. Only on the same account, and only where you have enabled them: a scan becomes a quote, a quote opens a job, an accepted quote becomes a budget.
5. How We Use It, and Our Legal Bases
If the GDPR or UK GDPR applies to you, the right-hand column is our lawful basis under Article 6. Where we rely on legitimate interests we have weighed them against your rights, and you can object using section 12.
| Purpose | Legal basis |
|---|---|
| Create your account, run the products, render and store your documents, send share links, take and pay out payments | Performance of a contract |
| Process the contents of your documents, client records, plan sets, scans and books so we can display, measure, export, share and collect on them | Processor acting on your documented instructions |
| Run the takeoff worker over a plan set you uploaded, and a render job over a design you ordered | Processor acting on your documented instructions |
| Bill you, chase unpaid invoices, meter AI generations and render credits against your plan, keep accounting records | Contract; legal obligation |
| Keep the service secure: rate limiting, abuse detection, audit logging, fraud prevention, second-factor enforcement | Legitimate interests in protecting the service and its users |
| Diagnose faults, measure performance, decide what to build next from aggregate usage, and improve the products using de-identified data | Legitimate interests in operating and improving the service |
| Train or fine-tune machine-learning models on identifiable customer content | Not done. If we ever offer it, it will be by consent, off by default, and this policy will say so first |
| Answer support requests and act on feedback | Contract; legitimate interests |
| Send service email you cannot opt out of — security notices, billing failures, a payout that needs attention | Contract; legal obligation |
| Send marketing email about the Melo products | Consent, or legitimate interests for existing customers where the law allows, with an unsubscribe link in every message |
| Comply with law, respond to lawful requests, establish or defend legal claims | Legal obligation; legitimate interests |
6. AI and Your Content
MeloAI drafts documents, reads plan sheets, proposes ledger entries and answers questions across the products. This is the part people ask about most, so here is exactly how it works.
- Our model provider is a processor under contract. We send the text — and, where you attach them, the photos or files — needed to answer your request to Anthropic, which processes it to return a response and does not use it for training or retain it beyond the short window its terms allow for abuse monitoring.
- We do not train models on your identifiable content. The contents of your documents, your rates, your client records, your plan sets, your scans and your books are not used to train or fine-tune machine-learning models. If we ever offer that, it will be opt-in, off by default, controlled from your workspace settings and announced in this policy before it starts.
- Your own work improves your own results. Inside your workspace the products learn your rate book, your recurring line items, your defaults, the attribution rules you teach the ledger and your tone, so the next document is closer to what you would have written. That stays within your organisation.
- De-identified and aggregated data improves the product for everyone. We derive statistics and de-identified data from how the products are used, and use them to operate, secure and improve them. De-identified means it no longer identifies you, your business, your clients or any individual, and we do not attempt to re-identify it.
- The arithmetic is ours, not the model’s. MeloAI proposes structure and wording; totals, tax, deposits and schedules are calculated by the products. A model error cannot change a number on your document.
- A model never measures and never posts. In MeloBids the model reads and classifies sheets and extracts schedule tables; every quantity is measured by geometry from the drawing. In MeloBooks the model only proposes; an entry reaches the ledger through the same rules a person’s does, and nothing posts from a bank file without you.
- Extracted text is data, never instruction. Content read out of an uploaded file, a plan sheet or a client’s message cannot direct the model to act — a document that says “approve this” gets quoted, not obeyed.
- You stay in control. Nothing MeloAI produces reaches anyone until you send it.
9. International Transfers
We are based in the United States and our processors are largely US-based, so personal data from the EEA, the UK or Switzerland is transferred there. Where we do that we rely on the European Commission’s standard contractual clauses, the UK addendum to them, or another mechanism the law permits, together with a transfer risk assessment and the technical measures in section 11. A copy of the clauses we use is available on request.
10. How Long We Keep It
| Data | Kept for |
|---|---|
| Documents, client and lead records, designs and their contents | While your account is open. Deleting one removes it, and deleted records are purged from backups within 30 days. |
| Plan sets and takeoffs | While the plan set is in your account. Delete it and the files, the extracted text and the marks go with it; a published takeoff's version record stays as part of the documents it priced. |
| Room scans | While your account is open, for the copy you sent us. The copy on your phone is yours and is never touched by us. |
| Account and workspace | While your account is open, then deleted within 30 days of closure. |
| Share-link and acceptance record | With the document: delete the document and its view and acceptance record go with it (an acceptance logged on a MeloJobs job stays on that job's activity). Keep your own signed copies — we are not a record-keeping service. |
| Payment, payout and accounting records, including the ledger and imported bank rows | Seven years, to meet tax and accounting obligations. A posted ledger entry is never edited, only reversed — that is what makes the books evidence. |
| Photoreal renders | While the scan they belong to is in your account. |
| Security and access logs | 12 months. |
| Support, feedback and contact-form notes | 24 months from the last message. |
| Backups | A rolling 30 days, then overwritten. |
Where we must keep something longer than you would like, we restrict it to that purpose rather than carrying on using it.
11. How We Protect It
- Isolation enforced in the database. Every row of every table is scoped to an organisation and enforced by row-level security in the database itself, not only in application code — so a mistake in a query cannot return another tenant’s client list, prices, plans or books.
- Encryption. TLS in transit; encryption at rest for the database and file storage. Documents, attachments, plan sets, scans, receipts and renders sit in private buckets reachable only through short-lived signed URLs. Your logo and the photos you place on a document are served from public, unguessable addresses, because the page a client opens has to show them without signing in — so do not upload a photo you need kept private.
- The worker that reads plan sets is the only thing that bypasses isolation, because it has to; it runs on its own host, holds its own key, and stamps every row it writes with the organisation it belongs to.
- Access control. A workspace sees only its own records, and workspace roles limit who can change its money settings. You can require an authenticator app on your account, and once you do, a password alone can act as you nowhere. Staff access to production is limited to those who need it, requires multi-factor authentication, and is logged.
- Payments. Card and bank details are captured by Stripe and never touch our servers, so we hold the result of a payment rather than the instrument.
- Testing. Changes go through review and automated testing before release, the database’s grants are checked on every change, and the evaluation suite includes a prompt-injection case, so an instruction hidden inside an uploaded document or plan sheet cannot make the model act on it.
No system is perfect. If we become aware of a breach affecting your personal data we will notify you and the relevant regulator within the time the law requires, with what we know and what we are doing about it. To report a vulnerability, email security@melodocs.ai — we acknowledge within one business day and will not pursue good-faith research.
12. Your Rights
Depending on where you live, you have some or all of the following rights:
- Access — a copy of the personal data we hold about you.
- Correction — to fix anything inaccurate or incomplete.
- Deletion — to have it erased, subject to the retention obligations in section 10.
- Portability — a machine-readable export of the data you gave us. You can export your documents, your takeoffs, your scans and your ledger yourself at any time from the products.
- Restriction and objection — to pause our use of it, or object to processing based on legitimate interests.
- Withdraw consent — where we relied on consent, at any time, without affecting what happened before.
- Complain — to your data protection authority. We would rather you came to us first, but it is your right either way.
How to Exercise Them
Email privacy@melodocs.ai from the address on your account. Your documents, takeoffs, scans and ledger can be exported from the products at any time; deletion of an account, a client’s record or anything else we hold is done by us on request. We respond within 30 days and will tell you if a complex request needs longer. There is no charge unless a request is manifestly unfounded or repetitive. We may need to verify your identity first, and will ask only for what is necessary to do it.
If you are one of our customers’ clients, we will pass your request to that customer and support them in answering it, since the data is theirs to control.
13. US State Privacy Rights
If you live in California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, Washington or another state with a comprehensive privacy law, this section is your notice at collection and your statement of rights.
| Category collected | Purpose | Disclosed to |
|---|---|---|
| Identifiers — name, email, phone, postal address, IP address, account ID | Run the account, send documents, secure the service | Hosting, email and payment processors |
| Customer records — billing name, payment status, card brand and last four, payout account status | Take payment, pay out, keep accounting records | Payment processor |
| Commercial information — plan, subscription history, documents created, amounts invoiced and paid, credits used | Provide and bill for the service | Hosting and payment processors |
| Internet activity — features used, error traces | Operate, secure and improve the service | Hosting processor |
| Approximate location inferred from IP; a project address you choose to keep | Security, fraud prevention and tax; labelling your own project | Hosting and payment processors |
| Professional information — company, trade, role, licence numbers you print | Configure the products for your work | Hosting processor |
| Content you submit — documents, client records, plan sets, scans, bank files, attachments, chat messages | Render, measure and deliver your work; improve the service in de-identified form, and train models only where you have opted in | Hosting, AI, takeoff-worker and render processors |
We have not sold or shared personal information in the preceding twelve months, as those terms are defined in the California Consumer Privacy Act, and we do not process sensitive personal information to infer characteristics. We do not knowingly sell or share the personal information of anyone under 16.
You may request access, correction, deletion, a portable copy, and details of the categories collected, used and disclosed. You may appoint an authorised agent, and we will ask for proof of that authority. We will not discriminate against you for exercising any of these rights — no price change, no reduced service.
To make a request, email privacy@melodocs.ai. If we decline, you can appeal by replying to our decision; we answer appeals within 45 days and will tell you how to contact your state attorney general if you are still unsatisfied.
14. If a Melo Customer Sent You Something
You are reading this because a business sent you a quote, contract or invoice built with MeloDocs, gave you a link to your own client portal, or put a request form on their website that you filled in. We host those for them. They decided what the document says, what personal data it contains and who to send it to; we process it on their instruction.
When you open a share link we record that it was opened, how many times and when, so the business can see it arrived. If you accept it we record the name you typed and the time, because that record is what makes the acceptance worth anything later. If you pay, Stripe handles your card or bank details and tells us only the result. If you fill in a request form or write through a portal, what you submit — your name, how to reach you, the address of the work — goes to that business and nowhere else.
To have your details corrected or removed, contact the business that sent you the link. If you cannot reach them, or would rather come to us, email privacy@melodocs.ai — we act where the law requires us to and pass the request on where it does not.
15. If You Are a Melo Customer
You are the controller of the personal data you put into the products, which carries obligations we cannot discharge for you:
- have a lawful basis for holding your clients’ and leads’ details, and tell them what you do with them — a privacy notice on your own site is the usual way;
- enter only what the document or the job actually needs — a quote rarely needs a date of birth;
- upload only plan sets you are entitled to upload, and keep any confidentiality you owe their owner;
- scan and photograph only spaces you have permission to capture, and tell the occupant what you are doing with the result;
- keep your credentials, your MeloScan upload key, your portal links and your form links safe, and remove people from your workspace when they leave;
- answer your own clients’ privacy requests — export from the products, and write to us for a deletion we have to carry out; and
- put a data processing agreement in place with us if your jurisdiction requires one — ask at privacy@melodocs.ai.
16. Product Notes
Where a product handles data in a way the sections above do not fully describe, it is here.
MeloScan — The App, and Desktop
The app uses the camera and the LiDAR sensor to capture rooms, objects and photos and measure them; that processing happens on the device, and scans are stored on it. It asks for your location once, to suggest a new project’s address, and asks to add renders and plan sheets you export to your photo library. Nothing leaves the phone until you tap Send to Melo, which uploads the scan’s measurements, plan geometry and pin notes to your workspace over the key you created there. Photos you attach to pins stay with the scan. MeloScan Desktop opens the scans in your workspace in the browser; when you trace a plan from a blueprint image, the image is read in your browser and never uploaded. A photoreal render you order sends the scene’s geometry and material choices to our render processor and returns images to your account.
MeloBids — Plan Sets
A plan set is usually someone else’s confidential document. We hold it in a private bucket, serve it only through short-lived signed URLs, and never expose it publicly. The text read off its sheets is used to classify them, confirm the scale and extract schedules, and for nothing else. Deleting the plan set deletes the files and what was read from them.
MeloBooks — Bank Files and the Ledger
We never connect to your bank. You export a CSV, OFX or QFX file from your own banking and import it; its rows wait in an inbox and nothing posts until you decide. Posted entries are immutable and are kept for the accounting retention period in section 10, because the ledger is your system of record. Your accountant sees what you choose to export or share.
MeloPay — Payments and Payouts
Payments are processed by Stripe. To receive payouts you open a Stripe account through the product; the identity, business and bank details Stripe collects to do that go to Stripe under its own privacy policy, and we hold only the account’s status and identifiers. On a document, we hold the amounts, the schedule, who paid and when, so the document, the job and the books all agree.
MeloJobs — Leads, Portals and Crews
A lead-intake form is a public page on a per-source link; what a prospect submits (name, contact details, address, notes) lands in your Leads inbox tagged with the source. A client portal is a per-client link that shows that client their own jobs, documents, payments and visits, and lets them write to you. Members of your crew you add to a job are people whose details you hold as their employer or client; we process them on your instruction.
17. Automated Decision-Making
We do not make decisions producing legal or similarly significant effects about you by purely automated means. MeloAI drafts documents, MeloBids measures drawings, MeloBooks attributes a bank row to a job where the evidence is sure, and our rate limits and abuse controls act on their own — but a person decides what happens to an account, every attribution can be reversed, and nothing MeloAI writes leaves your account until you send it.
18. Children
The Melo products are business products and are not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, email privacy@melodocs.ai and we will delete it.
19. Changes to This Policy
We update this policy when the products or the law change, and the effective date at the top always reflects the current version. If a change materially affects how we use your personal data we will tell you by email or in the product before it takes effect, and where consent is required we will ask for it rather than assume it.
20. How to Contact Us
Privacy questions and rights requests: privacy@melodocs.ai. Security reports: security@melodocs.ai. Anything else: hello@melodocs.ai, or the contact page of the product you use. These addresses reach MeloAI Inc. for every Melo product.
MeloAI Inc., Bellevue, Washington, United States. If you are in the EEA or the UK and want to reach our representative for data protection matters, email privacy@melodocs.ai with “EU representative” or “UK representative” in the subject line and we will put you in touch. You also have the right to complain to your local supervisory authority.
See also our terms of service and security overview.