How PinBridge protects credentials, isolates workspaces, and keeps publishing predictable for production teams.
PinBridge is built as a multi-tenant publishing platform with security controls focused on credential safety, tenant isolation, and operational reliability.
API traffic is protected with HTTPS/TLS, and sensitive credentials are encrypted at rest with scoped access boundaries.
Authentication and authorization are enforced at the workspace boundary to keep account, board, asset, pin, schedule, and billing data separated.
API keys and OAuth-linked credentials are managed with rotation, revocation, and operational monitoring practices designed for production workflows.
Request and workflow status context supports troubleshooting, incident response, and internal compliance processes.
PinBridge enforces controlled publish throughput with queueing, pacing, retries, and status visibility so teams can operate Pinterest automations with predictable behavior.
SOC 2 certification is in progress. Security controls and operational practices are aligned to common enterprise review domains, and we can support due-diligence requests through our security channel.
Security contact: security@pinbridge.io. Subprocessors and DPA requests: legal@pinbridge.io.
Use the following pages during implementation reviews, procurement questionnaires, and internal security audits.
Send security reports to security@pinbridge.io. Please include steps to reproduce, affected endpoints or workflows, and any impact assessment you can share. We acknowledge reports on a best-effort basis and will keep you informed as we investigate.
Reach out for our DPA, subprocessor list, and answers to your vendor review questionnaire.