Briu helps businesses use AI and builds workflow software. This policy explains what we collect on briu.ai, in proposals, and in the customer tools we operate.

We do not sell or rent personal information. Browsing the public site does not save a marketing identifier, your landing page, referring page, campaign tags, or browsing interests on your device. There is no cookie banner. The Ask Briu chat loads only when you open it.

When you send us something

The consultation form sends your name, email, and note when you submit it. You can also choose to share your business, role, topic, timing, and how you heard about us. We use this to answer your inquiry. It does not subscribe you to a mailing list.

A submission also includes the form's page path, the link you used to reach the form, and any campaign tags on the form's own URL. We do not carry attribution forward from earlier pages or send the full URL or referring page. Your inquiry is recorded in our customer relationship system and lead records; an internal notification may include your contact details and a short excerpt of your note.

When you join Field Notes, we record your email, optional name, signup location, chosen maximum frequency, subscription status, and signup and preference-update times. We send Field Notes and a confirmation with private preference and unsubscribe links. Unsubscribe anytime. Those links include your email and a signed token, so keep them private.

For the REAPS materials, we email a private link to the address you provide. Submitting the form does not unlock the materials or subscribe you. After you confirm the emailed link, we record your name, email, request and confirmation times, delivery status, and the choices you made. Field Notes is a separate, optional box, unchecked by default; leaving it unticked never subscribes you.

We do not collect individual reading statistics for the REAPS materials. We keep the verified access request, but do not record which presentation, guide or resource pages you read. A necessary access cookie keeps your materials available after you confirm your email.

We use rate limits and a keyed IP hash to limit abusive access-email requests. That hash is cleared after one day on the next resource request. Unconfirmed requests expire after seven days; confirmed request records after one year. Expired records are removed when this service next handles a request. Confirmed contact and consent records in our customer relationship system follow the retention policy below.

Ask Briu, the site assistant

Ask Briu answers questions about Briu from the pages of this site. It runs on Subsights and loads only when you open it. After that, it also loads on the pages you visit next, so the conversation can continue. Please do not type passwords, account numbers, or other sensitive details into it.

Subsights stores what you type and each answer, with the time of each message, any rating or comment you leave, and how the chat was used. It also keeps a summary and topic for each conversation. Briu reads these conversations to improve the answers.

To answer, your question and the most relevant parts of this site go to OpenAI, which writes the answer, and to Voyage AI, which ranks which parts fit best. LangSmith, by LangChain, keeps a trace of each answer, and Amazon Web Services hosts the service. These providers handle that information under their own terms.

We have not set an automatic deletion period for chat conversations. You can ask us to delete yours at hi@briu.ai.

Opening a proposal

Before optional engagement tracking starts, the proposal offers two choices. Continue records that the proposal was opened and which authored sections were viewed, so we can follow up. Open without tracking opens the same proposal with that beacon off. With JavaScript unavailable, the proposal remains readable without the beacon.

The choice and a temporary event-grouping ID stay in the loaded page's memory only. We do not save a proposal identifier in browser storage or recognize returning visitors. Reloading or opening a new page asks again. Workflow selections and anything you type stay on that page and are not sent by the beacon.

If you choose Continue, our server stores the proposal ID, opening and section events, temporary visit ID, event time, hashed IP address, and browser user agent. The hash is not a guarantee of anonymity. We do not collect reading duration, downloads, or button clicks through this beacon.

Access protection is separate from that choice. Requests for proposal links and sign-in link opens can record your email, proposal or token ID, authorization result, delivery status, time, hashed IP address, and user agent. These security records and necessary sign-in cookies still apply when you open without tracking.

Desk sign-ins and tool use

Desk records sign-ins and whether a tool was opened or run, when it happened, and whether it worked. Records can be associated with your account and sign-in identity. We use them for two purposes only: security, to spot misuse or unusual access; and engagement, to see whether tools are used and working so we can fix what is not.

These usage records must never include file or loan content. They are not for monitoring people's performance, scoring individuals, or upselling. Our retention policy for Desk sign-in and tool-use records is 12 months. Automatic deletion for those records is still being implemented; we cannot yet say that older records have been removed.

Working files are separate from usage records. Tools process the materials needed to do the work you request. Desk run files and results have seven-day access expiry; submitted uploads have a 90-day deletion sweep. Audit metadata can remain after a file expires. Older delivered tools have separate usage logging; we are reviewing that logging against the same content limits.

What stays on your device

We remember a theme only when you choose it. Protected proposals and workspaces use necessary sign-in cookies. Proposal and REAPS access cookies last seven days and portal access cookies last 30 days. Desk sign-in cookies can renew for up to 400 days, with a 180-day idle cutoff and server-side revocation. Clearing browser data removes saved appearance and sign-ins.

We do not use advertising cookies, session replay, or a persistent proposal tracking ID. Apart from Ask Briu, the public site does not save form drafts or browsing choices in local or session storage. If you open Ask Briu, your browser saves a random conversation ID, so the conversation can continue from page to page. Clearing browser data removes it.

Hosting and traffic measurement

Cloudflare hosts and secures the site and provides cookieless Web Analytics. We keep that traffic measurement separate from proposal engagement. Cloudflare also processes standard request and security information, which may include IP address, user agent, path, time, country, bandwidth, cache status, and threat signals. Briu's admin system holds traffic summaries such as page views, top pages, referrers, countries, and blocked threats.

Branded short links and Field Note share controls can record the link or action, campaign, referrer, country, time, and a daily visitor key derived from request information. They do not save that key on your device. Some proposals also load fonts from Google or scripts from jsDelivr, which receive the requests needed to serve those files.

Who helps us operate

Customer materials and retention

Customers may provide reports, exports, documents, or access to business systems. We process those materials to deliver the agreed work, on the customer's instructions. We do not sell them or use them for another customer. Contact us to arrange return or deletion when they are no longer needed for the work.

The 12-month Desk usage policy above does not describe every record we hold. Inquiries, mailing-list records, proposal access and engagement records, and business communications are kept as needed for the relationship, service, security, and business obligations. We have not established a single automatic deletion period for those records or all provider backups. Unsubscribe status may be kept to respect your choice.

Your choices

Use a Field Notes email's private link to change frequency or unsubscribe. Choose Open without tracking at proposal entry to decline its engagement beacon. To change a proposal choice, reload the page; declining then stops new beacon events but does not erase earlier records.

You can ask us to review, correct, or delete your information, or ask about our providers and retention. Some records may need to remain for active service, security, or legal obligations. If that affects your request, we will explain.

For privacy requests, email hi@briu.ai.