Privacy notice

Data processed

No account is required. A request may contain a request body with a public handle, topic, product name, public URL, time window, language, client request ID, and Agent preferences. Evidexa also processes an Evidexa request ID, Tool and route, timestamps, response status, bounded performance and Credit metrics, and cache or retry state.

Paid access is currently paused before payment processing. If x402 is re-enabled, the service processes a payment proof only long enough to verify and settle it. Application-controlled storage and custom logs do not retain the proof, request headers, private keys, seed phrases, Provider credentials, raw request body, full query, payer address, or settlement receipt.

Sources and service providers

Xquik receives the bounded public-data request needed to retrieve current Social/X signals only when paid execution is enabled. Cloudflare delivers the Worker, short-lived application state, custom logs, and role-based email routing. The configured x402 facilitator is retained for the inactive payment contract and is not invoked by paused paid routes. Email providers process messages that you choose to send. These services may process network, transaction, support, or operational metadata under their own terms.

Purposes

Evidexa processes data to validate requests, apply safety rules, retrieve public signals when execution is enabled, create derived intelligence, prevent duplicate charges, settle approved payments when available, detect abuse and operational failures, answer support or removal requests, and maintain service security. Evidexa does not sell application request data or share it for targeted advertising.

Application-controlled retention

Production does not persist raw X payloads by default and public results do not mirror raw post text. Derived result, synchronous retry, and async recovery lifetimes are bounded by Tool: up to 5 minutes for search_social, 15 minutes for topic_intelligence, and 30 minutes for user_intelligence and product_intelligence. Bounded operational samples normally cover 15 minutes. Custom logs follow the Cloudflare plan's configured retention. Support, security, refund, and removal correspondence is retained only as needed to handle the request, protect the service, and preserve necessary records.

Public blockchain records, including wallet addresses and transaction hashes, may remain publicly available and cannot be deleted by Evidexa. Source platforms and service providers control their own copies and retention.

Disclosure

Data is disclosed only to the service providers needed for delivery, to a client at its direction, to protect users or systems, or when required. Evidexa returns derived intelligence, public source identifiers and links, confidence, and uncertainty; it does not operate a raw social-data marketplace.

Access, correction, and removal

Send a privacy, access, correction, objection, or data-removal request to security@okmybot.com. Include enough information to identify the affected Evidexa request or public source, but do not send secrets. Evidexa may verify identity, wallet control, source authority, or other authorization before acting. Application cache and recovery state can be invalidated; Evidexa cannot alter a public blockchain or data independently controlled by an upstream source.

Security and children

Evidexa uses bounded inputs, access controls, encrypted secrets, sanitized logs, rate limits, and payment-replay guards. No system can guarantee complete security. The service is built for authorized Agents and professional workflows and is not directed to children. Analysis of minors for prohibited or high-impact purposes is not allowed.

Changes and contact

Material changes appear on this page with a new update date. Contact security@okmybot.com for privacy questions or requests.