When people use CarePair, they may share personal information, private messages, and important documents. This page explains, in simple terms, how that information is handled and why that matters. The aim is to help users understand the difference between public website content and private member information, and to explain some of the practical steps CarePair uses to help protect accounts and documents.

Why privacy and document security matter

Care and support arrangements often involve sensitive personal information. That can include contact details, messages, care-related documents, and information that people would not want treated like ordinary public website content.

Good privacy and document security help users feel more confident about creating a profile, sharing information, and managing documents through the platform. They also help make the service clearer and more accountable for everyone using it.

How CarePair handles account information

CarePair uses account information so people can sign in, manage profiles, find matches, send messages, and use the platform safely. That includes the information needed to run core features such as matching, messaging, account access, and service notifications.

Not everything on CarePair is public. Public pages that are intentionally published on the website are visible by design. Member account information, messages, and private library documents are handled differently and are not treated like open public content.

How messages and documents are handled

CarePair is designed to support private communication and controlled document sharing inside the platform. Private member documents are not simply left as open public files. Access is checked in the application before a private document is shown.

When a user shares a document through CarePair, that sharing is designed for in-app access between the relevant users. Access can also be revoked where needed. CarePair also keeps audit records of document views and downloads to improve accountability around document access.

The difference between public and private content

• Public pages and documents intentionally published through CarePair’s website content are public because they are meant to be viewed by visitors.
• Private member library documents use stricter access controls and are handled differently from public website content.
• Document sharing inside CarePair is designed around specific users and specific access, not open public links.

What security measures CarePair uses

• CarePair uses HTTPS on the live site, with certificates managed automatically so website connections are encrypted in transit.
• Traffic to CarePair passes through Laravel Cloud’s edge protections, including DDoS mitigation, load balancing, and managed firewall coverage.
• Admin accounts are protected with two-factor authentication.
• Sign-in, sign-up, and password reset flows use anti-bot checks, strong password rules, and rate limiting.
•   Security headers are applied across the site to help reduce common web risks.
• Private member documents are access-controlled in the application rather than left openly public.
• Document sharing can be revoked if needed.
• Document views and downloads are logged to improve accountability.
• Uploaded member documents are limited to safer file types, and uploaded images are sanitised by the system.
• Security alerts and login audit records help CarePair spot suspicious activity, such as repeated failed sign-ins or unusual admin actions.

What this means in practice

CarePair is designed to handle messages, documents, and account information carefully. It uses layered security measures around accounts, documents, and admin access to help protect user information and improve accountability.

No online platform can promise absolute protection, and CarePair does not claim formal certifications or end-to-end encryption where those are not in place. What it can say is that it uses practical safeguards to help protect private information and to make document sharing and account use more controlled than informal file sending or open public posting.

Practical reassurance for users

• Private documents are not treated the same way as public website pages.
• Sharing happens inside the platform with access checks and audit records.
• Admin access is protected with stronger controls than a password-only setup.
• Messages, documents, and account information are handled with privacy and accountability in mind.

A clear reminder

CarePair is designed to help people connect, communicate, and share relevant information in a more structured way. That includes practical privacy and security measures around accounts, messages, and documents.

Users should still be thoughtful about what they share, who they share it with, and when they decide to move conversations or document exchange away from the platform.