Your business information stays under your control.

When you contact Meridian, we receive the information in your message and any examples you intentionally provide. For an initial Workflow Leak Audit, we may ask for a small set of recent, representative examples with customer and employee details removed whenever possible.

Do not send passwords, payment-card information, health information, government IDs, or unredacted customer records through the public contact address.

When you submit the project inquiry, Meridian records the contact details, starting point, problem, recent example, and desired outcome you choose to provide. The system assigns a reference number, alerts Meridian, and sends an acknowledgement to the email address you entered.

The form also records limited campaign context—such as the referring site, first Meridian page visited, and any standard UTM campaign labels—so Meridian can understand which outreach is useful. Campaign context is kept with the inquiry; Meridian does not sell it or use third-party advertising trackers on this site.

To protect the inquiry system from automated abuse, Meridian temporarily stores a one-way digest derived from the network address used to submit the form. The original network address is not stored in the inquiry ledger, and abuse-prevention records are automatically removed after a short retention period.

Meridian counts a small set of interaction steps—page view, service selection, inquiry start, inquiry submission, and checkout opening—to see where the public path is unclear. The record uses a random session identifier that is converted to a one-way digest before storage.

The funnel record does not contain a name, email address, inquiry text, payment details, advertising identifier, or raw network address. Meridian does not use third-party advertising pixels on this site. Anonymous funnel events are retained for up to 90 days and then removed.

We use inquiry information to respond, determine whether the work is a fit, prepare an agreed diagnostic, protect the service, and maintain the records needed to support the engagement. Meridian does not sell personal information or use one client's private operating evidence to train or serve another client.

Any later access is separately documented and limited to the approved workflow. The client keeps ownership of its accounts, domain, data, credentials, and business records. Connected pilots begin read-only, use revocable access, and keep customer messages, payments, refunds, scheduling promises, and production changes under human authority.

Inquiry and engagement records are retained only as needed for the relationship, legal obligations, security, and dispute prevention. A client-specific agreement may define a shorter or more exact retention schedule. To ask about, correct, or request deletion of information you supplied, email the address below.

The guided demonstration uses a fictional business and prepared responses. It does not connect to an inbox or take action in a business system.

If you choose the live assessment, the business description, problem and desired outcome you enter are sent to OpenAI after you confirm the data-handling checkbox. Remove personal information, confidential records, credentials and payment details first. The result is an initial AI assessment for your review.

Meridian does not save your description or generated assessment in its demonstration database. It keeps a request identifier, time, completion status, cost reservation and a one-way keyed digest of the network address and day to enforce usage limits. These usage receipts are retained for launch accounting. The assessment is requested with OpenAI response storage disabled; OpenAI's own API data-handling policies still apply. Your result stays on the current page until you leave or reload, unless you copy it.

No demonstration action sends a customer message, makes a purchase, books work or changes a business system. Contacting Meridian through the separate inquiry form follows the inquiry handling described above.