⬡ Askhive
Askhive

Acceptable Use Policy

What Askhive may not be used for, and what happens when it is.

Last updated: 29 September 2026

Written by us, in plain language, and kept true rather than lawyerly: every factual sentence here is one we can show you the mechanism for. If anything looks wrong, tell us at support@bridgeshorelabs.com and we will correct it.

What this is

One page of rules that apply everywhere Askhive is used — the apps, Practice, shared reports, and the API. Breaking them can cost you access.

Do not use Askhive to

What we do about it

Two things happen automatically, and one is deliberately narrow.

Refusal. A request that asks for serious harm is refused. That check runs on the server, applies to the API as well as the app, and cannot be turned off.

Care, not refusal. A question about a sensitive subject — self-harm, abuse, a medical emergency — is not refused. It is answered, and the report leads with real sources of help. Asking for help is not misuse and we will not treat it as such.

We do not read your reports looking for violations. If something is reported to us, or abuse protections fire repeatedly, we may investigate and suspend access. For a serious or repeated breach we may terminate. Where it is reasonable we tell you first.

Reporting a problem

A report that was harmful or wrong: use Report a response on the report itself, which sends it to us with the report attached. Anything else: support@bridgeshorelabs.com.