PUBLIC SUPPORT RECORD · JULY 27, 2026

Report precisely. Share no secrets.

Never send Stripe keys, passwords, payment details, customer records, private exports, or other credentials through social media or chat.

Product questions

First inspect the formula guide, readiness benchmark, and submission dossier. They document the data, formulas, current limitations, and deployment status.

Corrections

A correction request should identify the exact page, the exact statement believed to be wrong, and a public primary source that supports the correction. Do not include private records.

Security reports

Report the affected public URL, expected behavior, observed behavior, and a minimal reproduction that contains no sensitive data. Do not test against accounts or systems you do not own.

Contact

Contact Marco through his verified LinkedIn or Instagram profile. Begin with a non-sensitive summary. A public social profile is not an appropriate channel for credentials or confidential attachments.

Response boundary

No response time or resolution is guaranteed. External platform issues remain subject to the relevant provider’s support process, availability, security policy, and terms.