Workspace isolation
Each workspace is intended to access only its own users, numbers, wallet and communication records.
Explore Workspace isolationBuilt around clear access boundaries
One team. Controlled access.
The ChatZonic architecture separates workspace administration from everyday calling and messaging. The controls below describe the planned service, with verification still ahead.
Architecture targets
Designed for accountable workspaces.
These are planned controls, not a claim of completed certification or a security audit.
Role-based access
The workspace owner manages administrative actions while activated users use permitted communication features.
Explore Role-based accessServer-side credentials
Communications provider credentials are intended to remain in the backend and never appear in public page code.
Review data protectionActivation and operations
Controls to verify before launch.
Account services are not yet connected to this public website.
Verify the owner
Identity, business information and required domain checks precede account activation.
Review payment
Approval gates precede workspace provisioning and wallet-funded actions.
Record key actions
Administrative, payment and access records are intended to support investigation and accountability.
Apply retention
Customer data is intended to be retained for 10 days after closure, then permanently deleted, subject to the Privacy Policy and legally required records.
EVERYDAY ACCOUNT PROTECTION
Safer habits. Clear responsibilities.
Practical steps your team can take to protect access, customer information and payment decisions.
Protect your sign-in
Use a unique password, protect your registered email and sign in through the official ChatZonic link. Do not share an owner login among teammates. Use account recovery through the official flow when available.
Give each person their own access
The intended model gives the workspace owner administrative responsibilities and paid users their permitted communication tools. Review access when someone joins, changes role or leaves the team.
Protect customer conversations
Only include information needed for the business purpose. Keep private conversations, contact lists and account records out of public screenshots, shared links and unnecessary support messages.
Approve wallet actions carefully
Check the selected user, plan, number and charge before approving an action. Keep transaction references and compare available wallet balance with recorded payment status.
Use messaging with permission
Required sender approval and recipient consent are separate. Keep opt-in evidence, identify the sender and honor supported opt-out requests. Never move numbers to bypass an opt-out.
Verify contact and payment requests
Use links from the official website and approved payment instructions. Be cautious with unexpected requests to change payment details or reveal credentials. Never send an OTP, seed phrase or private key to support.
DATA & PRIVACY
Understand the information lifecycle.
The Privacy Policy is the detailed reference for collection, permitted processing and closure requests.
Information for the service
Account and workspace details, transaction references and communication records may be needed for the activated service. Use only the information needed for the business purpose and avoid unnecessary disclosure in support requests.
Read the Privacy Policy ↗Closure and retention
Customer data is intended to remain for 10 days after account closure, then be permanently deleted. Legally required records may have exceptions. The deletion process and treatment of provider records and backups require verification before live account use.
Review retention details ↗REPORT A CONCERN
A clear route when something feels wrong.
For account problems, start with the Support guides. For a security, privacy or misuse concern, prepare a concise private report.
Protect access
Notify the workspace owner and use official recovery or security options when available. Do not share the affected credentials.
Keep the reference
Record the time, affected account or URL and the observed behavior. Hide unrelated personal information in screenshots.
Report privately
Use published contact options. Do not post secrets or customer conversations publicly or continue testing against other users’ data.
Follow up clearly
Keep your report reference when one is provided. Include new relevant details without sending passwords, OTPs or private keys.
TRUST QUESTIONS, ANSWERED
Know the boundaries before you begin.
Clear answers about roles, privacy, verification and the service’s current status.
Who operates ChatZonic?
ChatZonic is a product of Zonic Corporation, registered in Texas, USA. Published legal policies explain the service rules and privacy approach. Legal notices and policy enquiries can be directed to admin@chatzonic.com.
Are all backend security controls already live?
No. This public website is live, while workspace access controls, payment approval, provider integration, mailbox routing and deletion jobs still require connection and verification. Architecture descriptions on this page explain intended behavior.
Is traffic to this website encrypted?
This public website is served over HTTPS. HTTPS protects traffic in transit to the website; it does not establish that storage encryption, end-to-end encryption or every future app control has been implemented.
Does ChatZonic have a security certification?
No completed SOC 2, ISO 27001 or independent security certification is claimed here. Any future audit or certification will need its scope and evidence before it is advertised.
Can other workspaces see my team’s records?
The architecture requires workspace isolation so that users, numbers, wallet actions and communication records belong to their own workspace. This boundary must be enforced and tested in the backend before live account use.
What is the workspace owner responsible for?
The owner should manage team access, review activation and renewal actions, protect administrative credentials and ensure the team follows consent and acceptable-use rules. Renewing the owner does not automatically renew all other users.
What happens to data after account closure?
The stated customer-data policy is retention for 10 days after closure followed by permanent deletion. Legally required records may be treated differently as explained in the Privacy Policy. Retention jobs and provider/back-up handling must be verified before live account use.
Is recipient consent shared for marketing?
Mobile information and messaging consent must not be shared with third parties or affiliates for their marketing or promotional purposes. Necessary service processing must follow the Privacy Policy and the actual service purpose.
Are calls recorded?
A launch recording feature has not been confirmed. This page does not claim that recording is enabled. Any future recording feature must clearly explain its availability, permissions, consent requirements and retention before use.
Does paying for a number approve business SMS?
No. A plan payment or assigned number does not replace required sender verification, campaign eligibility or recipient permission. Follow the applicable A2P or number-specific registration path.
How do I report suspicious activity or a vulnerability?
Use the published contact options and provide a short description, relevant URL or account reference, approximate time and safe reproduction steps when appropriate. Avoid exposing other users’ information or sending credentials. The online contact form will deliver requests after support setup is connected.
What should I include in a privacy request?
Identify the affected account and the request you want reviewed. Verification may be needed before account-related action. Do not send unrelated conversations, passwords or identity documents in an initial enquiry.
Current status
The public website uses HTTPS. Backend access controls, mailbox routing, retention jobs and provider integrations still need implementation and testing. No security certification or uptime guarantee is claimed.
A question about trust?
Review our policies and the current contact options.