Privacy Policy

1. What personal data we collect

We may collect the following categories of data.

Account data

• name
• email address
• company name
• login credentials or authentication identifiers
• account settings
• plan and subscription details

Billing data

• billing contact details
• payment status
• invoices
• tax information
• transaction metadata

Payment card details are typically processed by our payment provider and not stored directly by us.

Support and contact data

• messages you send us
• support requests
• abuse reports
• sales inquiries
• contact form submissions

API and usage data

• API key identifiers
• request timestamps
• usage volume
• response status
• error logs
• target domains or URLs submitted to the API
• rendering/routing parameters
• IP address
• user agent
• account activity
• rate-limit and abuse-prevention signals

Website and analytics data

• pages visited
• referral source
• device/browser information
• approximate location
• cookies or similar technologies
• interaction events

2. How we use personal data

We use personal data to:

• provide and operate UnblockingAPI
• create and manage accounts
• authenticate users and API keys
• process payments and invoices
• provide support
• respond to contact, sales, legal and abuse inquiries
• monitor usage and enforce rate limits
• detect, prevent and investigate abuse
• protect our service and third parties
• debug errors and improve reliability
• improve the website, product and documentation
• comply with legal obligations
• communicate service updates, security notices and billing information
• send marketing communications where permitted

3. Legal bases for processing

If you are in the EU/EEA, UK or another region with similar data protection rules, our legal bases may include:

Contract

We process data necessary to provide the service, manage your account, process billing and deliver support.

Legitimate interests

We process data to operate, secure, improve and protect the service, prevent abuse, understand product usage and communicate with users.

Consent

We may rely on consent for certain cookies, analytics or marketing communications where required.

Legal obligation

We may process data to comply with tax, accounting, legal, regulatory or valid legal process requirements.

4. API logs and target URLs

Because UnblockingAPI is an API service, we may process technical logs related to API requests.

These logs may include target URLs, domains, timestamps, status codes, account identifiers, request parameters and error information.

We use API logs to:

• provide the service
• calculate usage
• troubleshoot issues
• improve reliability
• enforce rate limits
• prevent abuse
• investigate security or policy violations
• respond to legal or abuse reports

Customers should not submit sensitive personal data, secrets, passwords, private tokens or unauthorized content to UnblockingAPI.

5. MCP server and AI assistants

You can connect an AI assistant (such as Claude, Cursor or another app that supports the Model Context Protocol) to UnblockingAPI through our hosted MCP server at mcp.unblockingapi.com. This section explains what that connection shares with us.

What we receive

We receive only what the assistant sends to the MCP server: the tools it calls and their arguments, such as the URL to fetch, options like select or template, and search terms for templates. We do not receive or store your conversation, prompts, chat history or files. The assistant decides what goes into a tool call, so the guidance in section 4 applies: don't ask it to send personal data or secrets to UnblockingAPI.

Your conversation itself is handled by the provider of your AI assistant under its own privacy policy.

What the MCP server keeps

• Its own log records, for each request, what kind of request it was (for example which tool was called), the response status and how long it took. It does not log tool arguments, page contents, API keys or access tokens.
• A page fetched with unblock_fetch is kept in the server's memory for up to 10 minutes, so the assistant can read it again (for example a different part of it) without a new request or credit. Only your account can read that copy, and it is never written to disk. After 10 minutes it is no longer used, and it is removed from memory as newer pages take its place or when the server restarts.
• unblock_fetch makes an ordinary API request with your account, so it uses credits and appears in your request logs like any other API request (section 4). Those logs are kept as described in section 10. Looking up templates and reading build guides do not use credits and are not recorded in your request logs.

Signing in and disconnecting

• When you connect with OAuth, you sign in on app.unblockingapi.com and the assistant receives an access token for your account, which expires after two hours and can be renewed while the connection is active. The assistant never receives your password or your API key: the MCP server looks up your key on our side.
• You can disconnect an assistant at any time under Connected apps in your account Settings. Disconnecting revokes its tokens, and it stops working within a minute.
• If you connect with an API key instead of OAuth, the key is stored in the assistant's own configuration, under that app's control. Connected apps in Settings does not list these connections; remove the key from the app to end its access.

Running it yourself

If you run the open-source MCP server on your own computer, it runs there and calls our API directly with your key. We receive only those API requests, as described in section 4.

6. Cookies and analytics

We use essential cookies to operate our website and keep it secure. We also use Google Analytics and Google Ads to understand how unblockingapi.com, the editor (editor.unblockingapi.com) and the app (app.unblockingapi.com) are used and to measure which of our ads bring people to us, and Hotjar to see how pages are used. Your choice in the cookie banner applies to all three, and is stored in a cookie so we do not ask again.

If you are in the European Economic Area, the United Kingdom or Switzerland, no analytics or advertising cookies are set until you accept them. Until then Google's tag only sends cookieless signals (such as the page visited), which Google uses to estimate usage in aggregate. Elsewhere, Google Analytics and Google Ads measurement are on unless you choose Reject. Hotjar only loads after you accept, wherever you are.

When you sign up, sign in, call the API for the first time, publish a template or make a purchase, our servers report that event to Google Analytics together with your Google Analytics identifier, so we can tell which ads lead to sign-ups and purchases. Where you have consented (or, outside the regions above, have not opted out), we also send a hashed (SHA-256) form of your email address, which Google uses to match the event to its own records ("enhanced conversions"); Google does not receive the email address itself. We also remember which campaign or website first brought you to us (for example the ad's tracking parameters) and store it with your account.

You can change your choice at any time by clearing your browser's site data for unblockingapi.com, which resets it and shows the banner again.

7. Sharing personal data

We may share personal data with:

• hosting providers
• payment processors
• analytics providers
• customer support tools
• email and communication providers
• security and abuse-prevention providers
• professional advisors
• legal, regulatory or government authorities where required
• business successors in connection with a merger, acquisition or sale

We do not sell personal data.

8. Subprocessors

We may use third-party providers to help deliver UnblockingAPI.

A current list of subprocessors is available on request - contact us.

9. International transfers

We may process and store data in countries outside your country of residence.

Where required, we use appropriate safeguards for international transfers, such as standard contractual clauses or other lawful transfer mechanisms.

10. Data retention

We keep personal data only as long as necessary for the purposes described in this Privacy Policy.

Retention periods may depend on:

• account status
• billing and tax requirements
• security needs
• abuse-prevention needs
• support history
• legal obligations
• dispute resolution

Request logs (the URL, parameters, status and timing of each API request) are kept for the log retention period of your plan: 7 days on Pay as you Go, 30 days on Scout, 90 days on Builder and 365 days on Growth. A daily job deletes older entries. On Enterprise plans request logs are not deleted automatically.

Other technical logs may be retained for a limited period for security, debugging, abuse prevention and service reliability.

We may anonymize or aggregate data so it no longer identifies individuals.

11. Security

We use reasonable technical and organizational measures to protect personal data.

These may include access controls, encryption, logging, monitoring, backups and security review processes.

No system is completely secure, and we cannot guarantee absolute security.

12. Your rights

Depending on your location, you may have rights to:

• access your personal data
• correct inaccurate data
• delete your data
• restrict processing
• object to processing
• request data portability
• withdraw consent
• complain to a data protection authority

We may need to verify your identity before responding to a rights request.

13. Marketing communications

You can unsubscribe from marketing emails at any time using the unsubscribe link.

We may still send transactional or service-related messages, such as billing, security, account or API notices.

14. Children

UnblockingAPI is not intended for children.

You may not use the service if you are under the age required to enter into a binding contract in your jurisdiction.

15. Customer responsibility

Customers are responsible for ensuring that their use of UnblockingAPI complies with applicable privacy and data protection laws.

If you use UnblockingAPI to fetch, process or store personal data, you are responsible for determining your legal basis, providing required notices, honoring rights requests and complying with applicable law.

16. Changes to this Privacy Policy

We may update this Privacy Policy from time to time.

If we make material changes, we will update the "Last updated" date and may notify users where appropriate.

17. Contact

WK Operations Ltd

VAT: MT27822437

Tax number: 970564313

For privacy inquiries: [email protected]

For abuse reports: [email protected]