Data Protection and Security Policy
Effective October 8, 2026
data-protection-2026-10-08-v1
This policy describes safeguards for KeepCarrier customer data and the responsibilities shared by KeepCarrier LLC and its customers. It is incorporated into the Terms of Service. It is not a certification, a promise of uninterrupted availability or a guarantee that every security incident can be prevented.
On this page
Data boundaries and access
Customer-owned leads, notes, communications, settings and uploaded files are scoped to their organization. Shared public carrier facts remain separate. Server-side authentication, role, ownership and current subscription checks protect workspace operations. Support access must be authorized, scoped and recorded; another customer has no right to your private activity.
Customers must grant only appropriate permissions, maintain accurate account contacts, protect credentials and connected mailboxes, promptly remove access that is no longer needed, and report suspected compromise. Do not upload passwords, payment-card details, sensitive health data or special-category personal data into lead notes or other general-purpose fields.
Technical safeguards
The production application uses HTTPS, a private PostgreSQL database with encrypted storage, encrypted object storage, and server-side secret references. Connected mailbox credentials are encrypted and are not sent to client browsers. Tenant photo and attachment downloads enforce current ownership and entitlement; private tenant photos do not have anonymous raw-bucket access. Shared vehicle imagery may remain public.
Safeguards include permission checks, rate limits, session controls, abuse review, immutable commercial evidence and application monitoring. No statement here claims that every account has mandatory multi-factor authentication, that all content is encrypted end to end, or that KeepCarrier has an ISO 27001, SOC 2 or other independent certification.
Backups, retention and restoration
Database backups support operational recovery. They do not replace a customer's own lawful records or guarantee a particular recovery time or recovery point. Restored systems must preserve tenant isolation, opt-outs and commercial evidence. We review retention and deletion requests according to the Privacy Policy and Data Processing Addendum; payment holds do not erase stored data.
Commercial, security and suppression evidence may remain where necessary for legal obligations, disputes, abuse prevention or honoring an opt-out. Backups expire under their configured lifecycle. Where retained data cannot yet be erased lawfully, it remains restricted and is not used to restore a deleted customer's ordinary workspace.
Security incidents and reports
Report suspected exposure or a vulnerability to support@mail.keepcarrier.com with enough detail to investigate, without including passwords or unrelated personal data. Do not access other tenants, disrupt the service or conduct intrusive testing without written authorization.
We investigate reported incidents, contain unauthorized access, preserve relevant evidence and provide affected customers information without undue delay after becoming aware of a personal-data breach affecting data we process for them. Information may be provided in stages. Each party remains responsible for notifications to authorities or individuals that the applicable law requires. No paid subscription creates an unadvertised 24-hour incident-response SLA.
Assurance and data requests
Authorized organization representatives may request relevant security information, an export or a scoped deletion review through support. Identity and authority must be verified. Audit arrangements must protect other tenants and confidential security information; applicable legal audit rights are not excluded. Previously downloaded material, third-party caches and external communications cannot be recalled.