Skipsmasher, Inc.
This captured Vermont registry record for Skipsmasher, 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 Skipsmasher, Inc. removal guide
Step-by-step process, what documents they ask for, and what to do if they stall.
Registry contact
- Website
- https://skipsmasher.com
- Privacy contact
- info@skipsmasher.com
- Address
- PO Box 891329, Temecula, CA, 92589, USA
- Vermont Registration ID
- 368025
What Skipsmasher, Inc.'s Vermont filing tells you
Skipsmasher, 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.
Skipsmasher, Inc. disclosed that it does permit consumers to opt out. The stated scope: No. It also allows an authorized agent to submit the request on your behalf, which is what lets a tool like OfflistMe prepare the request for you to send.
To review a removal request, check Skipsmasher, Inc.'s current provider route and the captured registry contact at info@skipsmasher.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. Only verified, credentialed business users may use our service.
Skipsmasher, Inc.'s own registry note
We do not own or store personal information of any consumers, including those from Vermont.
Recorded from the captured Vermont Act 171 registration filing data.
Opt-out disclosure
Permits opt-out?
Yes
Opt-out method
Click link on homepage.
Scope
No
Third-party authorized agent allowed?
Yes
Activities not subject to opt-out
Non except criminal records.
Generate requests in under 60 seconds
Generate requests for 1000+ brokers, including Skipsmasher, Inc., for $9
FAQ
What does Vermont's registry record say about Skipsmasher, Inc.?+
The captured Vermont registry entry identifies Skipsmasher, Inc. as a data broker record under the annual-registration framework in 9 V.S.A. § 2446. Registration ID: 368025. Status in this record: ACTIVE. Verify the live Secretary of State record before treating the status or contact fields as current.
Does Skipsmasher, Inc. allow consumers to opt out?+
Per Skipsmasher, Inc.’s Vermont registry disclosure: Yes. Method: Click link on homepage.. Third-party authorized agent allowed: Yes.
Has Skipsmasher, 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 Skipsmasher, Inc.?+
Review Skipsmasher, Inc.'s current provider route and the captured registry contact at info@skipsmasher.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.