Skip to content
DexWP

LAST UPDATED OCTOBER 5, 2026

Privacy Policy

Extracense Labs, the US company behind DexWP, uses your information to provide and improve the service. This policy explains what we collect and your choices.

Information we collect

We collect the account and contact information you provide, your subscription and usage records, and information needed to connect the sites and services you authorize. We also process your conversations, uploaded files, site content, preferences and the results of work performed through DexWP.

When you use the service, we may collect technical information such as your browser, device, network address and error reports to operate the service and help prevent abuse.

How we use your information

We use this information to manage your account, carry out your requests, process payments, provide support, send service messages and maintain the reliability and security of DexWP. Optional analytics help us understand which pages and features people use.

Connected social accounts

When you connect YouTube, Instagram or another supported social account, DexWP stores its account or channel identifier, display name, granted permissions and encrypted authorization tokens. We use these details to show your publishing destination, renew authorized access and publish content you approve. Delivery records contain published post identifiers, links, upload status and errors.

DexWP uses YouTube API Services. With your consent, we read your channel identifier and display name, upload your selected video with the title, description and visibility you approve, and check its upload status. We send your video and these publishing details to YouTube when you publish or your approved schedule runs. See the Google Privacy Policy.

Google and YouTube data is used to provide the connected features you request. We do not sell this data, use it for advertising or use it to train AI models. Your channel display name and connection status may be included in the context sent to an AI provider when you ask Dex to help with social publishing. Authorization tokens are never included in that context. Content you supply or generate in DexWP is processed separately to create your videos, slideshows and captions.

You can disconnect an account in Publishing → Social content → Social accounts. For YouTube, this stops further publishing through that connection, requests revocation from Google and removes the stored channel details and YouTube delivery records. It also removes the connection from automations and returns them to review mode. Videos already on YouTube and your original DexWP files and drafts remain available in their respective services.

If Google is temporarily unavailable, DexWP disables the connection immediately and retains an encrypted token only to retry revocation, for no more than seven days. The account panel shows when revocation is pending or needs your help. You can also remove DexWP from your Google account’s third-party connections. We check connected YouTube authorizations daily and remove stored account data when revocation is detected. Channel details are refreshed during those checks; if we cannot verify continuing access, we remove them within 30 days. Completed YouTube delivery records are deleted after 30 days.

For other supported social platforms, disconnecting removes stored tokens and pauses scheduled deliveries. You can revoke access through the relevant platform’s app permissions. To request deletion of connected-account data, email [email protected] from your DexWP account email and identify the connection. We delete requested YouTube data as soon as possible and within seven days. You can request deletion of your entire DexWP account in Settings; this also starts YouTube revocation and deletion. Copies already published to social platforms remain there and can be managed on those platforms.

The video and subtitle download buttons in DexWP provide the original files generated or uploaded in DexWP. They do not download videos or audio from YouTube.

Service providers

We use service providers for hosting, AI processing, payments, email and related operations. We share information with them as needed to provide those functions. Your instructions and relevant content may be processed by AI providers to complete the work you request.

Our hosting and database providers process connected-account records on our behalf to operate DexWP. Stored authorization tokens are encrypted. Authorized personnel may access account information when needed to provide support, maintain the service or investigate security issues. Social platforms receive the content and publishing details you approve; AI providers receive relevant instructions and content for the work you request, including the limited publishing context described above. We do not share Google authorization tokens with AI, payment, email or analytics providers.

Stripe processes payments; we do not store full payment card numbers. Resend delivers account and service emails. These providers may process information in the United States or other countries where they operate.

We may also disclose information when required by law, to protect rights and safety, or as part of a business transfer subject to appropriate protections.

Cookies and analytics

Essential cookies support functions such as signing in. With your permission, we use Google Analytics to measure visits to our website, blog and dashboard pages. It processes cookie identifiers, browser and device information, and page activity. Dashboard page views use generic page names. We do not send conversation content, connected-site addresses, account IDs or page query parameters to Google Analytics.

You can accept or reject optional cookies and change your choice at any time using . Declining analytics does not prevent you from using DexWP. Your browser also provides cookie controls. Learn how Google uses information from sites that use its services.

How we protect sensitive data

We protect the personal and sensitive information DexWP processes, including Google and YouTube account data, channel details, authorization tokens and content you submit for publishing, through the following measures:

  • Encryption in transit. DexWP uses HTTPS/TLS to protect information sent between your browser and our service, and between our service and Google, YouTube and other connected social-platform APIs.
  • Encrypted authorization tokens. We encrypt stored social-account access and refresh tokens using AES-256-GCM. Tokens are kept on the server and excluded from customer-facing account responses.
  • Account access controls. Access to private account information requires authentication. Ownership and permission checks restrict access to connected accounts, content and publishing actions. Administrative functions require separate authorization.
  • Password and diagnostic protections. If you create a DexWP password, we store a salted password hash rather than the password itself. We use request limits to reduce abuse and filters designed to remove credentials and other sensitive values from diagnostic logs.

These measures reduce the risk of unauthorized access, disclosure or alteration. No online service can guarantee absolute security.

Data retention

We retain information as needed to provide the service, meet legal and accounting obligations, resolve disputes and prevent abuse. The connected-account section above explains how to disconnect accounts and request deletion of their stored data.

Your choices

You can update your account details, disconnect sites and request account deletion in Settings. Content already published to WordPress remains on your site. Some transaction records may need to be retained for legal or accounting reasons.

Depending on where you live, you may have rights to access, correct, delete or obtain a copy of your personal information, or object to certain uses. Contact us to make a request. We may need to verify your identity before fulfilling it.

Contact us

For privacy questions or requests, email [email protected]. DexWP is intended for adults and is not directed at children under 18. If we materially change this policy, we will update this page and provide additional notice where required.

Read our Terms of Service.