findbusinessclient portal
Privacy

Privacy Policy

This is the master privacy policy for FindBusiness. It covers businesses that sign in to the client portal to manage what we run for them, visitors to client websites where analytics is enabled, visitors who chat with a website assistant, shoppers who buy from a shop on a client website, and people who send a request or a message through a form on a client website, or book a time on one. It says what we collect, why we use it, who receives it, how long we keep it, and how we handle changes.

Last updated and effective · What changed

The short version. We collect what we need to run the portal, carry out the changes you request, run billing, generate assistant answers, report on traffic at client websites where analytics is enabled, and keep the service secure. When you chat with an assistant, your messages and its replies are kept for 90 days, plus a one way hash of your IP address for up to 14 days to stop abuse, and the business whose website you are on can read the conversation. If you buy from a shop on a client website, the business is the seller: we hold your order for it, Stripe takes the payment on the business's own Stripe account, and a photo you upload for an order is kept for one year after payment. A request you send through a form on a client website is kept for 12 months. Backups we keep only to recover from failures hold copies for up to 13 weeks after deletion. Our own records all live on Google Cloud, not on servers of our own. We set no advertising cookies, we do not sell your data, and you can ask us to delete your information at any time: admin@dependableaisolutions.com. We tell you about changes as section 13 describes.

1. Who we are and what this covers

Dependable AI Solutions LLC, a California limited liability company ("we", "us", "our"), based in Corona, California, operates FindBusiness and is the controller of the data described here, except for shop orders, form requests, contact messages, and bookings (below). This policy covers seven things: the client portal that businesses use to manage the site or agent we run for them, analytics on client websites we host, the website assistant, the chat panel in the corner of a business's site, shops on client websites we host, and request forms on client websites we host, such as a form for requesting a care package, contact forms on client websites we host, and booking a time with a business on its website.

If you are a visitor chatting with an assistant, the business whose website you are on is a separate company with its own privacy policy covering the rest of their site. If you asked the assistant to put you in touch with that business, what they do with that request is governed by their policy, not this one.

If you buy from a shop on a client website, the business is the seller. It decides how your order is made and delivered and what it does with your details, and its own privacy policy covers that. We run the shop for the business: we hold your order and any photo you upload on its behalf, as its service provider, and handle them as this policy describes.

If you send a request through a form on a client website, the organization that runs the site decides what happens with your request, and its own privacy policy covers that. We store the request for it, as its service provider.

If you send a message through a contact form or book a time on a client website, the business that runs the site decides what happens next, and its own privacy policy covers that. We store your message or booking for it, as its service provider.

2. What we collect

This section is organized by kind of information. Each kind says whose it is: a business with a portal account, a visitor who chats with an assistant, a shopper, or someone who sends a request through a form.

Account and contact details

  • Businesses: your email address and display name from sign-in, the website you tell us you want access to, your account status, and the sites we have linked to your account. We do not ask for or store a password: sign-in is passwordless (a Google account or a one-time email link).
  • Shoppers: a shop on a client website has no customer accounts. We hold your name, email address, and phone number. Stripe's checkout page collects them, and we copy them to the order so the business can reach you about it. If your order ships, the name and US shipping address you give at checkout; if you pick it up, your name. If the business sends you a quote, the name and email the business enters for it, and any phone number, event date, and message it adds.
  • People who send a request through a form: your own name, email, phone number, and relationship to the recipient, your confirmation that they agreed to receive packages, and the recipient's name, rank, mailing address, branch of service, and where they are stationed and until when to send.
  • People who send a message through a contact form: your name, email, phone number if you give one, your business or project name and website if you give them, the topics you pick, and your message.
  • People who book a time: your name and email, any note you add, your answers to the business's questions, your time zone, the time you booked, and your reason if you give one when you cancel.

What you send us

  • Requests and uploads (businesses): the change requests you submit (title and details) and any files you attach to them, such as images or PDFs.
  • Messages (businesses): support messages you send us through the portal.
  • Conversations with the portal's assistant (businesses), if we have turned it on for you: your messages and its replies. It answers from your own account and, when you confirm, files a request, sends us a message, answers a piece of our advice, or sends a version back for changes. These are stored and kept like visitor conversations (section 7), and our staff can read them.
  • Your shop (businesses): if you run a shop, your products, photos, prices, categories, and shop settings; the identifier of the Stripe account you connect and the status flags Stripe reports for it (your identity and bank details go to Stripe directly when you connect); the orders your customers place; and the listing advice we produce for your products.
  • Booking (businesses): if your site takes bookings, your calendar's private address or your Google calendar, the addresses that receive invites, your hours and questions, and your busy times read from the calendar. We keep the busy times only, never the events.
  • Your order (shoppers): what you bought, the options you chose, your answers to a product's questions (such as a name, a date, or a theme), any special instructions, what you paid, and the order's status, tracking, and refund history.
  • Photos you upload (shoppers): if a product asks for your photo, the photo you upload, even if you never check out, and a small preview copy of it where one can be made. When your browser can read a photo, the shop turns it into a new JPEG before uploading it, which leaves behind the location and other hidden details your camera saved. When it cannot, as with an iPhone HEIC photo in some browsers, the photo is uploaded exactly as taken and may keep its location data. Nobody gets a public link to your photo.
  • A request through a form: the details in Account and contact details above, and any dietary notes. Dietary notes can be health information.

Card details are entered on Stripe's checkout page and go to Stripe directly. They never pass through our systems or the business's website.

Conversations with an assistant (visitors)

When you chat with an assistant, we collect only what it needs to answer you, to bill the business fairly, to stop abuse, and to show the business what its customers ask.

  • Your messages and the assistant's replies. The text you type (up to 2,000 characters per message) and the answer generated for you. These are stored.
  • A session identifier. A random id generated in your browser, not by us, and not linked to any account. It groups the messages in one conversation.
  • The page you are on. The path and title of the page carrying the chat panel are sent to the assistant so it can answer in context, and where the business has enabled it, a short extract of that page's own visible text goes with them. This is stored, as part of our record of what we asked the assistant, and it expires on the same schedule as your message (see section 7).
  • Usage counters. Token counts and cost per answer, used for metering and billing the business.
  • On a site with a shop, the assistant answers from the shop's public product list. We store, with the conversation, which products and what kind of question (such as price or shipping) your message was about, and the words you searched for when nothing matched. The assistant cannot take an order, look one up, or accept payment, and it is told to refuse addresses, phone numbers, and card numbers.

What the assistant does not collect. There are no accounts for visitors. We do not record your browser's user agent string, we run no advertising or cross site tracking, we do not build a profile of you, and we do not collect your name, email, or phone number unless you type one into the chat yourself.

Please do not type confidential or sensitive information into the chat. It is an automated assistant on a public web page, your messages are stored for 90 days, the business whose website you are on can read them, and they are processed by a third party AI service. Do not enter payment card numbers, government identifiers, health information, passwords, or anything you would not want handled that way.

Usage and billing (businesses)

Your agent's usage, conversation counts, and remaining credits as shown to you, and a record of credit purchases (the payment itself is handled by Stripe).

Technical, security, and abuse-prevention information

  • Logs. Standard server and security logs.
  • Bot protection. A bot-protection token used to guard checkout (see section 6 for where reCAPTCHA Enterprise runs).
  • Error reports (businesses). Reports of errors in your browser while you use the portal: your account id, the site and page, your browser's user agent, which names the browser, its version and your operating system, and the error with its technical details.
  • A hashed IP address. We take a one way cryptographic hash of your IP address and store only that, to count requests and block abuse: when you chat with an assistant, when you start a checkout or upload a photo in a shop, when you send a request or a message through a form, and when you look at, book, change, or cancel a time. We do not store your raw IP address. A hash of this kind is a pseudonym rather than true anonymization, so we treat it as personal information and retain it as briefly as we can.
  • A random id for your browser tab in a shop, used to limit photo uploads.
  • On a contact form, a one way hash of your email address, and of your email with your message, to limit repeats.
  • Blocked messages. When our screening blocks a message to an assistant, what we keep is described in section 11.

Site traffic

On client websites we host, where analytics is enabled, Google Analytics collects visit and browser or device information, as section 6 describes. When it is enabled for your site, the portal reads summarized reports about visitors, sessions, pages viewed, traffic sources, devices, and approximate visitor locations. The reports come from Google Analytics and are filtered to your site before we show them to you.

3. How we use it

We use what we collect for these purposes.

  • To run the service. To give you access to the portal and connect you to the site or agent we manage for you; to generate an answer to a visitor's question and keep the conversation coherent across their messages; to pass a shopper's order to the business so it can make it and deliver it or have it ready for pickup; to let the organization that runs a request form export the recipient's name and address to ship to them; to deliver a contact message to the business; and to hold a time you booked and send the calendar invites.
  • To carry out the changes you request and keep you updated on them.
  • To take and record payments. To run billing for credit purchases and keep a record of them; to meter assistant usage, bill the business, and enforce the limits that keep costs bounded; and to take a shopper's payment through Stripe on the business's account and keep the business's record of the sale.
  • To send email about the service. For anyone who signs in by email: the sign-in link you ask for. For businesses: an immediate email when a version of your site is ready for you to review, a morning summary when a request is received, declined, or done, usage alerts, and a monthly recap (you can turn the optional ones off in Settings). For shoppers: emails about your order (confirmation, shipped or ready for pickup, tracking, refunds, and any quote), in the shop's name, with replies going to the business, or to us if the business has not set a reply address. For an organization with a request form and a portal account: an email with how many new requests came in, never their contents. For someone who books a time: the invite, any change or cancellation, a link to change or cancel it, and, if you ask, that link again.
  • To show the business what its customers ask. The business can read the conversations its assistant had, in the portal. We also group the questions visitors ask its assistant into topics, after removing personal details, so the business can see what its site does not answer (see section 8).
  • To improve the product. We review what visitors actually ask so the assistants answer better. This is why we keep the conversation text for 90 days. It means our staff can read stored conversations. It is not the same as training an AI model on your messages; see section 8.
  • To advise a shop owner on listings. To suggest other wording for shop listings that name licensed characters or brands, from the listing's text only.
  • To support orders. To support the business with an order.
  • To keep the service secure and prevent abuse (rate limiting, bot protection, and screening for attacks on the assistant), to find and fix errors, and to meet legal obligations.

What we do with a shopper's details, we do for the business they bought from.

A request sent through a form on a client website is used only to let the organization export the recipient's name and address to ship to them, to email the organization a count of new requests if it has a portal account, and to prevent abuse. The rest of the request, including the dietary notes and your own name, email, phone number, and relationship, is stored, unused, until the request is deleted; it is not shown to the organization or exported.

We do not sell your personal information, we do not share it with advertisers, and we do not use it for cross context behavioral advertising.

4. Who receives it

We share data only with these kinds of recipients, and only as needed. We do not sell your data or share it for advertising.

  • Our service providers. Companies that run part of FindBusiness for us: cloud hosting and storage, AI models and safety screening, web search, payments, email delivery, bot protection, analytics, and the tools we use to track and carry out work. Each is named, with what reaches it, in section 5.
  • The business whose website you are on, if you chat with its assistant. It can read your conversation with the assistant in its portal, for as long as we keep it (section 7), and it sees the grouped questions described in section 8.
  • The business you buy from. Everything in section 2 about your order, including your photos, which it can see and download in the portal once your order is paid.
  • The organization running a request form. The recipient's name and mailing address from each request, which its approved staff, or we for it, export, for example to print shipping labels; each export is logged. If it has a portal account, it gets an email with how many new requests came in.
  • The business you contact or book with. It reads your contact message in its portal, usually gets it by email too (not one flagged as spam), and can download its messages; it receives your booking and its invite, and so do up to three more people it names to get every invite.
  • Other approved owners of the same site, for a business's change requests. They see each request's title, type and status and when it changed, the versions we publish for it with our note on each and whether each was approved, and your display name and account id as the person who filed it, but not your own details, notes, or attachments.
  • FindBusiness staff, who can read stored conversations (section 3), see a shopper's photo to support the order, and export a form's recipients for the organization. Access to stored data is limited to staff who need it.
  • The websites the assistant reads. The assistant reads pages of the business's own site live to answer. It sends only the page address and its own identifier. The visitor's IP address and message are not sent; the request comes from our infrastructure.
  • Others, when the law requires it. We may also disclose data if the law requires it, to protect our rights or the safety of others, or as part of a business transfer, in which case this policy continues to apply.

Where it is held. Our records are stored in the United States. If you use FindBusiness from another country, what you send us is transferred to the United States. A request to an AI model or another provider in section 5 may be processed in another country.

5. Our service providers

These are the companies that process personal information for us today, each in a kind of role named in section 4. This list was last updated . When we add a provider in a kind of role already listed, or remove one, we update this list and record it under What changed. A new kind of role is a material change (section 13).

ProviderRoleWhat reaches them
Google Cloud and FirebaseCloud hosting and storageSign-in, database, file storage, hosting, and the functions that run the portal, the assistant, the shops, request and contact forms, and bookings. Stored data lives here, in the United States. Like most websites, our hosting provider records standard request data for security and reliability, under Google's own schedule.
Google Vertex AI (Gemini, and our agent on Vertex AI Agent Engine)AI modelsA visitor's message, the recent conversation, the page context, and facts about the business, in order to generate the reply, and the same for a client's conversation with the portal's assistant. We also use it for three summaries: to group the questions visitors ask a business's assistant into topics (the question and the reply, cut short, with emails, phone numbers, addresses, card and other long numbers, links, and names that follow phrases such as "my name is" replaced first); to compare those grouped questions with the business's public website text; and to suggest other wording for shop listings that name licensed characters or brands (the listing's text only, never photos or shopper details). Removing personal details is automatic and can miss some, such as a name given without one of those phrases. All of this runs on Google's global endpoint, so we cannot promise the request is processed in a specific country.
Google Model ArmorSafety screeningA visitor's message, and the generated reply, sent for screening for prompt injection, jailbreaks, and unsafe or sensitive content.
Google SearchWeb searchThe assistant can search the web when the business's site does not answer a question. A search query derived from the question goes to Google Search; the message is not sent verbatim and the visitor's IP address is not exposed to it.
Google Analytics for FirebaseAnalyticsOn client websites where it is enabled, Google processes visit and browser or device information, including page and session activity, to provide analytics. The portal requests reports filtered to the site's configured data stream and, where needed, its hosts. The assigned business can view summarized visitors, visits, pages, traffic sources, devices, and approximate locations. See Google's Privacy Policy and how Google uses information from sites and apps that use its services.
Google reCAPTCHA EnterpriseBot protectionBot protection on the portal's checkout, the free demo builder, the website assistant, and a request or contact form on a client website where it has been turned on.
StripePaymentsPayment processing for our own billing (credit purchases and orders): the business's email and order details. For a client's shop, payment is taken on the business's own Stripe account: Stripe's checkout page collects the shopper's card, name, email, and phone number, and the shipping address if the order ships, and we send Stripe each item's name, price, quantity, and product picture with its options, the shopper's answers, and instructions (a photo the shopper uploaded appears only as a count). When a business connects its Stripe account, Stripe collects the business's identity and bank details directly. Card details go to Stripe directly and never pass through our systems. See Stripe's Privacy Policy.
ResendEmail deliveryDelivery of the service emails described in section 3, and of a shop's emails about orders and quotes, to its customers and to the business.
Trello (Atlassian)Work trackingThe work cards for portal requests filed before November 12, 2026, with each request's details and links to its attachments. Cards for requests filed since then are on our own work board, stored on Google Cloud.
Fulfillment toolsCarrying out workThe code-hosting and AI automation we use to carry out a portal request may process the request's contents to do the work.

6. Cookies and browser storage

The chat assistant's conversation feature sets no cookies. It uses your browser's local storage, on the site you are visiting, for two things:

Stored itemWhyExpires
fb.agent.sessionIdGroups your messages into one conversation14 days
fb.agent.messages.*Keeps your transcript visible when you return14 days

Both expire 14 days after your last activity and are swept automatically. You can remove them at any time by clearing your browser's site data, which also ends the conversation on your side. If your browser blocks storage (private mode), the assistant keeps them in memory for the page visit and nothing is persisted. On a site with a shop, the assistant also keeps the product cards it showed you (name, link, and picture) in that transcript.

A shop sets no cookies either. It uses your browser's storage, on the shop's site, for:

Stored itemWhyExpires
fbshop:v1:*Your cart, including your answers to each product's questionsWhen you empty the cart, or when the order page you return to from Stripe confirms your payment; there is no time limit otherwise
fbshop:photos:v1:*Small previews of photos you uploaded, so the cart can show themRemoved once they are 3 days old, the next time you upload a photo; otherwise they stay until you clear your browser's site data
fbshop:sessionA random id for the browser tab, to limit uploads (session storage)When you close the tab

The portal queues an error report in your browser's session storage (portal:client-errors) while it sends it. One that fails is sent again with the next report or page load in that tab, and it is gone when you close the tab.

The portal's own pages do not use analytics to track your portal activity. When you preview your website inside the portal, whether your live site or a preview build of pending changes, the page you see loads your site's own analytics, which counts the visit like any other. On client websites we host, Firebase Analytics is enabled by default unless it is disabled for that site. It sends website visit and browser or device information to Google Analytics, including page and session activity. Google uses an IP address at collection time to derive approximate location, then discards the address before storing analytics data. Google Analytics sets first-party cookies (such as _ga) to distinguish visits and sessions. This analytics integration does not send assistant chat messages to Google Analytics. For Google's data handling and browser opt-out, see Google's Privacy Policy and the Google Analytics opt-out add-on. The portal and the assistant demo site load Google reCAPTCHA Enterprise, which inspects browser signals to tell a person from a bot, so that checkout and the free demo builder are not abused. On client websites, the chat assistant loads it the first time you interact with the chat, to protect the chat service from abuse. A request or contact form on a client website loads it only where it has been turned on, the first time you use the form. That is a Google service; see section 5.

Browser signals. Nothing we run changes what it collects when your browser sends a Do Not Track or Global Privacy Control signal. We do not sell personal information or share it for cross context behavioral advertising.

Activity across websites. Besides Google Analytics and reCAPTCHA, our pages and client websites can load web fonts from Google Fonts, and a client website can show a YouTube video the business chose. Through these services, Google may collect information about your activity across different websites over time, under its own privacy policy. A page can also load things from other companies a business chose, which receive your browser's request under their own privacy policies.

7. How long we keep it

For businesses, we keep your account data while your account is active. If we close or delete your account, we remove your account profile, your portal messages, and your sign-in. We retain your change-request records, including the files you attached to them, as a record of the work we did for you and for legitimate business and audit purposes; those are not automatically deleted along with your account. We also keep records we are legally required to keep, such as billing records. You can ask us to delete specific requests or files, and we will remove what we are not required to keep (see Your choices and rights). Your shop's products, settings, and listing advice are account data.

We stopped offering AI images on November 9, 2026. Pictures made before then that were not saved to your site's library are deleted 30 days after they were made. Pictures saved to the library stay until you ask us to delete them. A picture you chose to use was copied into your own uploads and is kept like any other upload. We keep the usage records of past AI image runs so we can show the costs for those months.

Reports of errors in your browser while you use the portal are kept in our logs for 30 days.

A message sent through a contact form is deleted 365 days after it was sent, or 30 days after it was sent if it is marked as spam. A booking is deleted 180 days after the booked time ends. The hashed IP address kept to limit how fast messages are sent and times are viewed or booked expires after about an hour, and is deleted automatically, usually within a day after that. The hashes of a contact form's email address and message expire at the end of the day, or after 24 hours.

A request sent through a form on a client website is deleted 12 months after it was sent. The hashed IP address kept to stop abuse expires after about an hour and is deleted automatically, usually within a day after that.

For assistant conversations, the items below expire automatically; we do not keep conversation data indefinitely.

Google Analytics data is retained according to the retention setting for the Analytics property and Google's policies. The portal does not save report results in your account; it briefly caches them in function memory for up to five minutes.

WhatKept forCounted from
Visitor messages, the assistant's replies, and the page context sent with them90 daysWhen the message was sent
Conversation state (usage counters, limits)14 daysLast activity
The working copy of the conversation our agent on Vertex AI uses while it answersNot stored: it is held only in the running service's memory and dropped as newer conversations replace it or the service restarts 
Hashed IP address (abuse prevention)7 days, and up to 14 days where it is kept with the conversation stateLast request, or last activity
Questions grouped for the business ("what customers ask"), including up to two short examples, in the visitor's words with personal details removed, for each question the site does not answer90 days; a question the business adds to its Advice keeps only the grouped question, as account dataThe day of the conversation
Transcript in the visitor's own browser14 daysLast activity, and it can be cleared sooner
Usage counters and spend limits for the businessUp to about 3 monthsThe billing period

Free demo agents. A demo agent built from our home page stops working seven days after it is created, and the demo and its entire conversation history are deleted about seven days after that. Backup copies of them age out as described below.

For shop orders:

WhatKept forCounted from
A checkout on the shop that is never paid, and any contact details it recorded7 daysCheckout
A paid order, and a quote the business sent you, paid or notNo set period: they are kept as the business's record of the sale until the business or we delete them 
A photo never used in a checkout48 hoursUpload
A photo in a checkout that was not paid7 daysCheckout
A photo on a paid order, including one later canceled or refunded1 yearPayment
Hashed IP address and tab id used to limit checkouts and uploadsAbout an hour, except that the hashed IP address is also kept with a photo's upload record for as long as the photoThe request

Backups. We back up our databases to recover from a failure or a mistake: a rolling seven day history, a daily copy kept for 14 days, and a weekly copy kept for 13 weeks. A file uploaded to us, such as a photo or an attachment, stays recoverable for 30 days after it is deleted. We use these copies only to restore the service. So the periods on this page are how long something stays in the live service. Once it is deleted there, whether on schedule or because you asked, a database record ages out of our backups within 13 weeks, and an uploaded file within 30 days.

8. About the AI itself

  • Answers are generated automatically and may be wrong. They are general information, not professional, legal, financial, or medical advice. For anything that matters, confirm it with the business directly.
  • No decisions are made about you. The assistant answers questions. It does not profile you and it makes no automated decision that produces a legal or similarly significant effect.
  • Summaries for the business. We also use Google Vertex AI to group the questions visitors ask a business's assistant, after removing personal details, and to suggest wording for shop listings. In those summaries, the business sees topics, counts, and, for a question its site does not answer, at most two short examples. Nothing in this is about you as a person, and it makes no decision about you. Separately, the business can read its assistant's conversations themselves (section 4).
  • On training. We do not use your conversations to train our own AI models, and we do not sell or give them to anyone to train theirs. Your messages are processed by Google Vertex AI to generate the reply, and Google's handling of that data is governed by Google Cloud's service terms. Separately, and as stated in section 3, our staff may read stored conversations for 90 days to improve how the assistants answer.

9. Your choices and rights

If you are a business with a portal account:

  • Email preferences. Turn the optional usage and digest emails on or off in the portal's Settings tab.
  • Access and deletion. Email admin@dependableaisolutions.com to see or correct your data, or to close your account. Closing it removes your profile, messages, and sign-in; we retain your request history and its attachments as described in How long we keep it, and will delete specific items on request where we are not required to keep them.
  • Sign-in. Because sign-in is tied to your Google account or your email inbox, you control access through those.

If you are a visitor who chatted with an assistant:

  • Do not chat. The assistant only receives what you type into it.
  • Clear it yourself. Clearing your browser's site data removes the session id and transcript immediately.
  • Ask us to delete it. Email admin@dependableaisolutions.com and we will delete your stored conversation. Because we hold no account for you, tell us the website you were on and roughly when you chatted so we can find the conversation. If we cannot identify it, we may not be able to act on the request.
  • Everything expires on its own regardless; see section 7.

If you sent a request through a form on a client website, or a request was sent for you:

  • Ask the organization first about the request. It decides what happens with it.
  • Ask us to see or delete it. Email admin@dependableaisolutions.com with the website and the recipient's name. Every request is deleted 12 months after it was sent anyway.

If you sent a contact message or booked a time on a client website:

  • Ask the business first. It decides what happens with your message or booking. You can cancel or change a booking from the link in its email.
  • Ask us to see or delete it. Email admin@dependableaisolutions.com with the website and the email address you used.

If you bought from a shop on a client website:

  • Ask the business first about anything to do with your order. It is the seller and decides what happens to it.
  • Ask us to see or delete your details. Email admin@dependableaisolutions.com with the shop's website and your order date or email address. We will work with the business, which may have to keep a record of the sale.

10. California privacy rights

If you are a California resident, the CCPA as amended by the CPRA gives you the right to know what personal information we collect and why, to request deletion or correction, and not to be discriminated against for exercising those rights. Exercise them at admin@dependableaisolutions.com.

We do not sell your personal information and we do not share it for cross context behavioral advertising. For visitors who use the assistant, the categories we collect are internet activity (your messages to the assistant) and identifiers (a hashed IP address and a random session id). For visitors to client websites where analytics is enabled, they are internet activity (pages viewed, sessions, traffic source and device), approximate location (city and country, derived by Google from the IP address) and identifiers (analytics cookies), collected through Google Analytics as described in section 6; for people who buy from a shop, they are identifiers (name, email, phone number, and a hashed IP address), customer records and commercial information (your address and what you ordered and paid), and any photo you choose to upload, held for the business you bought from as described in section 2; for people who send a request through a form on a client website, they are identifiers (names, email, phone number, and a hashed IP address), customer records (a mailing address, the region where the recipient is stationed, and your relationship to them), protected classification characteristics (military rank and branch of service), and sensitive personal information (health information, if you include it in dietary notes), held for the organization as described in section 2; for people who send a contact message or book a time, identifiers (name, email, phone number, business or project name and website, and hashed IP and email addresses) and the content of your message, note, or answers; for businesses, identifiers and account records as described in section 2. The kinds of recipients are in section 4. We may need to verify a request before acting on it, and we may be unable to locate a conversation you cannot help us identify.

11. Security

We do not run our own servers. FindBusiness runs entirely on Google Cloud, in the United States. Your data is held in Google Cloud (Firestore) and processed by Google's AI services. What we operate is the configuration and the connections between those services: which data is sent, what the assistant is allowed to do, and how long anything is kept. Google's physical, network, and platform security is what protects the underlying infrastructure.

On top of that, the specific protections we run:

  • Passwordless sign-in for the portal, with app-attestation and bot-protection checks on sensitive actions like checkout, and access rules that keep each client's data to their own account, sharing with the other approved owners of their site only what section 4 describes.
  • Messages are screened by Google Model Armor before the assistant runs, and we also screen the assistant's answers. It screens for sensitive data, prompt injection and jailbreak attempts, malicious links, and hateful, harassing, dangerous, or sexually explicit content. When it matches, the turn is blocked and the visitor gets a safe message instead. Like any automated filter it is not perfect and can miss things; a turn can pass unscreened if the screening service is unreachable, and answer screening in particular is a best-effort safety net rather than a guarantee, so do not rely on it.
  • Repeated blocked messages pause the chat. If several messages are blocked in a row, the assistant stops answering that browser for a short cooling-off period that grows if it keeps happening. It is keyed to a network address rather than any account, and it lapses on its own.
  • The assistant cannot go wandering. It may only fetch pages on a per business allowlist, and it is refused outright if a domain resolves to a private network address, so it cannot be tricked into reading internal systems.
  • The chat panel is locked to the business's domain. It only runs on the web addresses that business is registered for, so the panel cannot be lifted onto someone else's site to impersonate them.
  • Encrypted in transit with TLS. Access to stored data is limited to staff who need it.

What we keep when a message is blocked. We record that a block happened and which filter caught it. We only keep the message text itself when the filter caught an attack on the assistant, like a prompt injection or a malicious link, because that is something the business is entitled to see about its own traffic. In every other case, including sensitive data, abusive or explicit content, and anything our filters flag but cannot categorize, the text is discarded and only the category is stored.

An honest limit. That protection only works for what the filter actually catches, and it does not catch everything. Payment card numbers it spots reliably, while things like government identifiers or health details can pass straight through, reach the assistant, and be recorded in the conversation log like any other message, ageing out on the schedule in section 7. So screening is a safety net, not a reason to send us something sensitive.

No system is perfectly secure, and we cannot guarantee absolute security.

12. Children

FindBusiness is intended for businesses and adults. The assistant is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has sent information to the assistant, email admin@dependableaisolutions.com and we will delete it.

13. Changes to this policy

We may update this policy. Every update gets a date, and we list it under What changed. There are two kinds.

A material change is one that would:

  • collect a new kind of personal information;
  • use personal information for a new purpose;
  • share it with a new kind of recipient;
  • protect it less, for example by keeping it longer or making your rights harder to use.

A change to what a business's plan costs or includes is covered by our Terms of Service, section 21.

If you have a portal account, we tell you about a material change in the portal when you sign in, or by email, and the portal asks you to accept it. We do not apply it to you first and ask later: it applies to you only once you accept. Until then, the version you last accepted still applies to you, but you cannot use the portal; you can cancel instead, as section 14 of our Terms of Service describes.

If you are a business on a paid plan without a portal account, we tell you about a material change by email at least 30 days ahead, and you can cancel before it applies.

Anyone else, such as a visitor, a shopper, or someone who sent a request or a message through a form or booked a time: a material change applies only to information you give us after it is posted here. We will not apply it to information we already hold about you.

Any other update, such as a correction, clearer wording, removing something we stopped doing, or a new provider in a kind of role already listed in section 5, takes effect when we post it here. A signed-in client also sees a notice in the portal. If you keep using FindBusiness after an update is posted, you accept it. A change never applies to anything that happened before it took effect.

Past versions stay online, listed in section 14.

If you do not agree with a change, tell us at admin@dependableaisolutions.com. You can ask us to delete your information (section 9).

14. What changed, and past versions

Every change to this policy, newest first. A material change is one we asked account holders to accept.

  1. Update We now send the portal's sign-in link ourselves, through Resend, the email provider already listed in section 5, instead of through Google's sign-in service.
  2. Material change We set out how we handle future changes and reorganized this policy. We now say that a business can read its assistant's conversations; it always could, and our earlier policy did not say so. What we do has not changed; this policy now describes all of it. Also: our service providers are in one dated list (section 5); we now cover contact forms, bookings, and the portal's assistant, which were already running; we say where data is held, how we treat browser privacy signals, that Google may collect activity across websites, and that Trello no longer receives new requests. Changes to what a plan includes moved to the Terms of Service.

Earlier versions, by the date each one carried:

15. Contact

Questions or requests: admin@dependableaisolutions.com. See also our Terms of Service.