SECURITY
Security boundaries are part of the product architecture.
EchoVerse AI separates the public website, staff administration, customer workspaces, private configuration and provider credentials so sensitive operations do not need to live in the public browser.
Private configuration
Database credentials, application encryption keys, SMTP secrets, OAuth secrets and provider tokens belong outside the public webroot.
Workspace isolation
Customer data and actions should remain scoped to an authorized workspace and membership.
Role-based access
Administrative and workspace capabilities are controlled through roles and permissions rather than one unrestricted account model.
CSRF defenses
State-changing web forms use request-verification controls to reduce cross-site request-forgery risk.
Password protection
Passwords are verified using secure password hashing rather than stored as recoverable plaintext.
Credential protection
Connection secrets and provider authorization data should be stored and handled in private application infrastructure, not exposed in public pages or support messages.
Audit logging
Important administrative changes and security-relevant actions can be recorded for investigation and accountability.
Provider separation
Google, Meta, TikTok, payment and other provider credentials remain distinct from WordPress and the public customer browser.
Emergency controls
Automation can be paused or disabled when a workflow needs review.
Least disclosure
Public diagnostics should reveal only what is needed and should never expose secrets.
CUSTOMER SECURITY
Protect access to your own workspace and connected providers.
Use a unique password, limit team membership to people who need access, review connected accounts and revoke provider access you no longer use. Never send passwords, OAuth tokens or private keys in screenshots or support messages.
01Verify the domain
Customer login should lead to app.echoverse-ai.com over HTTPS.
02Protect provider credentials
Never publish tokens, secrets or private connection data in public repositories, screenshots or support posts.
03Review permissions
Grant only the workspace and provider access required for the job.
04Report concerns
Contact admin@echoverse-ai.com if you believe an EchoVerse AI account or connected credential is compromised.
Security reporting
If you believe you discovered a security issue affecting EchoVerse AI, avoid accessing data that does not belong to you and avoid destructive testing. Send a concise report to admin@echoverse-ai.com with the affected URL, reproduction steps and potential impact.
GET ANSWERS FASTER
Most questions can be resolved without opening a support request.
Use the Help Center for troubleshooting, Documentation for workflow guidance, Examples to understand output formats, and Pricing for current plan limits and billing information.