DataTidy
Responsible use

Public Data and Responsible Use

DataTidy is built for reviewing public local business information, cleaning result tables, and exporting fields that teams can verify before they act. This page explains the product boundary behind pages such as Google Maps scraper, CSV export, phone, email, and reviews workflows for local merchants.

Short answer

Public local business data can still carry legal, platform, privacy, and outreach obligations. DataTidy does not give legal advice. It gives teams a reviewable workflow: search, preview, select fields, export, verify, and use Google Maps contact details within the rules that apply to their use case.

Responsible use principles

  • Use public local business information for legitimate merchant review.
  • Collect only the fields needed for the current workflow.
  • Keep source URLs so important records can be verified.
  • Respect website terms, platform limits, robots policies, and local law.
  • Follow consent, anti-spam, and privacy rules before outreach.
  • Avoid collecting sensitive, private, or hidden information.

What DataTidy is built for

The product focuses on table workflows, not uncontrolled automation. A user should be able to inspect fields, hide columns, copy selected data, download a CSV, and keep a clear audit path back to the public source.

  • Local SEO audits and market research.
  • Local business contact list review before manual or compliant outreach.
  • CSV cleanup and source verification.
  • Responsible analysis of public ratings and review-count signals.

High-risk patterns to avoid

  • Bypassing access controls, logins, paywalls, or rate limits.
  • Collecting hidden, private, or sensitive personal information.
  • Exporting local business contact fields without a verification and consent process.
  • Sending unsolicited bulk messages without checking applicable rules.
  • Ignoring source terms or platform restrictions.

Before you export

Start with a small, focused search. Preview the table. Remove fields that are not needed. Keep the source URL. Verify records that matter. If Google Maps contact details are part of the workflow, decide how consent, unsubscribe handling, and local privacy rules will be managed before a local merchant campaign starts.

Continue with the Google Maps Scraper, the CSV export guide, or the email extractor guide.