Security at Portavi

Portavi requests read-only scopes from every tool it connects to. It cannot create, modify, or delete anything in your project management or communication tools — the OAuth grants themselves do not permit it.

When Portavi scans a mapped channel for delivery signals, message bodies are processed in memory only. What is stored is signal metadata: the signal type (blocker, delay, urgency, issue, progress), a timestamp, the sender name, the channel, and a deep link to the original message.

Following a deep link is subject to the reader’s own permissions in the source tool, so Portavi never becomes a way to read messages someone could not otherwise access.

Every workspace-scoped table in our database enforces Row-Level Security. Access is gated through workspace membership, so data from one customer workspace is never readable from another — the isolation is enforced by the database itself, not only by application code.

Integration OAuth tokens are stored server-side only and are never returned to the browser. A public-columns allowlist enforces that token fields cannot be exposed through any API response.

• Cloudflare Turnstile bot protection on password sign-up and sign-in
• Rate limiting on all API endpoints
• TLS encryption for all data in transit
• Encrypted database backups at rest

Account deletion is self-service and complete: it removes your user record, workspace memberships, and authentication identity. No support ticket required. Notifications are automatically deleted after 30 days, and signal metadata is deleted with its project or workspace.

If you believe you have found a security issue in Portavi, email support@portavipmo.com. We read every report and will respond.