Skip to main content
Vermont Secretary of State · Registration 367894 · Status: ACTIVE

Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)

This captured Vermont registry record for Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) is marked ACTIVE. It aggregates recorded filing fields, including opt-out disclosures, prior-year breach reporting, minors-data disclosures, and contact information; it does not independently verify current provider practices or request outcomes.

Legal context: 9 V.S.A. § 2446 sets the annual registration and disclosure framework. Vermont's 2026 Act 138 was signed on June 16, 2026; its substantive sections take effect January 1, 2027. Verify the live registry and provider route before relying on this snapshot.

Full opt-out walkthrough

Read the detailed Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) removal guide

Step-by-step process, what documents they ask for, and what to do if they stall.

Registry contact

Privacy contact
privacy@owneriq.com
Address
635 Vine Street, Winston-Salem, NC, 27101, USA
Vermont Registration ID
367894

What Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)'s Vermont filing tells you

Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)'s captured Vermont registry entry is marked ACTIVE and identifies the business as a data broker under Act 171 of 2018 (9 V.S.A. § 2446). Section 2446 requires annual registration and specified disclosures, including opt-out method information when a broker permits an opt-out, prior-year breach counts, and certain minors-data information. This record does not independently verify current collection practices, legal identity, or the current request route. Act 138 (2026) amended the framework; its substantive sections take effect on January 1, 2027.

Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) disclosed that it does permit consumers to opt out. The stated scope: The opt out is applied to using online browsing data to determine which ads to place. It does not accept requests through a third-party agent, so the opt-out has to come directly from you: OfflistMe handles this by pre-filling the email for you to send from your own inbox rather than acting as your agent.

To review a removal request, check Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)'s current provider route and the captured registry contact at privacy@owneriq.com. Cite the CCPA § 1798.105 or GDPR Article 17 only if that authority applies to your circumstances. Keep a dated copy for your records. OfflistMe can generate an email draft using the recorded contact: you review it and send it from your own account. The broker may still request matching information or verification.

Credentialing & access controls

Yes, we work with companies which abide by the NAI Code of Conduct.

Opt-out disclosure

Permits opt-out?

Yes

Opt-out method

There are three ways: 1) Clicking the opt out link in our privacy notice, 2) Choosing our company in the self-regulatory industry opt out platforms through NAI and DAA, 3) Click on the AdChoices icon when the online ad is delivered and choosing to opt out.

Scope

The opt out is applied to using online browsing data to determine which ads to place.

Third-party authorized agent allowed?

Only third parties which integrate a digital advertising opt out code. Our opt out cookie is tied to the computer browser. The opt out technology must be able to take our opt out cookie and replace it with a blank opt out cookie our systems will recognize. The NAI, DAA, and TrustArc can facilitate this.

Activities not subject to opt-out

The opt out does not apply to Ad Delivery and Reporting, as described in the NAI Code of Conduct (https://www.networkadvertising.org/code-enforcement/code).

Generate requests in under 60 seconds

Generate a Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) Opt-Out Request

OfflistMe has recorded provider workflows that include Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.); review the route and request scope before sending. No account, no ID upload.

FAQ

What does Vermont's registry record say about Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)?+

The captured Vermont registry entry identifies Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) as a data broker record under the annual-registration framework in 9 V.S.A. § 2446. Registration ID: 367894. Status in this record: ACTIVE. Verify the live Secretary of State record before treating the status or contact fields as current.

Does Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) allow consumers to opt out?+

Per Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)’s Vermont registry disclosure: Yes. Method: There are three ways: 1) Clicking the opt out link in our privacy notice, 2) Choosing our company in the self-regulatory industry opt out platforms through NAI and DAA, 3) Click on the AdChoices icon when the online ad is delivered and choosing to opt out.. Third-party authorized agent allowed: Only third parties which integrate a digital advertising opt out code. Our opt out cookie is tied to the computer browser. The opt out technology must be able to take our opt out cookie and replace it with a blank opt out cookie our systems will recognize. The NAI, DAA, and TrustArc can facilitate this..

Has Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.) experienced security breaches?+

The captured Vermont filing reports zero breaches in its prior-year field. That is not an independent finding about all historical or current incidents.

How do I remove my data from Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)?+

Review Inmar-OIQ, LLC (assignee in interest to OwnerIQ, Inc.)'s current provider route and the captured registry contact at privacy@owneriq.com. Cite CCPA § 1798.105 or GDPR Article 17 only if it applies to your circumstances. You can use OfflistMe to generate a pre-filled request draft for $9, then review and send it yourself.

Other Vermont registered brokers

Entries marked ACTIVE in this captured Vermont dataset. Each is a separate registry entry; status, legal obligations, and current request routes should be checked individually.

Related