FloppyData
14 fields evidenced · 41 with no public information. Every value below links to the document it came from and the date we checked it.
8 of those are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist
2 of the evidenced values quote wording our own later capture of the same page no longer contains. Marked below, awaiting an editor.
Also appears in
Trust gap
How this is scoredThese scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.
Are scope, spend, and authority enforced while the agent runs?
Is there a tamper-evident record of what it actually did?
Are compliance obligations attached per engagement?
Scored from 2 evidenced field(s): compliance_certs, regulatory_alignment. Automated score; capped at 2 pending review.
Counts Compliance certifications and Regulatory alignment, each cited below.
Does payment depend on a verified result?
Can the deployment be insured, and is the customer indemnified?
Assurance
- Insurance available
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Insurance carriers
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Coverage limits
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Indemnification
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Liability cap
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Audit trail
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Tamper-evident log
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Explainability
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Runtime governance
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Permission scopes
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Compliance certifications
- SOC 2, CCPA, GDPR
“SOC 2 CCPA GDPR”
floppydata.com · checked Aug 4, 2026 - Regulatory alignment
- SOC 2, CCPA, GDPR
“SOC 2 CCPA GDPR”
floppydata.com · checked Aug 4, 2026 - Outcome-based pricing
“Pay only for successful scrapes.”
floppydata.com · checked Aug 4, 2026- Settlement mechanism
“Pay only for successful scrapes.”
floppydata.com · checked Aug 4, 2026- Dispute process
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- SLA terms
“reliable uptime standards”
floppydata.com · checked Aug 4, 2026- Evaluation coverage
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Agency
- Autonomy level
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Human oversight
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Goal complexity
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Action space
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Operating environment
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Initiative
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Safety
- Safety evaluations
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Red teaming
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Safety policy
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Usage restrictions
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Model or system card
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Incident reporting
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Third-party evaluations
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Data handling
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Practicality
- Pricing model
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Price point
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Availability
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Deployment options
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Integrations
“Floppydata integrations”
floppydata.com · checked Aug 4, 2026- Supported regions
- Germany, Canada, Japan, Spain, Sweden, United Kingdom, United States, Argentina, Australia, Brazil, China, France, India, Italy, Korea, Mexico, Netherlands, New Zealand, Philippines, Poland
“Popular Locations German Canada Japan Spain Sweden United Kingdom United States World Location See All Locations Argentina Australia Brazil China France India Italy Korea Mexico Netherlands New Zealand Philippines Poland”
floppydata.com · checked Aug 4, 2026 - Support model
“exceptional support”
floppydata.com · checked Aug 4, 2026
Foundation models
- Base models
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Model provider
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Model swappable
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Open weights
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Fine-tuning
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Context window
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Ecosystem
- Protocols supported
“HTTP Proxy”
floppydata.com · checked Aug 4, 2026- Tool use
“Agent-friendly APIs for fresh, live page access”
floppydata.com · checked Aug 4, 2026- Multi-agent
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- API access
“Use one API for rotating proxies, static inventory, Web Data scraping, and the Cloud Browser.”
floppydata.com · checked Aug 4, 2026- Open source
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Marketplace presence
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Impact
- User base
- 10,000+ users
“Trusted by 10,000+ users”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 17, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
floppydata.com · checked Aug 4, 2026 - Deployment scale
- 80,000+ companies of all sizes
“Trusted by 80,000+ companies of all sizes”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 17, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
floppydata.com · checked Aug 4, 2026 - Target sectors
- Brand Protection, Ad Verification, Social Media, Traffic Arbitrage, Web Scraping, SEO, Price Monitoring, Market Research
“Popular Use Cases Brand Protection Proxy Ad Verification Proxy For Social Media Traffic Arbitrage Proxy Web Scraping Proxy For Use Cases SEO Proxy Price Monitoring Proxy Market Research Proxy”
floppydata.com · checked Aug 4, 2026 - High-risk domains
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
- Documented incidents
- no public informationfloppydata.com · checked Aug 4, 2026 · source did not state this
Compared with
Side-by-side on the fields where FloppyData and the other entry are both on record and actually differ.