Security and trust

Security-minded source data workflows

Source data tools need clear limits and operational controls. SourceOfTruth.io keeps crawler jobs bounded, separates owner and customer access, and routes public security contact through security@sourceoftruth.io.

Security focus
Controls
Security

Crawler controls first

Crawler work should be scoped and reviewable. SourceOfTruth.io uses bounded jobs, estimates, paid usage controls, and export evidence instead of unbounded crawler promises.

  • Target URLs
  • Usage estimates
  • Job evidence
  • Credit controls
Ask support
Security

Private routes stay private

Dashboard, auth, billing, owner, and API routes should not be treated as public SEO pages. Public crawling is limited to intentional marketing and support routes.

  • Dashboard noindex
  • Auth noindex
  • API disallow
  • Public sitemap only
Ask support
Security

Clear contact path

Public support starts with support@sourceoftruth.io. Security reports can be routed through security@sourceoftruth.io when a dedicated security disclosure process is needed.

  • Support mailbox
  • Security mailbox
  • Billing mailbox
  • Clean DNS records
Ask support
Operational model

Permission-aware scope

Crawler jobs should stay bounded to customer-approved public targets and clear export use cases; robots rules, access restrictions, and protected pages may limit output.

Launch gates

Billing and advanced workflows stay controlled until production readiness is confirmed.

Traceable output

Job IDs, source URLs, timestamps, and export evidence make crawler output reviewable.

Account controls

Dashboard, billing, and settings pages are protected behind the application account layer.

No unlimited crawler posture.Security and cost controls stay aligned around bounded, metered, reviewable source-data workflows. For crawler access questions, contact support@sourceoftruth.io.