System of record: Your designated system of record (CRM, spreadsheet, export-first workflow, or other approved destination) remains the source of truth.
Operational metadata: CallJune may store limited operational data required to run the service (for example: call IDs, routing status, integration status, and audit events).
No parallel system: We do not operate a second system of record intended to replace yours.
CallJune is designed to minimize retention by default and support customer-specific policies.
What we retain
Audio and transcripts
Identity and access
Credential handling
CallJune relies on widely used enterprise platforms and service providers that publish security programs and make security reporting available via trust centers or under NDA, where applicable. Vendor compliance supports a strong foundation, but security is enforced through system design, least-privilege access, and data minimization.
Commonly used categories include CRM platform (when used), voice processing, workflow orchestration, and storage for limited operational metadata.
Access is restricted to authorized personnel with least-privilege permissions and multi-factor authentication for administrative access.
No. CallJune does not sell, rent, or monetize customer data.
Yes. We can complete security questionnaires and provide architecture clarification. Additional details can be shared under NDA as appropriate.
June actually uses the top LLMs like ChatGPT and Gemini—but she’s wrapped in sales intelligence, CRM awareness, voice optimization, and a real-world interface reps will actually use. You're not buying raw AI—you’re buying a sales-specific, proven system that works in the wild.
June is designed to work with the most widely used CRMs. We already integrate with Salesforce and we’re expanding support quickly. If your team uses another system, such as HubSpot, Microsoft Dynamics, or Pipedrive, June can be set up to connect through API connectors. Our goal is simple: wherever your reps keep their customer data, June can capture their voice updates and get it into the right place- without them ever touching a keyboard. (NOTE: set up may take longer for first time CRM intergrations.)
Companies combining AI with sales coaching see a 3.3x increase in year-over-year sales quota attainment.
You can call our demo June, right now at (949) 731-5466. She’ll walk you through a sales recap demo, answer questions about herself, and even send you notes afterward.
No. Integrations use revocable authorization (tokens, service accounts, or API keys as appropriate). We do not store end-user passwords.
Only limited operational metadata required to run the service reliably, such as call IDs, routing state, integration status, and audit events.
Yes. Data is encrypted in transit (TLS). Data stored in managed systems is encrypted at rest using vendor-provided controls (AES-256 where supported).
Yes. Retention and deletion policies can be configured based on customer requirements. Reduced retention windows and deletion workflows are available on request.
CallJune can deliver structured outputs into the destination you approve during scoping, such as a spreadsheet destination (for example Google Sheets), an export-first CSV for customer-controlled import, or another endpoint.
Access is restricted to authorized personnel with least-privilege permissions and multi-factor authentication for administrative access.
No. CallJune does not sell, rent, or monetize customer data.
Yes. We can complete security questionnaires and provide architecture clarification. Additional details can be shared under NDA as appropriate.
June actually uses the top LLMs like ChatGPT and Gemini—but she’s wrapped in sales intelligence, CRM awareness, voice optimization, and a real-world interface reps will actually use. You're not buying raw AI—you’re buying a sales-specific, proven system that works in the wild.
June is designed to work with the most widely used CRMs. We already integrate with Salesforce and we’re expanding support quickly. If your team uses another system, such as HubSpot, Microsoft Dynamics, or Pipedrive, June can be set up to connect through API connectors. Our goal is simple: wherever your reps keep their customer data, June can capture their voice updates and get it into the right place- without them ever touching a keyboard. (NOTE: set up may take longer for first time CRM intergrations.)
Companies combining AI with sales coaching see a 3.3x increase in year-over-year sales quota attainment.
You can call our demo June, right now at (949) 731-5466. She’ll walk you through a sales recap demo, answer questions about herself, and even send you notes afterward.
CallJune captures sales-relevant deal truth by phone and delivers structured outputs into your designated system of record. We prioritize data minimization, least-privilege access, and trusted infrastructure so teams can deploy confidently
Contact Security
.svg)
.svg)
.svg)
.svg)
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
System of record: Your designated system of record (CRM, spreadsheet, export-first workflow, or other approved destination) remains the source of truth.
Operational metadata: CallJune may store limited operational data required to run the service (for example: call IDs, routing status, integration status, and audit events).
No parallel system: We do not operate a second system of record intended to replace yours.
CallJune is designed to minimize retention by default and support customer-specific policies.
What we retain
Audio and transcripts
Identity and access
Credential handling
CallJune relies on widely used enterprise platforms and service providers that publish security programs and make security reporting available via trust centers or under NDA, where applicable. Vendor compliance supports a strong foundation, but security is enforced through system design, least-privilege access, and data minimization. Commonly used categories include CRM platform (when used), voice processing, workflow orchestration, and storage for limited operational metadata.
No. Integrations use revocable authorization (tokens, service accounts, or API keys as appropriate). We do not store end-user passwords.
Only limited operational metadata required to run the service reliably, such as call IDs, routing state, integration status, and audit events.
Yes. Data is encrypted in transit (TLS). Data stored in managed systems is encrypted at rest using vendor-provided controls (AES-256 where supported).
Yes. Retention and deletion policies can be configured based on customer requirements. Reduced retention windows and deletion workflows are available on request.
CallJune can deliver structured outputs into the destination you approve during scoping, such as a spreadsheet destination (for example Google Sheets), an export-first CSV for customer-controlled import, or another endpoint.
Access is restricted to authorized personnel with least-privilege permissions and multi-factor authentication for administrative access.
No. CallJune does not sell, rent, or monetize customer data.
Yes. We can complete security questionnaires and provide architecture clarification. Additional details can be shared under NDA as appropriate.