⬡ Askhive
Askhive

Consent on file

A record, per client, that a required consent exists — for the professions that need one.

Last updated: 8 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. Some professions may not use a client's information for anything beyond the engagement without the client's written consent — a tax preparer's use of return information outside preparing the return is the clearest example in the United States (IRC §7216). Askhive does not decide whether a firm needs such a consent; the firm and its own counsel do. What Askhive gives a firm is a place to record that one is on file, per client, so the record travels with the client rather than in a drawer.

What the record holds

Askhive holds the record, not the document: the signed consent stays in the firm's own files. The record is on the client's page in Clients, exported with the firm's data, and deleted with the client.

What it is not

It is not legal advice about whether a consent is required, not a template for one, and not a substitute for keeping the signed original. Askhive's own privacy and data-processing terms are in the Privacy Policy and the Data Processing Agreement.

Last verified 28 September 2026. See also the security fit sheet and data controls.