1. Our approach
WizHub uses layered administrative and technical controls intended to reduce risk while preserving practical content workflows. Security controls are reviewed as the service, infrastructure, providers, and threat environment change.
This page is a transparency overview, not a guarantee that every risk can be eliminated. WizHub does not claim an ISO 27001, SOC 2, or similar certification unless that claim is expressly added here following completed certification.
2. Identity and access
- Staff access uses Microsoft identity integration and role-based permissions.
- Client access is scoped to the relevant workspace and role.
- Administrative and designer capabilities are separated.
- Sessions and authorization checks protect non-public routes and actions.
- Connected social actions require stored authorization granted through the provider's official OAuth flow.
3. Data and integration protection
- Traffic to the public service is protected with HTTPS in transit.
- Provider secrets, tokens, passwords, and session material are excluded from ordinary page output and redacted from operational logs.
- Workspace identifiers and access checks are used to maintain separation between clients.
- Social API access is limited by provider scopes, account authorization, and WizHub permissions.
- AI tasks use task-relevant context and are designed to avoid sending the entire client history where it is unnecessary.
Provider tokens are sensitive. WizHub continues to improve encryption, key management, token rotation, and production monitoring as the platform scales.
4. Upload and document security
Supported uploads are subject to size limits, filename handling, type and file-signature validation, quarantine controls, and malware scanning before supported document extraction. Unsupported or suspicious files may be rejected.
Extracted content remains subject to workspace authorization and the applicable retention policy.
5. Operational safeguards
- Operational events are logged with sensitive-field redaction.
- Background generation, image, intake, and publishing work uses tracked job states and errors.
- Backups support service recovery and expire through the defined retention cycle.
- Dependencies and provider API versions are reviewed and updated as needed.
- Security and integration failures can be investigated using actor, workspace, timing, status, and redacted error context.
6. Service providers
WizHub relies on established infrastructure, identity, email, AI, and social-platform providers. Their systems remain governed by their own security and privacy programs. We limit sharing to what is needed for the requested feature and the operation of the service.
7. Customer responsibilities
- Use unique credentials and protect access to your registered email and Microsoft account.
- Assign the least privilege necessary and remove users who no longer need access.
- Connect only social accounts you are authorized to manage.
- Do not upload unnecessary sensitive information, passwords, tokens, or secret keys.
- Review generated content and publishing actions before approval.
- Report suspicious activity promptly.
8. Responsible reporting
Report a suspected vulnerability or security incident to [email protected].
Include a clear description, affected URL or feature, date and time, and safe reproduction details. Do not access other users' data, disrupt the service, use social engineering, or publish the issue before we have had a reasonable opportunity to investigate.