Encryption in transit and at rest
Connections use industry-standard encryption protocols. Stored communication data is protected within secured provider infrastructure.
Security at LimePhone
Keep calls, messages, recordings, and customer details protected with encrypted connections, controlled access, and trusted cloud infrastructure.

Built for everyday business
LimePhone applies safeguards across the communication lifecycle, from sign-in and call handling to storage and account administration.
Connections use industry-standard encryption protocols. Stored communication data is protected within secured provider infrastructure.
Manage users from the admin dashboard and limit business data to the people who need it as teams change.
Call services use Twilio infrastructure, while application services run across AWS and Google Cloud data centers.
Data ownership
Security is stronger when businesses can manage their own data. LimePhone provides practical controls for communication records and customer details.
Privacy and compliance
LimePhone supports GDPR-aligned data handling and applicable telecom requirements. Businesses remain responsible for configuring their account and communication practices for their industry and region.
Security FAQs
Clear information for teams evaluating LimePhone.
LimePhone uses encryption for data in transit and at rest, access controls, and secured cloud infrastructure across its service providers.
Call-related services use Twilio infrastructure. Other application services use AWS and Google Cloud across distributed data centers.
Yes. Authorized users can manage recording settings, access stored recordings, and delete recordings when appropriate.
LimePhone provides GDPR-aligned processes and controls, including data deletion and do-not-disturb handling. Customers should review the GDPR policy for details.
Secure business calling
LimePhone is built to keep customer conversations available to the right people and protected from the wrong ones—with layered safeguards across data, access, operations, and infrastructure.
No single control does all the work. LimePhone uses overlapping technical and operational safeguards to reduce risk across the life of a business conversation.
Use encrypted connections and controlled storage practices to reduce exposure while data moves through and rests within the service.
Limit administrative and user access by role, workspace, and operational need, supported by account-level access controls.
Monitor service health, isolate issues, and maintain recovery processes that support dependable customer communications.
From the connection to the application and the people operating it, each layer has a different job—and each helps reduce the impact if another control fails.
Use individual accounts, role-aware access, and workspace boundaries. Remove access promptly when responsibilities change and avoid shared credentials.
Service-health signals and defined escalation processes help teams identify issues, investigate what happened, and restore normal operation.
LimePhone’s service is designed with operational monitoring and recovery processes that support availability and a controlled return to normal if disruption occurs.
Process customer information for clear service purposes and avoid making it available beyond the systems and people that need it.
Collect and retain information in line with service needs, customer choices, and applicable obligations.
Provide practical paths for account owners to manage users, content, and requests relating to their information.
Use privacy and legal documentation to describe how information is handled and which responsibilities apply.
Review LimePhone’s published policies for information about data handling, terms, and customer responsibilities.
Security works best when platform controls and good customer practices reinforce each other.
Use unique user accounts, remove former teammates promptly, and review workspace membership regularly.
Use strong, unique passwords and keep account recovery information current. Never share admin access.
If something looks wrong, contact LimePhone support with the affected workspace, time, and details you can safely share.
LimePhone uses encrypted network connections for supported service traffic so data is protected while moving between users, services, and infrastructure.
Access is limited through authentication, authorisation, workspace boundaries, and operational least-privilege practices. Customers should also keep workspace membership current.
Secure the affected credentials and contact LimePhone support promptly at support@limephone.io with the workspace name, approximate time, and a description of what you observed.
Read the LimePhone Privacy Policy and related legal pages for published information about data handling and customer rights.
Yes. Contact LimePhone through the contact page or support@limephone.io with the scope of your review and the information your organisation needs.
Send the context of your vendor review or security question and we’ll route it to the right person.