Security
Trust starts with clear boundaries.
Customer email and business Knowledge are sensitive. Preplyr is designed around data minimization, organization isolation, least privilege, and human control.
Organization isolation
Knowledge, conversations, drafts, preferences, and usage are scoped to the organization that owns them.
Protected inbox credentials
Gmail credentials stay server-side and are designed to be encrypted at rest with narrow OAuth access.
Minimum AI context
Reply generation should use only the relevant conversation context and approved Knowledge needed for the answer.
Human-controlled sending
Preplyr prepares drafts. A person reviews and explicitly sends every reply in V1.
Honest uncertainty
Missing or conflicting information is surfaced for review instead of becoming invented business policy.
Server-side authorization
Signing in is not enough. Protected operations must also verify organization membership and permissions.
Our approach
Collect less. Expose less. Verify on the server.
Preplyr should not store or transmit entire mailboxes, unnecessary headers, unrelated Knowledge, or customer details that do not help prepare a reply.
Provider notifications, reply sends, and billing events are designed to tolerate retries without duplicating important side effects.
Security and privacy claims are published only when the underlying implementation and provider terms support them.
A note about regulated data
Healthcare and appointment-based businesses can use niche templates for non-sensitive operational questions. Preplyr does not claim HIPAA suitability or regulated medical-record support.
Keep the human in control
Prepare grounded customer replies while your team retains the final decision to edit and send.
No credit card required