Italiano Back to the chat

Privacy notice

This notice explains what happens to personal data when you use Talk to MAIA. It is given under Article 13 of the General Data Protection Regulation, Regulation (EU) 2016/679, as applied in Malta by the Data Protection Act, Chapter 586 of the Laws of Malta.

A link to it is shown before you start a conversation, and it applies from that moment. Nothing on this page asks you to agree to anything; it tells you what happens if you go on.

Who is responsible

The controller is P MAIA AI LTD, a private limited liability company registered in Malta under registration number C99026 (VAT number MT28528403), with its registered office at Palace Court, Church Street, St Julians STJ 3049, Malta.

You can reach us about anything in this notice by email at info@maiabrain.com or by telephone on +356 2010 2020.

The notice at www.maiabrain.com/privacy covers our website and our email. This page covers Talk to MAIA, and the partner applications that the form on our website sends to it (see Partner applications from www.maiabrain.com).

You are talking to an AI

MAIA is an AI system, not a person. AI models that MAIA runs on its infrastructure in the cloud write most answers and compose the page on the left from our knowledge base; the service itself supplies a few fixed replies, described below. It can be wrong. Check anything that matters to you against the sources it cites under its answers.

There is no person behind the answers, and no one at MAIA Brain answers in MAIA's place. This notice speaks for P MAIA AI LTD, as "we".

What we collect

No sign-in. The service runs in a mode with no sign-in: before a conversation starts, your browser passes a bot check run by MAIA's cloud infrastructure, which can ask you to solve a short puzzle. Starting a conversation never asks for your name, email address or phone number; MAIA may later offer that we follow up on your request and ask for contact details, which is optional and set out under Contact details you give us. Its code also contains sign-in by a code sent by email or text message, but in this mode that path cannot be reached: it accepts no email address or phone number for sign-in, sends no code, and gives nothing to our text-message provider or our email provider, although both are configured on our server. If we ever switch sign-in on, we will change this notice first.

Please do not tell MAIA anything about your health, beliefs or other sensitive matters, or personal details about other people. Nothing in the service detects or removes them: whatever you type or say is stored with your conversation and sent to MAIA's AI models in the cloud with it.

How your notes are used. Within your conversation, what MAIA notes about you is shown to you on the page; is used to compose the page; is given to the conversation check described below; and is used by the checks on MAIA's own answers, so that a figure or a name you gave yourself is not refused as unsupported when MAIA repeats it. The checks on typed answers also use the questions you asked earlier in the conversation in the same way.

Images. Images on the page are stored files served from our server. The service picks an image topic from a fixed, closed list; your words and notes can decide which topic is picked, on our server. When no stored image fits that topic, the service may ask MAIA's fixed image model to make one from a fixed description written by us for that topic; your words are not part of that description. The description tells the model not to include text, numbers, faces, people, logos or trademarks. Generated image files have names derived from their contents, are not linked to you or your pass, are reused for later visitors, and are not deleted automatically. A manifest records the topic tag, display topic, tags, original dimensions, colour palette, output dimensions, file names and byte sizes, model, quality, generation mode and time, request latency, calculated cost, usage returned by the AI processing provider, and that provider's request identifier.

Contact details you give us

When and what. Once you have reached a result in a conversation and asked at least two questions, MAIA may offer, once, that we follow up on your request, and ask for your email address, phone number and company; you may also give your name and role. Giving them is optional. Before asking, MAIA shows you a short notice in writing, in a card with a link to this section and two buttons to agree, whether you are typing, speaking or using avatar mode; in the chat MAIA also says it in full, and in voice it says a shorter spoken version that points you to the card and to this policy. The notices are versioned: the text of each version is fixed and kept. MAIA asks separately whether you agree to be contacted about this request, and whether you also want occasional news from us; the answer is no unless you say yes. You can type the details or say them; MAIA records exactly what you gave, reads a spoken email address and phone number back to you, and the server checks only that the address and number are well formed. If you decline, MAIA does not ask again in that conversation.

Where they are kept. In the People section of our admin panel: the details you gave, the language of the conversation, a stage our staff set (new, contacted, qualified, customer or closed), the conversations you gave them in with the turn numbers, and the dates. Your contact details are never added to what MAIA notes about you and are never used to compose the page: e-mail addresses and phone numbers are replaced before the conversation is given to the page writer. Because you give them in the conversation, they are also part of your conversation: they are sent to MAIA's AI models in the cloud with it, like everything else you say, and kept with the conversation records as set out under How long we keep things.

Why, and on what basis. To follow up on your request (for example to arrange the pilot or the demo you asked about): Article 6(1)(b), steps taken at your request before entering into a contract. If you say you do not want to be contacted, nothing is stored. To send you occasional news about MAIA Brain: only if you said yes, on the basis of your consent, Article 6(1)(a). You can withdraw it at any time, without affecting what was done before, by writing to info@maiabrain.com.

The record of what you agreed to. Each answer is recorded: the purpose (contact about this request, or news), whether you agreed, declined or later withdrew, when, the version and language of the short notice you were shown (and, in voice, of the spoken version), whether in chat or voice, whether you said it in the conversation or pressed the button on the card, and the conversation and turn. These records can only be added to, never changed.

How long. Contact details are kept for 24 months after our last contact with you, then cleared automatically, unless you ask us to erase them sooner. The record of what you agreed to is kept for three years as proof; once your details are cleared it identifies you only by a one-way SHA-256 fingerprint of your email address or phone number.

Your rights over them. You can ask to see your contact record, to receive it as a file, to correct it or erase it, to withdraw either agreement, and to object, by writing to info@maiabrain.com; we find your record by your email address or phone number. Erasing clears your details and erases the conversations you gave them in; the proof of what you agreed to stays, as a fingerprint, for the three years. You may complain to the Information and Data Protection Commissioner (see below).

Who sees them. MAIA Brain staff, in the access-controlled admin panel; every person opened, changed, exported or erased is logged. We do not share your contact details with anyone beyond the processors listed on this page (MAIA's cloud infrastructure provider, which hosts the service, and MAIA's AI processing providers, which process the conversation you gave them in), we do not sell them, and this service sends you no e-mail.

Partner applications from www.maiabrain.com

What. The partner programme page on www.maiabrain.com has an application form. When you send it, your browser sends what you entered straight to this service at talk.maiabrain.com: your organisation, country, website, name, role, email address and phone number, the partner level you are applying for, your sectors, how many clients you have, the regions you cover, what you sell today, why you want to partner with us, and whether you ticked the box about the certification course. With it we record when it arrived, the website it was sent from, and one-way keyed fingerprints of your network address and of your browser's identification string, so that abuse can be recognised; they cannot be turned back into the address. Your network address is also used, in memory, to limit how many applications one address can send in an hour (five). Your name, email address and why you are applying are required; everything else is optional.

Why, and on what basis. To assess your application and to talk to you about it: Article 6(1)(b), steps taken at your request before entering into a contract. If you tick “You may contact me about the certification course when dates are set”, we record that as your consent, Article 6(1)(a), for that one purpose only: being contacted about the certification course when its dates are set. It is not consent to news or to anything else. You can withdraw it at any time by writing to us; withdrawing does not affect your application or what was done before.

Where it is kept. On our server in MAIA's cloud infrastructure in Frankfurt, Germany, in the Partner applications section of our admin panel, with a review status our staff set (new, reviewing, accepted or declined). It is linked to a contact record in the People section, found by your email address or created for it. If we already hold a contact record for you, the application only adds what that record lacks; it never overwrites what you told us before. An application is not passed to MAIA or to any AI model, and it reaches our server through our cloud network's edge and its bot protection, as described below.

How long. 24 months from the day we receive it, then cleared automatically, unless you ask us to erase it sooner. What remains holds no personal data: the application's number, its dates and its status. If you ticked the course box, the record of that consent is kept for three years as proof; once your details are cleared it identifies you only by a one-way SHA-256 fingerprint of your email address.

Your rights over it. You can ask to see your application, to receive it as a file, to correct or erase it, to withdraw the course consent, and to object, by writing to info@maiabrain.com; we find it by your email address. Erasing your contact record erases your applications with it. Only MAIA Brain staff see applications, in the access-controlled admin panel, and every application opened or changed is logged by its number alone. We do not share applications with anyone beyond our hosting provider, and we do not sell them.

Visit analytics

From 3 October 2026. To understand who our visitors are and to improve our marketing, the service records, for each conversation started from 3 October 2026, details that your browser and our cloud network send with every request anyway. Nothing is read from your device by script for this, nothing is stored in your browser for it, and no third-party tag or pixel is used.

How it is recorded: the first page you open is served with a short token, signed by our server, that holds the referring address, the campaign labels, the page you arrived on and your languages. The page hands it back when the conversation starts, and the record is created then, with the address, place, network and browser of that request, under the conversation's random number. A later renewal or reconnection updates when the conversation was last seen and can fill in a detail the first request lacked.

Why, and on what basis. To understand our audience and improve our marketing: which countries and sites our visitors come from, which campaigns bring them, and which devices they use. The legal basis is Article 6(1)(f), our legitimate interest in doing so. We consider that it does not override your interests, because it uses only what any website receives, is kept for a limited time, is read only by MAIA Brain staff in the access-controlled admin panel (where an administrator's export of it is logged), and you can stop it at any time.

How long. The full network address is kept for 90 days. After that, the sweep keeps only its network part (the first three of the four numbers of an IPv4 address, the first 48 bits of an IPv6 address) and deletes the fingerprint. Everything else is kept with the conversation's copy for quality review and deleted with it, at most twelve months later. Before deleting it, the sweep adds the visit to daily totals by country, city, browser, operating system, type of device, referring site, campaign and first or returning visit; those totals hold no address, no conversation number and nothing you said, and they are not deleted automatically.

Who receives it. No one outside MAIA Brain. MAIA's cloud infrastructure provider, which hosts the service and runs its edge network, processes it on our behalf. It is not sent to any other processor named in this notice.

How to object. You can stop it at any time, without giving a reason: choose “Don’t track my visit” under the chat, or the button below. Either one makes our server set a cookie, talk_no_track, holding only “1”, for two years; our server reads it only to honour your choice. The control under the chat also deletes what was recorded for the conversation under way. From then on, nothing is recorded or counted for visit analytics for a conversation started from this browser. If your browser sends the Global Privacy Control signal (Sec-GPC: 1) or Do Not Track (DNT: 1), we treat it as the same objection, automatically. Conversations started by our own staff while signed in to the admin panel, and conversations we mark as tests, are not recorded either.

Done: from now on, visits from this browser are not recorded for visit analytics.

Your company's website

If you give MAIA your company's website, or name your company, MAIA reads public pages of that website to understand what your company does and to fit its answers, and the page on the left, to it. When you name your company without a website, MAIA first reads a public web search page, and at most eight public pages it lists about the company, to find the company's website. A browser on MAIA's infrastructure in the cloud reads the pages. It reads public pages only: it never logs in, never fills in or sends a form and downloads nothing, and in one conversation it reads the website of one company only.

The text of the pages is processed by MAIA's AI models on MAIA infrastructure placed in the cloud, to write a short structured summary of the company: what it does, its products and services, its customers and markets, its sectors, its size, its locations and its recent news, each point tied to the pages it came from. The text of the pages itself is not kept: it is held only while it is being read, and removed within minutes if a reading is interrupted.

The summary is kept with your conversation, together with the website's address and the addresses and titles of the pages read, and is used for the rest of the conversation: MAIA's AI models receive it when they answer you and compose the page, and the pages read are shown as sources under MAIA's answers, by their web address. It is kept and deleted with the rest of your conversation, for the same twelve months as the copy kept for quality review (see How long we keep things). Nothing that is read is added to MAIA's knowledge base. A public page can itself mention people, for example in a news item or a team page; MAIA reads it to describe the company and is instructed to note only facts about the company.

Who else is involved

MAIA's cloud infrastructure provider and MAIA's AI processing providers process personal data for the live service as set out here, and a face-animation provider does too for visitors who use avatar mode. Each acts on our behalf as a processor, bound by data-processing terms. A text-message provider and an SMTP email provider are configured, but the live no-sign-in mode does not send them a phone number, email address or sign-in code.

MAIA's cloud infrastructure
Receives the service runs on MAIA's infrastructure in the cloud in Frankfurt, Germany, inside the European Union, so the server records listed under the next heading are held there. Your connection reaches it through the infrastructure provider's edge network and its bot protection. The provider receives your network address and request details; the complete signed session pass passes through the edge network and the bot protection in the WebSocket URL and, when the browser renews it, in the X-Talk-Renewal request header. The bot protection runs the bot check and puzzle.
Why hosting, delivery, and protecting the service from automated abuse.
How long what the provider keeps as a provider is governed by its data-processing terms; you may ask us about them.
MAIA's AI models
Receives everything the service sends to its AI models to answer you, keep the notes, compose the page and check the conversation. The models run in the cloud at AI processing providers that act for MAIA as processors. Each use is described below.
Answers. MAIA's text answers are usually written by MAIA's main conversation model in one conversation kept open for your pass. It receives MAIA's instructions, material from our knowledge base, each question, and your conversation so far. The conversation is sent in full while it is short; once it passes about six thousand tokens (roughly 24,000 characters), the oldest turns are replaced by a summary made on our server, not by a model, by shortening each earlier line to at most 280 characters and keeping the summary to about 3,600 characters. That open conversation is closed about a minute after your page disconnects, after five minutes without use, when the service restarts, or when your pass's records are deleted, and it is replaced every fifty-five minutes. If it is unavailable, the answer is written by an ordinary call to a second MAIA model with the same instructions, material and conversation. A few fixed replies are written by the service itself, without a model: for example when you only ask for the page to be built, or after the conversation check has stopped the conversation.
Notes about you. A question that speaks about yourself is sent on its own to one of MAIA's AI models, with the provider's option not to store it switched on.
The page. The page on the left is composed from your conversation by a second open conversation with MAIA's main conversation model, kept for your pass. With each question, typed or spoken, it receives the question, the knowledge-base material fetched for it, MAIA's previous answer, what MAIA has noted about you, the headings of the page on screen, and a short interest profile: some words from your questions, up to four questions that state a goal, and your last six questions. If it fails, the same material is sent, without storage at the provider, to MAIA's page model. A separate facts-mode page writer uses that same model first and, if it is unavailable, a second MAIA model.
Voice. A voice session is led by MAIA's live voice model, opened without storage at the provider. It receives the sound from your microphone, anything you type during the session, MAIA's instructions, your conversation so far (in the same full-or-summarised form as above), and the answers the service looks up for it. It makes the transcripts and speaks. When you ask something factual, the question is answered by the same knowledge-base lookup and ordinary model call as the text chat, and the answer is passed to the live voice model to say. If the live voice model cannot be started, that voice session uses MAIA's fallback voice model, with your speech transcribed by MAIA's transcription model, and after three such failures within a minute all voice sessions use it for the next five minutes; that path receives your microphone's sound, anything you type during the session, MAIA's instructions, your conversation so far and knowledge-base material.
The answer review. After a model-written text answer, or an answer spoken by the live voice model, has been given, its text is usually (MAIA's words only, not your question) sent to MAIA's fixed review model, without storage at the provider, to check it against our content rules. This happens in the background and never delays an answer; the log records the first ten characters of a SHA-256 fingerprint of the pass and the names of any rules it flags.
The conversation check. After your fourth question, and then every three to ten questions, MAIA's fixed review model, without storage at the provider, is sent your last ten questions, typed or spoken, without MAIA's answers; what MAIA has noted about you; and the seconds between those questions. It judges whether the conversation is a genuine one about MAIA and its field or misuse, such as gibberish, unrelated tasks or probing. It runs in the background after an answer. If it is confident that the conversation is misuse, or judges so twice in a row, MAIA says once that it will stop here, later questions with that pass get the same reply without any model being asked, a new voice session is not opened, and an open live voice session closes the next time you speak or type.
The AI processing providers do not receive your network address or the number of your pass or conversation.
Why to write MAIA's answers, note what you say about yourself, compose the page, hear you and speak in voice, review answers against our content rules, and keep the service from being misused.
How long what the AI processing providers keep, and whether they may use it, is governed by their terms for the services MAIA uses and the data-processing terms that bind them as our processors; you may ask us about them. We have not arranged terms of our own with them beyond those.
MAIA's face service (avatar mode only)
Receives in avatar mode only: the audio of MAIA's spoken answers, and your browser's network address and request details when it streams the face's video to you. Our server asks it to open and close each face session; it sends no pass number, conversation or notes about you.
Why to show MAIA's face speaking her answers.
How long what the face-animation provider keeps is governed by its terms for the service and its data-processing terms; you may ask us about them.

Inside our server. The service also hands work to a knowledge-base process on the same server, over a local connection: lookups written by the models, your notes (to plan the page) and the text of the page being composed.

We do not sell personal data, we do not share it for advertising, and nothing from this service goes anywhere other than the processors above, except to a public authority entitled to it.

How long we keep things

The session pass. Once the check is passed, the service gives your browser a signed session pass containing a version, a renewable random pass number, a separate stable random conversation number, its expiry and the time the conversation started; an HMAC signature follows that payload. The expiry is four hours after issue unless we configure otherwise. It carries no name, email address or phone number. Before it runs out, or when you come back after it has run out, the page quietly obtains a new pass for the same conversation. A conversation can be renewed for up to twenty-four hours from its start; renewal never moves or replaces its stored conversation record.

On the server's disk, in a small database, the service keeps against the stable random number of your conversation:

While the service is running, it also keeps a working copy of your conversation, notes and page in memory under the stable conversation number until the retention sweep removes it. Renewing a pass leaves that working copy and the chat, page, voice and avatar runtime state under the same conversation number. After a service restart, the server reloads the conversation, notes, page and check state from the database before it accepts more turns.

How long: all of this is deleted six hours after your last pass expires, by a sweep that runs when the service starts and every ten minutes. With the default settings, and while the service is running, a conversation is therefore gone at most about thirty hours and ten minutes after it began, and a conversation of one pass that is not carried over is gone at most about ten hours and ten minutes after it began. If the service is stopped at that moment, the records are deleted when it next starts.

Kept for quality review: separately, the conversation transcript (your typed and spoken turns and MAIA's answers, with their times), what MAIA noted about you, the summary of your company's website if MAIA read it (see Your company's website), the pages shown to you, and the conversation's counters, cost and check verdicts are kept for up to twelve months under the same random conversation number, for quality review by MAIA Brain staff, then deleted by the same sweep. This copy holds no pass. Staff read it in an access-controlled admin panel, and every view is logged.

Staff comments that improve MAIA. MAIA Brain staff reviewing this copy can rate the conversation, one of MAIA's answers or a page version, and add a comment. When the comment is saved, e-mail addresses, phone numbers and the name and company you gave us in the conversation (as contact details, or as the company MAIA noted) are replaced; only that version of the comment is kept, with who wrote it, when, and which conversation, answer or page it was about. Names or other details mentioned only in the free text of the conversation or of the comment are not detected and are not replaced. The comment then becomes suggested changes to how MAIA answers, which an administrator approves or discards. To write them, the comment is sent to one of MAIA's AI models, without storage at the provider, together with the smallest part of the conversation it is about: the commented answer and the question before it, the headings of the commented page, or, for a comment on the whole conversation, its last three turns; the same details are replaced in it. The model is instructed not to name any person or company, not to quote you and to describe the situation only in general terms, and a suggestion that contains one of the replaced details, or that the model reports as naming someone, is refused; an administrator reads every suggestion before it can be used. Only the approved wording of a suggestion becomes part of what MAIA knows; the suggestion's reasons stay in our records. This rests on the same legitimate interest as the copy kept for quality review, Article 6(1)(f). It is kept as long as that copy and deleted with it. When your conversation is erased, or turns out to have been one of our own tests, the comment's derived record is cleared and its suggestions still waiting are withdrawn; an approved suggestion holds no personal data and stays, marked for an administrator to review. A request for your data includes these ratings, comments and suggestions.

Deleting sooner. Choosing “New conversation” ends the current conversation immediately so its pass cannot be used again, clears the pass from this browser, and starts clean; the ended server record remains until the retention sweep, and the copy kept for quality review remains for up to twelve months. Closing the tab alone does not delete it sooner. These records hold no account, and a name or contact details only if you gave them in the conversation; what you typed or said may itself identify you. Contact details you give are also kept in the People section, as set out under Contact details you give us.

Other records on the server:

The service log. The service writes a log of technical events: connections closing, voice sessions starting and ending, word and character counts, timings, errors, and the names of rules when a check refuses or flags output. Entries can carry random question numbers made by the browser or server, a random voice-session number, the AI processing provider's call identifiers for voice lookups, the last twelve characters of its conversation-item identifiers on the fallback voice path, the first eight characters of face-session numbers with their timings, and, for the answer review and conversation check, the first ten characters of a SHA-256 fingerprint of the conversation number. It also writes one line for every request the service answers, and for every connection opened and closed: the method, the address path and the names (never the values) of its query parameters, the status, how long it took and how many bytes were sent, a random request number, the request number our cloud network's edge gave it, and a keyed one-way fingerprint of your network address, never the address itself; for a partner application, also the outcome, the names of any fields that were refused, and the application's number, never what you entered. It does not write your questions or MAIA's answers as log fields, and it clears the session pass from the address of its connections before accepting them. It can, however, hold short pieces of text: when a part of the page is refused, up to 500 characters of what the page model wrote; when the page model's reply cannot be read, up to 160 characters of it; and error messages, which can quote what was being processed. This log is kept for at most thirty days, and less once it reaches 200 MB.

Why, and on what basis

We send your conversation, what you tell MAIA about yourself and, if you use voice, what you say, to MAIA's AI models in the cloud, and keep the conversation records until six hours after the last pass expires (and the copy kept for quality review for up to twelve months, as set out above), because that is how the service you asked for answers you in context and composes the page for you. The legal basis for the processing necessary to provide the service you request is Article 6(1)(b). The separate quality-review copy rests on Article 6(1)(f), MAIA Brain's legitimate interest in reviewing and improving the service and its answers. It is read only by MAIA Brain staff; a part of it that staff comment on is sent to one of MAIA's AI models as set out under Staff comments that improve MAIA. You may object at any time by writing to info@maiabrain.com, quoting the conversation if you can.

We use the bot check, limit sessions per network address, review answers against our content rules, measure what each pass costs and watch spending, keep the service log, and let the conversation check end conversations that misuse the service, because every answer costs us money and an open service of this kind is abused quickly. The legal basis is Article 6(1)(f), our legitimate interest in keeping the service available, accurate and its cost bounded.

MAIA makes no decision about you that has legal or similarly significant effects. What it notes about you is used only within your conversation, as set out above. The conversation check can end a conversation automatically; that affects only this free conversation. If you think it stopped you wrongly, choose “New conversation”, or write to us.

Cookies and browser storage

The signed conversation pass is stored in this browser's localStorage under maia-talk-pass-v2. That lets the same server-side conversation reopen after navigation, in another tab, or after a service restart. Choosing “New conversation” ends the current server-side conversation and removes that browser entry. The pass is a bearer credential. Anyone who can read the current pass can use the conversation until it is ended, the conversation's twenty-four hours from its start run out, or its records are deleted as described above, even after the pass itself has expired, because the current pass can always be renewed. Renewal accepts only the current pass, or the pass it replaced for about two minutes after a renewal. Any older pass is refused.

The language you choose with the EN | IT switch, or that the address names (?lang=it), is kept in this browser's localStorage under maia-talk-lang-v1, so the next visit opens in it; the entry holds only “en” or “it”. The conversation's language is also stored on our server with the conversation, and is deleted with its records.

The bot check and the puzzle are run by MAIA's cloud infrastructure provider, which keeps its own token in your browser to show that the check was passed; according to the provider's documentation it does so in a cookie, and the provider decides what it holds and how long it lasts. Our service does not read it. The page loads the provider's script for the check and the puzzle from the address we configure for it.

That token is strictly necessary to protect the service from automated abuse, and without it the service cannot be used. For that reason, under Regulation 5 of the Processing of Personal Data (Electronic Communications Sector) Regulations, Subsidiary Legislation 586.01, you are not asked to consent to it.

The page migrates an older maia-talk-pass-v1 item from session storage once, if present. If you open the private avatar link, the page stores maia-talk-avatar-v1, the link's code (and removes it from the address bar), and maia-talk-avatar-on-v1, whether you switched the face off; both remain session storage for that tab. The page's own code sets no cookie.

If you object to visit analytics, our server sets the cookie talk_no_track, holding only “1”, for two years, and reads it only to honour that choice (see How to object). It is strictly necessary to respect the choice you made, so under the same Regulation 5 you are not asked to consent to it.

Where data goes

The service runs on MAIA's infrastructure in the cloud in Frankfurt, inside the European Union. Our cloud network carries your connection through edge locations, which may be outside the European Economic Area. MAIA's AI processing providers and its face-animation provider are established in the United States, and what they receive may be processed outside the European Economic Area. Those transfers happen under the mechanisms in Chapter V of the Regulation: the Standard Contractual Clauses adopted by the European Commission, in the processors' data-processing terms, and adequacy decisions, including the EU–US Data Privacy Framework, where they apply. You may ask us for information about the safeguards that apply and for a copy of them.

Your rights

You may ask for access to your personal data, for it to be corrected or erased, for its processing to be restricted, and, where the conditions in Article 20 are met, for it to be given to you in a portable form.

Where we process on the basis of our legitimate interests, you may object at any time on grounds relating to your particular situation, and we will stop unless we can show compelling legitimate grounds that override your interests. To object to visit analytics you need give no reason, and it takes effect at once: see How to object.

Write to info@maiabrain.com. We answer within one month, and we will tell you if we need longer and why. If you gave us contact details, we find that record and the conversations you gave them in by your email address or phone number. Otherwise, because the service asks for no account and files conversation records under a random conversation number, we will usually be unable to identify which conversation records are yours without information that links you to that pass. The pass is processed by our server and passes through our cloud network's edge as described above; conversation records are deleted on the six-hour schedule, service logs can remain for up to thirty days or 200 MB, and aggregate totals are not deleted automatically. A request about what one of our processors holds, we will pass on to it.

If you are not satisfied

You may lodge a complaint with the Information and Data Protection Commissioner, the supervisory authority for Malta, or with the authority in the country where you live or work. Doing so does not affect any other remedy available to you.

Changes to this notice

This notice describes what the service does today, and it is written from the code that was running when it was published. If that changes, this notice changes with it.

P MAIA AI LTD · Palace Court, Church Street, St Julians STJ 3049, Malta · Reg. C99026 · VAT MT28528403 · info@maiabrain.com · Back to the chat