Trust
Security & privacy
Straight answers about how we handle your calls and your customers' information.
What we store
For each call R1 answers we keep what your team needs to follow up: the caller's number, the recording and transcript, an AI summary, and any booking or message details. We use it to run the service for you — never to sell or advertise.
How we protect it
- Encrypted in transit: every connection to Reception One uses HTTPS (TLS).
- Calendar connections (Google Calendar, Cal.com) are stored encrypted, and you can disconnect them at any time.
- Your business only: every request is checked on our servers, so a business can only ever see its own calls and data.
- Roles and permissions: owners decide who on the team can see calls, bookings and settings.
- Two-factor sign-in is required for owners and admins.
- Limited staff access: our team can open an account only to help with support, and that access expires after an hour.
HIPAA (United States)
We don't sign HIPAA business associate agreements (BAAs) yet, so Reception One isn't set up for US healthcare providers that need one to share patient information with a vendor. If you're a US practice, talk to your compliance adviser — and contact us if you'd like to hear when this changes.
Your data
Want a copy of your data, or want it deleted? Questions about personal data under Singapore's PDPA or US privacy laws? Contact us and we'll help.
Calling and AI disclosure
You choose how R1 greets callers. We recommend saying it's an AI assistant — some US states and other jurisdictions require call-recording consent or AI disclosure, so check the rules where you operate.
Report a security issue
Email [email protected] with "Security" in the subject. We'll respond promptly.