Privacy at PEVENDE
Information about platform data and the connections each company chooses to use.
Version: 2026-10-08 · 1.0 ·
Who operates the service
DADOO CAPITAL LLC operates PEVENDE. Each customer company decides which customer data to add and why; it must inform those people and have the appropriate authorization or basis. Responsibilities for account data and customer data are reviewed according to the relationship and contracted service.
Data that may be processed
Depending on the enabled feature and provided data, this may include phone numbers, WhatsApp identifiers, names and profile photos if available, messages, contact and CRM records, account information and technical session, connection, security and operational metadata. Names or photos are not guaranteed to be available, nor is information about how another person saved a contact. Language and theme preferences are remembered in the browser.
Purposes
To organize contacts and conversations, collaborate within each company, follow up on sales, manage access and security and run configured automations. If a company enables a Claude agent, content needed for that feature may be sent to Anthropic. This description does not state that AI is active or already processing real conversations.
Connections and providers
Application data is processed on operator-controlled servers. The official connection, when configured, uses Meta Cloud API. The QR connection uses WAHA, an unofficial experimental integration that accesses data made available by the phone and linked session; interruptions or account restrictions may occur. Anthropic is involved only when the relevant AI feature is enabled. Account email may use the WEEM relay and its configured provider. Each connection determines which data its provider needs; configuration does not imply Meta approval or a compliance guarantee.
Retention and beta limits
The beta has no uniform retention period or automatic deletion of accounts, messages, CRM data or backups. Archiving a contact does not erase its data. Expiry of temporary technical data does not erase conversation history or backups. Requests require reviewing the affected categories, company responsibilities, security needs and applicable obligations; complete or immediate erasure across all systems or providers is not guaranteed.
Security and minimization
Application access is restricted by company and permissions. We aim to use only necessary data and restrict access to credentials and operational records. No measure removes every risk. Avoid adding sensitive information that the service does not need, and do not send secrets through the request channel.
Questions and rights
You can contact the privacy channel to request information, access, correction, deletion, objection or a review of how your data is used. Account export and closure are not automatic beta actions. Each request is manually reviewed with reasonable identity and authority verification and may require coordination with the company that added the data. The deletion instructions explain the minimum information to send; this page sets no response deadline and does not replace case review.