Privacy policy

PulsarOps AI is a unified event intelligence platform built by MIR Digital Solutions. "MIR", "we" and "us" mean MIR, which operates pulsarops.ai and answers sales@pulsarops.ai from the US, Canada and the UAE. More on the about page.

If you do not agree with it, do not use the site and do not send us your details.

For counsel: name the legal entity acting as controller, its registration number and its registered office.

This policy covers the public website at pulsarops.ai:

• These pages, plus Platform, Industries, Security and Compare.
• The demo request form and what you enter into it.
• The resource library and what you ask us to send.
• Email to sales@pulsarops.ai and what follows it.

It does not cover two things:

• Data inside a customer deployment. Section 06 covers it, and on an on-premise platform it is the distinction that matters most.
• Other websites. mirdigitalsolutions.com and every site we link to have their own policies.

Information you give us

When you request a demo or write to us, we collect what you send:

• Your name and your work email address.
• Your phone number, if you give one.
• Your company, job title and region.
• What you want to see: your infrastructure, its vendors, the incident behind it.
• Anything else you write in the message.

Information collected automatically

Our host records standard request data: pages viewed, referring page, device and browser type, approximate location from the IP address, and the time. We read it to see which pages get used.

Information from embedded media

Two explainer videos are embedded from YouTube in privacy-enhanced mode, so no advertising cookies are set until you press play. Then YouTube's own policy applies.

What we do not want

Do not send credentials, live configurations, raw log extracts, packet captures, or anything covered by an agreement with your own customers. A technical exchange that needs them gets a controlled channel first.

We use it to:

• Reply and schedule the call you asked for.
• Prepare, so the engineer arrives understanding your infrastructure.
• Send the material you asked for, such as the telco case study.
• Follow up where you asked, or where we have a legitimate interest and you have not objected.
• See how the site performs.
• Keep required records, protect the site and investigate misuse.

We do not sell personal information. We do not pass it to advertising networks or build profiles for unrelated advertising.

Where the GDPR, UK GDPR or a similar law applies, we rely on:

• Consent. When you submit a form or opt in to hear from us.
• Legitimate interests. Running and securing the site, replying to inquiries, and managing a relationship with organizations evaluating the platform.
• Contract. Where we need it to deliver something you asked for or to perform an agreement.
• Legal obligation. Where a law requires us to retain or disclose it.

Withdraw consent any time at sales@pulsarops.ai. It does not undo processing that was lawful before.

PulsarOps AI is deployed on-premise, sovereign-ready and cloud-agnostic, inside the customer perimeter. The syslogs, application logs, configurations, inventory, tickets and topology it ingests stay there, under that customer's control. MIR receives no copy by default, and this policy does not govern it.

Two situations change that, and both are bounded:

• Evaluations, installation and support. A customer may grant limited, time-bound access so we can install, tune or troubleshoot. That sits under their written agreement and change control, not this page.
• Where MIR acts as a processor. If a customer asks us to operate part of a deployment, they remain the controller. We act on their documented instructions under their agreement.

If your information sits inside a customer's deployment, your request goes to that organization. We pass on what we receive, but only they can act.

The security and deployment page has the detail.

We share what you send only with the providers that help us run the site and reply:

• Website hosting and content delivery.
• Email delivery and the sales@pulsarops.ai mailbox.
• Website analytics.
• Video embedding, as described in section 03.

We may also disclose it:

• Where a law, court or regulator requires it.
• To establish or defend a legal claim, or protect people or systems.
• In a merger or reorganization, where the receiving party is bound to handle it consistently with this policy.

For counsel: name each provider before publication, and confirm which require a data processing agreement.

The site uses browser storage in two groups:

• Strictly necessary. What makes the site load and behave correctly during your visit.
• Analytics. Which pages are read and where visitors stop, looked at in aggregate.

No cross-site advertising trackers run here. You can block cookies in your browser, though blocking the necessary group breaks the site.

For counsel: confirm whether a consent banner is required for analytics in each region, and whether UAE law adds anything beyond the GDPR position.

MIR works across the US, Canada and the UAE, and our providers may process information in any of them. What you send may be handled outside your own country.

Where we move information out of a region that restricts transfers, we rely on the safeguards that law provides, such as standard contractual clauses.

Where a customer's deployment runs is separate. A sovereign-ready deployment stays where the customer puts it.

We keep information as long as we need it for the purpose we collected it, then as long as our legal obligations require.

• Demo requests and correspondence. Kept while we are in contact, then as a record.
• Material you asked us to send. Part of the same record.
• Analytics. Kept in aggregate, no longer identifying you.

When it is no longer needed we delete it or strip what identifies you. Section 16 is how you ask us to delete sooner.

For counsel: set an explicit retention period per category. This draft states none rather than inventing one.

We take reasonable technical and organizational measures: encryption in transit, access control on the mailbox and the systems behind it, established hosting.

No method is completely secure, so we promise no absolute security. We hold as little as possible instead, which is why section 03 asks you not to email configurations.

Found a security issue? Write to sales@pulsarops.ai and mark it a security report.

Depending on where you live, you may have some or all of these rights:

• Ask what we hold and get a copy.
• Have it corrected if it is wrong.
• Have it deleted.
• Object to how we use it, or restrict that use.
• Ask for it in a portable format.
• Withdraw a consent.
• Complain to your supervisory authority.

Where those rights come from:

• EU and UK. The GDPR.
• Canada. PIPEDA and the applicable provincial law.
• California. The CCPA as amended, including the right not to be treated differently for exercising them.
• UAE. The federal personal data protection law.

Requests go to sales@pulsarops.ai. We respond within the time your local law requires, and we may need to verify who you are.

If your request concerns a customer's own deployment, section 06 explains why it belongs with them.

This site is aimed at network operations professionals and IT leadership. It is not directed at children, and we do not knowingly collect information from anyone under 18.

If a child has sent us information, write to us and we delete it.

The site links to and embeds material from others, including mirdigitalsolutions.com and the two explainer videos on YouTube.

We do not control those services and are not responsible for their content or how they handle your information. Their own terms apply.

We may update this policy. The date at the top changes when we do, and a significant change gets said plainly.

Continued use after an update means you accept the revised policy. The first will follow legal review and remove the draft notice above.

Questions about this policy, what we hold, or how a deployment handles data go to sales@pulsarops.ai. It reaches the team that runs the demos, so a technical question gets a technical answer.

For counsel: add the postal address for privacy correspondence, a named contact or data protection officer where required, and an EU or UK representative if needed.