Press 1 Voice is designed to support responsible voice outreach with practical controls around account access, campaign operations, caller identity, integrations, and data workflows.
Security starts with controlled access, responsible campaign setup, verified integrations, and clear ownership of compliance decisions.
Important: This page does not claim that Press 1 Voice is certified under SOC 2, ISO 27001, HIPAA, GDPR, CCPA, PCI DSS, FedRAMP, or any other framework unless such status is separately verified and formally documented by Press 1 Voice.
Security for outreach software is not just about servers. It also depends on who can access the platform, how lists enter the system, which numbers are used, and how campaign data moves between tools.
Limit platform access to authorized users and review who needs operational, administrative, or campaign-level access.
Treat imports, exports, APIs, webhooks, and connected applications as part of the security boundary.
Keep approved caller IDs, authentication tools, and number-health workflows organized for outbound calling.
Make campaign creation, list handling, and calling activity part of a deliberate operational process.
Confirm integration permissions, contact-source requirements, caller identity, and campaign rules before launch.
Press 1 Voice provides platform tools. Your organization remains responsible for lawful use, list eligibility, consent, content, and campaign decisions.
The safest campaign starts before the first call. Review who can access the platform, which data is uploaded, where it came from, and which connected systems can exchange information with Press 1 Voice.
Give access only to staff, organizers, volunteers, or administrators who need it.
Know where each list came from and whether your organization is permitted to contact it.
Use only the third-party credentials and access scopes needed for the workflow.
Confirm the audience, caller identity, message, timing, and follow-up process before launch.
No calling platform can determine every legal requirement for every campaign. Press 1 Voice supports the workflow, while your organization controls the audience, message, consent basis, timing, and campaign purpose.
Authentication, number reputation, caller ID selection, and campaign controls each solve a different operational problem. None of them should be treated as a blanket compliance guarantee.
Helps organize approved calling numbers by campaign, region, or workflow depending on configuration.
Supports number-health and reputation monitoring. It cannot guarantee that a carrier or third party will never apply a warning label.
Supports authenticated caller identity in compatible telecommunications environments. Authentication is separate from campaign consent or legal compliance.
Captures keypad intent and can support a clearer follow-up path. Your team remains responsible for the legality of the underlying call.
Gives callers structured scripts and campaign context while your organization controls the content and calling rules.
Helps standardize conversations, but your legal and compliance team should approve required disclosures and campaign language.
If Press 1 Voice later completes an independent audit, obtains a certification, publishes a security white paper, or formalizes a data-processing framework, this section can be updated with the exact verified scope, date, and documentation.
Until then, avoid badges or statements such as “SOC 2 Certified,” “ISO 27001 Certified,” “HIPAA Compliant,” “GDPR Certified,” or similar claims unless they are factually accurate and supported by current documentation.
CRM, voter, member, nonprofit, campaign, API, webhook, import, and export workflows can all move sensitive operational data. Use the minimum access required for the task.
Grant a connected application only the permissions necessary for the intended workflow.
Keep API keys, passwords, tokens, and connector credentials restricted to authorized administrators.
Remove unused connections and review whether existing integrations still need access.
Confirm which fields move between systems and avoid sending data that the receiving system does not need.
Handle exported contact and campaign files according to your organization’s own data-handling policies.
Review technical and security requirements before connecting private databases or internal applications.
Bring your security questionnaire, integration requirements, data-flow questions, or procurement checklist to the Press 1 Voice team.
Use the contact page to share the requirements your organization needs reviewed before purchasing or integrating Press 1 Voice.
Contact Press 1 Voice →Use a demo to review how account access, caller identity, integrations, and campaign workflows fit your organization.
Book a Demo →We’ll walk through the platform, your campaign workflow, connected systems, caller identity needs, and the questions your organization needs answered before launch.
