Terms of Service

Draft for testing · Updated 1 October 2026

These draft terms cover the test service. Commercial terms and production operating arrangements remain to be finalised.

ChirpHop is operated by Protologic Solutions Private Limited. Questions can be sent to kamal@protologicsln.com.

Using the service

Use ChirpHop only for business accounts, workspaces and recipient data you are authorised to manage. Keep account credentials private and assign team access carefully. Workspace owners control membership and shared resources.

Messaging responsibilities

You are responsible for recipient permissions, message content and compliance with applicable laws and the rules of your messaging provider. Do not use the service for spam, deception, harassment, unlawful content, unauthorised data collection or attempts to evade provider restrictions. Honour recipient requests to stop receiving messages.

Messaging integrations

The official API connection is subject to Meta's approval, permissions, template rules, limits and charges. The separate linked-device integration is not the official Meta API and may stop working or lead to account restrictions. ChirpHop cannot guarantee that any messaging account will remain available.

Campaign outcomes

A submitted message means the integration returned a message identifier; it does not by itself establish delivery or reading. An uncertain outcome may require checking the recipient conversation before retrying to avoid duplicate messages. Scheduling depends on server availability and an operational connection.

Your data

You retain your rights in content you provide and authorise its processing as needed to operate the features you use. Shared workspace data may be visible to other authorised members. Our Privacy Policy describes current data handling and the deletion request process.

Test availability and charges

The service is under development. Features can change, outages can occur, and production availability or support response times have not been promised. Any paid ChirpHop plan requires separate pricing and acceptance. Charges from Meta or other providers are separate from ChirpHop fees.

Suspension and ending use

Access may be restricted to investigate misuse or protect the service. You can stop using ChirpHop and request removal of your account or authorised workspace data. Removing a connection does not automatically erase records already stored or messages already sent.

Before production use

Final commercial terms, support commitments and any applicable liability and dispute provisions must be agreed before a paid production launch. Nothing in these draft terms is intended to remove rights that cannot legally be excluded.