Privacy policy

The merarobotics.com website, inquiries, the MERA Robotics app in ChatGPT and Claude, the MERA OS and MERA OS Event apps, and MERA RENT (mera.rent and the iOS and Android apps) · updated 3 November 2026 (previous version: 2 November 2026)

1. Controller

The controller of your personal data is MERA ROBOTICS sp. z o.o., ul. Komitetu Obrony Robotników 30 lok. 96, 02-148 Warsaw, Poland, KRS 0001266221, NIP (tax ID) 5223384081 ("MERA", "we"). For any data protection matter, write to contact@merarobotics.com.

2. Inquiries: website, API and the app in ChatGPT and Claude

You can send an inquiry to MERA:

• with a form on merarobotics.com,
• through the public API https://merarobotics.com/api/public/v1/inquiries, for example via an AI agent acting for you,
• through the MERA Robotics app in ChatGPT or Claude, i.e. the MCP server https://merarobotics.com/mcp (the form in the chat and the request_quote tool),
• by e-mail to contact@merarobotics.com.

What data

What you provide: full name, e-mail address and, if you choose, company, job title and phone. Plus the details of the event or deployment: service, robot, date, place, number of guests, how long the robot should be on site, languages, budget (if you state one) and a description of the goal.

For inquiries sent with a website form we also store the address of the page the form was sent from, the domain of the page that referred you to it, and campaign parameters (utm) if they were in the address. For inquiries sent through the MCP server we store the name of the app it came from (e.g. ChatGPT) and a hash of the connection's IP address created with a secret salt. We do not store the IP address itself; the hash is used for inquiry limits.

If someone else gave us your details, for example a colleague or an AI agent acting for them, we received them with that inquiry. The categories of data are the same.

Purpose and legal basis

• Replying to your inquiry and preparing an offer when you ask on your own behalf: Art. 6(1)(b) GDPR (steps taken at your request before entering into a contract).
• Replying to your inquiry and preparing an offer when you write on behalf of a company or institution: Art. 6(1)(f) GDPR (our legitimate interest in answering that organisation's request for an offer).
• Protecting the forms, API and MCP server against spam and abuse, including inquiry limits: Art. 6(1)(f) GDPR.

An inquiry reaches us only after you tick the consent box and click the send button. Providing data is voluntary, but without your name, e-mail address and a description we cannot reply.

What happens to an inquiry

The inquiry is stored in our CRM (a Supabase database), and a notification reaches the team's mailbox by e-mail (via the FormSubmit service). The team replies by e-mail. The CRM may prepare a draft reply with an AI model (Anthropic, OpenAI or Google); a person reviews and sends it. An inquiry does not book a date or confirm a price.

3. The MERA Robotics app in ChatGPT and Claude

• Your conversation in ChatGPT is processed by OpenAI and your conversation in Claude by Anthropic, each as a separate controller under its own policy (OpenAI privacy policy, Anthropic privacy policy). We have no access to your conversation with the assistant.
• When the assistant uses the MERA app, it sends tool parameters to our server, for example the language, the type of service or a search phrase. We answer with information about MERA and do not store these parameters.
• We receive only an inquiry that you send yourself: with the "Send inquiry" button in the form, after checking the details and ticking consent, or by asking the assistant to send details that you have seen and approved. From then on, section 2 applies.
• The app needs no sign-in and does not link your ChatGPT or Claude account to any data at MERA.

4. Clients: contracts and invoices

When an inquiry leads to a contract, we process data of the people who conclude and carry out the contract (name, job title, e-mail, phone, company details):

• to perform the contract: Art. 6(1)(b) GDPR, or Art. 6(1)(f) GDPR when the contracting party is the company you work for,
• to issue invoices and keep accounts: Art. 6(1)(c) GDPR,
• to establish, pursue or defend claims: Art. 6(1)(f) GDPR.

We issue invoices in the Fakturownia system and send them to the Polish National e-Invoicing System (KSeF).

5. The MERA OS and MERA OS Event apps

MERA OS is a phone app for talking to your robot by voice: you give it a name, a personality and a voice, then you talk. MERA OS Event is an app for controlling and talking to humanoid robots (e.g. Unitree G1) at events.

• Microphone: audio is streamed in real time to our conversational AI provider (ElevenLabs) so the robot can talk with you. The robot's reply is prepared by the Google Gemini language model within that service. In the MERA OS app we ask for your consent to this before the first conversation. We do not use recordings for profiling or advertising.
• Camera (MERA OS Event): used only on your request (scene preview, photos, image recognition). Images are not sent anywhere without your action. When you turn on image recognition, camera frames are analysed by the Gemini model (Google).
• Account: e-mail address and sign-in ID (Supabase Auth, a one-time code sent by e-mail or Google Sign-In), used solely for sign-in and syncing robot settings. In MERA OS your account also stores the robot profile (name, description, conversation background, remembered facts) and recent messages, so the same robot works on every phone; you can turn off saving history in settings. To delete your account, follow the steps on the account deletion page.
• Technical and usage data: conversation time and usage statistics per robot (for billing), error logs.
• Reported replies: when you report a robot reply in MERA OS, we store the reply, a few previous messages, the reason and your comment so that we can review it.
• Payments: handled by Stripe (payments in the MERA OS Event panel) and RevenueCat (subscriptions and top-ups in the mobile apps, paid through the App Store or Google Play). We do not see full card details.
• Local network and Bluetooth: the app connects to your robot over your Wi-Fi network and over Bluetooth (connection setup). This data stays within your network.

Legal basis: Art. 6(1)(b) GDPR (use of the app under a contract) and Art. 6(1)(f) GDPR (security and fixing errors).

6. MERA RENT: humanoid robot rental for events

MERA RENT is a platform for ordering a humanoid robot with an operator for an event. It runs as the website mera.rent (the same app is available at merarobotics.com/rent) and as the MERA RENT app for iOS and Android. The service is provided by MERA ROBOTICS sp. z o.o., which is the controller of your data (section 1). This section covers the website and both apps.

The iOS and Android apps

• The app displays the mera.rent website and collects no data other than the website does. It has no account, no ads and no analytics tools: it shows no cookie banner and does not load Google Analytics or the Meta pixel.
• It does not use an advertising identifier (IDFA, AAID) and does not track you across other apps or websites.
• On Android it only needs internet access and vibration (a short vibration when you tap a send button). It does not ask for location, contacts, camera, microphone or photos.
• You share a link to an offer through the system share sheet. It goes only where you send it.

What data

You provide the data yourself when you send a request: a booking, a request to hold a date, for a quote, an offer or a phone call, a request to change the date or cancel, an agenda, or a robot owner's application. Depending on the form, this is:

• full name, e-mail address, phone (optional in some forms), company or institution, tax ID or EU VAT number and, for a private person making a booking, an invoice address,
• event details: robot, package, date, city and country, venue address or name, type of event, the robot's tasks, languages, the robot's working hours, agenda, notes and the price shown in the app,
• if you provide them: purchase order (PO) number, end client name (agencies), the e-mail address of the payer or of a person we should also notify, the time and subject of the phone call,
• in a robot owner's application: robot model and number of robots, home city, information about the operator, a link to photos or a video, company and tax ID.

We add to the request the address of the page it was sent from, the domain of the page that referred you to it, and campaign parameters (utm) and ad click identifiers (e.g. gclid, fbclid) if they were in the address. If you give us another person's details, for example the payer's, we received them with your request.

What happens to a request

A request reaches MERA only after you tap the send button. The app passes it to the MERA public API (/api/public/v1/inquiries, the same as in section 2), which stores it in our CRM (a Supabase database). The MERA server sends a notification about the request by e-mail to the team's mailbox via the FormSubmit service. If FormSubmit rejects the request from the server, the server asks your browser or the app to send the same notification directly to FormSubmit: name, e-mail, phone, company, the content and the reference number of the request. The notification always goes to the fixed address of the MERA team's mailbox.

From then on, section 2 applies: the team replies by e-mail and, if you asked for a call, calls you back. A person always reviews a draft reply prepared with AI. A request is not yet a booking: MERA confirms the date, and when a contract follows, section 4 applies. Requests are processed by the same providers as website inquiries (section 7), including outside the EEA under section 8.

Data on your device

• The website and the apps store in your device's storage (localStorage) your choices (a draft request) and the "My requests" list (up to the last 50, with the reference number, date and contact details from each request). When the "Remember my details on this device" option is on (it is on by default), they also store your contact and invoice details so you do not have to type them again.
• Campaign parameters and click identifiers from the page address are kept in session storage (sessionStorage) so they can be added to the request. They disappear when you close the tab or the app.
• This data does not reach MERA until you send a request. You can turn off remembering your contact details with the switch and delete all stored data in Profile with the "Delete data from this device" button. In the app it is also deleted when you uninstall the app. Requests you have already sent stay in the MERA CRM; see below for how to delete them.

Calendar, city list and analytics

• The availability calendar downloads from the MERA server only the dates on which robots are booked, with no personal data. The app does not send your data with this request.
• The app downloads the city list (GeoNames) from the MERA server and searches it on your device.
• On your first visit, the mera.rent website (and merarobotics.com/rent) shows a banner with "Accept" and "Decline" buttons. Only after "Accept" does it load Google Analytics 4 (G-P7ZXV0KQ9W) and the Meta pixel (29406307232343123), as the MERA EVENTS pages do. We measure the ordering steps: screens, choice of robot, choice of date and number of days, sending a request (request type, robot, the net amount shown in the app, currency and request reference number), sending errors and the offer link. These events contain no name, e-mail, phone number, company, tax ID or request content. We store your decision in your browser (localStorage, the merarent_consent entry). You can change it at any time with the "Cookie settings" link in the website footer or in your Profile. Details in section 10.
• Fonts and images are served from MERA servers. Our hosting keeps technical logs as described in section 10.

Purpose and legal basis

• Handling your request (contact, date confirmation, offer, preparing a contract) when you order on your own behalf: Art. 6(1)(b) GDPR (steps taken at your request before entering into a contract).
• Handling a request sent on behalf of a company, agency or institution, or an application for a company's robot: Art. 6(1)(f) GDPR (our legitimate interest in answering that organisation's request).
• Protecting the forms against spam and abuse, including request limits, and establishing, pursuing or defending claims: Art. 6(1)(f) GDPR.
• When a request leads to a contract, we process contract and invoice data under section 4.

Providing data is voluntary, but without your name and e-mail address (and, in some forms, your phone number) we cannot handle the request.

How long we keep data

• Requests that did not lead to a contract: until any possible claims become time-barred, and no longer than 6 years from the last contact. We delete them earlier if you object or ask us to delete them.
• Contract and invoice data: 5 years from the end of the tax year, as required by tax and accounting law.
• Data on your device: until you delete it or uninstall the app.

Your rights and deleting your data

You have the right to access your data and get a copy, and the rights to rectification, erasure, restriction of processing, data portability and to object to processing based on Art. 6(1)(f) GDPR (details in section 11). To delete your requests from the MERA CRM or to exercise any other right, write to contact@merarobotics.com and give the e-mail address used in the request or its reference number. We reply within one month. You may also lodge a complaint with the President of the Personal Data Protection Office in Poland (UODO) or with the supervisory authority in your country.

7. Recipients

The MERA team has access to the data. The following processors handle it on our behalf:

• Supabase: database (CRM, inquiries, MERA OS and MERA OS Event accounts and settings), servers in Zurich, Switzerland,
• Netlify: hosting of the website and of the server functions that inquiries pass through; the functions run in the USA,
• FormSubmit: e-mail notification about a new inquiry,
• GoDaddy: e-mail for the merarobotics.com domain,
• Google: the team's Gmail mailbox and Google Calendar, Google sign-in and image recognition (Gemini) in MERA OS Event, the Gemini language model in voice conversations, draft replies in the CRM (Gemini),
• Anthropic and OpenAI: AI models the CRM uses for draft replies,
• ElevenLabs: voice conversation in MERA OS and MERA OS Event,
• Stripe and RevenueCat: payments in MERA OS and MERA OS Event,
• Fakturownia: invoices and sending them to KSeF.

Separate controllers: OpenAI and Anthropic (your conversation in ChatGPT and Claude, section 3), Google (Google Fonts and the YouTube player on the website, section 10), and public authorities where the law requires it (e.g. the tax administration via KSeF).

We do not sell data. We share it with Google and Meta for ad measurement only with your consent on the MERA EVENTS pages and the MERA RENT website (section 10).

8. Transfers outside the EEA

Some providers are based or have servers outside the European Economic Area, including in the USA and Switzerland. We transfer data on the basis of a European Commission adequacy decision (Switzerland, and in the USA companies certified under the EU-U.S. Data Privacy Framework) or standard contractual clauses approved by the European Commission. To get a copy of these safeguards, write to contact@merarobotics.com.

9. How long we keep data

• Inquiries that did not lead to a contract: until any possible claims become time-barred, and no longer than 6 years from the last contact. We delete them earlier if you object or ask us to delete them. We keep the contact history so that we know what we have already discussed and do not write again to people who do not want us to. The IP hash is kept with the inquiry.
• Contract and invoice data: for the period required by tax and accounting law, i.e. 5 years from the end of the tax year.
• Technical logs: up to 30 days.
• MERA OS and MERA OS Event: account data and robot settings until the account is deleted; usage statistics for as long as needed for billing. The audio stream is processed transiently by the voice provider under its own policy. Reported replies are kept until reviewed, for no longer than one year.

If you successfully object or ask us to erase your data, we delete it earlier, unless the law requires us to keep it.

10. Cookies, analytics and logs

• The website uses no analytics tools, advertising pixels or tracking cookies. The exceptions are the MERA EVENTS pages and the MERA RENT website, described below, where measurement runs only with your consent.
• After you sign in to MERA OS, MERA OS Event or a MERA panel, your browser stores the sign-in session (localStorage). After a site update, the app stores a timestamp in session storage (sessionStorage) that prevents a reload loop. These entries are needed for the site to work.
• The website loads the Space Grotesk font from Google Fonts, and some pages have a YouTube player in youtube-nocookie mode. Your browser then connects to Google servers and sends them your IP address.
• We count visits from search engine and AI assistant bots (e.g. GPTBot, ClaudeBot). We store only the bot name, the day and a page group, with no IP addresses and no personal data.
• Our hosting keeps technical logs (e.g. IP address, time and requested address) to diagnose errors, apply rate limits and protect the service against abuse (Art. 6(1)(f) GDPR). The functions that handle inquiries log only error codes, never the content of an inquiry.

Measurement on the MERA EVENTS pages (consent only)

This applies to the MERA EVENTS pages: /events and its language versions, the pages about the robot host and about Edward Warchocki at events, and the thank-you pages shown after you send the form. The other merarobotics.com pages have no such measurement. MERA RENT has its own banner, described below.

• Banner: on your first visit the page shows a banner with "Accept" and "Decline" buttons. Until you click "Accept", the page does not load any Google or Meta scripts, so none of their cookies are set. We store your decision (consent or refusal) in your browser (localStorage, the mera_consent entry) so we do not ask again. One consent covers both traffic measurement and ad measurement.
• Google Analytics 4 (ID G-P7ZXV0KQ9W, Google Ireland Limited): with your consent it measures page views and the events GA4 records automatically, plus our own events: a button click with its location (cta_click), playing a video (video_play), starting the form and each form step (form_start, form_step), a sending error (form_error) and a sent request (generate_lead with the type of event). Our events contain none of your contact details. Cookies: _ga and _ga_P7ZXV0KQ9W (up to 2 years under Google's default settings).
• Meta pixel (ID 29406307232343123, Meta Platforms Ireland Limited): with your consent it records a page view (PageView) and, after you send the form, a Lead event with the type of event and the request reference number. Cookies: _fbp and, when the page address contains a Meta ad click identifier (fbclid), also _fbc (up to 90 days under Meta's default settings).
• Google Ads: the page code also supports Google Ads conversion measurement with enhanced conversions (with your consent, the e-mail address and phone number from the form, hashed by the Google script before sending, and the request reference number). This tag is not enabled today, so this data is not sent to Google.
• What else Google and Meta receive: your IP address, the address of the current and referring page, browser and device information and cookie identifiers, as with any script loaded from their servers. With your consent they may also use this data under their own policies, for example to tailor ads (Google privacy policy, Meta privacy policy), and transfer it to the USA (section 8).
• Click identifiers: we add utm parameters and ad click identifiers from the page address (gclid, gbraid, wbraid, fbclid, msclkid) to your request and store them in the CRM (section 2), also without consent in the banner, because they come from the page address, not from cookies. We use them to see which ad a request came from (Art. 6(1)(f) GDPR). Today we do not send them back to Google or Meta.
• The thank-you page stores your first name and request reference number in session storage (sessionStorage) to display them. They disappear when you close the tab.
• Legal basis: Google Analytics and the Meta pixel run on the basis of your consent (Art. 6(1)(a) GDPR). You can withdraw consent at any time. Withdrawal does not affect the lawfulness of measurement before it.
• How to withdraw consent: the page has no separate button to change your decision. Delete the site data for merarobotics.com in your browser settings (cookies and site data). This removes the Google and Meta cookies and the mera_consent entry, the scripts stop loading, and on your next visit the banner asks again and you can click "Decline".

Measurement in MERA RENT (consent only)

This applies to the mera.rent website and the same website at merarobotics.com/rent. The MERA RENT apps for iOS and Android show no banner and do not load these tools.

• Banner: on your first visit the website shows a banner with equal "Accept" and "Decline" buttons and a link to this policy. Until you click "Accept", the website does not load any Google or Meta scripts, so none of their cookies are set. We store your decision in your browser (localStorage, the merarent_consent entry), separately from your decision on the MERA EVENTS pages.
• Google Analytics 4 (G-P7ZXV0KQ9W) and the Meta pixel (29406307232343123): the providers, the cookies and the data that reach Google and Meta are the same as on the MERA EVENTS pages (above). With your consent GA4 measures page views and our own events: ordering screens (rent_step), choosing a robot (select_robot), choosing a date with the number of event days and the number of days until the date (select_date), the "1 day" and "Several days" switch in the phone calendar (select_days_mode), sending a request (generate_lead: request type, robot, the net amount shown in the app, currency and request reference number), a sending error (rent_error), copying the offer link (offer_link) and your choice in the banner (consent). The Meta pixel records a page view (PageView), choosing a robot (ViewContent with the robot ID) and sending a request (Lead with the request type, robot and request reference number).
• What we do not send: the events contain no name, e-mail, phone number, company, tax ID or request content.
• Legal basis: your consent (Art. 6(1)(a) GDPR). Withdrawing consent does not affect the lawfulness of measurement before it.
• How to change your decision: the "Cookie settings" link in the website footer or in your Profile opens the banner again. After "Decline" the website stops measuring and removes the _ga, _gid, _fbp and _fbc cookies from its domain.

11. Your rights

You have the right to:

• access your data and get a copy,
• have your data rectified,
• have your data erased,
• restrict processing,
• data portability for data we process under a contract or steps before a contract,
• object to processing based on our legitimate interest (Art. 6(1)(f) GDPR).

Write to contact@merarobotics.com; we reply within one month. You may also lodge a complaint with the President of the Personal Data Protection Office in Poland (UODO) or with the supervisory authority in your country.

12. Profiling

We do not profile you or make decisions about you based solely on automated processing. A person always reviews a draft reply prepared with AI.

13. Children

The MERA OS and MERA OS Event apps are intended for users aged 13 and over. They are not directed at children and we do not knowingly collect their data.

14. Changes

We will announce changes to this policy on this page and, for MERA OS and MERA OS Event, also in the app. The update date is shown at the top of the page.

MERA ROBOTICS sp. z o.o. · KRS 0001266221 · contact@merarobotics.com · Terms of use · Polityka prywatności (polski)