This page contains several important disclosures and a Data Processing Addendum. The information contained on this page applies to Lead Paramedic LLC (d/b/a EmailMarketing.com) and all companies and brands under common control with Lead Paramedic LLC, including MailGenius LLC and InboxPro LLC (“Company,” “we,” “our,” “us”) and applies to all websites, including any sub domains thereof, affiliated websites, and mobile applications we operate (collectively, the “Site”), and any content, products, or services made available through the Site - unless otherwise noted. All information, especially information related to earnings of Company or its clients, is for general information purposes only.

Company assumes no responsibility for errors or omissions in the contents on the Service.

In no event shall Company be liable for any special, direct, indirect, consequential, or incidental damages or any damages whatsoever, whether in an action of contract, negligence or other tort, arising out of or in connection with the use of the Service or the contents of the Service. Company reserves the right to make additions, deletions, or modification to the contents on the Service at any time without prior notice. Company does not warrant that the Service is free of viruses or other harmful components.

Results shown on this site may not be "typical"

In accordance with the FTC guidelines concerning use of endorsements and testimonials in advertising, please be aware of the following: While every testimonial on this website is from a real customer who used the Service, and/or marketing/business advice listed on our website, any displayed earnings are those of the businesses or individuals depicted, and cannot be completely verified by the Company nor can the same results be guaranteed for anyone else. Running a successful business or making money requires many factors, including but not limited to education, work ethic, and skill. No product we sell can guarantee the same results as someone else. This is why we establish ranges of typical results with prospective customers based on their individual situations, relying on verifiable results we achieve for similar businesses. You may see less results, the same results, or better results.

Results (amount of money made, number of customers added, open and click through rates, etc) were self-reported by customers & businesses and therefore cannot be confirmed. Errors could have been made in revenue amounts and total profitability of their promotions. To create safe projections for your business when buying any product, you should assume that featured results are not typical. We encourage you to do your own research on all the advice, products, and services listed on this site. If you are not comfortable with this information, please do not purchase from us.

What You Might Expect

You should assume that any results shown in testimonials, advertisements, stories, blog posts, articles, forums or anywhere else on this site or our associated websites are not typical. Typical results for email marketing include 10-20% open rates with click-through rates of 0.25-1.5% and $0.50-$1 per subscriber per month in a moderately competitive niche like online coaching. When hiring Company to help achieve results, typical results are around 20-30% open rates with click-through rates of 0.25-3% and $1-3 per subscriber per month in a moderately competitive niche like online coaching. Typical results with or without Company's help vary by industry. If a person does not rely on fundamental marketing principles (outside of what Company teaches) in combination with the tactics shown, no results should be expected.

You have to do the work to get positive results. The reason that some people succeed more than others is that they have simply put forth more effort.

The majority of people who have had success in Online Marketing do not see success immediately. You may have to dedicate years worth of long workdays to see positive results.

Some products have guarantees or money-back guarantees. Please read more on each product to determine whether or not there is a guarantee. We want you to be happy.

Affiliate Disclosure

This affiliate disclosure details the affiliate relationships of Company with other companies and products.

Some of the links are "affiliate links", a link with a special tracking code. This means if you click on an affiliate link and purchase the item, we will receive an affiliate commission.

The price of the item is the same whether it is an affiliate link or not. Regardless, we only recommend products or services we have used or know the person behind the service. We only like recommending businesses that are run by people we know and trust.

By using the affiliate links, you are helping support the Service, and we genuinely appreciate your support.

External Links Disclosure

The Service may contain links to external websites that are not provided or maintained by or in any way affiliated with Company.

Please note that Company does not guarantee the accuracy, relevance, timeliness, or completeness of any information on these external websites.

Data Processing Addendum for InboxPro LLC's SMTP Service:


This Data Processing Addendum (the “DPA”) is entered into between InboxPro LLC, a Florida limited liability company (“InboxPro”), and the client identified in the applicable Email SMTP Agreement, Terms of Service, order form, or other agreement for the Services (“Client”). This DPA forms part of and is incorporated into that agreement (the “Agreement”) as of the effective date of the Agreement.

The Parties agree as follows:

1. DEFINITIONS

1.1. Applicable Data Protection Law means Regulation (EU) 2016/679 (the “GDPR”), laws implementing or supplementing the GDPR, and any other data-protection law that applies to the processing covered by this DPA.

1.2. Customer Personal Data. means personal data processed by InboxPro on behalf of Client in connection with the Services. It excludes data for which InboxPro independently determines the purposes and means of processing, including ordinary business-contact and billing information and the limited Service Protection Data described below.

1.3. Service Protection Data. means limited personal data that InboxPro processes for its own purposes to secure and protect the Services and shared sending infrastructure, investigate spam or abuse, maintain complaint and suppression records, prevent resending to recipients who opted out or complained, protect IP reputation, comply with law, and establish or defend legal claims.

1.4. Services means SMTP infrastructure, email transmission, deliverability support, event processing, performance and AI-assisted daily reporting, complaint and unsubscribe synchronization, optional email verification, and related support described in the Agreement.

1.5. Other Terms. “controller,” “processor,” “subprocessor,” “personal data,” “processing,” “data subject,” and “personal data breach” have the meanings given in Applicable Data Protection Law.

2. SCOPE, ROLES, AND INSTRUCTIONS

2.1. Applicability. This DPA applies when InboxPro processes Customer Personal Data as a processor or subprocessor in providing the Services.

2.2. Roles. Client is the controller and InboxPro is the processor of Customer Personal Data. If Client acts as a processor for another controller, Client appoints InboxPro as its subprocessor and represents that it is authorized to do so.

2.3. Documented Instructions. InboxPro will process Customer Personal Data only on Client’s documented instructions, including the Agreement, Client’s configuration and use of the Services, and written directions accepted by InboxPro. InboxPro will inform Client if it reasonably believes an instruction violates Applicable Data Protection Law, unless prohibited by law.

2.4. Client Responsibilities. Client is responsible for the lawfulness of its email activities, including its lawful basis, notices, consent where required, list acquisition, suppression practices, message content, and instructions to InboxPro. Client will not use the Services to process special-category data, protected health information, payment-card data, government identification numbers, or children’s data unless InboxPro expressly agrees in writing.

2.5. GHL and Other Client Systems. Where Client uses its own GoHighLevel or other CRM/ESP account, that provider is retained by Client and is not InboxPro’s subprocessor merely because the Services exchange data with it at Client’s direction. Where InboxPro provides or controls the applicable HighLevel subaccount or location, HighLevel is an InboxPro subprocessor for that use and is listed in Schedule 3.

2.6. Independent Controller Processing. InboxPro acts as an independent controller for Service Protection Data. That limited processing is outside the processor obligations of this DPA, but InboxPro will protect the data under Applicable Data Protection Law, restrict it to the stated purposes, and not use it to market to Client’s recipients.

3. PROCESSING OBLIGATIONS

3.1. Limited Purpose. InboxPro will process Customer Personal Data only as necessary to provide, secure, support, and troubleshoot the Services; transmit messages; generate delivery, engagement, and AI-assisted daily reporting; analyze sending patterns; process bounces, complaints, and unsubscribe events; synchronize status information with a CRM/ESP; perform optional verification; and comply with law.

3.2. No Sale or Independent Marketing. InboxPro will not sell Customer Personal Data or use it to advertise or market to Client’s recipients.

3.3. Confidentiality. InboxPro will ensure that personnel authorized to process Customer Personal Data are subject to confidentiality obligations and access it only as needed for their duties. Authorized access may include engineers and company or account managers with a legitimate need to operate or support the Services.

3.4. Legal Requirement. If law requires InboxPro to process Customer Personal Data contrary to Client’s instructions, InboxPro will notify Client before processing unless legally prohibited.

4. SECURITY AND PERSONAL DATA BREACHES

4.1. Security Measures. InboxPro will maintain appropriate technical and organizational measures designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access. Current measures are summarized in Schedule 2 and may be updated so long as the overall level of protection is not materially reduced.

4.2. Breach Notice. InboxPro will notify Client without undue delay and, where reasonably practicable, within seventy-two (72) hours after becoming aware of a confirmed personal data breach affecting Customer Personal Data. The notice will include available information reasonably necessary for Client to meet its legal obligations and may be provided in phases.

4.3. Cooperation and Escalation. InboxPro will take reasonable steps to contain, investigate, and remediate a personal data breach and reasonably cooperate with Client. Security incidents involving Customer Personal Data will be escalated to Troy Ericson at [email protected]. Notice of an incident is not an admission of fault or liability.

5. SUBPROCESSORS

5.1. General Authorization. Client generally authorizes InboxPro to use the subprocessors listed in Schedule 3 to process Customer Personal Data for the Services.

5.2. Changes. InboxPro will provide at least fifteen (15) days’ prior notice of a new or replacement subprocessor, including through email or an updated online subprocessor list. Client may object during that period on reasonable data-protection grounds. The Parties will work in good faith to resolve the objection. If no reasonable alternative is available, Client may terminate only the affected Services before the new subprocessor begins processing.

5.3. Flow-Down Obligations. InboxPro will impose written data-protection obligations on each subprocessor that are no less protective than the obligations applicable to InboxPro under this DPA, to the extent relevant to that subprocessor’s services. InboxPro remains responsible for its subprocessors as required by Applicable Data Protection Law.

6. ASSISTANCE AND DATA SUBJECT REQUESTS

6.1. Requests. Taking into account the nature of the processing, InboxPro will provide reasonable assistance to help Client respond to data-subject requests. If InboxPro receives a request relating to Customer Personal Data, InboxPro will direct the requester to Client unless law requires otherwise.

6.2. Technical Limitations. InboxPro can manually search certain active logs and tracking records by email address, message identifier, or tracking identifier. Some rolling log systems, including aggregated Loki chunks, are not designed for individual record deletion before expiration; those records expire under the retention periods in Schedule 1. InboxPro will provide assistance to the extent technically possible.

6.3. Compliance Assistance. Taking into account the nature of the processing and information available to InboxPro, InboxPro will reasonably assist Client with security obligations, breach notifications, data-protection impact assessments, and supervisory-authority consultations.

6.4. Costs. InboxPro may charge reasonable fees for unusually burdensome, repetitive, or out-of-scope assistance after advance notice, unless the assistance is required because of InboxPro’s breach of this DPA.

7. DATA MINIMIZATION, RETENTION, AND DELETION

7.1. Contact Systems. InboxPro’s SMTP infrastructure is not a CRM or the system of record for Client’s contact list. InboxPro does not maintain a separate hosted mailing-list database in the SMTP platform. Contact records may nevertheless be stored in HighLevel where Client uses an InboxPro-provided or controlled HighLevel subaccount or location.

7.2. Transmission and Queues. Recipient email addresses and message content are processed and temporarily stored in message queues or spool files while a message is awaiting delivery or retry. Message bodies are removed after terminal delivery or permanent failure and are not retained as a designed archive.

7.3. Operational Data. Recipient and sender addresses, subject lines, message identifiers, delivery and failure information, open/click/unsubscribe events, complaint data, tracking identifiers, hashed IP addresses, user-agent data, and similar logs may be retained for up to thirty (30) days. Reporting markdown failure records may be retained for up to seven (7) days. Webhook payloads are ordinarily processed and discarded without a durable store, apart from operational logs or alerts.

7.4. Operational Alerts and Suppression Records. Operational alerts in Slack and Discord may contain recipient addresses, subject lines, bounce, complaint, unsubscribe, delivery, or diagnostic information. Those alert records are deleted after ninety (90) days. InboxPro may retain complaint, unsubscribe, suppression, abuse-prevention, security, and IP-reputation records in other systems beyond the ordinary 30-day log period where reasonably necessary to prevent prohibited resending, protect shared infrastructure, investigate abuse, comply with law, or establish or defend claims. InboxPro will restrict access and use of retained records to those purposes.

7.5. Termination. After termination, InboxPro will delete Customer Personal Data from active processor systems according to the retention periods in Schedule 1, unless earlier deletion is technically feasible and requested by Client or law requires retention. Subject lines and other Customer Personal Data in the aggregate reporting database will be deleted or anonymized within ninety (90) days after termination; de-identified aggregate statistics may be retained. Service Protection Data and the limited operational records described in Section 7.4 may be retained for the purposes described there. Any retained data will remain protected and will not be used for unrelated purposes.

7.6. Aggregate Reporting Database. InboxPro stores campaign-level reporting records in a Heroku Postgres database hosted in the AWS us-east-1 region. The records may include subject lines, first and last sending timestamps, and aggregate delivery, open, click, bounce, and unsubscribe counts and rates. The MTA statistics API does not pass recipient addresses into this database, and the database does not contain message bodies, credentials, delivery logs, or recipient-level tracking records. Subject lines and other Customer Personal Data in this database may be retained while Client’s account is active and will be deleted or anonymized within ninety (90) days after termination. De-identified aggregate statistics may be retained after that period.

7.7. Backups and Managed Storage. InboxPro does not maintain a dedicated backup system for KumoMTA production data. Heroku Postgres storage is encrypted at rest using AES-256 block-level encryption managed through its underlying Amazon Web Services infrastructure. InboxPro does not apply separate Postgres-level encryption. Any Heroku-managed physical backup files are subject to Heroku’s managed backup and encryption controls.

8. INTERNATIONAL DATA TRANSFERS

8.1. Processing Location. The MTA and related production systems currently process data in the United States, principally on OVHcloud infrastructure in the Vint Hill, Virginia area. Aggregate reporting and automation data is hosted through Heroku in the AWS us-east-1 region. Customer Personal Data submitted to OpenAI may be processed in the United States and other locations disclosed by OpenAI. Customer Personal Data cannot currently be restricted to EU-only infrastructure. Authorized U.S.-based personnel may access the systems as necessary to provide and support the Services.

8.2. Transfer Mechanism. InboxPro will use a lawful transfer mechanism where Applicable Data Protection Law requires one. Where no adequacy decision or other valid mechanism applies, the European Commission Standard Contractual Clauses adopted by Implementing Decision (EU) 2021/914 (the “EU SCCs”) are incorporated into this DPA as described below.

8.3. EU SCC Configuration. Module Two applies when Client is a controller and InboxPro is a processor; Module Three applies when Client is a processor and InboxPro is a subprocessor. Clause 7 (docking) does not apply unless agreed in writing. For Clause 9, Option 2 (general written authorization) applies with the notice period in Section 5.2. The optional language in Clause 11 does not apply. For Clause 17, Option 1 applies and the governing law is the law of the EU Member State in which Client is established if that law permits third-party beneficiary rights; otherwise Irish law applies. For Clause 18(b), the courts corresponding to Clause 17 apply. Annex I is completed by Schedule 1, Annex II by Schedule 2, and Annex III by Schedule 3.

8.4. Binding Effect and Cooperation. Acceptance of the Agreement or this DPA constitutes binding acceptance of the applicable EU SCCs and the completed annexes. InboxPro will provide a completed copy on request. The Parties will reasonably cooperate on transfer assessments and supplementary safeguards where required.

9. INFORMATION AND AUDITS

9.1. Information. InboxPro will make available information reasonably necessary to demonstrate compliance with this DPA and Article 28 of the GDPR, including available policies, summaries, questionnaires, or independent reports.

9.2. Audit Procedure. No more than once annually, Client may request a reasonable remote audit or questionnaire on at least thirty (30) days’ notice. An on-site audit may occur only when reasonably required by a supervisory authority, a personal data breach, or material concerns not resolved through documentation. Audits must occur during normal business hours, minimize disruption, protect other customers’ information, and be subject to confidentiality. Client bears its audit costs unless the audit identifies a material breach by InboxPro.

10. TERM, PRIORITY, LIABILITY, AND CHANGES

10.1. Term. This DPA remains in effect while InboxPro processes Customer Personal Data.

10.2. Priority. If this DPA conflicts with the Agreement regarding processing of Customer Personal Data, this DPA controls. If the EU SCCs apply and conflict with this DPA or the Agreement, the EU SCCs control to the extent of the conflict.

10.3. Liability. The liability provisions of the Agreement apply to this DPA between the Parties, except to the extent prohibited by Applicable Data Protection Law or inconsistent with the EU SCCs. Nothing limits rights or remedies of data subjects or supervisory authorities that cannot lawfully be limited.

10.4. Governing Law. Except where the EU SCCs or Applicable Data Protection Law require otherwise, the governing-law and venue provisions of the Agreement apply.

10.5. Updates. InboxPro may update this DPA to reflect changes in law, the Services, subprocessors, or security practices, provided an update does not materially reduce Client’s data-protection rights during a current paid term. Material changes will be communicated through reasonable notice.

11. CONTACT AND ACCEPTANCE

11.1. Privacy Contact. Privacy, DPA, and security-notification communications should be sent to Troy Ericson at [email protected].

11.2. Acceptance. This DPA may be accepted by signature, electronic acceptance, or incorporation into the Agreement.

SCHEDULE 1

DETAILS OF PROCESSING AND TRANSFERS

Parties and roles

Data exporter/controller or processor: Client identified in the Agreement. Data importer/processor or subprocessor: InboxPro LLC, a Florida limited liability company. Privacy and security contact: Troy Ericson, [email protected].

Subject matter

SMTP infrastructure, email transmission, deliverability support, event and performance reporting, AI-assisted analysis and daily report generation, bounce and complaint processing, unsubscribe synchronization, optional email verification, HighLevel synchronization where applicable, and related support.

Duration

For the term of the Agreement and the retention periods below. Certain Service Protection Data may be retained beyond termination for suppression, anti-abuse, security, IP-reputation, legal-compliance, and claims purposes.

Nature and purpose

Receiving, queuing, transmitting, and delivering messages; collecting and displaying delivery and engagement events; analyzing sending patterns and generating daily reports; processing bounces, complaints, and unsubscribe requests; updating CRM records; verification; support; troubleshooting; security; and abuse prevention.

Data subjects

Client subscribers, leads, customers, prospective customers, and other recipients; Client users and administrators; and senders identified in message headers.

Personal data

Recipient and sender email addresses; contact fields stored in InboxPro-provided HighLevel subaccounts where applicable; subject lines; message body while queued or retried; message identifiers and headers; timestamps; delivery status and errors; bounce, complaint, unsubscribe, open, and click events; tracking identifiers; partial clicked URLs; hashed IP addresses; user-agent/device data; aggregate campaign metrics; credentials and tokens; and support or diagnostic content.

Special categories

The Services are not designed for special-category data, criminal-conviction data, protected health information, payment-card data, government identifiers, or children’s data. Client must not intentionally submit such data without prior written approval.

Frequency

Continuous or recurring, as initiated by Client’s use of the Services.

Retention

Queue/spool: until terminal delivery or permanent failure. Message bodies: removed after terminal disposition. Operational, tracking, complaint, unsubscribe, and application logs: up to 30 days. Reporting markdown failures: up to 7 days. Slack and Discord operational alerts: 90 days. Heroku aggregate reporting records: during the active account; subject lines and other Customer Personal Data deleted or anonymized within 90 days after termination, while de-identified aggregate statistics may be retained. Emailable verification data: according to configured settings and no later than 30 days after verification. OpenAI API data: according to the configured endpoint and data-control settings; standard abuse-monitoring logs may be retained for up to 30 days. Service Protection Data: for as long as reasonably necessary for the purposes in Sections 1.3, 2.6, and 7.4.

Processing locations

United States. Primary MTA location: OVHcloud, us-east-vin / vin1, Vint Hill, Virginia area. Aggregate reporting database: Heroku on AWS us-east-1. OpenAI processing: United States and other locations disclosed by OpenAI. No EU-only hosting option is currently available.

Transfers

Transfers from the EEA to InboxPro are supported by the applicable EU SCC module unless another lawful transfer mechanism applies. Transfers to subprocessors are subject to applicable contractual and transfer safeguards.

Supervisory authority

The supervisory authority determined under Applicable Data Protection Law and, where the EU SCCs apply, Clause 13 of the EU SCCs, ordinarily Client’s lead or local supervisory authority.

SCHEDULE 2

TECHNICAL AND ORGANIZATIONAL MEASURES

Encryption in transit

HTTPS/TLS is used for web-based transmission. SMTP TLS is used for message transmission where supported and configured by communicating systems.

Encryption at rest

Production storage containing Customer Personal Data is encrypted at rest where supported by the applicable platform. Heroku Postgres uses AES-256 block-level storage encryption managed through Amazon Web Services. InboxPro does not apply separate Postgres-level encryption to the aggregate reporting database.

Authentication

Multi-factor authentication is required for privileged production and administrative access.

Access controls

Access is restricted to authorized personnel with a business need. Engineers and company/account managers have separate access levels. Least-privilege controls are partially implemented and are supplemented by role separation, administrative logging, and periodic access reviews.

Logical separation

The Services use shared infrastructure with logical tenant routing and controls designed to prevent one client from accessing another client’s data.

Credentials and secrets

SMTP credentials are protected using Ansible Vault with AES-256 and deployed to server authentication stores. Other credentials and tokens may be stored in vaults, environment variables, server files, or Bitwarden. Access is limited to authorized operators. Secrets are not intentionally written to logs.

Logging and monitoring

Self-hosted Loki, Prometheus, and Grafana and related administrative logs are used to monitor service health, delivery failures, abuse, and security events. Operational logs are generally retained for up to 30 days.

Data minimization

Message bodies are retained only while queued or retried and removed after terminal disposition. Webhook payloads are ordinarily processed and discarded without a separate durable store. Full clicked URLs are not retained; only partial or sanitized URL information is stored. The MTA statistics API does not pass recipient addresses into the aggregate Heroku reporting database.

Incident response

Prometheus/Alertmanager sends operational alerts to Slack and Discord. InboxPro maintains processes to investigate, contain, remediate, document, and notify affected clients of confirmed personal data breaches. Customer-data incidents are escalated to Troy Ericson at [email protected].

Vendor management

Subprocessors are subject to contractual confidentiality, data-protection, and security obligations appropriate to their services, including transfer safeguards where required.

Backups and recovery

No dedicated backup system is currently used for KumoMTA production data. Heroku Postgres uses managed, encrypted block-level storage. Any Heroku-managed physical backups are subject to Heroku’s managed backup, regional storage, and encryption controls.

SCHEDULE 3

AUTHORIZED SUBPROCESSORS

OVHcloud (applicable contracting affiliate)

Purpose and data: Dedicated bare-metal hosting, IP addressing, network, firewall, storage, and production infrastructure. May process all MTA data at rest and in transit, including queued message content and operational logs.

Location: United States - us-east-vin / vin1, Vint Hill, Virginia area

Slack Technologies, LLC

Purpose and data: Operational alerts and internal support communications, including delivery failures, bounce, complaint, unsubscribe, and security notifications that may contain recipient addresses and message metadata. Relevant alert records are deleted after 90 days.

Location: United States / global infrastructure

Discord Inc.

Purpose and data: Operational alerting and webhook notifications that may contain delivery or complaint metadata and, in some cases, email addresses. Relevant alert records are deleted after 90 days.

Location: United States / global infrastructure

HighLevel, Inc.

Purpose and data: CRM contact lookup, contact storage, engagement-field updates, complaint/unsubscribe synchronization, and SMTP injection where InboxPro provides or controls the applicable HighLevel subaccount or location. Not an InboxPro subprocessor when Client independently owns and controls its HighLevel account.

Location: United States and other locations disclosed by HighLevel

EMAILABLE LLC

Purpose and data: Optional email verification. Processes full recipient email addresses and verification results. Retention is configurable, and verification data is permanently deleted no later than 30 days after verification.

Location: United States

Google LLC (Google Workspace/Gmail)

Purpose and data: Inbound processing of Yahoo ARF complaint messages and related operational email. Complaint messages may contain recipient and sender addresses, subject lines, and complaint metadata.

Location: United States / global infrastructure

Salesforce, Inc. (Heroku)

Purpose and data: Managed Heroku Postgres database for aggregate campaign reporting and automation/product workflows. May process subject lines, sending timestamps, aggregate delivery/open/click/bounce/unsubscribe counts and rates, account metadata, and automation metadata. The MTA statistics API does not pass recipient addresses into this database. Subject lines and other Customer Personal Data are deleted or anonymized within 90 days after termination; de-identified aggregate statistics may be retained.

Location: United States - AWS us-east-1

OpenAI OpCo, LLC (and affiliates, as applicable)

Purpose and data: AI-assisted analysis of sending patterns and generation of daily reports. May process recipient email addresses, subject lines, sender information, delivery and engagement events, bounce/complaint/unsubscribe data, message metadata, aggregate metrics, prompts, and model outputs. Under standard API controls, abuse-monitoring logs may be retained for up to 30 days; endpoint-specific application-state and approved data-retention settings may differ.

Location: United States and other locations disclosed in OpenAI’s subprocessor list

Not subprocessors merely because their software is used: KumoMTA, SQLite, Loki, Prometheus, Grafana, Caddy, Redis/BullMQ, and other self-hosted software are not listed when operated entirely on InboxPro-controlled infrastructure and their vendors cannot access Customer Personal Data.

Return To Top