Here is what Tayoca will and will not publish, automate or claim.
Trust is not a badge we add after the work. It shows up in what evidence is required, what data stays private, where automation stops, and who is accountable for a public statement.
When a claim cannot be supported or disclosed safely, the right answer is to leave it out until the evidence and permission are in place.
The rules we apply to public work
These controls cover the material Tayoca publishes about projects, outcomes, reviews, automation and generated media.
Public claims
Material claims need traceable evidence, review and an explicit publication decision. A modelled saving, internal estimate or unverified narrative is not presented as a verified outcome.
Private information
Repository, client, payment and security data stay out of public material unless the information is deliberately approved for publication and safely redacted where necessary.
Automation boundaries
Automation may gather evidence, prepare drafts, route work and execute approved operational steps. Sensitive communications and material public publication remain approval-gated where human accountability is required.
Buyer review integrity
A review is labelled as a verified buyer review only after the purchase is checked against the commerce provider, the submitted buyer email matches the verified purchase record, publication consent is explicit, and a human publication decision is recorded. Critical sentiment alone is never a rejection criterion.
Corrections
Material factual errors are corrected and recorded rather than silently rewritten. Contact support@tayoca.com if you believe a public statement needs correction.
AI assistance
AI may assist research, analysis, drafting and automation. Human accountability remains with Tayoca. AI assistance does not remove the evidence, approval or disclosure requirements that apply to the underlying work.
Credentials and attestations
Professional credentials, certifications, customer logos and similar attestations are displayed only when a current evidence record and publication approval are retained.
Commercial disclosure
Material sponsorships, affiliate relationships, referral compensation and conflicts of interest are disclosed where they could affect how a recommendation is interpreted.
Generated media
Synthetic or AI-generated imagery is not treated as documentary evidence. When generated media could reasonably be mistaken for a real customer, deployment or production screenshot, it is labelled or presented as illustrative rather than factual proof.
A project can be real and still stay off the public website.
Existence is not permission. Client, community and jointly held work can be technically important without being appropriate to name publicly.
Security boundaries
The public website and connected automation are designed so that browser-facing code does not need production credentials or unrestricted operating access.
Browser-facing code
Production credentials do not belong in public HTML or JavaScript. Automation credentials are handled server-side, and administrative capability is separated from ordinary content operations.
Reported concerns
Security or evidence concerns are treated as production-incident class: recorded, contained, corrected and then certified with a rollback path. Report them to support@tayoca.com.
Need the evidence behind a public statement?
The Results page explains what Tayoca counts as public proof and what is deliberately excluded while verification is incomplete.