privacy policy
Effective date: October 1, 2026
Last updated: October 28, 2026
The short version
- faxB2B is a business fax service run by HELPERG LLC, a Wyoming company. It is for organizations and for people aged 18 or over. It is not for children or for personal use. We do not offer it in the European Economic Area, the United Kingdom, Brazil or some other countries (sections 17 and 19).
- We handle two kinds of information. We decide how to use account, sign-in, billing, website and support information. We handle the documents and faxes your organization sends, receives and stores ("Customer Content") on your organization's behalf and follow its instructions.
- We do not sell personal information, and we never use Customer Content — the documents and faxes your organization sends and receives — for advertising or to train AI models.
- Only if you accept it, we measure our advertising with Meta. Two things then happen: our public pages load Meta's advertising pixel, and our server tells Meta when a sign-up, trial, checkout or payment is confirmed, matched with a scrambled (hashed) form of your email address and an account reference. Meta never receives the contents of your documents or faxes, or any fax number. Under some US state privacy laws this counts as "sharing" personal information for targeted advertising. It is off until you accept, and you can switch it off at any time with "Cookie preferences" at the foot of any public page (section 8).
- A few service providers help us run faxB2B, including Hetzner for hosting, Telnyx for faxes and numbers, Stripe for payments and Resend for email. Our servers are in Germany, and our staff access information only from countries of the European Union (section 15). A fax sent to another country travels through telephone carriers in that country.
- Our support staff can see fax details such as status, page counts and fax numbers. Staff can open your organization's documents and faxes only in the limited cases listed in section 6, and that access is logged.
- The Service uses only the cookies it needs to work, plus one first-party cookie that records which campaign or website brought you to our sign-up page. We use no third-party analytics unless you accept it: with your consent our public pages also report, using anonymous browser-storage identifiers, page views and actions with canonical public URLs without query strings or fragments, fixed action names and browser information to Webmaster ID, an analytics service, and our console and server report activity with your internal user ID after consent (section 3). The only technologies of another company on our website are that service and the advertising pixel above, both off until you accept them (section 8).
- Wherever you live, you can ask to access, correct, delete or get a copy of your information, and your local law may give you more rights. Write to info@faxb2b.com. If your question is about the contents of a fax, start with the organization that sent or received it.
- faxB2B is not designed for protected health information, and we do not sign HIPAA business associate agreements.
1. Who we are and what this Policy covers
faxB2B is operated by HELPERG LLC, a Wyoming limited liability company ("HELPERG", "we", "us", "our"). Our mailing address is HELPERG LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA.
- For privacy questions, privacy requests and legal notices, write to info@faxb2b.com.
- For help with your account or a fax, write to support@faxb2b.com.
This Privacy Policy (the "Policy") explains how we handle personal information in connection with the faxB2B website at faxb2b.com and the faxB2B web application, including sending and receiving faxes, fax numbers, the team inbox, document tools, billing pages, and related email and support (together, the "Service"). This Policy is published at https://faxb2b.com/legal/privacy.
This Policy does not cover mobile apps. Apps or services that link to their own terms or privacy notices are governed by those terms and notices.
Key terms
- Customer: the business or other organization that creates a faxB2B organization account (called an "Organization" in the product) and accepts the faxB2B Terms of Use at https://faxb2b.com/legal/terms (the "Terms").
- User: an individual the Customer authorizes to use the Service in its Organization, with the owner, admin or member role.
- Customer Content: documents and files uploaded, faxes sent and received (images, PDFs and metadata such as fax numbers and cover-sheet text), contacts, notes, and other content the Customer or its Users submit or receive through the Service.
- Fax Numbers: telephone numbers we assign to the Customer for receiving faxes.
- you: any individual whose personal information we handle, such as a website visitor, a prospective customer, a User, or a person whose information appears in a fax.
Other capitalized terms, such as Subscription, Seat, Pages and Trial, have the meanings given in the Terms.
faxB2B is a service for businesses and other organizations. It is not offered for personal, family or household use, and Users must be at least 18 years old.
This Policy is a notice of our practices, not a contract. Our contract with each Customer is the Terms, which include our Data Processing Addendum ("DPA") at https://faxb2b.com/legal/dpa for personal information in Customer Content (section 15). Nothing in this Policy limits rights you have under mandatory law that cannot be waived by contract.
2. Our two roles
Information we decide how to use
For the personal information we handle to run our own business, we decide how and why it is used. Where a law uses a term such as "controller" for this role, that is our role for this information:
- account information, and the sign-in and security information connected to it;
- billing and payment information;
- website, sales and marketing information, including inquiries sent through our contact-sales form;
- support requests and other messages you send us.
Sections 3 and 4 describe this information and how we use it.
Information we handle for Customers
We handle Customer Content on behalf of the Customer that owns the Organization. The Customer decides what is uploaded, sent, received and kept, and to whom faxes go. For Customer Content, the Customer is the controller and we are its service provider or processor. The Customer's own privacy notice explains how it uses that information. Section 5 explains how we handle Customer Content.
Some fax details, such as fax numbers, page counts, times and delivery status, are part of Customer Content. As part of the Service, and as the Terms and the DPA instruct us, we also use those details to count and bill Pages, to keep the Service secure, to prevent fraud and junk faxes, to meet legal duties that apply to us, and to produce aggregated statistics that do not identify any Customer, User or other person, which we use to understand and improve the Service. We do not try to re-identify anyone from those statistics, and we do not use fax details for any other purpose.
3. Information we collect
Information you give us
- Account and Organization. To start a Trial or create an Organization, you give us your work email address and your organization's name; if you sign in with a new address without giving a name, we name the Organization after your email address until you change it. In your settings you can also choose a time zone and which notification emails you receive, and owners and admins can set the Organization's time zone and the sender name shown on cover sheets.
- Invitations. When an owner or admin invites a colleague, they give us the colleague's email address. If you were invited, we received your email address from them. The invitation email links to this Policy.
- Billing. Owners pay and manage payment details on Stripe's hosted checkout and customer portal pages, not ours, and we never receive or store card numbers. We give Stripe the owner's email address, the Organization's name and our internal Organization ID and, on monthly plans, the number of extra Pages used. Stripe collects the payment and billing details it needs, such as the cardholder's name, the billing address and a tax ID, under its own privacy policy. From Stripe we keep customer, subscription and invoice references, the plan, Seats, billing interval and period dates, payment and invoice status, and invoice numbers, amounts and line items. If an owner cancels, we also keep the reason and any comment they give.
- Sales inquiries. Our contact-sales form asks for your name, work email, company, how many people will use faxB2B and, optionally, what you need.
- Support and other messages. When you write to us, we receive your email address, your message and any attachments. Please do not send fax contents or recipient numbers by ordinary email.
- Number porting. Owners and admins can ask to move existing fax numbers to faxB2B. The request form collects the numbers, the name of the current carrier, the account holder's business name, the name of the person who signs the letter of authorization, the service address, the account number and any transfer PIN with the current carrier, and a signed letter of authorization as a PDF. The account number and PIN are stored encrypted. Our staff handle each request by hand. We use and share these details only to move the numbers, with our carrier and, through it, your current carrier. We keep the request, the letter and the encrypted account number and PIN until the Organization is deleted.
- Verification. If we or our carriers need to verify a Customer's identity, business, authority or right to use a Fax Number (Terms, Section 3.3), we may ask for business registration details, proof of address or authority and, only where a carrier or the law requires it, an identity document of the person acting for the Customer. We use it only for verification, fraud prevention and legal compliance, share it only with the carrier concerned, and keep it only as long as the carrier or the law requires.
Information created when you use the Service
- Sign-in and security. One-time sign-in codes (stored only in hashed form and valid for 10 minutes), the email address and time of each code request, attempt counts and lockouts, your authenticator app (TOTP) secret (stored encrypted), recovery codes (stored only in hashed form), your sessions and signed-in devices, with each device's browser and operating system and when it signed in and was last active, and records of the extra verification required before sensitive actions. No IP address or location is kept with your devices.
- Memberships and roles. Which Organizations you belong to and your role in each one.
- Audit records. Each Organization's audit log records sign-ins, team, role, settings and billing changes, downloads, exports, deletions and other sensitive actions: who acted (shown by email address), what was done, when, to which item, whether it succeeded, and short details such as a new role or the reason given for a two-factor reset. It also shows when our staff opened the Organization's documents, and why (section 6). It does not record Users' IP addresses or browsers.
- Billing and usage. The status of the Subscription, its Seats and any Trial; the Pages ledger (Pages bought, used, refunded and expired); the Fax Numbers the Organization holds; and refunds.
- Usage events. Records of steps taken in the Service, such as signing up, inviting a colleague, sending a fax or changing a plan, and your answer if you reply to our one-question satisfaction survey. They hold no email addresses, fax numbers or document content.
- Emails we send. Records of the service emails we send, such as sign-in codes, invitations and notices, and whether they were delivered.
Information collected automatically
- Device and log information. When you use the Service, our servers receive your IP address, browser type, the pages or actions you request and the time. We use this to run and secure the Service, for example to limit repeated requests; for that we keep IP addresses only in a scrambled (hashed) form. Our application logs record the page or action requested, its result and the time it took. They leave out IP addresses, browser details, sign-in codes, tokens, email addresses, phone and fax numbers and links to documents.
- Website visits. Our server counts visits to our public pages: for each day, only the number of visits per page and per source (the campaign name in the link, such as
utm_source, otherwise the name of the website you came from, otherwise "direct"). It stores no IP address, browser details or identifier and uses no cookie or browser storage for this. Visits by search engines and similar automated tools are not counted. - How you found us. If you open our sign-up page from a link with campaign tags (such as
utm_source) or from another website, theftcookie (section 8) records the campaign tags, the referring website's name, the page of our website you came from and the date, and we keep them with your Organization if you sign up. We use this only to see which of our marketing works. - Advertising pixel (only if you accept it). On our public marketing, guides and legal pages we can load Meta's advertising pixel. It runs only after you accept it, and never on the pages of the signed-in application, the billing, document, inbox, settings or staff pages, our sign-in and sign-up pages, our browser PDF tools or our contact-sales form. When it runs, Meta Platforms, Inc. receives your IP address, information about your browser and device, the address of the public page you are reading, the address of the page you came from, and the identifiers in its own
_fbpand_fbccookies, including thefbclidclick identifier if you arrived from one of our advertisements. From the page itself it reports only that you opened it: no form entries, no button or link clicks, no recording of your session, no field you typed. We have switched off Meta's automatic event collection and do not use its advanced matching. - Confirmed events we report to Meta ourselves (only if you accept it). Separately from the pixel, and only while your choice is on record, our own server tells Meta when one of these six things has actually happened. Each one is established by the server, never by anything a page or a form claims:
- a sign-in code confirmed the email address of a person who did not have an account before;
- a new Organization, and therefore a new Trial, was created;
- our payment provider created a Checkout session for an Organization's owner;
- a contact-sales enquiry passed validation and was stored;
- an invoice read back from our payment provider is paid, with a real amount on it. The amount and its currency travel with that one event;
- that invoice was the first paid invoice of a Subscription (sent without an amount, so revenue is reported once).
With each event we send, so that Meta can match it to the right advertisement: a scrambled (SHA-256 hashed) form of your email address after standardising it, a scrambled form of an internal account reference, the
_fbpand_fbcidentifiers your browser offered when you accepted, your browser's user agent string, and the time. Your email address itself is not sent, and the scrambled values cannot be read back by us or by Meta. Nothing else goes: no name, no telephone or fax number, no postal address, no document, no fax, no page count, no fax status, no free text you typed, and no address of a page inside the Service. Cancellations, failures and fax activity are never reported. Section 8 explains how to withdraw, and section 10 how long the queue keeps anything.
- Webmaster ID visit analytics (only if you accept it). After you accept the current notice, our own collector on eligible public pages reports page views, fixed CTA names, app-store link clicks and contact-form submission intentions. It sends only the canonical public page address (no query string or fragment), browser user agent, language and viewport width. It excludes referrers, page titles, form values and document content. Anonymous visitor and session identifiers in localStorage (
wmid:av:v1) and sessionStorage (wmid:as:v1,wmid:as:last:v1) accompany these requests; no analytics cookies or third-party tracker script are used. The provider receives the network IP address with requests. On signed-in console pages, our own local collector sends fixed section/action names, your internal account UUID, anonymous visitor/session IDs, browser user agent, language and viewport width. All private views use the common/appaddress; actual document paths, query strings, fragments, referrers, private page titles, form values, fax content and fax numbers are excluded. No third-party code is loaded there. Our server checks the account and current consent before each event. Device/browser reports come from browser information, not a hardware identifier or fingerprint. Separately, server conversions and product milestones carry the verified internal account UUID under valid consent; we do not invent device context for background payments or resend historical events to add identity. We do not load the Universal Integration Kit or send browser conversions that duplicate our server outbox. Identified console activity is collected by our own code. - Cookies and browser storage. See section 8.
Information from other sources
- Your organization. Owners and admins can add you as a User, change your role or remove you.
- Stripe. Payment and subscription status, refunds and disputes, and the billing details listed above.
- Telnyx. Fax delivery events, records about the Fax Numbers we provide, and, for incoming faxes, the sender's and receiving fax numbers. The fax details are part of Customer Content.
What we do not collect
We do not ask for health information, we ask for government identification only for the verification described above, and we do not collect precise geolocation. Customer Content may still contain sensitive information. Section 5 explains how we handle it.
The free PDF tools on our website (image to PDF, merge, compress and cover sheet) run entirely in your browser. The files and text you use with them are not sent to us.
4. How we use information
We use the information described in section 3 for these purposes:
- Provide the Service. Create and run accounts and Organizations, send and receive faxes, show statuses and receipts, provide Fax Numbers and the team inbox, and let owners and admins manage their teams.
- Sign you in and keep the Service secure. Verify sign-ins, require two-factor authentication, limit request rates, scan files for malware, detect and stop abuse, investigate incidents and keep audit records.
- Bill and keep records. Charge Subscriptions and extra Pages through Stripe, handle refunds and disputes, and keep tax and accounting records.
- Communicate with you. Send sign-in codes, invitations, fax and account notices, and billing and security messages; answer inquiries and support requests. Section 9 covers marketing email.
- Operate and improve the Service. Understand how our website and the Service are used, fix problems and plan capacity. We do this with our own records. We use no third-party analytics product; the only technology of another company on our website is the advertising pixel in section 8.
- Prevent fraud and misuse, including junk faxes, and enforce the Terms.
- Comply with law. Meet tax, accounting, sanctions and other legal duties, which can include checking Customers, Users and their owners against sanctions lists; respond to valid legal requests; and establish, exercise or defend legal claims.
- Carry out a business transfer, as described in section 7.
- Measure our advertising, if you accept it: see which of our advertisements bring people to our public website and which of them lead to a sign-up, a trial, a checkout, a sales enquiry or a payment, and let Meta show our advertisements to people who have visited our website (sections 3 and 8). This happens only with your consent and never with Customer Content.
We do not:
- sell personal information;
- share personal information for cross-context behavioral advertising, or use it for targeted advertising, except through the optional advertising pixel on our public website, which runs only if you accept it and which you can switch off at any time (section 8);
- use Customer Content for advertising, or to build profiles of individuals; or
- collect, use or sell personal information or Customer Content to train artificial intelligence models, including large language models.
The Service has no artificial intelligence features.
We do not make decisions based solely on automated processing that have legal or similarly significant effects on you. Some security controls are automated. Examples are sign-in rate limits, the hourly limit on faxes per Organization and the blocking of files that fail the malware scan. Billing limits also apply automatically: when a Trial ends without a paid Subscription, a Subscription ends, or a payment is still unpaid after the 7-day grace period, sending, invitations and new Fax Numbers stop. If no paid plan follows, the Organization's Fax Numbers are released 30 days later, after we email the owner (Terms, Sections 7.5, 14.2 and 17.1). Only our staff can pause or close an Organization because of its content or conduct. When they do, they record a reason, and we email the owner. If you think an automated control has affected you wrongly, write to support@faxb2b.com and a person will review it.
5. Customer Content
How we handle it
We handle Customer Content only to provide, secure and support the Service for the Customer. We follow the Customer's instructions (given through the Service, the Terms and the DPA) and the law. This includes:
- checking uploaded files, scanning them for malware and converting them to fax format;
- storing documents, faxes, cover sheets, contacts, notes and delivery receipts;
- passing outgoing faxes to our carrier, Telnyx, which delivers them over the telephone network to the recipient's fax machine or service;
- receiving incoming faxes on a Customer's Fax Numbers and placing them in that Organization's inbox;
- deleting Customer Content under our retention rules (section 10) or when the Customer deletes it.
We do not sell Customer Content or use it for advertising. We use it only as this section, section 2 (fax details) and section 6 (for example, investigating a complaint or misuse) describe.
If your information is in a fax
Faxes contain information about people who are not Users, such as the recipient of an outgoing fax, the sender of an incoming fax and anyone named in a document. The Customer decides what is sent and to whom, and it is responsible for having a lawful basis to do so.
If you have a question or request about a fax, contact the organization that sent or received it. If you write to us, we will pass your request to that organization or tell you how to reach it, and we will help it respond. We answer requests ourselves if they concern a report you sent us or other information we decide how to use (section 2).
If you received an unwanted fax sent through faxB2B, report it to support@faxb2b.com. Include the sending number and the date and time. We use these reports to stop misuse, and we pass them to the Organization that sent the fax (section 7).
Previously used Fax Numbers
When a Fax Number is released, for example when an owner or admin releases it, or 30 days after a Trial or Subscription ends (Terms, Sections 7.5 and 14.2), faxes sent to it stop reaching the Organization at once. We then keep the number for 90 days and do not give it to another Customer. A fax that arrives on it during those 90 days goes into no inbox automatically. Our operations staff may deliver it, without opening it, to the Organization that last held the number, if that Organization still exists; if our carrier no longer makes the file available, that Organization receives only the fax's details (the sending number, the time and the number of pages). Otherwise we do not download or open the fax: we keep only its details (the sending and receiving numbers and the time), without a fixed deletion date, and the file stays with our carrier under its own policies (section 10). After the 90 days we return the number to our carrier, which may later assign it to someone else, including another faxB2B Customer; faxes sent to it then reach the new holder. We keep a record of which Organization held each Fax Number and when, also after the Organization is deleted, so that faxes sent to a previously used number do not reach the wrong Customer.
Sensitive information and health information
faxB2B is not designed for special categories of personal data, such as health information, or for other highly sensitive data. If a Customer still sends or receives such data, the Customer is responsible for having the legal basis and permissions its law requires.
faxB2B is not designed for protected health information ("PHI") under the US Health Insurance Portability and Accountability Act ("HIPAA"). A Customer that is a HIPAA covered entity or business associate must not use faxB2B to send, receive or store PHI unless it and HELPERG have both signed a business associate agreement. We do not offer business associate agreements at this time.
Documents you fax may contain Social Security numbers or other government identification numbers. We protect their confidentiality, prohibit their unlawful disclosure and limit access to them, as described in sections 6 and 11.
6. Who can see Customer Content
- Your organization. Users in an Organization can see the faxes, documents, contacts and notes their role allows. Owners and admins can also see the audit log, the team and the Fax Numbers.
- HELPERG staff. Authorized staff run the Service through a separate staff console. Every staff account requires two-factor authentication, and every staff action is recorded in our staff audit log.
- Support staff can search for Customers, see account, billing and fax metadata (such as statuses, times, page counts, the Organization's Fax Numbers and partly masked numbers of senders and recipients), extend Trials, and ask our carrier for the status of a fax. They cannot open documents, fax images or cover sheets.
- Operations staff can also fix operational problems. Examples are retrying a fax, holding a suspicious incoming fax, or resetting two-factor sign-in at a User's request. To see an Organization's documents or fax images, a staff member must open temporary "break-glass" access for that Organization and record a reason. The access lasts 30 minutes, works only for that staff member, and is logged with every document opened. The Organization's audit log always shows the access and its reason, and we notify the owner by email and in the Service unless the owner has turned these notices off in the Organization's settings.
- A few senior staff can export or delete an Organization's data when the Customer asks, the law requires it or the Terms allow it. They can also suspend an Organization and issue refunds. They too need break-glass access to see content; an export the Customer asked for is built automatically, and only the person who asked for it can download it.
- Our carrier and hosting providers handle Customer Content as needed to transmit and store it (section 7).
Our staff open documents, fax images and cover-sheet text only for these reasons:
- when the Customer or one of its Users asks for support that needs it, for example to investigate a failed fax;
- to keep the Service secure, and to investigate a security incident, abuse, a complaint or a suspected breach of the Terms, including removing content the Terms do not allow;
- to comply with law.
We route a fax that arrives on a released Fax Number during quarantine (section 5) from its details alone, without opening it.
7. How we share information
Service providers
We use service providers to run the Service. Except as described below, they may use personal information only to provide their services to us, under contracts that require them to protect it.
| Provider | What it does for us | Information involved |
|---|---|---|
| Telnyx | Sends and receives faxes; provides and manages Fax Numbers | Fax files, fax numbers, delivery events, number records |
| Stripe | Payments, subscriptions, invoices and refunds | Billing contact and payment details; Subscription status; extra Pages used |
| Resend | Delivers our emails | Email addresses and message content, such as sign-in codes, invitations and notices |
| Hetzner Online GmbH | Hosts our servers, database, file storage and backups | All information in the Service, including Customer Content (stored documents and fax files are encrypted) |
| Namecheap, Inc. (Private Email) | Hosts our email mailboxes | Messages you send us |
Stripe and Telnyx also use some information as independent controllers under their own privacy policies. Stripe does so for payment information, for example to prevent fraud and meet financial rules. Telnyx does so for some call and fax records, such as numbers, times and routing data, for example to bill, prevent fraud and abuse, and meet telecommunications rules.
A fax also passes through telephone networks, which we do not control, to the recipient's fax equipment or service. Telephone carriers handle a fax as needed to deliver it.
Our current list of service providers, with their locations, is at https://faxb2b.com/legal/subprocessors. Before we add a provider that processes Customer Content, we tell Customers as the DPA describes.
Other disclosures
- Fax recipients. When a User sends a fax, the recipient receives the fax and the sender details shown on it: the calling number, which is one of your Organization's Fax Numbers or, if it has none, a shared faxB2B number, and any details the User puts on the cover sheet. We do not add an identification line to the pages.
- Your organization. Owners and admins see information about their Users, such as email addresses, roles, audit-log activity, and the faxes sent and received.
- Complaints about faxes. If someone complains about a fax sent through faxB2B or asks not to receive faxes, we pass the complaint, including the complainant's name and contact details, to the sending Organization. Where the law allows, we may give the complainant, telephone carriers, our payment processor or authorities investigating misuse the sending Customer's name and contact details and details of the fax, but not its content.
- Meta, for advertising measurement. If you accept, Meta Platforms, Inc. receives the information in section 3 under "Advertising pixel" and "Confirmed events we report to Meta ourselves", and uses it both for us and for its own purposes, under its own privacy policy at https://www.facebook.com/privacy/policy. Meta is a recipient for our own marketing only. It is not one of our service providers and not a subprocessor of Customer Content: it never receives documents, fax files, fax numbers, the contents of a fax, a page count or a fax status, and the pixel never runs in the signed-in application. The only account information it receives is the scrambled email address and account reference described in section 3, and the amount of a paid invoice. This is the only place where we share information with a company that also uses it for its own purposes.
- Webmaster ID, for visit analytics. With consent, the provider processes the browser events, anonymous identifiers, canonical public URLs without query strings or fragments, fixed action names and browser information described in section 3, plus the internal account UUID with limited console activity and server conversions described above. We do not deliberately send names, email addresses, documents, faxes or fax numbers through the tracker. Public query strings, fragments and referrers are excluded; private URLs and document content are excluded from the console collector.
- Professional advisers, such as lawyers, accountants and auditors, who owe us confidentiality.
- Legal requests and safety. We disclose information when we believe in good faith that the law or valid legal process requires it. We also disclose information other than the contents of faxes and documents when that is necessary to protect someone from death or serious physical injury, to protect the security of the Service, or to protect our rights.
- We disclose the contents of faxes and documents only when the law or valid legal process requires it, with the Customer's consent, or, where the law allows, to a government authority in an emergency involving danger of death or serious physical injury.
- Unless the law forbids it or there is an emergency, we tell the Customer before we disclose its Customer Content.
- As a US company, we may be required to disclose information we control wherever it is stored.
- Business transfers. HELPERG, or the faxB2B business, may be involved in a merger, acquisition, financing, reorganization or sale of assets. If so, information may pass to the new owner, which must keep protecting it as this Policy describes.
- With consent, or when the Customer directs us.
8. Cookies and similar technologies
Webmaster ID sets no cookies but, only after consent, uses localStorage and sessionStorage for anonymous analytics identifiers. Meta also uses advertising cookies. All of our cookies except the ft cookie are needed to run the Service.
Cookies and browser storage we set
| Name or type | Purpose | How long |
|---|---|---|
pre_csrf cookie | Protects the sign-in, sign-up, code-entry and contact-sales forms against cross-site request forgery | 10 minutes |
sid cookie | Keeps you signed in and secures your session | 12 hours; the session also ends after 120 minutes without activity, or when you sign out |
csrf cookie | Protects the actions you take while signed in against cross-site request forgery | 12 hours, or until you sign out |
invite cookie | Remembers an invitation you opened before signing in, so you join the right Organization | 24 hours, or until you sign in |
ft cookie | Remembers the campaign or website that brought you to our sign-up page (section 3), so we can see which of our marketing works | 30 days, or until you finish signing up |
faxb2b-theme (browser local storage) | Remembers light or dark display, only if you choose one with the theme switch | Until you clear your browser storage |
fax-request-… (browser local storage) | Stops the same fax being sent twice if you press Send again or reload the page | Removed when the fax is sent; otherwise until you clear your browser storage |
faxb2b-ads-consent (browser local storage) | Remembers whether you accepted or refused advertising measurement, with the date of your choice and the version of the question we asked | 180 days, then we ask again |
ads_consent cookie | Set only if you accept advertising. A random value with no meaning of its own, which links your browser to the record of your choice on our server, so the events in section 3 can be reported with consent and stopped without it | 180 days, or until you withdraw |
Every cookie in the table above is set by our own server, is marked Secure, and is marked HttpOnly: the JavaScript in the page cannot read it — including ads_consent, which is why a script can ask us to end a consent but can never read or copy the key to it. The browser local storage entries are not cookies, are written and read only by our own JavaScript in your browser, and are never sent to a server. Our staff console has its own sign-in cookies, set only for our staff. We use no third-party analytics cookies. When you pay, Stripe's hosted pages may set Stripe's own cookies under Stripe's policy.
The ft cookie is set only when you open our sign-up page from a campaign link or another website, and it holds no identifier. You can block or delete it in your browser without affecting the Service.
Advertising cookies, set by Meta only if you accept
| Name | Set by | Purpose | How long |
|---|---|---|---|
_fbp | Meta's pixel, through JavaScript running in your browser | Identifies your browser to Meta, so Meta can tell it apart from others that saw our advertising | Up to 90 days, and refreshed while you keep visiting |
_fbc | Meta's pixel, through JavaScript running in your browser | Keeps the fbclid click identifier from the advertisement you arrived from, so the visit can be matched to it | Up to 90 days |
Unlike our own cookies, these two are written by JavaScript, so they are not HttpOnly and the page can read them. They appear only on our public marketing, guides and legal pages, only after you accept, and never in the signed-in application, on the billing, document, inbox, settings or staff pages, on our sign-in and sign-up pages, or on the pages of our browser PDF tools and our contact-sales form.
Accepting, refusing and changing your mind
- Nothing of Meta's loads, no advertising cookie is set and no event is reported until you choose "Accept" in the panel our pages show. Refusing leaves the website and the Service working exactly as they did.
- The panel offers accepting and refusing with the same prominence, and you can reach either from the keyboard. It appears on public pages and in the signed-in console; use Cookie preferences in the public footer or the console account menu to change it.
- One choice covers both the pixel and the events in section 3. Your choice is kept in your browser for 180 days, with the date and the version of the question, and on our server for the same period. After that we ask again. If the record is missing, unreadable, out of date, or was made against an earlier version of this notice, we treat it as no consent and ask again. The current version is 5 and includes identified console activity and user IDs on server conversions. All choices made against versions 1, 2, 3 or 4 are invalid; we ask again before enabling measurement.
- To change your mind, open Cookie preferences at the foot of a public page or in the console account menu. Refusing stops the pixel in the page at once, deletes the
_fbpand_fbccookies, ends the record of your consent on our server, and deletes every event that was still waiting to be sent. We tell you it is done only once our server has confirmed it; if we cannot reach our server, the panel says so and asks you to try again, the browser pixel stays stopped. Server withdrawal takes effect when our server receives it; events already in transit may still arrive at Meta. - Your choice lives in your browser, so it applies to that browser on that device. Clearing your browser storage clears it, and we ask again. Withdrawing in one tab stops the other tabs of the same browser as well.
- Information Meta already received before you withdrew stays with Meta under its own policy.
- If we add other cookies or similar technologies that are not strictly necessary, we will update this Policy first and, where the law requires, ask for your consent in the same way.
Do Not Track and Global Privacy Control. We treat a browser "Do Not Track" signal and a Global Privacy Control (GPC) signal as a valid instruction not to share your information for advertising. When either signal is present, the advertising pixel does not load, the _fbp and _fbc cookies are deleted, no event is reported to Meta or to Webmaster ID, and your browser tells our server to end the record of any consent it holds. This is so even if you accepted advertising earlier: the signal overrides the earlier choice. Nothing else about our website or the Service changes, because nothing else tracks you across websites. The one thing these signals cannot reach is payment: on its hosted payment pages, Stripe may collect device, browser and usage information and combine it with information from other websites that use Stripe, to prevent fraud (https://stripe.com/privacy). We do not sell personal information.
9. Emails from us
Service emails include sign-in codes, security notices, invitations, and plan and payment messages, such as Trial reminders, failed-payment notices and plan changes. They are part of the Service, so you cannot turn them off while you are a User, except that the owner can turn off the emails that tell the owner when our staff open the Organization's documents (section 6). Notifications about faxes, Fax Numbers and page usage are also service emails, and you can turn each kind off in your account settings or with the unsubscribe link in the email.
Other emails. The owner of a new Organization may receive a few emails with tips for getting started (getting a Fax Number, sending a first fax and inviting the team). Any User can also choose to receive a weekly summary of the Organization's fax activity. Each of these emails has an unsubscribe link, and you can turn them off in your account settings. We do not send newsletters or other promotional emails at present.
- Every email that has an unsubscribe link identifies HELPERG and includes our postal address.
- If we start sending promotional emails, we will first ask for your consent where the law requires it, including in Canada.
- You can object to marketing email at any time by writing to info@faxb2b.com.
If you send a sales inquiry, we use your details to answer it. We do not add you to marketing emails because you sent an inquiry.
10. How long we keep information
This is how long we keep personal information:
| Information | How long we keep it |
|---|---|
| Account and Organization information | While the account or Organization exists, then as described under "Deletion" below |
| Files of faxes sent (the pages as transmitted, including any cover sheet) | 90 days after the last attempt to send the fax ends. Only the file is deleted; the fax record (recipient number and name, subject, status, timeline and page count) stays until the Organization is deleted |
| Documents uploaded or created to send a fax | Until the Organization is deleted, except that a converted copy sent as the fax file (without a cover sheet) goes with that file |
| Delivery receipts | As long as the fax record they belong to. A receipt shows a small image of the fax's first page unless the Organization turns this off in its settings |
| Incoming faxes | Until an owner or admin deletes them, the period an owner or admin sets in the inbox settings ends (30 days to 7 years; by default none is set), or the Organization is deleted. Deleting a fax removes its files; a record of it (the numbers, time and page count) stays until the Organization is deleted |
| Porting requests | Until the Organization is deleted |
| Records of which Organization held each Fax Number, and when | Without a fixed deletion date, also after the Organization is deleted (section 5) |
| Records of emails we sent | 30 days; 90 days for emails that could not be delivered |
| Staff audit log | 730 days (two years) |
| Website visit counts | 13 months |
| Your advertising choice (browser local storage, and the matching record on our server) | 180 days from the day you made it, then we ask again. Withdrawing, or a browser opt-out signal, ends the record at once |
| Webmaster ID browser identifiers | Visitor identifier: until browser storage is cleared or consent is withdrawn; session identifiers: for the browser tab session. We remove wmid:* and wmid_pay_ref* entries from localStorage and sessionStorage when consent is withdrawn and stop both public and console collectors immediately. This does not erase events already received by the provider; provider-side retention is not controlled by browser storage. |
| An event waiting to be reported to Webmaster ID by our server (section 3) | At most 7 days, then it is dropped. It may carry the internal account UUID. Afterwards, a minimal processing record remains to prevent duplicate reports, subject to our event-record retention schedule |
| An event waiting to be reported to Meta (section 3) | At most 7 days, which is the oldest event Meta accepts. What it carries is deleted the moment the event is sent, or the moment you withdraw; what stays is a note that the event happened, so it cannot be reported twice |
Meta's _fbp and _fbc cookies, if you accepted advertising | Up to 90 days in your browser, and deleted at once if you withdraw or your browser sends an opt-out signal. What Meta keeps, and for how long, is governed by Meta's own policy |
| Organization audit log | While the Organization exists, and afterwards without a fixed deletion date (see "Deletion" below) |
| Sign-in code records, session and device records, usage events, export files after their 7-day download period, and the hashed values we use to limit repeated requests | Without a fixed deletion date, also after an account is deleted |
| Sales inquiries sent through our contact-sales form | Without a fixed deletion date |
| Support and other messages sent to our mailboxes | 2 years after our last contact with you |
| Billing, tax and accounting records | Without a fixed deletion date, and at least as long as tax and accounting law requires |
| Application logs | Without a fixed deletion date. They hold no IP addresses, email addresses or fax numbers (section 3) |
| Backups | When we make backups, they are encrypted and we keep each one for no more than 30 days |
Deletion.
- Organization deletion. The owner can ask to delete an Organization in its settings. When we carry out the request, we close it: its Users are signed out, sending stops, its Subscription is canceled and its Fax Numbers are released. We delete it permanently 30 days later. Until then, the owner can ask support@faxb2b.com to cancel the deletion; the content is then restored, but not the Subscription or the Fax Numbers. At deletion we remove the Organization's name, documents, fax files and records, contacts, cover sheets, notes, invitations, porting requests, notifications and memberships. Its Users' accounts are not deleted. Export anything you need first.
- When a Trial or Subscription ends. If a Trial ends without a paid Subscription, a Subscription ends, or a payment stays overdue after the grace period, sending, invitations and new Fax Numbers stop. For 30 days, Users can still sign in and read and download Customer Content, the owner can ask for a full export (section 12), and the Fax Numbers keep receiving faxes. We email the owner 7 days and 1 day before the Fax Numbers are released. After those 30 days, we release them (section 5) and may delete the Organization and its Customer Content.
- Account deletion. A User can ask us to delete their own account in the account settings, after a fresh two-factor check; our staff carry out the request within 30 days. A User who owns an Organization that has other active Users must first transfer ownership, or ask us to delete that Organization. We then end the account's sessions; delete its authenticator secret, recovery codes, personal settings, notifications and unsent fax drafts; remove it from every Organization; and replace its email address with a placeholder. Organizations the User owns alone are closed at the same time and deleted 30 days later. Faxes, documents, contacts and notes the User created stay with the Organization, and its audit log keeps its entries without the User's email address. Sign-in code records and records of emails we sent, which contain the address, are kept as the table above shows, and invitations sent to the address stay with the Organization that sent them until that Organization is deleted.
- What we keep after deletion. We keep billing records (invoices, refunds, the Pages ledger and the Subscription record), the history of which Organization held each Fax Number and when, the Organization's audit log, usage events and our staff audit log, for the periods in the table above. We also keep information the law requires us to keep and information needed for legal claims. Deleted information may remain in a backup until that backup is deleted. We limit how we use anything we keep.
- Providers' own records. Stripe and Telnyx keep some records under their own policies and legal duties. Telnyx keeps records of faxes, such as numbers, times and delivery status, and may keep fax files, for periods set by its own policies. We download each received fax from Telnyx within minutes and keep our own encrypted copy. We do not ask Telnyx to store the files of faxes we send, or currently to delete its copies.
11. Security
We protect personal information with measures designed for a service that handles business documents:
- Passwordless sign-in with one-time codes sent by email. Codes are stored only in hashed form, expire after 10 minutes and allow a limited number of attempts.
- Mandatory two-factor authentication with an authenticator app before a User can open a workspace, with single-use recovery codes. Sensitive actions, such as changing roles, asking to delete an account or downloading an export, require a fresh two-factor check.
- Session controls. You can see your signed-in devices and sign out of any one or all of them, and sessions end after a period without activity.
- Encryption in transit (HTTPS with HSTS) for the website and the application.
- Encryption at rest with AES-256-GCM for stored documents and fax files, with a separate key derived for each Organization. Authenticator secrets are also stored encrypted.
- Isolation between Organizations through row-level security in our database, so one Organization cannot read another's records.
- Malware scanning of every uploaded and received file before processing. If the scanner is unavailable, no file is processed or sent unscanned: an upload is held, unopened, and you are asked to try again, and a received fax is kept encrypted and scanned when the scanner is back.
- Sandboxed document conversion. Files are converted in an isolated process with no network access. If that isolation is not available, files are not converted.
- Audit logs of sensitive actions in each Organization and of every staff action.
- Limited staff access, as described in section 6.
- Protected provider connections. Our carrier fetches fax files through signed, temporary links, and we check the signatures on messages from our carrier and payment provider.
No system is perfectly secure, and we cannot guarantee the security of information. Faxes travel over the public telephone network, which is not end-to-end encrypted, and email is not end-to-end encrypted either. We do not hold a third-party security certification such as SOC 2 or ISO 27001. Our security page at https://faxb2b.com/security gives more detail.
You can help protect your account. Keep the email account you sign in with secure and your recovery codes safe, and remove Users who leave your organization.
Security incidents. If a security incident affects personal information, we will notify affected individuals, Customers and authorities as the law requires. If we discover a breach of security that leads to unauthorized access to, or acquisition, disclosure, destruction, loss or alteration of, Customer Content, we will tell the Customer without undue delay, and within any shorter time the law requires, so that it can meet its own obligations.
12. Your privacy rights
Depending on where you live and whether a particular law applies to us, you may have the right to:
- know whether we process your personal information, and get access to it and a copy of it;
- correct inaccurate information;
- delete your information;
- receive your information in a portable format;
- object to or restrict certain uses of your information;
- withdraw consent where we rely on it, without affecting processing that took place before;
- appeal our decision on your request; and
- complain to a data protection authority.
We offer access, correction, deletion and a copy of your information to everyone, wherever they live. Some limits apply, whether or not a law gives you the right. We do not send security credentials, such as sign-in secrets or recovery codes, or full identification or financial account numbers, but we tell you that we hold them. We keep information as section 10 describes under "What we keep after deletion". We may decline a request we cannot verify, or one that would reveal another person's information or weaken our security.
How to make a request.
- In the Service. Users can change their email address and preferences, see and end their signed-in sessions, and, in their account settings, ask for a copy of their account information or for their account to be deleted. Users can download the faxes, receipts and lists their role allows, such as a received fax as a PDF or the sent-fax and contact lists as CSV files; owners and admins can also download the audit log. The owner can ask for a full export of the Organization: a ZIP file with CSV files of its records and the PDFs of its received faxes and of the sent faxes we still hold. We prepare exports, email you when one is ready, and you can download it for 7 days.
- By email. Anyone can write to info@faxb2b.com. Tell us what you are asking for and which email address or Organization the request concerns.
Requests about Customer Content. If your request concerns information in faxes or documents held for a Customer, including fax details (section 2), we will refer you to that Customer or pass the request on, and we will help the Customer respond.
Verification. We verify requests by confirming that you control the email address linked to the information, for example with a one-time code. We may instead ask for details that match our records. We ask only for what we need to verify you, and we use it only for that.
Authorized agents. Where the law allows, you can make a request through an authorized agent. We may ask the agent for your signed permission and ask you to confirm your identity with us directly.
Timing and fees. We aim to respond within 30 days. If the law that applies to you sets a shorter period, we meet it. If we need more time and the law allows it, we will tell you why. Requests are free. Where the law allows, we may charge a reasonable fee for, or decline, requests that are manifestly unfounded or excessive.
Appeals. If we decline your request in whole or in part, we will explain why. To appeal, reply to our decision or write to info@faxb2b.com with "Privacy appeal" in the subject line. We will decide on your appeal within 45 days and explain the result.
Complaints to us. You can complain about how we handle your personal information by email to info@faxb2b.com, with "Privacy complaint" in the subject line, or by post to the address in section 23. We acknowledge complaints within 30 days, look into them and tell you the outcome without undue delay. You can also complain to an authority (sections 13 and 17 to 19).
No discrimination or retaliation. If you exercise your privacy rights, we will not deny you the Service, charge you a different price or give you a different level of service. We will not retaliate against you in any other way.
13. US state privacy rights
Several US states give residents privacy rights. Many of these laws apply only to larger businesses, or exclude people acting in a business or employment role, so they may not apply to us or to you. Even so, we offer all US residents the rights in section 12: to confirm whether we process your personal information, access it, get a portable copy, correct it, delete it, and appeal our decision.
- No sale, and no profiling. We do not sell personal information, including sensitive information, and we do not use it for profiling that produces legal or similarly significant effects.
- Targeted advertising: your opt-out. If you accept advertising measurement, the information in sections 3 and 8 goes to Meta, which uses it for advertising. Several state laws call that "sharing" or processing for "targeted advertising", so we treat it as something you can opt out of. It is off unless you accept it. To opt out, or to withdraw after accepting, open Cookie preferences at the foot of any public page and choose "Reject"; a browser Global Privacy Control signal also switches it off and overrides an earlier acceptance (section 8). You can also write to info@faxb2b.com. Nothing else we do is targeted advertising, and we never use Customer Content for advertising.
- Service providers. Section 7 names the service providers we use.
- Appeals and complaints. If we deny your appeal, you can contact your state's Attorney General.
Nevada. We do not sell covered information as Nevada law (NRS 603A) defines it. Nevada residents can still send a sale opt-out request to info@faxb2b.com.
14. California notice (given whether or not the CCPA applies)
We give this notice to California residents whether or not the California Consumer Privacy Act (CCPA) applies to HELPERG. It covers the personal information we handle for our own purposes (section 2). It does not cover Customer Content, which we handle as a service provider (section 5).
Categories we collected in the 12 months before the effective date of this Policy. The purpose numbers refer to the list in section 4.
| Category | Examples | Sources | Purposes | Disclosed for a business purpose to |
|---|---|---|---|---|
| Identifiers | Name, email address, IP address, account and customer references, Fax Numbers held | You; your organization (invitations); automatic collection; Stripe; Telnyx | 1–9 | Hosting provider, Resend, Stripe, Telnyx; your organization; people who complain about faxes, and carriers (section 7); professional advisers; authorities where the law requires; Meta, in the scrambled form described in section 3, only if you accept advertising |
| Customer records (Cal. Civ. Code §1798.80(e)) | Name, organization name, and the service address and carrier account number given for number porting | You | 1, 3, 7 | Stripe (organization name); Telnyx (porting); hosting provider; professional advisers |
| Commercial information | Subscription, Seats, Trial, Pages used, invoices, refunds | You; your use of the Service; Stripe | 1, 3, 5, 7 | Stripe; hosting provider; your organization |
| Internet or other electronic network activity | Logs, sessions and devices, usage events, the campaign and referring website that led to sign-up, audit-log entries, and — only if you accept advertising — the IP address, browser details, public page address, referring page, advertising cookie identifiers and confirmed sign-up, trial, checkout, enquiry and payment events described in sections 3 and 8 | Automatic collection | 2, 5, 6, 7, 9 | Hosting provider; Meta, only if you accept advertising |
| Professional or employment-related information | Your organization and your role in it | You; your organization | 1, 2 | Hosting provider; your organization |
| Sensitive personal information | Account log-in details: your email address with one-time codes and authenticator data; a carrier account number and PIN if you ask to port a number; an identity document, only where verification requires it (section 3) | You; your use of the Service | 1, 2, 6 | Hosting provider; Resend (sign-in code emails); Telnyx (porting); the carrier concerned (verification) |
- Retention. Section 10 explains how long we keep each category.
- No sale; sharing only with your consent. We have not sold personal information. We share personal information for cross-context behavioral advertising in one case only: the advertising pixel on our public website, which runs only if you accept it and which you can switch off at any time (sections 8 and 13). We have no actual knowledge of selling or sharing the personal information of consumers under 16.
- Sensitive personal information. We use it only to provide the Service you asked for, sign you in, keep your account secure and prevent fraud, which the CCPA regulations permit (11 CCR §7027(m)). We do not use it to infer characteristics about you. The right to limit its use therefore does not apply.
Your California rights. Whether or not the CCPA applies to us, we give California residents these rights:
- to know what personal information we collect, use and disclose, and to get the specific pieces of information we hold about you (subject to the limits in section 12);
- to delete it;
- to correct it;
- to opt out of the sale or sharing of personal information (we do not sell; the one case of sharing is the advertising pixel in section 8, which is off unless you accept it and which you can switch off again at any time);
- to limit the use of sensitive personal information (we use it only for permitted purposes);
- not to be discriminated or retaliated against for using these rights, including as an employee, job applicant or independent contractor.
To use these rights, follow section 12. That section also covers verification, authorized agents and appeals. Section 8 explains how we treat opt-out preference signals such as GPC.
We do not disclose personal information to third parties for their own direct marketing purposes (Cal. Civ. Code §1798.83).
15. International processing and transfers
People can sign up for faxB2B from many countries, but what the Service can do differs by country. Faxes can be sent only to the destinations shown in the Service, which currently are the United States, Canada and countries of the European Union. Fax Numbers are available only in the United States and Canada.
Where we process information. Your information may be processed outside the country where you live, in these places:
- The United States. HELPERG LLC is a US company, organized in Wyoming. Our main service providers, Telnyx, Stripe and Resend, process personal information there. Our list of service providers at https://faxb2b.com/legal/subprocessors names the countries where each of them processes personal information.
- Germany. Our servers, database, stored files and backups are hosted in Germany (Hetzner Online GmbH). Hetzner processes information for us under a data processing agreement.
- Where our staff work. Our staff and contractors access information only from countries of the European Union.
- Meta, if you accept advertising. Meta Platforms, Inc. is a US company, and what we send it (sections 3, 7 and 8) is processed in the United States and in the other countries Meta's own policy names. This happens only if you accept it. We rely on your consent for it and claim no other safeguard, certification or transfer contract for it. Refusing, withdrawing, or sending a Global Privacy Control signal stops it.
- Fax destinations. A fax sent outside the United States, and the personal information in it, goes to the destination country through telephone carriers.
These countries' data protection laws may differ from yours. While your information is in another country, the courts, law enforcement and national security authorities of that country may be able to access it under its laws.
Safeguards.
- Information we control. When we collect information directly from you, that collection is not itself treated as an international transfer. When we pass it to a service provider in another country (section 7), we rely on a safeguard for that provider: its certification under the EU-U.S. Data Privacy Framework, the UK Extension and the Swiss-U.S. Data Privacy Framework, where it holds one, or otherwise the European Commission's Standard Contractual Clauses, with the UK Addendum and the Swiss adaptations, in its data processing terms. HELPERG itself is not certified under the Data Privacy Framework. For Switzerland, these safeguards are the Federal Council's finding of adequate protection for US companies certified under the Swiss-U.S. Data Privacy Framework (Federal Act on Data Protection, Art. 16(1)) and standard data protection clauses recognized by the Federal Data Protection and Information Commissioner (Art. 16(2)(d)). We apply the protections in this Policy wherever the information is processed.
- Customer Content. Our DPA at https://faxb2b.com/legal/dpa forms part of the Terms and applies automatically to personal information in Customer Content, without a separate signature (Terms, Section 20.3). For transfers, the DPA includes the European Commission's Standard Contractual Clauses with the Swiss adaptations. It can also include other transfer terms that we agree to in writing.
HELPERG is a US company. We therefore treat Customer Content from Customers in Switzerland as transferred out of Switzerland, wherever it is stored.
- Copies. You can ask for a copy of the safeguards we rely on at info@faxb2b.com. We may remove commercial terms from the copy.
16. Legal bases for processing
Section 4 lists why we use personal information. The data protection laws of the European Economic Area (EEA), the United Kingdom and several other countries also require us to name a legal basis for each use. The table below does that for the information we control. For Customer Content, the Customer decides the legal basis.
| Purpose | Main information | Legal basis |
|---|---|---|
| Provide the Service, including invitations and team management | Account, Organization, membership and usage information | Performance of our contract with the Customer. For Users who are not the contracting party, our and the Customer's legitimate interest in providing the Service the Customer ordered |
| Sign-in, two-factor authentication, security, rate limits, malware scanning and audit logs | Sign-in and security data, logs, audit records | Legitimate interests in keeping accounts and the Service secure; legal obligation where security law requires it |
| Billing, payments, tax and accounting | Billing and usage information | Performance of the contract; legal obligation to keep tax and accounting records |
| Service emails | Email address and account information | Performance of the contract; legitimate interest in informing Users about their account |
| Support and correspondence | Messages and account information | Legitimate interest in answering you; performance of the contract |
| Sales inquiries | Contact-sales form details | Steps taken at your request before a contract; legitimate interest in answering business inquiries |
| Website visit counts, how you found us, and service improvement | Visit counts, campaign and referral details, logs and usage information | Legitimate interest in understanding and improving our website and the Service, with our own records; the Webmaster ID visit analytics of section 3 rest on your consent instead |
| Advertising measurement | The information in sections 3 and 8: IP address, browser and device details, the public page address, the referring page, advertising cookie identifiers, and for a confirmed sign-up, trial, checkout, enquiry or payment a scrambled email address and account reference with the amount of a paid invoice | Consent, which you give in the cookie panel and can withdraw at any time. Without consent nothing is collected or reported for this purpose |
| Tips, weekly summaries and marketing emails | Email address | Consent where the law requires it; otherwise legitimate interest in helping Users use the Service and in promoting it, which you can object to at any time |
| Preventing fraud and junk faxes; enforcing the Terms | Account and usage information, and reports we receive | Legitimate interests in protecting the Service, fax recipients and the public |
| Legal compliance and legal claims | Any information relevant to the legal duty or claim | Legal obligation; legitimate interest in establishing, exercising or defending legal claims |
| Business transfers | Information needed for the transaction | Legitimate interest in selling or reorganizing our business |
You must give us your email address to create an account. Billing details are needed for a paid Subscription. Without them we cannot provide the Service. You can ask info@faxb2b.com for more information about how we balance our legitimate interests against your rights.
17. EEA, United Kingdom and Switzerland
Controller. HELPERG LLC is the controller of the information described in section 2 ("Information we decide how to use"). Contact details are in section 23.
Availability. faxB2B is not offered to organizations or Users in the EEA or the United Kingdom. This section still applies to people there whose information we handle, for example because they visit our website, write to us or appear in a fax.
Your rights. You have the rights listed in section 12. These include access, rectification, erasure, restriction, data portability and withdrawal of consent. In the EEA, you also have the right not to be subject to decisions based solely on automated processing that significantly affect you. In the UK and Switzerland, you can be told about such a decision, give your view and ask for a person to review it. We do not make such decisions (section 4).
Your right to object. You can object at any time, on grounds relating to your particular situation, to processing we base on legitimate interests. You can also object at any time, without giving a reason, to the use of your information for direct marketing. Write to info@faxb2b.com or use the unsubscribe link in any marketing email.
Complaints. You can complain to us (section 12). You can also complain to a data protection authority:
- EEA: the supervisory authority in the country where you live or work, or where you believe the infringement happened. The list is at https://www.edpb.europa.eu/about-edpb/about-edpb/members_en.
- United Kingdom: the Information Commission (formerly the Information Commissioner's Office) at https://ico.org.uk. We ask you to complain to us first.
- Switzerland: the Federal Data Protection and Information Commissioner (FDPIC) at https://www.edoeb.admin.ch.
Transfers. Section 15 explains where we process information and the safeguards we use.
Data processing agreements. Our DPA at https://faxb2b.com/legal/dpa, which forms part of the Terms, sets out how we process personal information in Customer Content for Customers, including the terms Swiss law requires (section 15).
18. Canada, including Quebec
Person in charge of personal information. Privacy Officer, HELPERG LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA; info@faxb2b.com.
Your rights.
- You can ask to access and correct your personal information.
- You can withdraw your consent, subject to legal and contractual limits. If you withdraw consent that we need to run your account, we may no longer be able to provide the Service.
- You can complain to us (section 12). You can also complain to the Office of the Privacy Commissioner of Canada (https://www.priv.gc.ca) or, in Quebec, to the Commission d'accès à l'information du Québec (https://www.cai.gouv.qc.ca).
Processing outside Canada and Quebec.
- Your information is processed outside Canada, and outside Quebec, by us and by the service providers in section 7, in the countries listed in section 15.
- While it is there, the courts, law enforcement and national security authorities of those countries may be able to access it.
- Before we communicate personal information outside Quebec, we assess whether it will be adequately protected.
Other information.
- Section 6 describes which categories of staff can access information.
- We do not use technology to profile you, to track you across websites or to locate you (section 8).
- We send commercial emails to people in Canada only with the consent that Canada's Anti-Spam Legislation requires.
French versions. French versions of this Policy, the Terms and our DPA are available at https://faxb2b.com/legal/fr/privacy, https://faxb2b.com/legal/fr/terms and https://faxb2b.com/legal/fr/dpa.
19. Other countries
Many other countries have data protection laws, including those in the table below.
Countries where faxB2B is not offered. faxB2B is not offered to organizations or Users located in Russia, Belarus, mainland China, Turkey (Türkiye), Kenya, Brazil, the European Economic Area or the United Kingdom (Terms, Section 3.5), or in the places under comprehensive sanctions listed in Section 11.1 of the Terms. Do not sign up for or use faxB2B from those places; we may refuse, suspend or close accounts connected with them (Terms, Sections 3.5 and 11.3).
Wherever you are, you can use the rights in section 12 where your law gives them to you. These usually include access, correction, deletion, objection or restriction, portability, withdrawal of consent and the right to complain. Make requests as section 12 describes. You can also complain to your local authority:
| Country | Authority |
|---|---|
| Australia | Office of the Australian Information Commissioner (oaic.gov.au) |
| New Zealand | Office of the Privacy Commissioner (privacy.org.nz) |
| Japan | Personal Information Protection Commission (ppc.go.jp/en) |
| South Korea | Personal Information Protection Commission (pipc.go.kr/eng) |
| India | Data Protection Board of India (once the Act's duties apply) |
| Singapore | Personal Data Protection Commission (pdpc.gov.sg) |
| Hong Kong | Office of the Privacy Commissioner for Personal Data (pcpd.org.hk) |
| South Africa | Information Regulator (inforegulator.org.za) |
| Nigeria | Nigeria Data Protection Commission (ndpc.gov.ng) |
| Mexico | Secretaría Anticorrupción y Buen Gobierno |
| Argentina | Agency for Access to Public Information (AAIP) |
| Israel | Privacy Protection Authority |
| Saudi Arabia | Saudi Data and AI Authority (sdaia.gov.sa) |
Country-specific information.
- Japan. Section 15 lists the foreign countries where we process personal information. Japan's Personal Information Protection Commission publishes information about foreign countries' personal information protection systems. On request, we will tell you the name of the person who heads HELPERG LLC and the other matters the Act on the Protection of Personal Information requires. We have no representative in Japan.
- South Korea. The person responsible for privacy is our Privacy Officer, reachable at info@faxb2b.com.
- Section 7 lists the companies we entrust with processing.
- Sections 7 and 15 describe overseas transfers: which information goes where, when (as you use the Service, over the network), and why. Section 10 says how long we keep it. Our list of service providers at https://faxb2b.com/legal/subprocessors gives each overseas recipient's name, country and privacy contact, and how long it keeps the information.
- You can refuse the overseas transfer by not using the Service or by asking us to delete your account, but we cannot provide the Service without it.
- Singapore. You can reach the person we have designated for data protection, our Privacy Officer, at info@faxb2b.com.
- India. When the notice, consent and rights duties of the Digital Personal Data Protection Act, 2023 and its Rules apply to us, you may nominate a person to exercise your rights if you die or become unable to do so. After using our grievance process (write to info@faxb2b.com), you may complain to the Data Protection Board of India.
- Mexico. You can exercise your rights of access, rectification, cancellation and opposition (ARCO rights) and ask us to limit the use or disclosure of your information by writing to info@faxb2b.com.
- South Africa. The Protection of Personal Information Act also protects information about juristic persons, such as companies. We apply this Policy to that information in the same way.
20. Children
faxB2B is a business service. It is not directed to children, and no one under 18 may use it. We do not knowingly collect personal information from children under 13, or under a higher age where local law sets one. If we learn that a child has created an account or given us personal information through our website or the Service, we will close the account and delete that information. Information about a child in a fax or document is Customer Content, and the Customer decides what to do with it (section 5). If you believe a child has given us personal information, write to info@faxb2b.com.
21. Changes to this Policy
We may update this Policy from time to time. The dates at the top show when this version takes effect and when it last changed. When we post a new version before it takes effect, the current version stays available until then. Earlier versions of this Policy are available at https://faxb2b.com/legal/archive.
If we make a material change, we will tell Customers' owners by email and show a notice in the Service at least 30 days before the change takes effect, unless the law or security requires a faster change. Where the law requires your consent to a change, we will ask for it. If a material change would let us use information we already hold in a materially different way, we will not apply it to that information without the consent of the people affected, and we will tell them directly where we have their email address.
22. Language
This Policy is written in English. A French version is available (section 18). Any translation is provided for convenience. If a translation differs from the English version, the English version controls, except where the law of your country requires otherwise.
23. Contact us
HELPERG LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA
- Privacy questions, privacy requests, complaints, appeals and legal notices: info@faxb2b.com
- Support and account requests: support@faxb2b.com
If your question is about information in a fax, contact the organization that sent or received the fax first (section 5).
