Security

Security designed around verification, least privilege and customer control.

VidPropel separates guidance from authority: support can help quickly, but sensitive changes stay inside authenticated, permission-checked workflows.

Protected account actions

Billing, campaign, privacy and security-sensitive changes require authenticated first-party workflows, permissions and explicit customer approval where applicable.

Payment boundaries

VidPropel does not ask customers to send full card numbers or CVVs through support. Payment entry stays with the hosted payment provider.

Google permissions

Ordinary Google sign-in is kept separate from creator-data permissions, and connected access is limited to the feature being used.

AI support safeguards

Support email is treated as untrusted input. The AI can explain, troubleshoot and guide, while sensitive account actions remain behind secure sign-in.

Auditable automation

State-changing automated decisions are recorded and protected actions fail closed when identity, provider state or evidence is ambiguous.

Responsible disclosure

Good-faith security reports are triaged without asking researchers to expose customer secrets or access data they do not own.

Report a vulnerability

Use the secure Help Center for responsible disclosure.

If you believe you found a security issue, send a concise description through the VidPropel Help Center. Do not include passwords, MFA codes, API keys, full payment-card details or unrelated personal data. Please avoid destructive testing, service disruption, social engineering, automated credential attacks or accessing data that is not yours.

Reports are reviewed on their technical merits. A report does not authorize access beyond your own account or ordinary public surfaces.