Privacy Policy

Last updated: 22 October 2026

النسخة العربية

Changed in this version

This is the first version written for the Omani Personal Data Protection Law (Royal Decree 6/2022). Every place where we ask for your email, number or words now shows a notice and stores your consent (new section 5); the lawful bases are now consent, contract and legal obligation, and “legitimate interests” is removed because that law has no such basis; sections 3 and 8 now say that our team uses AI services outside Oman (Anthropic and OpenAI, United States), that our server is in Malaysia and that you consent to that transfer, and that text reaches DeepSeek (China) only if automated screening finds no obvious personal details in it, and the screening can miss some; the WhatsApp notice now asks you to reply AGREE (a plain “yes” is no longer taken as consent); each place that states a lawful basis now says whether it is consent or contract; your rights are listed in full and requests are answered within 45 days (it was 30); and the retention section lists each kind of record. Version 2026-10-22.3 also corrects the company’s registered Arabic name to the register’s spelling, names the company in full in the notices (TechMate, registered as the joint partnership, with its CR 1661879), and uses the Arabic brand name in the Arabic notices. Earlier versions: 9 October 2026 corrected the company’s name and legal form in section 1 (the controller and its CR 1661879 are unchanged), and 3 October 2026 changed where the service is hosted.

1. Who we are

HatchLoop and AgentBroker are products of TechMate (registered as «شركه رفيق التقنية تضامنية», a joint partnership), CR 1661879, registered in the Sultanate of Oman, Muscat. TechMate is the legal entity behind this site and the data controller for everything described below; HatchLoop is the name of the product, not a separate company.

This policy covers the website hatchloop.dev and the AgentBroker service at hatchloop.dev and api.hatchloop.dev: an MCP server and API that lets AI agents check and find businesses and, on the channels that are enabled, message and book with them. Contact for anything in this policy: hello@hatchloop.dev.

2. What we collect

When you visit hatchloop.dev or call the API.

  • Our web server keeps an access log of every request: time, IP address, the address requested (with session tokens and key parameters removed), user agent, response status and size. API key headers are replaced with a placeholder before anything is written.
  • We measure visits with Umami, which runs on our own server and not at an analytics company. It sets no cookies. It records the page address, referrer, page title, browser, operating system, device type, screen size, language and approximate location (country, region, city). Its database has no field for your IP address.
  • Every page asks our API whether you are signed in, which is a request to our server like any other. The only cookie we set is the sign-in session cookie (hl_portal, 30 days) after you sign in; your browser also remembers, in local storage, which credit package you chose while signing in.

When your agent calls a tool. For each call the usage log records:

  • the time, the tool name, the outcome and status, and how long it took;
  • the client name and version your software reports, and whether a key was used and its state;
  • the names of the arguments you sent, never their values, and a short one-way hash of the arguments;
  • a short one-way hash of your IP address, and your user agent.
  • The values you pass to lookup and screening tools (a company name, a person’s name, a place) are not written to the usage log and are not stored by the service. Tools that change state (sending a message, capturing a lead, booking, escalating) store a record of the operation, described under “Messaging” below.
  • A billing record of each charge: the tool, the amount, the status, the time and your key identifier.

Keys, sign-in and payments.

  • If you request a free key we store your email address (lower-cased), a verification token with an expiry (deleted once you use the link), and the key we issue to you.
  • Sign-in is by an emailed link; there are no passwords. We keep your email, your plan, your credit balance and the ledger of credits granted and spent.
  • Card payments are handled by Polar as merchant of record. We receive your email address, the order and the amount. We never see or store card numbers.

Forms and email.

  • The feedback form stores the note you type and your browser’s user agent. The waitlist forms store your email address, the page you used and an optional note. Neither is sent to anyone else. Each of these forms, and the free-key form, shows a consent notice with a box you tick before you can send; see section 5.
  • Email you send to hello@hatchloop.dev is received by our email-forwarding provider and delivered to a Gmail mailbox read by our team.

3. Lookup tools: where the text you send goes

  • screen_sanctions and the party screening inside map_trade_restriction compare the name with copies of the OFAC, EU and UK sanctions lists that we download from their publishers and hold on our server. The name is not sent to the publishers or to anyone else.
  • verify_company_record sends the company name (and country, if given) to the GLEIF LEI registry. For US public companies it downloads the SEC’s public company file and matches the name on our server.
  • lookup_us_contracts sends the company name to the USAspending.gov public API.
  • find_business sends the place text you give it (up to 200 characters), the search area and the business category to the public OpenStreetMap services (Nominatim for geocoding and the Overpass API for businesses), together with our server’s IP address. Treat that field as public and do not put a private person’s home address in it. Results are cached on our server for up to 7 days.
  • import_booking_url fetches the booking page address you give it, from our server.
  • The Retail Broker at hatchloop.dev/retail forwards a visitor’s product search to the public catalogue endpoints of the stores it searches.

The service itself does not send tool inputs or messages to an AI model provider. HatchLoop is, however, operated with the help of AI assistants, and the people and assistants who operate it can read the records described in this policy. Our team uses AI services located outside Oman, Anthropic and OpenAI in the United States, to help run the service, so personal data in those records may be processed there; see section 8. Text is sent to DeepSeek (China) only if automated screening finds no obvious personal details in it (such as email addresses, phone numbers and names on our private list); the screening can miss other personal details.

4. How we use it

To provide and bill the service, run the compliance gate (including opt-outs), prevent abuse and keep the service reliable. We do not sell personal data and we do not use message content for advertising. The legal bases we rely on are your consent (the waitlist, feedback and WhatsApp notices described in section 5, which you can withdraw at any time), contract (delivering the service you asked for, such as your free API key and your TechMate OS team account, which includes preventing abuse, keeping security logs and keeping the service reliable) and legal obligation (tax records and regulatory disclosures).

5. Your consent, and how we record it

Wherever we ask for your email address, phone number or words, we show a notice first and keep a record that you agreed. For each agreement we store the date and time, the version of the notice (currently 2026-10-22.3), the language you saw, how you agreed, and a fingerprint (SHA-256) of the exact text you were shown. The record holds a one-way hash of your email address or number, not the address or number itself, and no IP address. A change of wording gets a new version. If you withdraw consent, that is stored as a new record; the earlier one is not edited.

  • Waitlist forms. A box you tick before you can send, with the notice in English or Arabic. Without it the form is refused. Legal basis: consent.
  • Free API key. The same box on the key request form. Without it no key is requested. Legal basis: contract (issuing the key you asked for); the tick records that you were told.
  • Feedback form. The same box. The feedback itself is stored only after the consent record has been stored. Legal basis: consent.
  • WhatsApp replies. The notice is delivered in the conversation and you agree by replying AGREE; replying STOP opts out. Legal basis: consent. If you answer a booking request that we sent you, we keep your reply with that request on a different basis: contract (an Omani lawyer is to confirm).
  • TechMate OS team chat. Team members see the notice when they sign in and agree once for each version. Legal basis: contract (running your team account); the notice records that you were told.

6. Messaging

Messaging tools work on the channels enabled on the current deployment, which are WhatsApp and email. SMS and voice calling are not enabled, and nothing is sent to an SMS or voice provider. When your agent sends a message we process its content and the recipient’s identifier to deliver it and to run the compliance gate (TCPA, GDPR and CASL checks, consent and opt-out enforcement). Replying STOP on a channel, including WhatsApp, records an opt-out that blocks further messages to you on that channel.

What these tools store:

  • The compliance audit log keeps a SHA-256 hash of each recipient identifier, with the channel, the decision and the reason, and no plaintext identifier.
  • Other records hold identifiers in readable form: opt-outs (the recipient and the channel), leads your agent captures (name, phone, email, notes), conversation records (the numbers involved and the message text) and replies received on WhatsApp (sender number, profile name and text), which are kept so the requesting agent can read them.
  • Receipts of operations that change state, which can include the free text your agent supplied (for example a note passed to a human escalation).

7. Who else receives data

Providers we use to run the service.

  • Hostinger (Hostinger International Limited) rents us the virtual server that runs the website, the API, the database and its backups.
  • Vercel hosts the DNS records (the name servers) for hatchloop.dev. It does not serve the site or carry its traffic.
  • Resend sends our email: sign-in links, key verification, billing notices, and email sent through the messaging tools. It receives the recipient address and the message.
  • Polar is the merchant of record for card payments, and receives your email and order details.
  • Forward Email and Google (Gmail) receive and hold the email you send to our contact address.
  • Anthropic (United States) is an AI service our team uses to help run the service, including the TechMate OS team chat and the requirements features; text in those features can reach it.
  • OpenAI (United States) is an AI service our team uses in the same way, for the TechMate OS team chat and the requirements features.
  • DeepSeek (China) is an AI service our team uses for the TechMate OS team chat and the requirements features. Text is sent to DeepSeek (China) only if automated screening finds no obvious personal details in it (such as email addresses, phone numbers and names on our private list); the screening can miss other personal details.
  • Telegram receives internal purchase alerts for our team, in which the customer’s email address is masked. The Telegram Mini App page at hatchloop.dev/app loads a script from telegram.org.

Providers involved only in particular cases.

  • Meta (WhatsApp Business Platform) carries WhatsApp messages and receives the recipient’s number and the text. Meta’s own terms and privacy policy also apply to that channel.
  • Cal.com receives the attendee’s name, email address and notes when a booking is made.
  • Render runs only a redirect from our former address (smb-broker.onrender.com) to api.hatchloop.dev. A client that still uses the old address sends its first request there, so Render sees that request.

Public sources that receive the text you ask us to look up are listed in section 3: GLEIF, OpenStreetMap services, USAspending.gov and the stores searched by the Retail Broker.

Integrations that exist but are switched off and receive nothing: SMS (Twilio), voice calls (Vapi) and on-chain payments (Coinbase).

8. Where data is processed

The server is in Kuala Lumpur, Malaysia. We operate from Oman, and the database backups are also copied to a company computer. The providers in section 7 process data in their own locations, which include the United States and Europe.

AI service providers. Our team uses AI services outside Oman, Anthropic and OpenAI in the United States, to help run the service. Personal data you give us may therefore be processed there, and our server is in Malaysia. Sending personal data outside Oman is a transfer under Article 23 of the Personal Data Protection Law, and each consent notice asks for your agreement to it. Text is sent to DeepSeek (China) only if automated screening finds no obvious personal details in it (such as email addresses, phone numbers and names on our private list); the screening can miss other personal details. China is outside Oman, so that too is a transfer under Article 23; the screening is automatic and can miss a personal detail.

9. How long we keep it

We do not yet delete most records on a fixed schedule. The periods for them are being set; until they are, a record is kept for as long as it is needed for the purpose shown below, and we will publish the periods here when they are confirmed. The two periods that already exist are stated as they run today.

RecordsHow long
Web server access logsRotating files limited by size (20 MB a file, 10 files per site), which at current traffic is a matter of days. The server’s system journal keeps at most 7 days.
Database backupsWritten every 12 hours and kept for 30 days, on the server and on a company computer.
Waitlist entriesKept while needed to tell you the result. Period being set.
Free-key requests and accountsKept while the account exists. Period being set.
Feedback notesKept while needed to improve the service. Period being set.
WhatsApp replies and conversation recordsKept so the requesting agent can read them. Period being set. Opt-outs are kept indefinitely because that is what makes them enforceable.
TechMate OS team chatKept while the member’s account is active. Period being set.
Usage, billing and compliance audit recordsKept so that we can bill, prevent abuse and show what the compliance gate decided. Billing and tax records are kept as long as the law requires. Period being set.
Consent recordsKept as evidence that you were told and chose, including after you ask us to delete the other records. They hold a one-way hash, not your email address or number.

To have your records deleted, email hello@hatchloop.dev; we answer within 45 days. Billing and tax records can only be deleted where the law allows it.

10. Your rights and how to reach us

You may withdraw your consent at any time, ask for a copy of your data, ask us to correct it, ask us to delete it, and ask for it in a portable form. You may also ask for restriction of its use. Withdrawing consent does not undo what we did before you withdrew. We answer within 45 days. If you are not satisfied, you may complain to the Ministry of Transport, Communications and Information Technology of Oman, which supervises the Personal Data Protection Law; residents of the EU and UK may also complain to their own supervisory authority. We do not sell personal information, including for California residents.

Send requests to hello@hatchloop.dev. That address is also the contact for data protection questions.

11. Children

The service is for adults (see the Terms of Service) and is not directed at children. We do not knowingly collect data from them.

12. Changes

We will update this page when our practices change and adjust the date above. Material changes will be noted on this page.