Reference and Case Study Publishing Policy: What, When, and With What Permission Do We Publish?

References and case studies on a technology company's website are the primary areas people look to for trust in that company. Precisely for this reason, they are the easiest places to abuse: unauthorized logos, exaggerated percentages, and brands labeled as "our clients" that were never actually worked with. At Cy Logic, we wanted to clearly outline the rules we apply in these sections; so that you know what stands behind every reference and every case study you see on the site.

1. No references without written publishing permission

Every business we work with does not automatically become a reference. A business name or logo appears in the references section only after written publishing permission is obtained. For group companies, this permission goes through an internal approval process; for other businesses, it is obtained from the authorized representative of the enterprise. References for which permission has not been granted or has not yet been received are recorded in the system but are not listed on the site; they remain in the management panel with the note "awaiting publishing permission."

2. Verification status: the gate between draft and publication

When product, project, and reference records are created in the panel, they are in "unverified" status. Only verified records appear on the site, and this rule is enforced at the database level; meaning it is technically impossible for an editor to accidentally publish a draft project. Verification is answering the following questions: is the scope really this, is the text approved by the client, and are the visuals actual product screens?

3. Numeric claims only with their source

Statements such as "efficiency increased by this much" or "costs dropped by that much" are included only if they are based on the client's own measurement and the client has approved the publication of this figure. Otherwise, we describe the results qualitatively: what became visible, which process was consolidated into a single place, and which discussion was reduced. This may be less striking from a marketing standpoint; however, it is the only form of narration that we will not have to explain in a meeting.

If we cannot prove a figure, we do not write it. If we do not use a logo with permission, we do not display it. If a feature is not yet finished, we say "in development."

4. Worked examples are clearly marked

Some of the case studies in the Insights section are fictional worked examples: narratives written to materialize our approach, not representing a real client. This is clearly stated at the beginning of each worked example, and it carries the "worked example" tag. Real case studies, on the other hand, are published only with the content approved by the relevant client and are linked to the reference record.

5. Certification and guarantee statements

Our service pages feature warning notes under security, infrastructure, and artificial intelligence headings: what we describe is the approach we implement, not a documented certificate or result guarantee. When a certification is completed, we announce it together with its document number and scope; we do not use the phrase "we are compliant" before completion.

6. Visuals and screenshots

Screenshots on product pages are taken from real product versions; design drafts or concept visuals are not presented as screenshots. Screens containing client data are prepared with anonymized or sample data. The publishing permissions of individuals in photographs and the licensing scope of stock visuals are recorded in the media library.

7. AI-assisted content

Artificial intelligence tools may be utilized in the draft stage of preparing Insights articles. These articles are verified by an editor before being published; publication is technically blocked without a verification record. News compiled from external sources is published after editorial review, together with the source link and original publication date.

8. Error reporting and correction

If you find information on the site that you consider incorrect, outdated, or misleading, you can report it via the contact form. Corrections go through a verification process, and the content update date appears on the relevant page. If the publishing permission of a reference is withdrawn, the record is removed from publication on the same day.

Why are we writing this?

For us, these rules are not a marketing preference, but a way of doing business. In the systems we develop for our clients, we apply the principles of "authority resides in data, records are kept, unverified content is not published"; it would be inconsistent for us to behave differently on our own site. That everything you see on the site remains the same in meetings and contracts is the starting condition of a long-term relationship.

In the references and projects sections, you can review records published according to this policy; each record includes verification and publishing status information.