online fax security,
written down.
How faxB2B protects the documents your team sends and receives. This page describes the measures that are in place today. It is deliberately specific, and it also says what we do not offer yet.
In place
- Encryption in transitThe service only runs over HTTPS with HSTS, and our carrier fetches fax files over HTTPS; sign-in and session cookies are marked Secure and HttpOnly. The fax call itself crosses the telephone network unencrypted.
- Encryption at restStored documents are encrypted with AES-256-GCM, with a separate key derived for each organization.
- Isolation between organizationsEvery organization’s data is separated with row-level security in the database, so one team cannot read another’s records.
- Virus scanningEvery upload and received fax is scanned before processing. If the scanner is unavailable, nothing is processed or sent unscanned: uploads stop until you retry, and received faxes wait until they can be scanned.
- Safe document processingFiles are checked by content type, converted to plain black-and-white pages in an isolated process, and every version is fingerprinted with SHA-256.
- Two-factor sign-inSign-in uses one-time email codes. Team workspaces also require an authenticator app, with single-use recovery codes.
- Session controlEvery signed-in device is listed and can be signed out; sensitive actions ask for a fresh two-factor check.
- Audit trailSign-ins, role changes and sensitive actions are recorded with who did what and when.
- Abuse protectionSign-in attempts and verification codes are rate-limited; carrier and payment notifications must carry a valid signature.
- Strict browser policyA strict Content Security Policy allows only our own scripts and styles; pages cannot be framed by other sites. The one exception is the optional advertising measurement described in our Privacy Policy: its script loads only on public marketing pages, only if you accept it, and never in the application.
- Advertising, only with consentOur public pages can measure our own advertising with Meta, and confirmed sign-ups, trials, checkouts and payments are reported to Meta from our server — only after you accept, matched by a scrambled form of your email address, and never with fax contents, fax numbers or document names. One choice covers both, and Cookie preferences at the foot of any page withdraws it.
- Retention and exportHow long we keep each kind of information is listed in our Privacy Policy. The owner can request a full export of the organization in Settings; we email when it is ready to download.
Not offered yet
- We do not sign Business Associate Agreements and do not claim HIPAA compliance. Please do not use faxB2B for protected health information.
- No third-party security certification (such as SOC 2 or ISO 27001) has been completed.
Report a vulnerability
Found a security issue? Please write to us before disclosing it publicly. Do not test the service for vulnerabilities without our written permission, and never access other people's data.
