What OfflineCreator records in MCP audit logs

Start with the fields OfflineCreator documents publicly

OfflineCreator's Privacy Policy says its sampled API request logs record four categories: route, status code, key identifier, and a truncated one-way hash of the network address. The policy covers Studio's web app, public API, MCP server, and CLI, so this is the current public disclosure relevant to an MCP request. It does not publish a sample rate, a complete event-selection rule, or a promise that every request produces a durable row.

Read each field narrowly. A route identifies the requested application path, while a status code records the response category. A key identifier can associate a logged event with a credential record without being the secret itself. A truncated one-way network-address hash is pseudonymous metadata, not a statement that the underlying address can never be inferred. The public policy does not add prompt text, request bodies, tool arguments, or media to its audit-log field list, but an enumerated list is not proof about every other operational log.

Route

The application path named by the policyThe disclosure does not say that query strings, headers, or complete request bodies are part of this field.

Status

The response status codeA status can show success or failure, but the policy does not promise a complete census of requests.

Identity and network metadata

Key identifier plus a truncated one-way address hashThe policy distinguishes a key identifier from the key secret.

Know the validation level before relying on the log

The verified product evidence for this page is the live Version 2.0 Privacy Policy, effective August 7, 2026. It supports the disclosed field list and an up-to-12-month period for sampled security and audit logs. This research did not capture a production request, inspect a stored row, query a production database, observe a deletion job, or test backups. The retention statement therefore sets a public upper-bound policy, not the observed lifetime of a particular event.

A local implementation review was retained only as rejected provenance because its repository URLs return 404 to unauthenticated readers. Those files cannot serve as rendered support. In particular, this page does not publish the private review's sample rate, schema details, caller attribution, or unit-test result as verified product behavior. A future review needs an accessible first-party implementation document or a controlled production test before those details can move into supported copy.

Verified

Public policy field list and retention statementThe policy is accessible without repository credentials.

Not verified

Deployed sampling, write success, row contents, access grants, and deletionSource inspection is not equivalent to observing production behavior.

Refresh trigger

A public implementation source or controlled runtime evidenceUntil then, implementation-specific candidates remain rejected from rendered support.

Treat sampled logs as partial evidence

The word sampled is the central interpretation limit. An event missing from a sampled dataset is not evidence that the underlying request did not occur. Conversely, a recorded route and status support only what that row shows; they do not establish the full tool arguments, response body, user intent, or all activity around the same session. OfflineCreator's public policy does not disclose enough detail to calculate a total request denominator from these logs.

Do not describe critical events as always retained. The local implementation review produced a more specific candidate, but its source is not publicly accessible and this pass did not test deployed writes. That candidate is rejected from rendered product support. The publishable conclusion remains limited to the policy's word sampled: selection rules, no-op paths, write failures, and durable retention all require accessible evidence or controlled runtime verification.

Safe conclusion

A present sampled row is evidence of the metadata it containsKeep conclusions bounded to the documented fields.

Unsafe conclusion

No row means no requestSampling and untested write behavior prevent that inference.

Needed for incident use

Published selection rules, write-failure behavior, and completeness testsThe public policy alone does not supply those controls.

Do not turn a short field list into a prompt promise

OfflineCreator separately says prompts, settings, and source media submitted through MCP are processed in the same way as web generations. It also says key secrets are shown once, stored only as a hash, and not written to application logs. Those are different statements from the sampled request-log disclosure. The key-secret statement does not say that generation prompts are never processed, and the audit field list does not prove that every infrastructure, provider, moderation, support, or error log excludes free text.

OWASP's application logging guidance recommends excluding or transforming access tokens, passwords, encryption keys, sensitive personal data, and other primary secrets. It also distinguishes ordinary event attributes from extended details such as request bodies and response bodies. That guidance provides a review checklist, not evidence that OfflineCreator implements every recommendation. Ask for a field-by-field data-flow test before treating body exclusion as a system-wide guarantee.

Public product statement

Key secrets are not written to application logsThis statement is about key secrets, not all generation content.

Separate generation path

MCP prompts and source media follow Studio processingReview provider, moderation, history, and analytics evidence on the prompt-privacy page.

Security review

Check tokens, secrets, sensitive data, and body fields explicitlyOWASP recommends exclusion, masking, sanitization, hashing, or encryption depending on the data.

Choose the next review by the unresolved question

Use the MCP security directory when the open question concerns authentication, scopes, uploads, media access, or credential handling. Use the prompt-privacy page when the concern is generation content, provider processing, moderation, account history, or analytics. These links separate adjacent evidence boundaries; they do not imply that a sampled audit row can answer those broader questions.

For an audit-readiness review, request evidence for selection rules, attempted-write failures, production access roles, retention enforcement, deletion, backup handling, and correlation identifiers. OWASP recommends testing logging failures such as database connectivity loss, missing write permissions, storage exhaustion, and runtime errors, while ensuring logging failures do not stop the application or leak information. That is a testing agenda, not a claim about OfflineCreator's current deployment.

Evidence boundary for OfflineCreator MCP audit logs

The supported product conclusion is intentionally narrow: OfflineCreator publicly describes sampled request logs containing route, status code, key identifier, and a truncated one-way network-address hash, with sampled security and audit logs kept for up to 12 months. The public evidence does not establish a sample rate, complete capture, durable writes, exact deletion timing, prompt exclusion across all systems, tamper evidence, or production access roles.

Cloudflare documents waitUntil as a way to extend Worker lifetime for non-blocking tasks such as logging after a response, but that platform behavior is not a guarantee that a database insert succeeds. PostgreSQL documents default-deny behavior when row-level security is enabled without an applicable policy, with important owner, superuser, and BYPASSRLS exceptions; this page does not claim the inaccessible product migration or production roles satisfy that condition. The required recent-community pass found no OfflineCreator-specific audit evidence after classification, while Instagram errored, Reddit was partial, and X was unconfigured, so degraded retrieval is disclosed rather than treated as silence.