Privacy Policy

How MEKA handles information when you browse the website, run a limited preview, or use the tool workspaces.

Last updated October 21, 2026

Scope

This policy explains how MEKA handles information on meka.im, including the public catalog, documentation, recorded examples, status pages, tool workspaces, and limited live previews. MEKA is the service brand used on this website.

Actors listed on meka.im are hosted and run on Apify. MEKA is the creator of those Actors and may process Actor inputs and outputs as needed to provide their features and within the permissions you grant. Apify separately provides platform accounts, authentication, billing, and hosted storage; its privacy policy and the settings of the relevant Actor govern those platform services.

Website visits and live previews

When you browse the site, our hosting and security providers process request metadata needed to deliver pages, protect the service, and prevent abuse. This can include your IP address, browser headers, timestamps, the requested URL, and similar connection details. Cloudflare provides hosting, network protection, rate limiting, and Turnstile verification. Live previews are rate-limited by IP, and the Turnstile token and IP address are sent to Cloudflare for verification.

Editing fields, viewing recorded examples, or generating request code does not start a live collection run. If you select Run, the product you chose, target, domain, URL or query, validation token, and related inputs are sent to the MEKA preview service and the execution or data services needed to return a limited result. Preview availability, input limits, and result limits can change. Preview requests that fail or are rejected may still be processed for validation, rate limiting, and abuse prevention.

The website preview does not ask for your Apify token. Do not enter API keys, passwords, session cookies, or other sensitive information that should not be public. Direct calls to an Actor on Apify use your own token and account.

Tool history and shared URLs

Tool workspaces store a recent run history in window.sessionStorage, with a maximum of eight entries and a 1.5 MB limit. This history can contain target drafts and completed results returned by a live preview. It is local to the browser tab session and is not synchronized to a MEKA account.

You can clear this history with Clear history in the relevant tool or by clearing site data in your browser. Tab sessions and browser session restore can affect how long the data remains. Clearing browser history does not delete files you downloaded, text you copied, or data held by a service provider.

Some query parameters and share URLs contain a target. Sharing such a link can reveal that target to the recipient, to browser history, or to website request logs. Copy and Download actions write to your clipboard or a file on your device; you are responsible for keeping those copies.

Recorded examples and source links

Recorded examples are historical snapshots from public sources and keep their source and original date where available. They are not live results for your input and are not guaranteed to be accurate, current, or complete. Public pages can still contain personal information.

When you open a source link or view rendered source media, third parties may receive a network request and handle information under their own policies.

Cookies, security and service providers

Security components may use cookies or similar technologies to maintain sessions, provide the service, and prevent abuse. The specific cookies and their retention periods depend on the services involved and their configurations.

Cloudflare, Apify, and other services involved in delivering a page, executing a preview, or hosting linked content process data under their own configurations and policies. Their logs and retention periods are governed by those policies. See the Cloudflare privacy policy and the Apify privacy policy.

How we use information

Website and preview information is used to deliver requested pages and results, verify requests, enforce limits, maintain service reliability, investigate abuse, and communicate about a request when needed. MEKA does not offer user accounts, API key issuance, top-ups, credits, or checkout on meka.im.

MEKA processes preview inputs and, as Actor Creator, Actor inputs and outputs to provide the requested features and within granted permissions. Apify account management and Dataset storage or export are handled through Apify. Review the relevant Actor and Apify account settings before submitting data there.

Retention and your choices

Request metadata and service logs are retained according to the configurations and policies of the providers involved in delivering the site or a preview. A single fixed retention period cannot be stated for every provider.

Tool history remains in the browser session as described above and can be cleared through the tool or browser controls. You may choose not to submit a live preview; recorded examples and request contracts are available without starting a collection run.

Your rights and contact

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, or objection regarding personal information. Include only the minimum non-sensitive details needed to identify the page, Actor, or request. Do not post tokens, full records, or personal data in a public issue.

To contact MEKA about this website or a preview, open the MEKA Apify profile, select the relevant Actor, and use its Issues or support entry. The Similarweb Actor's public Issues page is one example. Apify account or platform privacy matters should go through the official contact channel in Apify's privacy policy, separately from a MEKA website request.

Changes to this policy

MEKA may update this policy as the website, providers, or legal requirements change. The Last updated date records the current version. If a change materially affects how information is handled, the updated policy will be published on this page.