Agency isolation
Every authenticated request resolves the user and agency before accessing tenant data. Enforced row-level boundaries prevent one agency from reading another agency's records.
Polca is built around enforced tenant boundaries, scoped access, data portability, and calling controls that support the compliance program your agency operates.
Plain-language details about how Polca separates agency data, handles records, and enforces calling workflows.
Every authenticated request resolves the user and agency before accessing tenant data. Enforced row-level boundaries prevent one agency from reading another agency's records.
Seats and administrative capabilities belong to a specific agency environment. Account access can be revoked without waiting for a long-lived remembered session to expire.
Your contacts, scripts, recordings, summaries, and presentation history remain your agency's data. Export and offboarding expectations are documented in the Privacy Policy and Terms.
Call recordings are retained for approximately 90 days unless an Order Form or legal hold requires otherwise. Production deletion and backup aging are described in the Privacy Policy.
DNC and opt-out controls apply across AI and human dialing. The agency remains responsible for the lawful basis and consent attached to the leads it chooses to contact.
Calls travel through an authorized carrier network with attestation, while recordings, dispositions, and follow-up outcomes preserve an operational history for the agency.
The operational overview above does not replace the governing agreements. These documents define responsibilities, retention, acceptable use, and data processing.
This page is an operational overview, not a certification or legal opinion. Questions about a specific agency deployment can be addressed during onboarding or by emailing security@polca.ai.