Privacy Policy

1. Information We Collect

We collect information that you provide directly, information generated through your use of the Services, and information obtained from authorized third-party services.

1.1 Account and Registration Information

When you create or manage a MonitorCTL account, we may collect:

• Full name and display name.
• Email address and email verification status.
• Organization or company name.
• Account username and unique account identifier.
• Authentication credentials or securely processed authentication information.
• Account preferences and profile settings.
• Organization membership and assigned roles.
• Subscription and billing-related information.
• Account creation, login, and activity timestamps.

We use this information to create accounts, authenticate users, manage organizations, provide access to monitoring services, and maintain account security.

1.2 Google Sign-In Information

MonitorCTL supports signing in using a Google account through Google’s OAuth 2.0 and OpenID Connect authentication services.

For standard Google Sign-In, MonitorCTL may request the following permissions:

• openid: Allows MonitorCTL to authenticate your Google identity and receive a unique account identifier.
• email: Allows MonitorCTL to access your Google account email address and email verification status.
• profile: Allows MonitorCTL to access basic profile information, such as your name and profile picture, where available.

Depending on the information Google provides, MonitorCTL may receive:

• Your Google account name and display name.
• Your Google email address.
• Your email verification status.
• Your unique Google account identifier.
• Your Google profile picture URL, where available.
• Authentication-related information necessary to establish a secure session.

How Google Information Is Used: We use this information exclusively for supported account authentication, account creation or linking, user identification, session management, account administration, security, and related user-facing functionality.

We do not receive or store your Google account password.

Standard Google Sign-In does not grant MonitorCTL access to your Gmail messages, Google Drive documents, Google Calendar, Google Contacts, or other Google Workspace content.

If we introduce optional features that require additional Google API permissions, we will disclose the additional information requested, explain its intended use, and obtain any required authorization before accessing it.

1.3 Microsoft Sign-In Information

MonitorCTL may offer authentication through Microsoft accounts, Microsoft Entra ID, and Microsoft identity platform services in a future phase of the Services.

When Microsoft Sign-In is available and you choose to use it, MonitorCTL may request appropriate Microsoft identity permissions, including:

• openid: To authenticate your Microsoft identity.
• email: To obtain your email address where available.
• profile: To obtain basic profile information.
• User.Read: If required and authorized, to read basic Microsoft user profile information.
• offline_access: If required, to support authorized session renewal using refresh tokens.

Depending on permissions and account configuration, the information received may include your name, email address, unique user identifier, tenant identifier, organization information, and other basic identity claims.

Microsoft identity information will be used for authentication, account provisioning, account linking, organizational access control, and security purposes.

MonitorCTL does not receive your Microsoft account password through Microsoft Sign-In.

Microsoft Sign-In does not automatically grant MonitorCTL access to Outlook email, OneDrive files, SharePoint documents, Teams conversations, or other Microsoft 365 content.

Any future integration requiring additional Microsoft Graph API permissions will be disclosed separately, and necessary user or administrator consent will be obtained.

1.4 Organization and User Management Information

When an account is associated with a MonitorCTL organization, we may process:

• Organization names and identifiers.
• Organization administrators and members.
• User invitations and membership status.
• Role-based permissions and access settings.
• Notification recipients and contact information.
• Administrative and audit activities.

1.5 Monitoring Configuration and Operational Data

MonitorCTL collects and processes information required to provide infrastructure and service monitoring functionality.

Depending on the monitoring services configured, this information may include:

• Hostnames, domain names, URLs, and IP addresses.
• DNS records and domain-related information.
• SSL/TLS certificate information and expiration dates.
• Server, operating system, network, and application metrics.
• CPU, memory, storage, network, and availability measurements.
• SNMP and supported device monitoring information.
• Service availability and performance measurements.
• Monitoring configuration and polling intervals.
• Infrastructure identifiers, tags, and organizational metadata.
• Monitoring events, alerts, incident details, and historical measurements.
• Notification delivery status and incident acknowledgment information.

Customers are responsible for ensuring they have the appropriate authority to monitor their configured systems and submit related information to MonitorCTL.

1.6 Enterprise Probe and Agent Information

If customers deploy an Enterprise Probe or other supported monitoring component, MonitorCTL may process device identifiers, connectivity information, configuration details, health status, monitoring results, and diagnostic information needed to operate the monitoring service.

Customers remain responsible for the configuration, security, and authorization of their monitored infrastructure and installed monitoring components.

1.7 Technical and Usage Information

When you interact with our website or Services, we may automatically collect:

• Public IP address.
• Browser type and version.
• Operating system and device characteristics.
• Pages visited and interactions with the Services.
• Login attempts and authentication events.
• Session identifiers and related timestamps.
• Error reports, diagnostic logs, and application performance information.
• Security events and suspicious activity indicators.
• General geographic information inferred from IP addresses.

1.8 Billing and Subscription Information

When you subscribe to paid Services, we may collect billing names, company details, billing addresses, invoice information, subscription plans, transaction identifiers, payment status, and related financial records.

Payments may be processed through third-party payment service providers. Payment card information supplied directly to a payment processor is governed by that processor’s privacy and security practices. We do not need to receive full payment card numbers to administer subscriptions.

1.9 Support and Communications

If you contact MonitorCTL for support, request information, or communicate with our team, we may process your name, email address, organization, correspondence, technical details, and any information you voluntarily provide.

2. How We Use Personal Information

We use personal information for legitimate service-related purposes, including:

• Providing, maintaining, and operating MonitorCTL.
• Creating and administering user accounts and organizations.
• Authenticating users through supported login methods.
• Managing role-based access and authorization.
• Running monitoring checks and maintaining monitoring history.
• Generating alerts, incident notifications, and operational reports.
• Delivering notifications through configured channels.
• Managing subscriptions, invoices, and billing.
• Providing technical assistance and customer support.
• Detecting misuse, security threats, fraud, and unauthorized access.
• Troubleshooting, maintaining, and improving platform reliability.
• Meeting legal, regulatory, and contractual obligations.
• Sending essential service and administrative communications.
• Sending optional marketing communications where permitted by law or consented to by the recipient.

We do not use Google or Microsoft authentication data for unrelated advertising, data brokerage, or resale.

3. Legal Bases for Processing

Where the General Data Protection Regulation (GDPR), UK GDPR, or similar laws apply, we process personal data under one or more applicable legal bases:

• Contractual necessity: Processing needed to deliver the Services and manage accounts and subscriptions.
• Legitimate interests: Processing needed for security, fraud prevention, service administration, reliability, and appropriate business operations, balanced against individuals’ rights.
• Consent: Processing based on permission where required, including certain optional communications or third-party authorizations.
• Legal obligations: Processing necessary to comply with applicable laws, accounting requirements, or lawful requests.

Where consent is the applicable legal basis, you may withdraw consent using the relevant controls or by contacting us. Withdrawal does not affect processing lawfully conducted before withdrawal.

4. Google API Services User Data Policy and Limited Use

MonitorCTL’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including applicable Limited Use requirements.

4.1 Access and Purpose Limitation

We request only the Google information reasonably necessary to provide the authorized authentication and related account functionality.

Google user data is used only for the disclosed purposes of providing or improving the corresponding user-facing Services and maintaining their security.

4.2 Storage and Security

Google identity information may be stored as part of the corresponding MonitorCTL user account. Authentication information, including tokens where applicable, is handled using access controls and appropriate technical and organizational safeguards.

Communications involving Google authentication are protected using secure communication protocols. Access to stored account information is limited to authorized personnel and systems with an operational need.

4.3 Sharing and Transfers

We do not sell, rent, or transfer Google user data to advertisers, advertising platforms, data brokers, or information resellers.

Google user data may be disclosed only as permitted by applicable Google policies and law, such as:

• To service providers where necessary to operate authorized functionality, subject to appropriate safeguards.
• For legitimate security, fraud prevention, and abuse investigations.
• Where disclosure is legally required.
• Where the user has provided any authorization required for a particular disclosure.

4.4 Prohibited Uses

We do not use Google user data for:

• Targeted, personalized, or interest-based advertising.
• Advertising retargeting.
• Sale to data brokers or information resellers.
• Creditworthiness assessment or lending decisions.
• Creating unrelated commercial identity databases.
• Training generalized or non-personalized artificial intelligence or machine-learning models.
• Any purpose inconsistent with the permissions granted by the user and applicable Google policies.

We do not use Google Workspace API data to develop, improve, or train generalized or non-personalized AI or machine-learning models.

4.5 Human Access

Access to Google user data by MonitorCTL personnel is restricted to legitimate operational needs, such as authorized support, security investigations, compliance with law, or circumstances in which the user has provided any required permission.

4.6 Retention and Deletion

Google identity information linked to a MonitorCTL account is retained only for as long as reasonably necessary to provide the Services or satisfy applicable legal, security, or operational requirements.

Users may request deletion of their MonitorCTL account and associated eligible personal information using the process described in Section 14.

Revoking access through Google’s account permissions settings prevents continued authorized access through the revoked connection but does not automatically delete an existing MonitorCTL account or its separately maintained data.

5. Microsoft Identity Platform Data Handling

When Microsoft Sign-In becomes available, MonitorCTL will use Microsoft identity information only for authorized authentication, account administration, organizational access control, and related security functionality.

We will request permissions appropriate to the functionality being provided and will not use Microsoft identity information for unrelated advertising or resale.

Microsoft authentication may involve Microsoft Entra ID tenant-level policies, user consent, or administrator consent, depending on the customer’s organization.

Microsoft account permissions and enterprise application access can be managed through Microsoft’s account and organizational administration tools.

Any Microsoft access tokens or refresh tokens used by MonitorCTL will be handled according to the application’s implemented security and token-retention procedures.

Microsoft account information associated with MonitorCTL may be retained for the period required to provide the Services, subject to account deletion procedures and applicable legal obligations.

6. Monitoring Data and Customer Responsibilities

MonitorCTL processes monitoring information on behalf of customers to provide infrastructure monitoring and alerting functionality.

Customers determine the monitoring targets, configurations, notification recipients, and other monitoring activities performed through their accounts.

Depending on the circumstances and applicable law, customers may act as data controllers and MonitorCTL may act as a service provider or processor for information submitted through the monitoring platform.

Customers are responsible for:

• Ensuring they are authorized to monitor configured systems.
• Maintaining appropriate access rights for their infrastructure.
• Protecting monitoring credentials and integration secrets.
• Managing organizational users and assigned roles.
• Configuring notification destinations appropriately.
• Avoiding the unnecessary submission of sensitive personal information.
• Providing legally required notices to affected individuals where appropriate.

We use customer monitoring data to deliver the requested monitoring services, generate events and alerts, maintain monitoring history, troubleshoot service issues, and protect platform integrity.

7. Alerts, Notifications, and Communication Channels

MonitorCTL may deliver alerts through email, push notification services, messaging platforms, incident management systems, and other integrations enabled by the customer.

Depending on the configured integration, transmitted information may include monitoring resource names, incident descriptions, timestamps, status changes, relevant performance measurements, and organizational information.

Customers control which supported notification channels they configure and are responsible for selecting appropriate recipients.

Data transmitted to third-party notification services may be processed according to those providers’ privacy policies and terms.

8. Third-Party Integrations

MonitorCTL supports or may support integrations with communication, automation, service management, and incident response platforms, including:

• Google services.
• Microsoft services, including Teams.
• Slack.
• Discord.
• Telegram.
• WhatsApp messaging services.
• Pushbullet and Pushover.
• Splunk.
• Zendesk and ServiceNow.
• PagerDuty and SIGNL4.
• Zapier.
• Customer-configured webhooks and other supported integrations.

The availability of integrations may vary according to subscription plan, technical availability, and current product functionality.

When a customer enables an integration, MonitorCTL may transmit the data necessary to perform the requested function. Customers should review the privacy terms of the relevant third-party service before enabling an integration.

We do not authorize third-party integrations to use Google authentication data for advertising, resale, or other purposes prohibited by Google’s policies.

9. Cookies and Similar Technologies

Our websites and Services may use cookies, session identifiers, and similar technologies to:

• Maintain authenticated sessions.
• Remember preferences.
• Protect against unauthorized activity.
• Support application functionality.
• Understand website usage and diagnose performance problems, where applicable.

Essential cookies are used where necessary to operate the Services. Non-essential analytics or marketing technologies, if used, are subject to applicable consent and privacy requirements.

Most browsers allow users to control or disable cookies. Blocking necessary cookies may affect authentication and application functionality.

10. Disclosure of Personal Information

We may share relevant personal information with trusted recipients when reasonably necessary to provide the Services.

10.1 Service Providers

These may include hosting providers, cloud infrastructure providers, authentication services, email delivery providers, payment processors, security providers, support platforms, and technical service providers.

Such providers are expected to process information only for authorized purposes and subject to applicable contractual, confidentiality, and security safeguards.

10.2 Organizational Administrators

If your account belongs to a customer organization, authorized organization administrators may be able to view and manage account membership, roles, monitoring configurations, activity records, and information relevant to the organization.

10.3 Legal and Security Requirements

We may disclose information when necessary to comply with applicable law, valid legal process, protect legal rights, investigate security incidents, or prevent misuse of the Services.

10.4 Business Transactions

Information may be involved in a merger, acquisition, financing, restructuring, or transfer of business assets, subject to applicable law, contractual obligations, and any additional consent requirements applicable to Google or other third-party API data.

We do not sell personal information to data brokers.

11. Data Security

MonitorCTL uses technical and organizational measures designed to protect information against unauthorized access, misuse, alteration, disclosure, or loss.

These measures may include:

• HTTPS and TLS encryption for supported network communications.
• Access controls and role-based permissions.
• Authentication and session-management controls.
• Protection of credentials, secrets, and authentication tokens.
• Security monitoring and audit logging.
• Infrastructure and application security maintenance.
• Restricted administrative access.
• Backup and recovery procedures.
• Incident investigation and response processes.

No method of internet transmission or electronic storage can be guaranteed to be completely secure. We continuously evaluate appropriate measures based on the nature of the data and associated risks.

Users are responsible for safeguarding their account credentials, maintaining appropriate organizational permissions, and promptly reporting suspected unauthorized access.

12. International Data Processing and Transfers

MonitorCTL provides services to customers in multiple regions. Personal information and monitoring data may be processed in countries other than the country where a user or customer resides.

Processing locations may depend on the Services, infrastructure, subprocessors, and integrations used.

Where applicable data protection laws require safeguards for international transfers, we will use appropriate transfer mechanisms, contractual commitments, or other lawful protections.

Customers should not assume that all monitoring or account information remains within a particular jurisdiction unless a specific contractual or product commitment provides for such residency.

13. Data Retention

We retain personal information only for as long as reasonably necessary to fulfill the purposes described in this Privacy Policy, satisfy contractual requirements, resolve disputes, support security investigations, or comply with applicable legal obligations.

Retention depends on the type of information and purpose of processing.

• Account information: Generally retained while the account is active and for any applicable post-closure retention period.
• Monitoring history: Retained according to the applicable subscription plan, product configuration, and operational requirements.
• Authentication and security logs: Retained for a period appropriate for security, troubleshooting, and compliance.
• Billing and transaction records: Retained as required by applicable accounting, taxation, and other legal obligations.
• Support records: Retained while needed to provide support, resolve issues, or meet applicable obligations.
• Backups: May retain residual information temporarily until the relevant backup retention cycle expires.

When information is no longer required, it is deleted, anonymized, or otherwise handled according to applicable retention and disposal procedures.

14. Account Deletion and Data Removal

Users may request deletion of their MonitorCTL account and associated eligible personal information.

14.1 How to Request Deletion

To request deletion, contact us at privacy@monitorctl.com with the subject “MonitorCTL Account Deletion Request”.

Please include the email address associated with your MonitorCTL account. We may request reasonable verification to protect your account against unauthorized deletion requests.

14.2 Information Subject to Deletion

Depending on the request, account ownership, contractual obligations, and applicable law, eligible information may include:

• Account profile details.
• Associated third-party identity information.
• Stored authentication connections and tokens, where applicable.
• Account-specific preferences.
• Customer monitoring configurations and eligible monitoring data.
• Other personal information no longer required for legitimate purposes.

Some information may need to be retained where required by law, necessary for security or fraud prevention, or subject to an organization’s legitimate control over its monitoring records.

14.3 Organization Accounts

If your account belongs to an organization, deletion of your individual account may not result in deletion of monitoring records or other information controlled by that organization.

Requests concerning organization-controlled information may need to be directed to the authorized organization administrator.

14.4 Google and Microsoft Account Revocation

Users may independently revoke application permissions through their Google or Microsoft account settings.

Google permissions can be managed through Google Account Connections.

Microsoft account and enterprise application permissions may be managed using the applicable Microsoft account, My Apps, or Entra administration interfaces.

Revoking access to an identity provider does not automatically remove the MonitorCTL account or historical information already maintained by MonitorCTL. Account deletion must be requested separately unless an applicable in-product deletion process is available.

15. User Privacy Rights

Depending on your location and applicable laws, you may have rights to:

• Request access to your personal information.
• Request correction of inaccurate information.
• Request deletion of eligible information.
• Request restriction of certain processing.
• Object to certain processing activities.
• Request portability of eligible personal data.
• Withdraw consent where processing relies on consent.
• Lodge a complaint with a relevant data protection authority.

We will evaluate and respond to privacy requests according to applicable legal requirements, including any legally permitted exceptions.

To exercise your rights, contact privacy@monitorctl.com.

16. European Economic Area, UK, and Swiss Privacy Rights

Where applicable, users in the European Economic Area, United Kingdom, and Switzerland may exercise rights provided under GDPR, UK GDPR, and relevant national privacy laws.

These may include rights of access, rectification, erasure, restriction, objection, portability, and withdrawal of consent.

Where MonitorCTL processes personal information on behalf of an organization, requests relating to that organization’s controlled data may need to be handled through the relevant organization.

We will provide information about applicable processing and international transfer safeguards where required by law.

17. United States State Privacy Rights

Residents of certain US states, including California and other states with applicable consumer privacy laws, may have additional rights concerning their personal information.

Depending on eligibility and statutory exceptions, these may include rights to know, access, correct, delete, or obtain certain personal information, and to opt out of processing activities covered by applicable law.

MonitorCTL does not sell personal information to data brokers and does not use Google authentication data for cross-context behavioral advertising.

We will not unlawfully discriminate against individuals for exercising applicable privacy rights.

Requests can be submitted using the privacy contact information provided below.

18. Children’s Privacy

MonitorCTL is intended for business, professional, and IT infrastructure monitoring purposes.

The Services are not directed toward children under the age of 16, and we do not knowingly collect personal information directly from children for account registration or service use.

If we become aware that personal information has been collected from a child in circumstances prohibited by applicable law, we will take appropriate steps to remove the information.

19. Marketing and Service Communications

We may send service-related emails concerning account security, subscription administration, incidents, billing, service changes, and important operational matters.

These communications are necessary for the operation or administration of the Services and may not be subject to general marketing opt-out preferences.

Where we send promotional communications, recipients may unsubscribe using the instructions provided in the communication or by contacting us.

Google and Microsoft authentication information will not be used for unrelated targeted advertising.

20. Automated Monitoring and Decision-Making

MonitorCTL automatically evaluates monitoring measurements against configured conditions to identify service availability issues, threshold violations, and operational events.

These automated monitoring functions are designed to generate technical alerts and support infrastructure management.

We do not use Google or Microsoft authentication data to make automated decisions concerning credit eligibility, lending, employment eligibility, or similarly significant individual outcomes.

21. External Websites and Services

Our website and application may contain links to external websites, authentication providers, integrations, and third-party resources.

We do not control the independent privacy practices of these external services.

We encourage users to review the privacy policies and terms of services they choose to access.

Relevant third-party privacy policies include:

• Google Privacy Policy.
• Microsoft Privacy Statement.

22. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in the Services, applicable laws, security practices, integrations, or data-processing activities.

When changes are made, we will update the “Last Updated” date at the beginning of this policy.

For material changes, we will provide additional notice or request consent where required by applicable law or third-party platform policies.

If we materially change how information obtained from Google APIs is used, we will provide the disclosures and obtain any required consent before using that information for the new purpose.

Users are encouraged to review this Privacy Policy periodically.

23. Contact Information

If you have questions regarding this Privacy Policy, our handling of personal information, data access requests, or account deletion, you may contact:

Infocellent Technologies Inc.
Product: MonitorCTL
Website: https://www.monitorctl.com/
Privacy Email: privacy@monitorctl.com
Privacy Policy: https://www.monitorctl.com/privacy-policy/

We will review privacy-related requests and respond within applicable legal timeframes.

© 2026 Infocellent Technologies Inc. All rights reserved. MonitorCTL is a product of Infocellent Technologies Inc.