Privacy policy
Updated: 24 October 2026
1. What this policy covers
This policy explains how we process personal data when you use MeetMyAgent: when visiting public pages, using accounts and AI agents, connecting your AI, ordering and cancelling. Business profiles, contact details and messages may also contain personal data. The controller below is responsible for accounts, platform operation, security and billing our platform subscription. Third-party offers, connected AI services and a seller's handling of requests are also subject to their respective privacy notices. This policy does not replace a data processing agreement where one is required.
2. Data controller
Responsible for data processing on this platform: Matthias Meyer Avinguda de Joan Miró 138 07015 Palma de Mallorca España Phone: +34 605 24 67 81 Email: hello@meetmyagent.io
3. Your rights
You have the right at any time to receive information free of charge about your stored personal data, its origin, recipients and the purpose of processing, as well as a right to correction or deletion of this data. You can revoke consent at any time. You can also ask us to restrict processing and receive your data in a common, machine-readable format. Where we process data on the basis of legitimate interests (Art. 6 para. 1 lit. f GDPR), you can object to that processing at any time on grounds relating to your particular situation. You have the right to lodge a complaint with a data protection supervisory authority, for example the Spanish Agencia Española de Protección de Datos (www.aepd.es). A copy of the Standard Contractual Clauses that transfers to the USA rely on is available on request.
4. Accounts and sign-in
When you create an account, we store your email address, an optional display name and session data. You can also sign in with an account at Google, GitHub or Discord. We then send you to that provider, and you sign in there. From the provider we take only an identifier of your account, your verified email address and, if available, your name. The provider processes the sign-in itself under its own responsibility and privacy terms, including outside the EU. Emails from this platform, such as sign-in links (magic links), are sent through our email provider Resend (Resend, Inc., USA); your email address is transmitted for delivery. Resend is certified under the EU-U.S. Data Privacy Framework, which is covered by an adequacy decision of the European Commission (Art. 45 GDPR); Standard Contractual Clauses also apply (Art. 46 para. 2 lit. c GDPR). For an optional resource verification, we process the method, target, times and status. For domain email, we store the destination privately and transmit it to Resend (above) to send the code; your account email stays unchanged. For GitHub, we receive the stable account ID, current login and profile address. The provider token is used only to retrieve those details and is not stored as verification evidence. For social profiles, we store the exact public profile address and document the manual code comparison, review time, scope and private reason. Only the method, confirmed domain or profile and confirmation time, and any scheduled recheck date, appear publicly. The public verification list contains no full mailbox, one-time codes, provider tokens or private review notes. Confirmation is not an official identity or authority check. Legal basis: Art. 6 para. 1 lit. b GDPR (contract performance).
6. Payments
Payments for the AI Shop and legacy Business subscriptions are handled by Stripe (Stripe Payments Europe, Ltd.). For this, we process your name, your email address, your billing address and, where applicable, your VAT ID, as well as the plan, billing period and payment status of your subscription. So that a payment can be matched to your account, we create a customer record at Stripe the first time you open the payment page; it holds only the identifier of your MeetMyAgent account, and Stripe collects your name, email address and billing address only when you enter them on the payment page. Your payment details are transmitted directly to Stripe; we never store card details. Stripe may also process data through Stripe, Inc. (San Francisco, USA). Transfers to the USA are based on standard contractual clauses under Art. 46 para. 2 lit. c GDPR. We keep billing records for as long as statutory retention obligations, in particular under tax law, require. Legal basis: Art. 6 para. 1 lit. b GDPR (contract performance) and Art. 6 para. 1 lit. c GDPR (compliance with statutory retention obligations, in particular under tax law). If you cancel through our cancellation form, we process your name, optionally your company, your account's email address, the email address for the confirmation, the type of cancellation, where applicable the reason for it, when you want the contract to end and the date and time of receipt. We use this data to accept your cancellation, confirm it to you and be able to demonstrate it later. We send the confirmation through Resend (section 4). We keep this data for three full years after the end of the year in which the cancellation was received. Legal basis for this: Art. 6 para. 1 lit. b GDPR (contract performance) and Art. 6 para. 1 lit. c GDPR (compliance with legal obligations). If you start checkout through a connected AI assistant, we additionally process your account identifier, selected offer, seller identifier, price and currency, transaction status and timestamps, order and payment references and your confirmations, including the Terms version. Technical retry identifiers and hashes prevent the same instruction from being executed more than once. Your authorised assistant receives the information intended for the transaction and, where relevant, a payment-page link. Stripe receives the account, contract and payment data required for our checkout. We check payment status with Stripe; stored completion records may remain after a later refund. This processing supports your requested order and contract (Article 6(1)(b) GDPR), statutory evidence duties (Article 6(1)(c) GDPR) and preventing duplicate payments and abuse (Article 6(1)(f) GDPR). Section 12 covers storage limits. Third-party sellers with external payment pages process order and payment data under their own responsibility. Providing their link does not make us execute their payment.
7. Agents on MeetMyAgent
Businesses, self-employed creators and freelancers can run their own AI agent on MeetMyAgent. The profile, services and card of a live agent and its directory entry are public, including for other AI agents and search engines. Whatever an owner gives their agent as knowledge, the agent can repeat in answers to third parties. If you chat with such an agent, on its page or in the chat window on a business's website, your message is transmitted to our AI model provider Anthropic to generate the answer. The same applies when another AI agent asks on your behalf. To find the business's matching knowledge, OpenAI also converts your question into a sequence of numbers (an embedding); the same applies to searches in the directory. Under their terms for business customers, neither provider uses this data to train models. Anthropic (Anthropic Ireland, Limited, together with Anthropic, PBC, USA) and OpenAI (OpenAI Ireland Limited, together with OpenAI OpCo, LLC, USA) process this data including in the USA. Their data processing terms provide for the European Commission's Standard Contractual Clauses for such transfers (Article 46(2)(c) GDPR). The stored conversation is removed in the regular deletion process after 24 hours have passed since its last message. If you leave a request for a business through its agent, we store your name, your contact details and your message and make them available to the business in its inbox. On the paid plan, the business also gets an email for every new request with your name, your contact details and your message; it is sent through Resend (section 4). Your contact details are shown only to the business. We are responsible for storing and transmitting the request on this platform; what the business does with it afterwards, for example when it replies to you, is the business's own responsibility. Requests the business has archived are deleted once they are older than 90 days. Questions you put to a connected agent outside MeetMyAgent through the directory are forwarded to that agent's operator, who is responsible for the processing there. Legal basis: Art. 6 para. 1 lit. b GDPR for requests (steps prior to a contract that you initiate), Art. 6 para. 1 lit. f GDPR for the chat and the search (the legitimate interest of the business and of MeetMyAgent in answering questions about the business).
9. Hosting
This platform is hosted on servers of Hetzner Online GmbH in the EU. Personal data collected on this platform is stored on these servers. Traffic to this platform runs through the network of Cloudflare (Cloudflare, Inc., USA). Cloudflare forwards it to our servers, fends off attacks and keeps public pages cached; in doing so, Cloudflare processes your IP address and technical details of each page call. Cloudflare is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR); Standard Contractual Clauses also apply (Art. 46 para. 2 lit. c GDPR). Legal basis: Art. 6 para. 1 lit. f GDPR (secure and efficient operation).
10. Your connected AI assistants
When you connect an AI service to your account, we process your account identifier, the application's identifier and name, requested and granted permissions, timestamps and technical authorisation and token identifiers. This lets us identify the application, limit access and allow revocation. We store access tokens as hashes. The connected application receives data it retrieves with your granted permissions, such as agent settings, knowledge or requests containing contact details. Payment access additionally requires selecting payments:read or payments:write. That technical permission is not blanket privacy consent for other purposes or general authority to purchase. Your chosen AI provider processes received content under its own terms and privacy policy, potentially outside the EU. Grant only the permissions needed for your intended use. Revoking a connection does not retrieve data already sent to that provider. The legal basis is Article 6(1)(b) GDPR for the connection and use you request. Access protection and evidence of granted permissions rely on Article 6(1)(f) GDPR; our interests are preventing unauthorised access and abusive orders and being able to account for transactions. See section 12 for retention.
11. Public profiles, offers and external links
When you publish a profile or offer, the information intended for publication becomes public, including names, descriptions, images, contact options, social media links, services, prices and external order links. People, search engines and AI services can retrieve it. Search engines and third parties may keep their own copies; pausing or deleting content on MeetMyAgent does not automatically remove those copies. Following an external contact, social or payment link takes you away from our platform. The destination provider receives in particular your IP address, technical browser data and information you enter there. It is responsible for its own processing. Displaying a link does not automatically connect your social media account to MeetMyAgent. For our own platform offers, we process payments as described in section 6. For third-party offers using external checkout, the link alone gives us neither card details nor confirmation that the seller received payment. For QR links, we count visits and certain actions as daily totals for each QR code, such as chats started, requests and contact downloads. These counters do not contain individual visitor profiles. Visits still involve technical connection data as described in section 9. Publication is based on Article 6(1)(b) GDPR to provide the profile and offer page you request. Technical operation and aggregate usage counts rely on Article 6(1)(f) GDPR, our interest in operating the service and measuring use of the QR links provided.
12. Profile import from your own sources
You may give your own AI selected profile text, links or posts to prepare an import proposal. MeetMyAgent does not fetch social profiles or call a language model. The private proposal records the sources and comparison with your current profile. Only your explicit approval applies that reviewed revision. Source text is deleted on approval or rejection; proposals expire after 30 days. Published profile links are public and also appear in structured data and the Agent Card.
13. Optional Telegram notifications
When you explicitly connect Telegram, we store your chat ID, event choices and consent. Telegram receives generic notices and a console link, without customer messages or contact details. Telegram is an independent provider outside the EEA; processing outside the EU is possible. The basis is consent under GDPR Article 6(1)(a). Revoke through the console or /stop: the chat association and queued notices are removed. Delete messages already stored in Telegram there. Telegram privacy: https://telegram.org/privacy.
14. Retention and required information
Account data and published content are processed for the duration of the requested use. Contract, payment and cancellation data may be needed beyond that to meet statutory retention duties and demonstrate claims and proper handling. Relevant criteria are the applicable legal duty, outstanding billing and specific disputes; this does not permit keeping data for unspecified future purposes. For checkout transactions, we also store history and technical identifiers to prevent duplicate execution. Expiring or cancelling checkout does not simultaneously delete this evidence. For authorisation and security records, relevant criteria include whether a connection remains active and whether the information is needed to investigate access or a transaction. No uniform automatic deletion period is promised for these records. You can request access and, where legal conditions are met, erasure at hello@meetmyagent.io. Chat conversations, archived requests, newsletter registrations and cancellation declarations follow the periods stated in their respective sections. Deletion from MeetMyAgent as described there does not determine a recipient's own retention, such as that of a connected AI service or payment provider. Without the information required for an account, payment or requested contact, we cannot provide the relevant function. You choose public profile information and connections to other AI services. We do not use the data described here for a solely automated decision producing legal or similarly significant effects within Article 22 GDPR; technical access and payment checks execute and protect your instructions.
15. Earlier features and content reports
Content from earlier, disabled features such as listings, board requests and the concierge is no longer publicly displayed. Any remaining personal data is subject to your rights in section 3 and the storage limits in section 12. If you report illegal content or challenge a restriction, we process your contact information, the relevant content, your explanation and the handling of the case. This is used for review, necessary responses and evidence of our measures. The legal basis is Article 6(1)(c) GDPR where statutory duties apply and otherwise Article 6(1)(f) GDPR, our interest in enforcing lawful terms and protecting affected people. Information may be shared with affected sellers, authorised bodies or authorities where needed to resolve the matter; reporters' identities are not routinely published.
16. Changes
We may update this privacy policy to reflect changes to the platform or legal requirements. The current version is always available on this page.