Security & Privacy
Built with privacy
at the centre.
Ring Fenced is designed to protect you — not just from callers, but as a product. Here is how we handle your data, your calls, and your trust.
Not an emergency service. Ring Fenced must not be used as a primary contact route in emergencies. Always maintain a direct, unscreened emergency contact method.
AI classifications are probabilistic. Risk scores may not always be accurate. Legitimate callers may be flagged and scam callers may receive lower scores. Do not rely solely on Ring Fenced to identify fraud.
Callers are notified they are speaking to AI. Ring Fenced does not impersonate a human. Every call begins with a clear AI disclosure.
End-to-end encryption
All data transmitted between your browser, our servers, and our telephony infrastructure is encrypted in transit using TLS 1.2 or higher. Call audio and transcripts are encrypted at rest using AES-256.
Your forwarding number — the personal phone you want calls delivered to — is stored encrypted and is never exposed to callers, logs, or third parties.
- TLS 1.2+ for all API and web traffic
- AES-256 encryption for stored call data
- Your personal number stored in encrypted form only
- Agent credentials isolated per user account
Data retention policies
We retain only what is necessary to provide the service. You can delete individual call records or all data at any time from your dashboard. Deleting your account triggers immediate removal of all personal data within 30 days.
| Data type | Default retention | User control |
|---|---|---|
| Call transcripts | 90 days | Delete individually or all |
| Call recordings | 30 days (Pro/Team) | Delete individually or all |
| Risk reports | 90 days | Delete with transcript |
| Account data | Duration of account | Account deletion removes all |
| Payment data | As required by law | Managed via billing portal |
| Access logs | 30 days | Not individually deletable |
AI disclosure notice
Every Ring Fenced call agent discloses to the caller at the outset that they are speaking to an automated AI screening system. This disclosure is mandatory and cannot be disabled or removed.
The agent will identify itself as an AI and explain its purpose (call screening) before proceeding with any questions. Callers may end the call at any time.
Example disclosure: "Hi, you've reached [name]'s line. I'm an AI call screening assistant. I'll ask you a few questions before connecting your call. Your conversation may be recorded and transcribed for screening purposes."
Recording consent
Calls handled by Ring Fenced may be recorded and transcribed for the purpose of screening. Callers are informed of this at the start of every call. By using Ring Fenced, you accept responsibility for ensuring that call recording in your jurisdiction is conducted lawfully.
- Callers are notified before recording begins
- Recordings are used solely for screening and your review
- Recordings are not used to train external AI models without consent
- You are responsible for compliance with local recording laws (e.g. GDPR, UK PECR)
In the UK, one-party consent generally allows you to record calls you are a party to. However, requirements vary. Ring Fenced is not a legal service and cannot advise on your specific obligations. Please consult a legal professional if you are unsure.
Privacy commitment
Ring Fenced does not sell your data. We do not share call transcripts, recordings, or personal information with third parties for advertising or marketing purposes.
We use a limited number of trusted sub-processors to provide the service (telephony, cloud infrastructure, payment processing). Each sub-processor is bound by data processing agreements. A list of sub-processors is available on request.
- No data sold to third parties
- No advertising targeting based on call content
- Sub-processors bound by DPAs
- Data processed in the UK / EU where possible
- Full data export available on request
- Right to erasure honoured within 30 days of verified request
Platform security practices
Ring Fenced is built with security as a first-class concern. We apply security best practices across the platform and aim to respond rapidly to any vulnerabilities.
- CSRF protection on all authenticated routes
- Rate limiting on login and sensitive endpoints
- Input sanitisation and parameterised queries throughout
- Secure session management with rotation on privilege change
- Security headers (CSP, X-Frame-Options, HSTS)
- Vulnerability disclosure: security@ringfenced.io
Contact & questions
If you have questions about how we handle your data, wish to exercise your data rights, or want to report a security issue, please contact us at:
- Data enquiries: privacy@ringfenced.io
- Security reports: security@ringfenced.io
- General support: support@ringfenced.io
For our full Privacy Policy see /privacy. For our Terms of Service see /terms.