Review the baseline usage terms, responsibilities, acceptable use expectations, and service boundaries for NeptunePro LeadGEN.
These terms describe the expected use of the platform, acceptable behavior, customer responsibilities, and important limitations around service delivery.
Users are expected to use the service lawfully and in accordance with applicable platform, data, outreach, privacy, and anti-spam rules.
Access may be restricted, suspended, or removed if use creates operational, legal, reputational, or security risk for the platform or other users.
Customers are responsible for reviewing their own campaign practices, outreach compliance, destination systems, and regulatory obligations before deployment.
Customers are also responsible for the quality and legality of the data sources, automations, and outbound workflows they choose to operate.
Features, support availability, pricing, implementation details, and technical integrations may evolve as the platform improves over time.
We may update or refine functionality to improve reliability, security, maintainability, and customer experience.
Paid plans, trial periods, billing cycles, cancellations, and refunds are governed by the applicable pricing and refund terms shown on the site or in your account workflow.
Failure to pay for a paid plan may result in suspension or limitation of access until the billing issue is resolved.
The platform is provided on an as-available basis. While we aim for reliability, uptime, and support responsiveness, we cannot guarantee uninterrupted availability in all circumstances.
Customers should maintain their own operational review processes and should not rely on the platform as the sole control point for critical business or compliance decisions.
Continue exploring the platform, policies, and setup guidance.
Short answers to common questions related to this page.
Yes. Customers are responsible for reviewing their own outreach practices, destination systems, and regulatory obligations before deployment.
Yes. Features, integrations, support details, and implementation patterns may evolve as the platform improves.