Melso, Inc. (“Melso,” “we,” “us,” or “our”) operates melso.ai and related products and services (the “Service”). This Privacy Policy explains how we collect, use, share, and protect personal information when you visit our websites, create an account, or otherwise use the Service.
Information we collect
We collect information you provide directly, information generated when you use the Service, and limited information from third-party providers you connect.
- Account and contact details, such as name, email address, company name, and other information you submit in forms or support requests.
- Company content and usage data needed to operate the Service, including messages, files you upload, settings, and activity logs.
- Tax and accounting information, including tax returns and filing receipts, tax identification numbers (such as NIF, NIE or CIF), fiscal addresses, invoices, receipts, income, expenses and supporting documents. These records may contain information about your customers and suppliers.
- Bank information you provide or authorize us to access, including account holder names, IBANs, account details and transactions needed for accounting, reconciliation or an authorized tax payment.
- WhatsApp messages and attachments you send to Melso, together with your phone number and message delivery information.
- Technical data such as IP address, device/browser type, approximate location derived from IP, cookies, and similar identifiers.
- Job applications you send through our careers page: your name, contact details, the area you would like to work in, any link or message you add, and your CV.
- Details you leave in a form in one of our ads, for example on Facebook or Instagram: your name, phone number, email if you give it and your answers to its questions, together with the ad you came from.
- Billing-related details processed by our payment providers when you purchase paid features (we do not store full payment card numbers).
- Information from integrations you authorize (for example GitHub, Google, or messaging tools), limited to what those providers make available under your permissions.
How we use information
We use personal information to:
- Provide, maintain, secure, and improve the Service.
- Create and manage accounts, companies, and access controls.
- Read and organize invoices and WhatsApp messages with AI, extract accounting details, reconcile bank transactions, and help our professionals prepare and file the tax returns you approve.
- Respond to inquiries, provide support, and send service-related notices.
- Consider job applications and contact candidates about them.
- Answer people who ask for information in a form in our ads: we open a Melso account linked to the phone number they gave, so they can talk with our agent, message them on WhatsApp or call them, and stop writing to them if they tell us they are not interested. We also tell Meta, with only the reference Meta gave their form, how far each request gets (they reply, we speak with them, they are not interested or they become a client) to measure and improve those ads.
- Process transactions and send related billing communications.
- Analyze product usage to improve reliability, performance, and features.
- Detect, prevent, and investigate abuse, fraud, or security incidents.
- Comply with legal obligations and enforce our Terms of Service.
- With your consent where required, send product updates or marketing communications (you can unsubscribe at any time).
How we share information
We do not sell personal information. We share information only as needed to operate the Service or as required by law:
- Service providers who process data on our behalf (for example hosting, analytics, email delivery, ad and contact management, and payment processing), under contractual confidentiality and security obligations.
- Integration partners you choose to connect, so the Service can perform the actions you request.
- The AI assistant you connect to Melso, which receives the results of the tools it calls, as described in “AI assistants you connect”.
- Professional advisors, auditors, or authorities when reasonably necessary to protect rights, safety, or comply with legal process.
- A successor entity in connection with a merger, acquisition, financing, or sale of assets, subject to appropriate continuity of privacy protections.
AI and financial service providers
Our AI service processes the messages, invoices and other documents needed for your request. This can include tax IDs, bank details and other financial information contained in those records.
We use Anthropic’s Claude models through an API, with zero data retention for prompts and responses at the AI provider. Invoice extraction and fallback assistance also use OpenAI GPT models. Our production AI APIs are served through Amazon Web Services (AWS) Amazon Bedrock. Customer content is not used to train these models. Provider zero data retention is separate from the records and conversations Melso stores to provide your service, as described below.
- Melso and the tax professionals assigned to your company prepare and submit your approved tax returns to Spain’s Agencia Estatal de Administración Tributaria (AEAT). They receive the fiscal identity, tax records, supporting documents and bank details necessary for the authorized service. Tax-return filing requires your approval in the app.
- Meta’s WhatsApp service carries messages and attachments between you and Melso when you use WhatsApp. Melso’s AI and assigned professionals may read that content to carry out your requests. WhatsApp’s own privacy terms also apply to its messaging service.
AI assistants you connect
You can connect an external AI assistant, such as ChatGPT, Claude or Codex, to Melso through our MCP server at mcp.melso.ai. You sign in to Melso and authorize the assistant for one company; any member of that company can authorize it, and the connection covers that company only. The assistant can use only the tools listed when you connect, with the same role and plan limits as in the app. It cannot approve or file tax returns or approve procedures; those still require your approval in the Melso app. Issuing an invoice through an assistant requires the company owner and the exact version of the invoice that was reviewed.
When the assistant calls a tool, Melso sends it the result, which can include tax identification numbers, amounts, names of customers and suppliers, and the contents of documents. From then on the assistant’s provider (for example OpenAI or Anthropic) handles that information under its own terms and privacy policy, not ours. Melso does not receive your conversation with the assistant, only the tool calls it makes.
- What Melso keeps about a connection: the assistant’s registration (its name and redirect addresses) and the connection itself (who authorized it, for which company, when, and when it was last used). We store access and refresh tokens only as hashes.
- What Melso keeps about each call: a technical log entry with the tool name and request identifiers, but not the tool’s arguments or results. Records an assistant creates or changes, such as an expense or a draft invoice, are stored like those you create in the app and follow the retention described below.
- How long a connection lasts: an access token expires after one hour and a refresh token after 90 days without use. After you disconnect an assistant, we keep the record of the connection, with tokens that no longer work, as security evidence.
- Your controls: disconnect an assistant at any time in Settings → Connect your AI → Connected assistants; it stops working immediately. Deleting a company removes all its connections.
Cookies, analytics and advertising
Melso uses necessary cookies for sign-in, security and your settings. We measure site use and advertising from the first visit unless you have turned measurement off. The legal basis for this measurement is Melso's legitimate interest in measuring and improving its advertising (Article 6(1)(f) GDPR). You can turn off measurement cookies and server-side conversion reporting on this page before signing in or under Settings → Profile → Cookies after signing in. You can also email privacy@melso.ai.
If you opt out and then sign up or contact us on WhatsApp, we still keep the referring site, campaign tags and first page you visited.
On our public pages we also count visits without cookies, so we know how many people each page and campaign brings and what they do there. This audience count is a separate PostHog measurement that stores nothing on your device and identifies no one. For each page view it records the page and its campaign tags (never ad click identifiers), the address of the website that referred you without its page, your device type, browser and screen size, how long the page stayed open and how far it was scrolled, which of our buttons were pressed and which questions were opened. PostHog counts visitors with a code computed from your IP address and browser with a key that changes every day, and does not keep the IP address. We use these figures only to measure our own website's audience: they are never combined with your account, shared with advertising providers or used to record your session. We keep them for at most 25 months. You can object to this count by writing to privacy@melso.ai.
The first-party melso_attribution cookie lasts 90 days and refers to a record shared across Melso sites. It keeps your first landing and the latest visit with campaign tags or an ad click. The record includes the landing path, referring site, campaign tags, click identifiers and visit times. It can link a later signup to the visit, including when you continue on WhatsApp. The first-party melso_consent_receipt cookie links your browser to the record of which measurement purposes apply. The cookie lasts up to 180 days. If you change your preferences, melso_consent remembers your choice for up to 180 days.
The melso_acquisition_binding cookie links this browser to its attribution record for up to 180 days. For up to 30 days, melso_signup_source stores the campaign tags, referring site or landing path used to measure signups. The cookie melso_receipt_permissions pauses tracking until we check your receipt. It then stores the permitted purposes until the receipt expires. The melso_permissions_checked cookie remembers the check for up to 60 seconds.
Google Analytics and PostHog receive page views to measure site use. Google Analytics 4 (GA4) also receives events when you request an S.L. incorporation. Microsoft Clarity records clicks, scrolling and page layout. In the signed-in app, Clarity masks text and form inputs. Turning measurement off stops Clarity recordings and Google measurement. Melso also records steps such as registration, an S.L. request, checkout and confirmed payment for up to 180 days. Turning measurement off stops these milestones and removes the affected records.
Google Ads can receive the ad click identifier and event time. With or without an ad click, Google Ads and Meta can match conversions to an account using contact details transformed into SHA-256 hashes. Both providers can receive hashes of your verified email address and phone number. Meta can also receive hashes of your name and, if you have told us you live in Spain, your country of residence.
Google Ads can receive a transaction ID for events that are not payments. That transaction ID can include your Melso account or company identifier.
GA4 receives a GA4 client identifier (client ID) and, when available for the event, a session identifier. At checkout and purchase, GA4 can receive item identifiers, names, prices and quantities. For purchases it also receives the tax amount.
Meta can receive an event when you connect Gmail or WhatsApp, start a trial or begin checkout.
For eligible payments, Google Ads, Meta, ChatGPT Ads (OpenAI) and GA4 can receive the amount, currency and an identifier for that payment. Google Ads and GA4 receive a transaction ID. Meta and OpenAI use an event ID.
Melso sends OpenAI server-side events for account registration, S.L. requests, checkout starts and confirmed payments. They include the event time, an opaque event ID, a generic Melso URL and the OpenAI click reference (oppref) when available. Melso does not load an OpenAI advertising pixel or send OpenAI contact details, fiscal records or browser fingerprints for this purpose.
Meta Pixel and Conversions API measure visits to public marketing pages and account registrations. Meta also receives subscription, renewal and one-off purchase events. When you register through WhatsApp, a click-to-WhatsApp ad or one of Meta’s lead forms, Melso can report that registration to Meta as a CRM or system event. Meta can receive a pseudonymous identifier, the _fbp browser identifier, the _fbc click reference, browser information and the request IP address. Fiscal records, form contents and authentication links are excluded. Turning off measurement stops pending advertising deliveries.
On eligible paid visits, melso_landing_hop keeps a random visit reference and the redirect path for up to 60 seconds so we can count a redirect chain once. If your browser still has the melso_landing_signup cookie, it may send it to /auth for up to 15 minutes after it was set. Melso no longer sets or reads it. To count a new account against the right campaign, we use the reference from the tab where you signed up. We do not set the redirect cookie after you opt out.
Data retention
We normally keep tax records, tax returns and uploaded invoices for four years after the relevant tax filing deadline. An uploaded invoice not associated with a tax return is normally kept for four years from upload. You can request earlier deletion, subject to the legal retention obligations below.
Some records must be kept longer for legal, tax or accounting obligations, an audit or a legal claim. Issued invoices, their original PDFs and related legal evidence are retained for at least six years from issuance. Filed returns, submission receipts and other records subject to a legal retention obligation may remain after account or company deletion. We restrict their use to the reason they must be retained.
We keep a job application and its CV only while it is relevant to our hiring, and delete it earlier when the candidate asks us to.
We delete the details of an ad form 12 months after we receive them, or earlier if you ask us to. The account we open for you is deleted when you ask us to, like any other account.
Other personal information is kept only as long as needed to provide the Service, secure it, resolve disputes and meet legal obligations. Model request diagnostics held by Melso are normally kept for 14 days; the AI provider’s zero data retention does not delete records held by Melso. When information is no longer needed, we delete or de-identify it.
Security
We use administrative, technical, and organizational measures designed to protect personal information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Your choices and rights
Depending on your location, you may have rights to access, correct, delete, or export personal information, or to object to or restrict certain processing. You may also withdraw consent where processing is based on consent. To exercise these rights, contact us using the details below. We may need to verify your request before responding.
You can delete your account in Settings → Profile → Delete account, or request deletion of all your data by emailing privacy@melso.ai. This includes tax records, uploaded invoices, bank data and messages, except information we are required to retain as explained under Data retention. You can request an export before deletion.
Company administrators may manage member access and company content. Deleting your personal account does not delete a company that other members still use; an authorized company owner can request deletion of the company’s data. We verify your identity and authority before acting on these requests.
Children’s privacy
The Service is not directed to children under 16, and we do not knowingly collect personal information from children under 16. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it.
International transfers
We may process and store information in the United States and other countries where we or our service providers operate. Those locations may have different data-protection laws than your home country. Where required, we use appropriate safeguards for cross-border transfers.
Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version on this page and revise the effective date. Material changes may also be communicated by email or in-product notice when appropriate. Continued use of the Service after an update means you acknowledge the revised policy.
Contact
Questions about this Privacy Policy or Melso’s privacy practices can be sent to privacy@melso.ai.
Melso, Inc.
Website: https://melso.ai
Related: Delete your account