privacy policy

service and data

dubd is an ai assistant for social network interactions and for requests to create real blockchain tokens. the current stage of each integration is disclosed to the user; a simulation does not represent the creation of a token.

we receive public account identifiers and names, the text of comments and mentions, comment and post ids, dates and processing states. where a messaging integration is enabled, we also process the content and identifiers of those conversations. we store request drafts, proposed replies and delivery records to preserve context and avoid duplicates. integration credentials are kept in protected storage, never on public pages.

on this website, signing in to collect keeps a short-lived session token in your browser tab only (it is cleared when the tab closes).

to enforce the daily limits for printing without signing in and for predictions, we read the ip address of each request and store only a keyed hash of it — never the address itself. the hash is used to count requests per day and to prevent abuse.

for predictions we read public data from polymarket (events, results, odds and the pictures it publishes); no personal data is sent to polymarket. for ai agents, we store the agent's name, the x account that asked for the key, and the key only as a hash — the key itself is shown once and not kept.

purposes and recipients

we use this data to identify the interaction, prepare ai replies, fulfil requests, verify permissions, record outcomes and investigate failures. the text needed for this may be processed by openai/codex. the infrastructure includes hostinger and openclaw; enabled integrations may use meta, ayrshare and telegram; sign-in uses privy, x, twitch, github and steam. predictions read public data from polymarket. providers may process data in other countries under their own terms. we do not claim that public comments, or data sent to third parties, remain private.

retention and rights

the current implementation keeps records in local databases for history, recovery and deduplication, with no automatic expiry routine configured. we do not promise a deletion deadline the system does not meet. requests for access, correction, revocation or deletion should be sent to @dubdfun on x (direct message); execution is manual and requires proportionate verification of ownership, without asking for passwords or keys. the final policy must define the periods and align the backup configuration.

disconnecting an account stops future access after revocation, but does not automatically erase earlier records. deletion requests cover the records under our control; content on social networks is also subject to those platforms' own controls. blockchain transactions that are eventually transmitted are public and cannot be erased by us.

controller and contact

the controller of dubd data is dubd dev, the administrator of the service. contact for privacy, exercise of rights and deletion requests: @dubdfun on x (direct message). no e-mail address is published yet. no company registration or legal entity is declared in this policy.