1. Scope
This is an architecture overview, not a certification or independent audit report. It describes HostRecaps intended local-processing design and the boundaries customers should validate in their own environment.
Security, privacy and regulatory suitability depend on enabled features, endpoint configuration, connected integrations and organizational policies.
2. Local processing boundary
- Local content: audio, transcripts, notes and recaps are designed to be processed on the users device.
- No meeting bot: HostRecap is designed not to join conferences as a hosted participant.
- User-directed exports: only material a user selects is sent directly to a connected destination.
- Credentials: integration credentials are intended to use operating-system credential storage where available.
3. Verify the deployment
Before relying on HostRecap for sensitive work, organizations should validate their installed build: review network activity in a local session, ensure unnecessary integrations are disabled, test deletion behaviour, and apply their normal endpoint-management controls.
Website copy is not a substitute for a risk assessment, penetration test, procurement review or legal determination.
4. Regulated use and security reports
HostRecap does not claim that local architecture alone makes an organization HIPAA, GDPR or otherwise compliant. Whether a Business Associate Agreement, data-processing agreement or transfer safeguard is required depends on the actual relationship and data flow.
To report a vulnerability, email security@hostrecap.com with the affected version, steps and impact. Do not send sensitive meeting content unless requested through a secure channel.