AEC FieldHunt.Directory preview
← Back to the directory

HOW AEC FIELDHUNT WORKS

What this preview stores.

This describes the current application, not a legal compliance certification. Some account-specific hosting and AI-service processing and retention details have not been confirmed; the limits below explain what we can and cannot promise.

This information describes the directory preview. Listing approval does not grant access to owner controls.

Operator and contact

AEC FieldHunt is operated personally by Jr Mariano. This notice explains how the directory uses information and how to contact the operator.

Mailbox review and AI assistance

Jr Mariano is responsible for operating and curating the directory and reviewing privacy requests sent directly to hello@aecfieldhunt.com. JRM is his AI assistant. Scheduled AI mailbox monitoring is paused for the low-data preview; Jr Mariano handles incoming requests. The read-only mailbox connection remains connected, but is not disconnected or revoked by pausing the schedule. It cannot send replies or delete email through that connection. Information previously processed by JRM may remain in its context as described below. Please send only the information needed to describe your request.

AI context and deletion limits

JRM is an OpenAI dot and may retain context from mailbox messages and conversations for as long as the dot is kept. Disconnecting the mailbox stops new access through that connection but does not remove context already retained. There is currently no self-service control to selectively delete individual dot memories, including details learned from connected services. Deleting the dot starts deletion of its own context; it does not delete separately stored chats, files or ChatGPT memories. Those copies require separate review under their respective controls. We therefore do not promise selective or immediate removal of every AI-held copy. For provider-held personal information, requests can also be made through OpenAI’s Privacy Portal. Whether provider assistance can remove a specific item from dot context has not been confirmed; we do not promise that outcome. See OpenAI’s dots privacy FAQ, checked November 17, 2026.

Services used

The directory uses Airtable for editorial records, OpenAI Sites with Cloudflare-backed application storage for the website, Namecheap Private Email for messages, and JRM, an AI assistant, to support review. Hosting sign-in information is used to authorize protected operations; application operation records can include the acting user ID. Hosting and AI services can also hold records separate from the directory’s application data.

Access and identity

The planned public preview is designed for browsing, searching, filtering and comparing approved listings without a visitor account. Until the operator authorizes public access, the Site’s existing access restrictions still apply. Sign-in remains required for protected owner operations; an invitation does not grant editorial authority. Account-free browsing does not mean that the hosting provider receives no request, device or security information.

Application operation records can include the acting user ID. Hosting-provider account records and logs are separate from application records; this notice does not describe or limit those providers’ practices.

The approved catalog

Airtable is the editorial source. The website reads an approved-only published snapshot stored in Cloudflare D1, not Airtable on every visitor request. Publication includes selected listing and classification fields, record IDs, source links with recorded check dates, and publication timing. Private Airtable Notes are excluded.

Edits and approval withdrawals require an owner refresh before the website snapshot changes. Snapshots expire; expiry prevents display but is not a promise to delete stored data. Source dates describe recorded checks, not independent verification or product testing.

Submissions and retained operational records

Tool submissions are open to visitors who sign in with ChatGPT. The separate owner write pilot remains paused. No newsletter signup, payment or automatic approval-email workflow is being opened. The signed-in submission workflow writes listing information directly to Airtable as Pending Review with sponsorship off. It does not automatically publish submissions. The form requests tool information, not payment details, attachments, or personal contact details. Do not include confidential project records, credentials, or personal information in free text.

The server keeps a submission-operation ledger in D1, including request key, actor ID, payload hash, operation state, timestamps, and result references. This supports duplicate prevention and investigation of uncertain outcomes. The browser tab retains a request key and outcome message in session storage so an interrupted request is not blindly repeated.

Legacy prototype records, audit history, and previously stored images may remain in D1 or Cloudflare R2. Retiring the old editing workflow does not mean those records were deleted.

Saved tools and browser state

Saved tool IDs are kept in browser local storage under “cm-ai-directory:saved”. The application does not send that saved list to its server or synchronize it across devices. Unsave tools or clear this Site’s browser storage to remove the local list. Other users of the same browser profile may see it.

Search text, category, software, task, role, pricing, and listing selections can appear in URLs and browser history. Avoid entering confidential or personal information. Vendor and source links lead to other websites with their own data practices.

Privacy questions and requests

Email hello@aecfieldhunt.com for privacy questions or to request access to, correction of or deletion of personal information associated with you. Please do not send passwords, identity documents or confidential project records.

The link opens your email app. Nothing is sent until you send the message there; you can also copy the address into your preferred email service. Emailing shares your email address and message with the operator and the email services used to deliver it. There is no self-service privacy request form or automatic deletion action on this page.

How requests are reviewed

We may ask for proportionate information to verify your identity or authority before disclosing or changing records. Creating a record or appearing in an email thread does not establish authority over another person’s information. Listing corrections and withdrawals are considered separately from personal-data requests.

For personal-data requests, we identify relevant accessible application, Airtable and email records, document coverage gaps, and explain unresolved copies. We will explain the action taken, any information needed and any applicable limits. This process does not limit rights or response requirements under applicable law.

Retention and deletion

Retention decisions consider why the information is needed: maintaining and correcting the directory, responding to inquiries, preventing duplicate operations or abuse, resolving disputes, meeting applicable legal obligations and recovering the service. There is no single deletion period covering every system.

Removing a listing from the active catalog does not erase historical snapshots or other stored copies. Related case records and AI-assisted review conversations or saved outputs may also contain personal information. Provider histories, logs and backups are subject to separate controls; a complete inventory or provider-level erasure is not assumed.

We do not claim that a request immediately removes every copy. We will distinguish verified changes from records or provider copies whose deletion has not been confirmed.