Datasleeper

Support and Deceptive Site Remediation

Use this page to contact support and document false-positive remediation. Messages are forwarded to caelan-james@datasleeper.com.

Review note: do not submit repeated review requests until every listed issue is fixed. Repeat submissions can increase review time.

Current Pricing

AI chat is $0.10 per message. General API usage and Google API usage are each $0.10 per billable call. Application generation is $5.00 per build, and application edits are $2.00 each.

Hosting is $200.00 per month per hosted app. Domain registration and renewal charges are passed through at AWS cost with no DataSleeper markup or added domain fees; the current domain charge is shown before purchase when available.

Building and updating an application requires more AI processing than a regular chat message. The build and edit prices are fixed customer prices; internal token usage does not create a separate customer surcharge.

Contact Support

Mitigation Checklist (Policy-Aligned)

  • Use Search Console Security Issues as the source of truth for flagged URLs and categories.
  • Remove deceptive UX patterns: fake system updates, fake login prompts, misleading download buttons, and spoofed branding.
  • Audit all third-party resources, especially ads and embeds, on desktop and mobile views.
  • Make third-party relationships explicit when services operate on your behalf.
  • Scan for unauthorized files/routes and rotate credentials if compromise is suspected.
  • After all fixes are complete site-wide, submit one review request with exact remediation details.
  • Report false positives directly to Safe Browsing if no deceptive behavior remains.
Recommended evidence package: before and after screenshots, list of removed scripts, deploy commit IDs, and timeline of fixes.

Persistent Prevention

  • Keep all script assets first-party or verified; remove stale third-party tags.
  • Maintain clear company identity, visible support contact, and transparent ownership language.
  • Use strict response headers (CSP, X-Frame-Options, Referrer-Policy) and keep dependency updates current.
  • Add continuous monitoring for changed templates, new redirects, and suspicious injected markup.

Security contact is also exposed at /.well-known/security.txt for automated security tooling.