Data policy

1. Appropriate information

Share a general business problem, intended audience, project goals, desired deliverables, timeline, and optional budget range. Use fictional or anonymized examples to describe workflows. The public inquiry form accepts text only; it is not a document-upload or credential-sharing service. Public article comments also accept text and are moderated before display. Private management image uploads are a separate authenticated feature; they stay private until the owner explicitly changes visibility.

2. Information to keep out

Do not submit passwords, access tokens, private keys, API keys, payment card or financial account details, government identifiers, health records, or private customer and employee records. Do not share confidential source code or other material without permission.

Validation rejects some recognizable secret patterns, but this is not a complete data-loss prevention system. You remain responsible for checking what you send.

3. Current inquiry lifecycle

The browser sends your brief to the website’s same-origin endpoint. The backend validates it, applies abuse limits, stores the inquiry and duplicate-prevention metadata, and returns a receipt identifier. An identical brief or retry may return the existing receipt instead of creating another record.

The stored request is available for administrative review. It does not trigger an AI response, paid task, automated email, n8n workflow, or public publication. A successful receipt confirms storage, not acceptance of a project or completion of review.

4. AI and automation boundaries

The inquiry form does not forward submissions to AI providers or n8n. A separate owner-configured editorial workflow can send public article titles, slugs and editorial instructions to Gemini or Grok after the owner enables the provider, approves generation and sets positive per-run and monthly budgets within a shared application cap of $2 per Los Angeles calendar day. It first creates drafts. Owner-approved automated publication requires independent review of the exact draft, primary sources, claims and links; provider costs depend on the configured model and rates. Application estimates do not guarantee the provider invoice. The separate cloud reviewer may read these editorial drafts and public articles, without access to inquiry, comment or account data. Model responses are not proof that sources or claims have been verified. If a later project uses AI or automation, the provider, data categories, permissions, costs, review requirements, and retention must be agreed before activation. Any such change to this website’s practices requires an updated policy.

5. Project and production data

Before sharing real customer data, regulated information, or production-system access, agree on access roles, storage, transfer methods, retention, deletion, and recovery requirements. Arrange an appropriate secure channel outside this public form. Do not send credentials through inquiry forms or public comments. Authorized owners may enter editorial API keys only in the private management provider-settings form.

Test and staging environments should use synthetic or anonymized data. Production access and public release require their own agreed approvals.

6. Retention and removal

Inquiry records currently have no automatic deletion schedule. For the storage and retention details, read the Privacy policy. To request removal, use the contact form and identify the original email and any receipt identifier without repeating the data to be removed.

If you accidentally submit a secret, revoke or rotate it in the affected service promptly and request removal of the submission. Deleting an inquiry does not revoke credentials that were exposed.

7. Questions and changes

Use the contact form to clarify data requirements before sharing anything sensitive. This page describes the current public website; client-specific data policies and commitments belong in a separate agreement.