Service terms · version 1.0
Clear boundaries for a read-only reliability service.
Updated 7 September 2026. These terms govern access to the free StackFirefly beta, Firefly Agent, trial, Free plan, and non-binding plan reservations.
1. Agreement and eligibility
These terms apply when a person creates an account, joins a workspace, installs or pairs the Firefly Agent, or uses the StackFirefly beta. The person accepting them confirms that they have legal capacity and, when acting for an organization, authority to bind that organization.
StackFirefly is designed for WordPress developers, agencies, WooCommerce operators, and technically capable site owners. Users must be authorized to monitor every site and environment they connect.
2. Service scope
StackFirefly monitors supported WordPress sites through independent probes and the Firefly Agent. It detects, diagnoses, recommends, and verifies; it does not automatically modify WordPress, plugins, themes, databases, hosting, DNS, Cloudflare, or other customer systems.
Capability depends on the installed Agent, WordPress and PHP versions, hosting environment, plan entitlement, and available evidence. States such as unavailable, unsupported, paused, stale, and unknown are not promises of healthy operation.
3. Accounts, workspaces, and security
Users must provide accurate account information, keep credentials and recovery codes secure, use individual accounts, maintain current contact details, and promptly revoke access that is no longer needed. Workspace owners control membership and are responsible for assigning suitable roles.
A user must notify security@stackfirefly.com when they reasonably suspect unauthorized account, workspace, Agent, or site access. StackFirefly may require email verification, recent authentication, or multi-factor authentication for sensitive actions.
4. Firefly Agent and site authorization
The Firefly Agent is licensed for use with the StackFirefly service; it is not sold. Users may install it only on WordPress sites they are authorized to administer. Pairing creates a scoped identity for that site and does not give StackFirefly WordPress administrator credentials or general remote-control access.
Users are responsible for WordPress backups, update decisions, compatibility checks, and safely removing or revoking the Agent when access ends. They must not modify the Agent to impersonate another site, forge evidence, evade limits, or access another workspace.
5. Beta, trial, Free plan, and reservations
Beta access is provided without a contractual SLA. The planned 15-day no-card trial starts on the first successful site pairing. Without an eligible reservation, the workspace falls back to the constrained one-site Free plan when the trial ends; excess sites are paused rather than deleted.
A plan reservation records non-binding interest in a named future plan and planned price. It is not a purchase or subscription, collects no payment instrument, and authorizes no current or future charge. Paid service can begin only after the final merchant identity, price, tax, billing period, cancellation terms, and contract are presented and the user separately accepts and authorizes payment.
6. Acceptable use
Users must not use StackFirefly to:
- monitor, scan, or probe systems without authorization;
- upload secrets, authentication material, customer records, raw dumps, or malicious content;
- bypass rate limits, tenant boundaries, authentication, or security controls;
- interfere with the service, other users, providers, or connected systems;
- reverse engineer the service where restriction is permitted by applicable law, or misuse interfaces outside documented purposes;
- use results as proof of legal compliance, security certification, or guaranteed availability.
7. Monitoring data, privacy, and confidentiality
StackFirefly processes account and minimized operational data to provide and secure the service. The Privacy notice describes the categories, purposes, retention, deletion, and user choices. Users must configure sites and submissions so prohibited secrets, personal data, form contents, order records, and complete response bodies are not sent.
Each party must protect non-public information received through the beta using reasonable care and use it only for the service relationship, except where disclosure is authorized or legally required.
8. Incidents, diagnosis, and AI guidance
Deterministic checks establish health states and recovery. Incident correlation, probable causes, and AI-assisted explanations may be incomplete or incorrect and must be evaluated against the displayed evidence. AI cannot independently establish health, open or close an incident, access a customer system, or authorize a change.
Recommendations are informational technical guidance, not a substitute for qualified security, legal, accounting, hosting, or engineering advice. Users decide whether and how to investigate or apply changes.
9. Third-party services and dependencies
WordPress, hosting providers, DNS, Cloudflare, email providers, OAuth providers, external probes, and other integrations are controlled by third parties. Their availability and terms are separate from StackFirefly. A third-party failure may limit evidence or service operation without establishing liability or causality by itself.
10. Human expert help
A request for WordPress expert help is separate lead intake, not an included monitoring feature or authorization to access or modify a site. Submitting a request is free. Any paid consulting or development requires a separate written scope, quote, terms, and explicit acceptance.
11. Intellectual property and feedback
StackFirefly, its software, branding, documentation, and service design remain owned by their applicable rights holder. Users retain ownership of their sites and submitted content. A user grants only the limited rights necessary to process authorized data and operate the service.
Feedback may be used to improve StackFirefly without payment or a duty to implement it, provided confidential information and personal data continue to be protected.
12. Changes, suspension, and termination
Beta features, limits, and availability may change as the product is tested. Material terms changes should be communicated in clear language before they take effect, with any consent required by applicable law. StackFirefly may restrict or suspend access to protect users, providers, or the service; address abuse or legal requirements; or respond to security and capacity risks.
Users may stop using the beta, disconnect Agents, cancel plan reservations, and request workspace deletion through available account controls. Termination does not convert a reservation into a charge and does not erase records that must be retained for security, disputes, or law under the published retention policy.
13. Customer responsibility
Monitoring and diagnosis are not backups, a firewall, malware removal, hosting management, or guaranteed prevention. Customers remain responsible for administration, backups, change control, professional judgment, and validating actions before applying them.
14. Availability, warranties, and liability
The beta may contain defects, interruptions, delayed alerts, incomplete evidence, or unavailable capabilities and is provided without a contractual service-level commitment. Nothing in these terms excludes rights, remedies, guarantees, or liability that cannot lawfully be excluded or limited.
To the extent permitted by applicable law, StackFirefly is not responsible for indirect or consequential loss caused solely by reliance on beta monitoring or guidance instead of appropriate backups, administration, or professional review. This does not exclude liability for fraud, wilful misconduct, or any responsibility that applicable law does not permit the operator to exclude or limit.
15. General terms and contact
These terms are governed by Romanian law, without depriving consumers of mandatory protections available under the law of their habitual residence. Courts and dispute procedures are determined by applicable law. Questions and notices may be sent to support@stackfirefly.com.
If part of these terms is unenforceable, the remaining parts continue to apply. A failure to enforce a term is not a waiver. Users may not assign their account or obligations without permission; the operator may transfer the service and these terms to a future business entity that assumes the same obligations, with advance notice where required. These terms, the Privacy Notice, Beta Terms, and any expressly accepted workspace or plan terms form the agreement for the beta.
