1. The project and its public demo
SignalHub is an open-source project maintained by an individual developer. Its public trial and demo instance is operated by Ramesh Maharaddi (the maintainer or operator; references to we and us mean that individual), based in Singapore. SignalHub is the project name, not a separate company. Public support and privacy contact: support@signalhub.at.
These terms govern use of the public demo, including trial accounts, workspaces, monitoring, status pages and notifications. By accepting them when registering or creating a demo workspace, you agree to them for that instance. The privacy notice explains how demo information is handled; acknowledging it is not blanket consent to every use of personal data.
2. Evaluation first; self-host for ongoing use
The public instance is provided free so you can try SignalHub before downloading and self-hosting it. It is an evaluation environment, not a managed production-hosting offering. Do not use it for production monitoring, business-critical status communications, live customer subscriber lists or storing information you cannot afford to lose. Use fictional sample content, test systems you control, and test recipients who agree to participate. Account verification requires a working email address; avoid putting real personal information, passwords or private credentials in demo content.
Demo features, availability and capacity may change. Demo workspaces and their content may be reset or removed for maintenance, testing, abuse prevention or resource management. We will give reasonable notice where practicable; urgent issues may require immediate action. Do not treat the demo as a backup or expect permanent storage. No particular automatic reset schedule is promised.
For ongoing use, download SignalHub and run it on infrastructure you control. These demo terms do not impose additional conditions on using, modifying or distributing the source code under Apache-2.0. A self-hosted operator is responsible for deployment, security updates, access controls, backups, providers and its own terms and privacy notices. Running a copy does not make the maintainer its hosting provider or create an obligation to administer it. Project support is provided as availability permits, without a guaranteed response time.
3. Eligibility and organizational authority
You must be at least 18 and legally able to enter this agreement. If you act for a business or other organization, you confirm that you have authority to bind it, and references to you include that organization. Do not register using another person's identity or misleading organizational details.
Workspace administrators manage invitations, roles, content and integrations for their organization. They must ensure that members are authorized and follow these terms. Joining a workspace does not give you ownership of its content or permission to act outside your assigned role.
4. Account security and access
Provide accurate account information, keep your email address current, protect passwords, recovery codes, API keys and integration secrets, and use the available security controls. Do not share individual sign-in credentials. Revoke access when a member no longer needs it, and notify us promptly of suspected unauthorized use.
You are responsible for activity you authorize and for reasonable steps to protect your account. We may verify identity or authority before restoring access or acting on sensitive requests. Account recovery may be delayed or refused if ownership cannot reasonably be established; it is not a guaranteed bypass of multi-factor authentication.
5. Free demo and usage limits
The public demo is free. Its current technical limits are 10 pages, 50 monitors, 10 members and 1,000 subscribers per workspace, with monitor intervals starting at 60 seconds. These are evaluation limits, not a promise of production capacity or permission to import live customer lists. Pending invitations and unverified subscriptions can count toward limits. An account may create one workspace and join others by invitation.
The shared delivery allowance is 25 combined email and SMS sends per calendar month, resetting at 00:00 UTC on the first day. Each recipient and provider retry counts; subscription verification codes and tests count. Account-security email is separate. Delivery remains subject to configuration, provider availability and platform controls.
Limits protect demo capacity and may be enforced by rejecting, pausing or restricting requests. Do not evade them through duplicate accounts, automated registrations or other circumvention. The trial does not create a paid subscription, require a purchase or automatically convert to a paid service.
6. Authorized monitoring and safe use
Monitor only systems you own or are authorized to test, and use intervals and request volumes permitted by their owners. You are responsible for the targets, credentials, headers and other settings you supply. Monitoring can generate network traffic and requests to third-party infrastructure. Do not configure requests that change or damage a target unless you have explicit authorization and understand their effects.
Do not bypass network restrictions, probe internal infrastructure without permission, scan for unauthorized access, harvest credentials, distribute malicious code, disrupt services, or interfere with other workspaces. The service is not a penetration-testing authorization or a substitute for your own security review.
7. Acceptable use and public content
Do not use the service for unlawful activity, fraud, harassment, impersonation, infringement, unsolicited messaging, or publishing information you have no right to disclose. Do not upload highly sensitive personal information into status messages or monitor responses, or expose passwords, private keys or access tokens in public content.
You choose what to publish and who may view it. Public pages, incidents, metrics and announcements may be copied, indexed or retained by others. Access restrictions reduce exposure but do not prevent authorized viewers from sharing information. Check page visibility and audience settings before publishing.
8. Subscribers and communications
Test notification features only with contact methods you control or recipients who have agreed to help evaluate the demo. Email, SMS and configured integrations can send real messages; a demo label does not make delivery simulated. Do not import production subscriber lists.
Before collecting or importing subscriber contact information, establish the permissions and legal basis required for the intended messages and publish an accurate workspace privacy notice. Maintain evidence where required, honor unsubscribe and privacy requests, and do not use operational status subscriptions for unrelated marketing.
You are responsible for your message content, recipient lists, sender identity and applicable messaging rules. Verification codes confirm access to a contact method; they do not establish every permission required by law. We may restrict messaging that creates abuse, complaint or provider-policy risks.
9. Your content and our permission to process it
You retain your rights in the content and data you supply. You grant the operator a non-exclusive permission to host, store, reproduce, process, transmit and display that material only as needed to provide, secure and support the service, follow your settings and instructions, and meet legal obligations. This includes transmission to configured delivery and integration providers.
You confirm that you have the rights and permissions necessary for that processing. This permission does not transfer ownership or grant a right to sell your content. It ends when the relevant content is removed, except for retained records and backups described in the privacy notice or records that law requires us to keep. Copies already delivered to recipients are outside our control.
10. Software, brands and third-party services
These terms govern access to the public demo. Rights to use, modify and distribute the open-source software remain governed by its Apache-2.0 license and applicable dependency licenses, including their warranty and liability provisions. These demo terms do not revoke or replace those licenses or grant trademark rights. Downloading the project does not require a demo account.
Names, logos and content belonging to others remain subject to their owners' rights. A reference to an integration, protocol or provider describes compatibility or functionality, not sponsorship, endorsement or affiliation. Do not imply that your workspace or status page is operated or endorsed by an organization without its permission.
Third-party hosting, identity, email, SMS, webhook and other services may have separate terms and policies. You are responsible for integrations you choose and configure. We do not control independent providers or guarantee their continued availability, but remain responsible for our own obligations under this agreement and applicable law.
11. Monitoring accuracy and availability
Monitoring is based on observations at particular times and locations. Results may be incomplete, delayed or incorrect because of network conditions, configuration, capacity, software faults or third-party failures. Notifications may be filtered, blocked, delayed, duplicated or not delivered. A successful check is not a guarantee that a system is secure or available to every user.
The demo includes no contractual uptime guarantee, response-time commitment, managed support or service credits. It is not intended for production operations. Self-host for ongoing use and arrange your own monitoring and backups. Do not rely on the demo for detecting a critical outage, protecting life or safety, or delivering emergency communications.
12. Changes to the service and these terms
We may maintain, repair or improve the service and adjust features or capacity limits for operational, security or legal reasons. For a material reduction or discontinuation, we will give reasonable advance notice where practicable and a reasonable opportunity to export available data. Urgent security issues, abuse or legal requirements may require immediate action.
Material changes to these terms will be identified by a new version and effective date and communicated through the service or your account contact where reasonably possible. Changes apply prospectively. Where agreement is required, we will obtain it before applying the changed terms to you. If you do not agree, you may stop using the service and request closure.
13. Suspension and termination
We may restrict or suspend affected features or accounts for a material breach, suspected compromise, abuse, unlawful content, serious risk to the service or others, or a binding legal requirement. We will use a proportionate response and explain the reason and steps to resolve it where practicable, unless doing so would compromise security or be prohibited by law.
We may terminate access for a serious or repeated breach, or an unresolved material breach after a reasonable opportunity to remedy it. Contact us to question a restriction. You may stop using the service at any time and use available workspace deletion or privacy-request controls, or contact the operator, to request closure. Workspace administrators should address ownership and export needs before deleting shared data.
14. Exports, retention and deletion
Keep independent copies of any test information you need. Demo monitoring, metrics, analytics and delivery history use retention windows of up to 90 days; this is not a minimum storage commitment and a demo reset or deletion can remove data sooner. Other data follows different retention rules. Available exports are time-limited and may not include every internal record or third-party copy. Request exports before closure or the end of a retention window.
Deletion can remove access and cannot necessarily be reversed. Some security, acceptance, consent, dispute and legal records may be retained for justified periods, and backups may expire on a separate cycle. The privacy notice describes these distinctions. We do not promise indefinite storage or immediate removal from all backups and recipients.
15. Warranties and responsibilities
Except for obligations expressly stated in these terms or imposed by law, the free service is provided on an as-available basis. We do not promise uninterrupted or error-free operation, perfect detection, successful delivery of every notification, or suitability for a particular critical use. You remain responsible for evaluating the service and your configuration for your needs.
These statements do not exclude any legally required standard of care, binding express promise, or warranty or remedy that cannot lawfully be excluded. They do not excuse us from our own security and data-protection duties.
16. Limits of liability
For business use, and where permitted by applicable law, neither party is liable under this agreement for indirect or consequential losses, including indirect loss of profit, revenue, business opportunity or goodwill. Responsibility for other loss depends on the applicable law, the breach, causation and reasonable steps to mitigate loss; these terms do not create a promise to insure your operations against outages.
Nothing excludes or limits liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence, deliberate misconduct, or any other liability or statutory remedy that applicable law does not permit the parties to exclude or limit. Consumer rights, where applicable, remain protected. No zero-liability rule follows merely because the service is free.
You remain responsible for claims arising from content you supply or unlawful conduct you authorize, to the extent you are legally responsible. This does not make you responsible for the operator's own wrongdoing or create an unlimited indemnity.
17. Disputes, notices and general provisions
Contact support@signalhub.at with a description of a concern so the parties can try to resolve it. These terms do not select a governing law or court. Any dispute is subject to the laws and courts that apply to it. These terms impose no mandatory arbitration or class-action waiver.
If a provision is unenforceable, the remaining provisions continue to the extent they can operate lawfully. A delay in enforcing a right does not waive it. Neither party may transfer this agreement in a way that reduces the other's mandatory rights. These terms describe the public-demo agreement; they do not override applicable open-source licenses or mandatory law.
Send contractual, abuse, intellectual-property and privacy concerns to Ramesh Maharaddi at support@signalhub.at. Operator location: Singapore. Include enough information to identify the affected account, page or material without sending passwords or private keys.