COMPLIANCE & ACCEPTABLE USE

What we will, and will not, do.

AuraCrawl works with public data, in the schema you define, under accounts you own. This page is the canonical statement of that boundary — the same one referenced from our docs, our contracts, and every engagement.

THE LINE WE HOLD

Public data, your scope, your accounts

This is the whole policy, stated plainly. It is the same boundary our engineers work to, our contracts reflect, and our API enforces — there is no quieter version of it for a bigger deal.

WHAT WE DO

  • Work only with publicly accessible pages — anything a person can open without signing in.
  • Extract into the schema you define, and deliver only what your scope covers.
  • Run bring-your-own sessions strictly under your own account, on your warranty of ownership and authority.
  • Tell you plainly, before any commitment, what a target involves and whether it is a fit.
  • Hold only the data needed to run and replay your pipeline, and never resell or reuse your extractions.

WHAT WE NEVER DO

  • Operate logins, warm accounts, or run credentialed sessions of our own on any platform.
  • Create accounts on any site, for any reason.
  • Place orders, submit forms, or take any transactional action on a target.
  • Touch data behind a login, paywall, or credential you do not own.
  • Collect personal data without a documented lawful basis.
  • Use licensed third-party datasets we do not hold the rights to.

AUTHENTICATED ACCESS

Bring-your-own sessions, and only those

Where a workflow needs a signed-in session, that session is always one you supply and one you own. You warrant that the account is yours and that you are authorised to access it and its data through AuraCrawl. The account, its credentials, and its terms of use remain entirely yours — we act only as the executor of the session you provide, and we never generate accounts.

This is a hard limit, not a default we relax on request. If a target can only be reached by an account we would have to create or operate, it is out of scope, and we will say so rather than work around it.

SELF-SERVE API

Coming soon.

We are building an API so smaller jobs will not need a call with us first. It is not ready yet, and we would rather say that here than after you sign up. For now, every project starts with an email.

Talk to us instead

Not sure a target sits inside the line?

Send it. We would rather tell you up front that something is out of scope than take on work we will not stand behind.

Ask an engineer