Privacy Policy

Preplyr needs limited information to provide account access, organization workspaces, inbox connections, business Knowledge, customer conversations, prepared drafts, usage limits, and billing-related functionality.

• Account and organization information
• Connected mailbox identity and authorization data
• Customer messages needed for the reply workflow
• Business Knowledge and reply preferences
• Usage, plan, and operational metadata

Information is used to operate Preplyr, retrieve relevant business Knowledge, prepare customer reply drafts, maintain conversation state, enforce plan limits, support users, and protect the service.

Gmail access should use the minimum OAuth scopes required for the supported workflow. Authorization credentials are treated as sensitive server-side data and are never intended for browser exposure.

Disconnecting an inbox should stop future access and trigger credential revocation or removal where supported.

Preplyr is designed to send only the conversation context and organization Knowledge relevant to preparing a reply. Unrelated customer details and unrelated Knowledge should not be included when they are unnecessary.

AI provider retention, training, and regional terms must be reviewed before production use. Preplyr does not promise zero retention unless the selected provider configuration supports it.

Retention depends on the type of information, the selected plan, operational needs, and applicable legal requirements. Draft-history limits do not automatically define retention for every category of customer data.

Account, organization, connection, Knowledge, and customer-data deletion workflows may need to account for dependent records, backups, security records, and billing obligations.

Preplyr is designed around organization isolation, least privilege, encrypted credential storage, server-side authorization, and minimal logging of customer content. No internet service can guarantee absolute security.

This policy may change as Preplyr’s features, providers, and legal obligations develop. Material updates should be reflected by a revised date on this page.