Active Intel Investigations LLC
This captured Vermont registry record for Active Intel Investigations LLC is marked EXPIRED. 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 Active Intel Investigations LLC removal guide
Step-by-step process, what documents they ask for, and what to do if they stall.
Registry contact
- Website
- https://activeintel.com
- Privacy contact
- daveafx@gmail.com
- Address
- 5080 Spectrum Drive Suite 1000 East, Suite 1000 East, Addison, TX, 75001, USA
- Vermont Registration ID
- 354190
What Active Intel Investigations LLC's Vermont filing tells you
Active Intel Investigations LLC's captured Vermont registry entry shows a status of expired. Treat that status as a filing record, not proof that the company currently operates, has stopped operating, or deleted data. The entry may describe an earlier filing, so verify the live Secretary of State record and the provider's current request route before relying on it. Act 138 (2026) amended the framework; its substantive sections take effect on January 1, 2027.
Active Intel Investigations LLC's registry entry records its opt-out position as: No. Depending on your location, the provider's role, the request type, and applicable exceptions, the CCPA or EU GDPR may provide deletion rights. This registry field does not determine legal coverage, verification, or outcome.
To review a removal request, check Active Intel Investigations LLC's current provider route and the captured registry contact at daveafx@gmail.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, identificationn required.
Active Intel Investigations LLC's own registry note
none known
Recorded from the captured Vermont Act 171 registration filing data.
Opt-out disclosure
Permits opt-out?
No
Activities not subject to opt-out
Third party databases accessed.
Risk disclosures
Security breaches (prior year)
0
Collects minors’ data
Yes (per registry disclosure)
none known
Generate requests in under 60 seconds
Generate Your Active Intel Investigations LLC Opt-Out Request
FAQ
What does Vermont's registry record say about Active Intel Investigations LLC?+
The captured Vermont registry entry identifies Active Intel Investigations LLC as a data broker record under the annual-registration framework in 9 V.S.A. § 2446. Registration ID: 354190. Status in this record: EXPIRED. Verify the live Secretary of State record before treating the status or contact fields as current.
Does Active Intel Investigations LLC allow consumers to opt out?+
Per Active Intel Investigations LLC’s Vermont registry disclosure: No.
Has Active Intel Investigations LLC 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 Active Intel Investigations LLC?+
Review Active Intel Investigations LLC's current provider route and the captured registry contact at daveafx@gmail.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.