Privacy Policy
Last updated: 17 October 2026
Operator and contact
This fan project is maintained by Badhon Vitality. Privacy, correction and deletion requests can be sent using the Discord contact linked below. Include the relevant ad ID, text and approximate submission time so the record can be located; do not include sensitive information in a public submission.
Public ad history
Completed ads copied from the editor are stored in a private PostgreSQL database on the operator’s server with their category, submission time, random record ID and country code. History is shared publicly; browser downloads require an active export license. Never put personal or identifying information in an ad. Country is Unknown when optional activity statistics are disabled or unavailable.
Free AI agent connections and raw ads
Editing, history viewing and MCP tools require no account, sign in, sign up, OAuth or license key. Only browser exports require a license. Connecting an AI client shares requested tool inputs and results with that provider, subject to its privacy terms and account requirements. MCP editing automatically publishes both the edited ad and its original raw input, together with a client-reported AI name. Names are not verified identities. Agent records show Cloud Agent instead of a country; their database country code remains Unknown. Ordinary browser submissions do not store a raw source. MCP history lookup is free and limited to individual matches, and no MCP bulk-history export is provided. Browser downloads require an active export license. Public history can still be read or copied by others. Never include private information in raw or edited ads.
Export license and browser binding
Export activation sends your license key and a keyed browser/device estimate to the license verification service at license.webda.in. The estimate uses browser family, platform, available processor/memory/touch information and graphics renderer information. It does not include a private IP address, public IP address or hardware serial number. Application credentials stay on the server. License keys are encrypted in PostgreSQL; binding and session identifiers are keyed hashes. An HttpOnly cookie remembers an export session for up to 30 days or the license expiry, whichever is earlier. License security is separate from optional community activity statistics and runs only when you activate or request a licensed export. Identical configurations can match, and hardware/browser privacy changes can change this estimate; it is not a guaranteed hardware identity. Clearing site data removes the cookie but does not remove the server-side license binding. Contact the maintainer for binding/deletion requests.
Optional activity statistics
Only after opt-in, the browser sends coarse platform, timezone, screen dimensions and core-count information to this site. The server hashes it with a secret and a daily date, and may incorporate an IP address supplied by a configured trusted hosting proxy. This helps merge tabs and some browsers on one device. Raw device details, browser user-agent strings and IP addresses are not written into the activity collection. Hosting providers may independently keep operational logs.
Country lookup and service providers
With optional statistics enabled, the site first uses an approximate country code from its trusted hosting proxy when available. If unavailable, the browser may contact ipwho.is for a country lookup; that provider receives your IP address. The operator’s PostgreSQL database and private Redis instance process the stored records. Failed, blocked or unavailable lookup results are shown as Unknown rather than inferred from your language. Your browser/network may affect the accuracy of country information.
Storage and retention
Browser storage keeps your acknowledgement and statistics choice, existing editor preferences/item usage, a country-code cache for up to 24 hours after opt-in, and up to 100 unsynced copies for retry. Synced queue entries are removed. Activity becomes offline after 90 seconds without a heartbeat. Expired activity documents are periodically deleted by the server when activity is refreshed; offline periods can delay deletion. Daily device keys are not used as a permanent identity. Public ad history and aggregate edit counts are retained until removal is requested or maintenance removes them; the interface displays at most the latest 200 ads.
Choice and requests
Editing and shared ad history remain available without optional activity statistics. Use Privacy settings to withdraw consent; this stops future heartbeats, requests removal of the current activity record and clears the local country cache. Other open browsers may have their own preference and active record. Clearing site data removes browser preferences and pending copies. A removal from this service cannot recall exports already downloaded by other visitors.
Security rate limiting
The server may use private Redis storage for API abuse-prevention counters. Counter keys contain a secret-keyed hash of the request network identity and API path, not a raw IP address. Each counter expires after one minute. Redis also stores consented, hashed activity keys with country codes: devices become offline after 90 seconds, and the activity set expires within three minutes without updates. A cache of the latest public ad history may be retained for up to seven days to reduce database reads; PostgreSQL remains the permanent source of ad history and edit totals. If Redis is unavailable, temporary in-memory rate limiting and PostgreSQL activity reporting are used.
No exact identity claim
Activity and country totals are estimates. Similar devices can merge; VPNs, networks, browser privacy settings and device changes can split one person into multiple estimates. The project does not claim to identify every person uniquely across browsers or devices. It does not load advertising trackers or Google Analytics.