Privacy Policy

Operator: Operator details pending confirmation, Jurisdiction pending confirmation. Contact: tartykov2012@gmail.com. This document describes the inspected implementation; it needs publisher approval before becoming effective.

Information processed

• Account email and password hashes; session, API-key and OAuth credential hashes; connection permissions and consent records.
• Tool inputs needed for procurement searches, collection jobs, private watches, document reading allowances, saved analyses and digests.
• Operational records such as tool name, account identifier, time, duration, outcome and usage counters. Rate limiting uses hashed network identifiers.
• Public procurement and company records, source URLs, downloaded public documents and extracted text. Published source records may contain names and business contact information.

How information is used

To authenticate requests, enforce account permissions and limits, collect and read public procurement evidence, maintain user-requested watches and saved results, and diagnose failures. The service is not designed to receive passwords or payment-card details through MCP tools.

Recipients and external services

Your selected AI client receives results of tools you use. Public-source searches send relevant query and request information to the source being consulted. This website does not load analytics. International subscriptions are processed by lava.top in USD when configured and approved. The configured provider processes payment details; MCP Bids retains checkout email, invoice/subscription identifiers, verified billing periods and reversal review records. lava.top acts as a payment agent under its own terms. Card details are not stored by MCP Bids. Procurement search metering stores a query fingerprint and short-lived session identifier, not the query text in that counter. Public checkout remains disabled pending merchant setup and policy approval.

Hosting providers, processor locations, any additional recipients and international-transfer arrangements still require confirmation.

Account boundaries

Public source records and prepared public documents form a shared index available to authorized service users. Jobs, watches, evidence packets, saved analyses and digests have account ownership checks. Do not submit confidential material expecting a private document repository.

Retention

OAuth access tokens expire after ten minutes; refresh-token families after at most thirty days. Authorization codes are short lived. Expiry or connection revocation does not itself delete account records, audit history, saved analyses, public documents or backups.

The publisher must set retention periods for accounts, queries/jobs, operational logs, public documents and backups, and a verified deletion-request timeline before launch. No automatic deletion schedule for these records is claimed here.

Your controls

Revoke OAuth connections and keys in your account; disable watches to stop future checks. For access, correction or deletion requests, contact tartykov2012@gmail.com. Account verification may be necessary. Revoke does not delete data already returned to your AI client; that client’s own controls apply.

Items pending approval

Effective date, lawful-processing grounds, legal contact details, retention and deletion timelines, processor inventory, applicable user rights and international-transfer disclosures.