Privacy, in plain language.

What the site records

If you submit a question, the site stores the question, an optional email address, the page you used, and useful search context such as the query, results shown, and any result opened.

First-party usage events can record the event type, page path, search result count, feedback choice, referrer host, acquisition category, and a redacted version of search text used to identify missing answers. Email addresses, phone-like strings, and full URLs are removed from that operational search text.

If you allow optional analytics, randomly generated visitor and session identifiers are also used. They are not names, accounts, advertising IDs, or email addresses. Google Analytics and Microsoft Clarity receive only bounded event names and public page or resource identifiers. They do not receive search text, submitted questions, email addresses, phone numbers, or complete referrer URLs from Adalocado.

Browser storage and cookies

The answer bank works with optional analytics turned off. The privacy control stores your choice in an essential cookie. Your interaction-sound preference and recent search context can use browser storage to provide those features.

If you allow analytics, Adalocado and its analytics providers can set first-party analytics cookies and create random visitor and session identifiers. A PII-safe first-and-last attribution record can be retained for up to 90 days. Turning analytics off removes Adalocado’s optional attribution and analytics identifiers and asks the analytics providers to stop optional storage. Clearing site data in your browser removes the remaining local values.

Adalocado honors a supported Global Privacy Control browser signal by keeping optional analytics off. Advertising storage, advertising user data, and ad personalization remain denied in every consent state.

Why the data is used

The information supports the editorial question queue, detects repeated missing answers, measures whether resources are opened or rated helpful, measures voluntary handoffs to Rehost monthly management, prevents the team from treating test traffic as demand, and diagnoses operational problems. Reports used for planning are aggregated and suppress one-off search text.

Subprocessor and data-processing disclosure

Cloudflare processes site requests and provides hosting, database storage, security, and aggregate traffic analytics. Google provides the privacy-enhanced YouTube player used on video pages and, after consent, Google Analytics. Microsoft provides Clarity session analytics after consent. These providers process information under their own terms and privacy programs; Adalocado does not authorize them to sell question submissions or use them for Adalocado advertising.

• Cloudflare: request metadata, submitted form data, database records, security events, and aggregate analytics. Read its privacy policy and Data Processing Addendum.
• Google/YouTube: requests made when a visitor loads or interacts with an embedded video, plus consented analytics events that exclude search and question text. Google privacy policy
• Microsoft Clarity: consented interaction and session analytics. Search and question interfaces are explicitly masked in addition to Clarity’s standard input masking. Microsoft privacy statement

Links to Adalo documentation, the Adalo Forum, YouTube, and other external sites follow those sites’ own privacy practices after you leave Adalocado. This list will be updated if another provider begins processing submitted personal information for the site.

Retention and choices

Question and first-party operational records currently have no fixed automatic deletion schedule. They are retained while useful for operating the answer bank, understanding demand, and handling a submitted request. The optional attribution cookie expires after 90 days and the consent-choice cookie after one year. Provider retention follows the configured provider account and applicable provider terms.

Email is optional on the question form, and you can use every published resource with optional analytics turned off. Use the cookie control at the lower-left corner of any page to change the choice.

To ask about or request deletion of information you submitted, use the contact page, describe the privacy request, and include the same email address only if you originally supplied one. Do not submit passwords, API keys, private app data, or other sensitive information.