closerrHow Closerr handles your data.
Closerr is a CRM for UK payment consultants, field sales representatives and commercial teams. This page describes application features and their limits, without making assurances about controls we cannot substantiate.
Last updated: 29 October 2026
Application controls
Access and visibility depend on workspace roles, permissions and feature settings.
Workspace permissions
The application has configurable roles and server-side capability checks. Record visibility depends on the user's permissions and scope; it is not limited to four fixed roles or one assignment rule.
Sign-in and sessions
Google, Microsoft and Apple sign-in and email/password sign-in are supported. New password hashes use bcrypt. Session cookies are HttpOnly and SameSite=Lax, with the Secure flag enabled in production.
Connected-account tokens
Selected integration-token paths use application-level AES-256-GCM encryption. This is not a claim that all CRM fields, documents or recordings have an additional application encryption layer.
Audit events
The application records selected permission, KYC, financial, provider and export events. Coverage varies by feature; this page does not promise a universal audit-log retention period.
Web billing
Web subscription purchases use Stripe-hosted Checkout. The current native client does not offer in-app purchases. RevenueCat entitlement integration remains available where configured; Apple sign-in is separate from purchasing. Please do not upload full payment card numbers in notes or documents.
Additional sign-in protection
There is no in-app multi-factor authentication setup flow. If you use Google or Microsoft sign-in, consider enabling the protections offered by that account provider.
CRM records and connected features
CRM records can include leads, merchants, contacts, deals, tasks, notes, statements and documents. Application records are stored using a configured PostgreSQL database connection; files use the application's storage services.
AI features can send selected text, audio, permitted CRM context and tool results to OpenAI. This page does not make a provider training, contractual or zero-retention assurance.
Voice features are disabled by default for an organisation. Recording and spoken-disclosure behavior depend on the voice configuration. Cleanup of stored recording copies is separate from copies held by a telephony provider.
Sub-processors
Closerr integrates hosting, storage, email, payments, AI and optional connected-account services. Which optional services are used depends on the features and connections enabled.
View the code-verified services and their purposes in the Data Processing Addendum summary. This page does not claim a particular processing region or transfer agreement.
Exports and account deletion
CSV exports are implemented for leads, deals and merchants, subject to permissions and field restrictions. Export availability is not a promise to export every object type.
Account deletion is available in More → Delete account. The public deletion page explains the request process. Ownership restrictions can apply, and shared workspace records and history are not all removed by deleting an individual account.
For the existing privacy and service terms, see Privacy and Terms. This summary does not promise a backup, deletion, incident-response or retention deadline.
Questions or a signed copy
For security or data-handling questions, or to request a signed copy of the Data Processing Addendum, email support@closerr.co.uk.