Privacy Policy

1. Agreement

This Privacy Policy explains what information MarionetteOps.com, also referred to as "MarionetteOps", "we", "us", or "our", collects from people and organizations that visit the website, create an account, install an agent, use the dashboard, API, alerting tools, status pages, reports, or other MarionetteOps services.

By using MarionetteOps, you acknowledge that you have read and understood this Privacy Policy. If you use MarionetteOps on behalf of an organization, this policy applies to the information submitted through that organization's account.

The "service" means the MarionetteOps website, API, agents, dashboards, monitoring checks, notifications, public status pages, reports, billing tools, support workflows, and related operational features.

2. Information We Collect

2.1 Account and authentication data

When you create or use an account, we may collect your name, username, email address, password, organization membership, login credentials, account preferences, API keys, session data, email verification status, password reset events, and related account security records.

When signup, login, password reset, verification, account setting, API key, and other account forms are processed, we may record technical context such as IP address, approximate country or region, browser details, request time, and security signals needed to protect the service.

2.2 Monitoring and service data

You may provide monitoring targets and operational details such as hostnames, URLs, IP addresses, ports, SSL certificate details, cron endpoints, monitor names, labels, status page content, public uptime report settings, agent pairing tokens, agent reports, system metrics, error messages, response times, status codes, maintenance windows, thresholds, and incident history.

You may also provide notification contacts and delivery destinations such as email addresses, phone numbers, webhook URLs, chat or incident-management integrations, escalation settings, and do-not-disturb schedules.

2.3 Billing, support, and communications

If you use paid services, we may collect billing plan, invoice, transaction, tax, organization, and payment status information. Payment card or bank details may be processed by our payment providers rather than stored directly by MarionetteOps.

When you contact us, we may collect support messages, sales inquiries, troubleshooting context, attachments, and any contact details you choose to provide.

2.4 Analytics and website data

With your consent, we may collect website analytics, referral information, page views, registration attribution, device and browser details, and similar usage data to understand how people find and use MarionetteOps. We may use analytics providers or self-hosted analytics tools for this purpose.

2.5 Cookies, consent, and local storage

We use strictly necessary first-party cookies and sessions to keep you signed in, preserve session integrity, protect against abuse, and operate core service features. The PHP session cookie, commonly named PHPSESSID, is an essential first-party session cookie. It is not treated as a third-party advertising or analytics cookie, and it is required for secure account and form workflows.

Optional analytics and registration-attribution scripts are not loaded unless you accept analytics cookies and similar technologies in the consent banner. If you reject analytics, MarionetteOps does not load the analytics script from analytics.johnqdeveloper.com or the registration-attribution script, and stored attribution data is removed where browser storage is available.

You can withdraw or change analytics consent at any time by selecting "Cookie Settings" in the footer or floating settings control and choosing "Reject analytics." You can also clear MarionetteOps site data in your browser. Authentication, security, billing, monitoring, alerting, and account-service communications may still require essential cookies or similar technologies.

Some authentication pages may load Cloudflare Turnstile to distinguish legitimate users from automated abuse. Turnstile is used for security and fraud prevention, not analytics profiling.

3. Use of Information

3.1 How we use information

We use collected information to provide and operate MarionetteOps, including account access, monitoring checks, agent pairing, dashboards, status pages, reports, alerts, notification delivery, billing, support, abuse prevention, security monitoring, troubleshooting, service improvement, and legal compliance.

• Identify you and keep your account secure.
• Run uptime, cron, server, SSL, status page, and reporting features.
• Send alerts, reports, account messages, billing notices, verification messages, and important service announcements.
• Investigate errors, outages, suspicious activity, abuse, payment issues, and security events.
• Improve reliability, usability, performance, plan limits, documentation, and customer support.

3.2 How we do not use information

We do not sell your private account data, monitoring data, notification contact data, or payment-related data. We do not use your private data to send spam.

No mobile information, text message opt-in data, or messaging consent information is shared with third parties or affiliates for marketing or promotional purposes.

4. Sharing and Disclosure

We may share limited information with service providers that help us operate MarionetteOps, such as payment processors, email and notification providers, analytics providers, infrastructure providers, error monitoring tools, customer support tools, and security vendors. These providers may access information only as needed to perform services for us.

We may disclose information when required to comply with law, regulation, legal process, court order, governmental request, enforceable platform rules, security investigations, fraud prevention, or to protect the rights, safety, and property of MarionetteOps, our users, or others.

If MarionetteOps is involved in a merger, acquisition, financing, reorganization, asset sale, or similar transaction, information may be transferred to a successor or prospective successor as part of that transaction, subject to appropriate confidentiality and privacy protections.

Public status pages, public uptime reports, shared incident pages, or other public features may display the content and availability information you choose to publish. You are responsible for the data you make public through those features.

5. Security of Information

We use administrative, technical, and organizational safeguards designed to protect user information, including limited access controls, encrypted connections where appropriate, password hashing, secret handling practices, audit and activity logs, monitoring, and least-privilege access for critical systems.

No internet service can guarantee perfect security. You are responsible for protecting your password, API keys, pairing tokens, webhook secrets, and account access devices, and for limiting access to trusted users within your organization.

6. Retention

We retain information for as long as needed to provide the service, comply with legal and billing obligations, resolve disputes, maintain security, enforce agreements, and operate backups. Different categories of data may have different retention periods.

Some short-lived operational logs, such as account activity or request metadata, may be retained for a limited period. Monitoring history, reports, alert logs, billing records, and support records may be retained longer when required for service functionality, accounting, security, or legal reasons.

When you delete monitors, agents, notification contacts, status pages, organizations, or account data, we may remove or anonymize the active record while retaining backups, audit records, billing records, or security logs for a reasonable period.

7. Your Choices and Rights

You can update many account details, notification contacts, monitors, status pages, preferences, and organization settings from your dashboard. You can also remove optional monitoring targets, notification destinations, public page content, and API keys when you no longer need them.

You may request access, correction, deletion, export, or restriction of your personal information by contacting support. We may need to verify your identity and may retain information where required for security, legal, billing, or legitimate operational reasons.

If privacy laws such as the GDPR, UK GDPR, CCPA, or similar laws apply to your use of MarionetteOps, you may have additional rights under those laws. We will respond to applicable privacy requests according to the requirements that apply to MarionetteOps and your account. You can read more on our GDPR Compliance and California Privacy Rights pages.

You can unsubscribe from non-essential marketing messages where an unsubscribe option is provided. We may still send transactional or service-related messages, including security, billing, alerting, verification, support, and policy notices.

8. Children

MarionetteOps is intended for business and technical operations use and is not directed to children. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to MarionetteOps, please contact us so we can review and take appropriate action.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Updated versions apply when posted on this page, unless a later effective date is stated. Please review this page periodically so you remain familiar with our current privacy practices.

10. Contact

Privacy questions, account requests, and support inquiries can be sent to support@johnqdeveloper.zendesk.com.

Sales and plan questions can be sent to support@johnqdeveloper.zendesk.com.