Loading...
Security
Security is designed around workspace and portal boundaries.
OnloZap handles internal workspace users, client portal users, shared signing links, billing flows, and AI-assisted actions as distinct security contexts.
Workspace isolation
Workspace data is scoped by organization context, user access, and permission checks before sensitive records are read or changed.
- Workspace membership is separate from client portal access.
- Team permissions should be configured before inviting users.
Client portal boundary
Portal users should only see eligible client records such as quotes, invoices, projects, files, messages, and signing tasks.
- Portal sessions are not internal workspace sessions.
- Client visibility should be controlled by portal eligibility and linked client context.
Authentication
Authentication relies on server-side session verification, secure cookie handling, and host-aware public route behavior.
- Public marketing pages should not force workspace auth.
- Workspace routes should fail closed when access cannot be verified.
Documents and files
OnloSign, secure files, signature evidence, and document links are treated as sensitive workflow surfaces.
- Signing links and portal routes should remain scoped to the intended recipient.
- Document activity should preserve enough context for audit and support.
Billing safety
Subscription checkout and payment details are handled through Stripe. OnloZap stores only the references needed to reconcile billing state.
- Do not send full card details to support.
- Checkout configuration should be verified before relying on a plan in production.
Security reporting
If you believe you found a security issue, send a concise report with impact, reproduction steps, and affected routes.
- Email support@onlozap.com.
- Avoid public disclosure until the issue can be investigated.
AI trust
Zapling is useful because it is governed.
AI features are designed to assist workspace users through summaries, drafts, and recommendations without bypassing sensitive permissions or review steps.
Review before execution
Generated content and recommended actions should be reviewed by a human before they affect client-facing records.
Workspace-only context
Zapling belongs to internal workspace workflows and should not become an uncontrolled client-portal tool.
Moderation and credits
AI requests can be checked for policy, usage, and feature eligibility before work is performed.
Auditability
Tool-backed AI actions should preserve enough detail to understand what was proposed and what was approved.
Next step
Found something concerning?
Send the affected route, expected access, actual access, reproduction steps, and any non-sensitive screenshots.