What Askhive collects, what we do with it, and what we never do with it.
We collect what Askhive needs to answer your question, remember your reports, and bill your subscription. We do not sell your data and we do not share it for anyone else's advertising. We do not run ads. There is no third-party analytics or advertising SDK in the Askhive app — no Google Analytics, no Facebook SDK, no PostHog, no Mixpanel.
We never record what you asked. The usage measurements we take record that an ask happened, not its content, and you can switch them off in Account → Privacy.
Bridgeshore Labs, LLC is the controller of the personal data described here, except for Askhive Practice client data — a professional's client list and the reports they draft for their clients. For that data the professional is the controller and we are their processor, under the Data Processing Agreement.
Privacy contact: privacy@bridgeshorelabs.com. We answer data-subject requests within 30 days.
Written against the actual database. The second line of each row names the table or bucket the data is really in, so you can hold this page to it.
| Category | Why | Legal basis (GDPR Art. 6) | How long |
|---|---|---|---|
| AccountYour email address and the plan you are on. | Sign in, restore your reports on another device, contact you about your account | Performance of a contract | Until you delete your account, which deletes the record itself rather than hiding it |
| Anonymous device identityA random code this browser or app made up for itself. Not your name, not your phone. | Let you use Askhive before signing in, and count the free daily allowance | Performance of a contract | Until the device record is deleted or migrated into an account on sign-in |
| Questions, answers and reportsWhat you asked and the report it produced. | Produce your report and show it to you again when you come back | Performance of a contract | Until you delete the report or your account |
| Reports you chose to share by linkA copy of the one report you published, and the passcode or end date you set. | Show that one report to anyone you send the link to | Performance of a contract | 90 days, enforced daily — or immediately when you stop sharing, which deletes the copy |
| AttachmentsPractice only: a document a firm attached to a client's deliverable. | Keep a professional's source document with the deliverable it produced | Performance of a contract | Until the report or the account is deleted |
| Practice client recordsA firm's notes about its own client — name, email, and the details it keeps so it does not retype them. | Let a professional address a deliverable to their client, draft without asking the same questions twice, and track engagement | Performance of a contract — the professional is the controller of this data; we are their processor | Until the professional deletes the client or the account |
| Usage counters and rate limitsHow many questions have been asked, so limits and abuse protection work. No question text. | Enforce plan limits and stop abuse | Legitimate interests — running the service and protecting it | 24 hours, enforced daily |
| Product analyticsWhich steps happened, as counts. Never what you asked. | See where the product fails people — that an ask happened, not what was asked | Legitimate interests, with an opt-out in the app | 13 months, then kept only as daily totals — enforced daily |
| Engagement eventsWhether a delivered report was opened, read or replied to. | Show a professional whether their client opened the report | Legitimate interests of the professional, as controller | Cascades when the report is deleted |
| BillingWho is paying and for what. Card details go to Stripe and never reach us. | Run the subscription and keep a record of what was charged | Performance of a contract; legal obligation for tax and accounting records | Kept while the subscription exists and afterwards for accounting purposes |
| WaitlistAn email address someone left to hear when we open. | Tell you when the thing you asked about is ready | Consent | 24 months, or until you ask to be removed — enforced daily |
| Operational telemetryHow long the engine took and what it cost. No personal data. | Know what a report costs and when the model provider is failing | Legitimate interests | 24 months, enforced daily. No personal data: token counts, latency and model names only |
Every period above is enforced by a job that runs daily and records what it deleted, not by a promise. Automatic deletion started on 14 September 2026. The retention policy has the full schedule and explains how it is monitored.
The periods are ours. They live in one configuration table, so changing any of them is a one-line change rather than a code release.
We use it to run Askhive: to understand your question, produce and store your report, enforce plan limits, keep the service secure, and email you about your account. We look at aggregate usage to decide what to build. We do not use your questions or reports to advertise to you, and we do not sell them.
Askhive uses a language model to draft reports. That is drafting, not deciding. Askhive does not make automated decisions that produce legal effects concerning you or similarly significantly affect you within the meaning of GDPR Art. 22 — it does not approve or refuse credit, employment, insurance, benefits, or anything of that kind. A report is a document for a person to read and act on, and where a professional is involved, a person reviews and approves it before it is sent. Two automated steps exist and neither decides anything about you: the model judges how long an answer should be, and a moderation layer can refuse a request that asks for harm.
Only companies that help us run the service, and only for that purpose. The current list is on the sub-processors page, which is the authoritative version and carries the change-notice commitment.
Askhive Practice can take a forwarded client email and turn it into a draft. That message arrives through our mail provider, and there are two copies of it to account for, not one. Plainly: the mail provider keeps a copy for thirty days and its backups for seven more; we delete our own copy at once, and ask the provider to remove a specific message sooner when a firm asks us to. We never write the body of the message, or its attachments, to our own systems — what we keep is the draft the professional then edits, and a log line recording who it came from, which address it reached, its subject, and what we did with it. We keep that line for thirteen months so a firm can answer "did my forward arrive?". The provider offers no way for us to delete a received message ourselves, so removal sooner is a request a person makes to their support, and we make it when a firm asks.
We also disclose data if the law requires it. If we are ever compelled to hand over your content, we will tell you unless we are legally prohibited from doing so.
Askhive runs in the United States (AWS us-east-1, Northern Virginia). If you use Askhive from the European Economic Area, the United Kingdom or Switzerland, your data is transferred to the United States.
The transfer mechanism is the Standard Contractual Clauses. We rely on the SCCs our processors incorporate into their own data-processing terms, and we incorporate the SCCs into our DPA with Practice firms.
You have the right to access your data, to have it corrected, to have it deleted, to restrict or object to processing, to data portability, and to withdraw consent where we rely on it. You also have the right to complain to your supervisory authority.
How to exercise them. Three of them you can do yourself, immediately and without asking us: take a copy of your data from Account → Export my data, which downloads a zip of JSON containing everything deleting your account would remove (if you are signed out it is built on your device and never reaches us); delete your account from Account → Delete account, which deletes rather than deactivates; and turn off usage measurement from Account → Privacy. For anything else, email privacy@bridgeshorelabs.com from the address on the account and we will respond within 30 days. We do not charge for this.
What deletion does to a file. A file is removed from the live store the moment it is deleted. Askhive also keeps its own nightly copy of every file — the provider's database backups hold the records of files, not the files — so a deleted file can still exist in that copy for up to 30 days, until the copy's own retention rule removes it. The copy is a private bucket: no client and no signed-in person can read it, and only a restore run by Askhive can reach it.
If your data is in a professional's Practice workspace, they are the controller — we will refer your request to them and help them answer it.
If you are a California resident you have the right to know what we collect and why, to delete it, to correct it, to opt out of sale or sharing, and to limit the use of sensitive personal information — and not to be discriminated against for exercising any of them.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined by the CPRA. We have not done so in the preceding twelve months. There is therefore no "Do Not Sell or Share My Personal Information" mechanism to offer, because there is nothing to opt out of. Requests go to privacy@bridgeshorelabs.com.
We maintain a data security programme with administrative, technical and physical safeguards reasonable for our size and the sensitivity of the data: row-level security on every table, no implicit database grants, encryption in transit and at rest through our infrastructure provider, redaction of identifiers before Practice briefs reach the model, passcode protection with brute-force limits on shared client reports, and a written retention and deletion policy. If a breach of New York residents' private information occurs we will notify affected residents and the required State offices as the SHIELD Act requires.
Askhive is for people aged 13 and over. We do not knowingly collect personal data from children under 13. The app has a "written for" setting that produces reports in simpler language for a child, intended for an adult asking on a child's behalf; it does not create an account for a child. If you believe a child under 13 has given us data, write to privacy@bridgeshorelabs.com and we will delete it.
We measure the shape of a session so we can tell where Askhive is failing people: that an ask was started, that clarifying questions were shown, answered or skipped, that a report was produced, that it was shared, and whether the app had been used before.
We never record what you asked — not the text, not a summary, not a hash of it. The server accepts a fixed list of event names and a fixed list of fields, each of which is a number or a choice from a list; there is no free-text field to fill.
Signed out, these events carry nothing but a random identifier created when you open the app and discarded when you close it, and that identifier is deliberately not the one that identifies your device elsewhere. Signed in, they also carry your account id — so that switching analytics off applies to you wherever you are signed in, and so that deleting your account deletes these events with it. That is a join key, and we would rather say so than let you infer otherwise.
Turn it off in Account → Privacy → Help improve Askhive. When it is off we send nothing at all — the check happens before the request is built, not on our side afterwards.
The plain-language version is on the security page. In short: your rows are readable only by you, enforced in the database rather than in application code; a professional's client data is isolated to their workspace; identifiers in Practice briefs are replaced with tokens before the model sees them; shared reports carry a passcode by default and refuse repeated wrong guesses; and we hold no card details.
When this policy changes materially we will update the date at the top and, for changes that affect how we use data you have already given us, tell account holders by email before the change takes effect.