LOADING THE EXPERIENCE · 000

Security & Trust

Security is part of the design, not a final checkbox.

How we think about your data, your systems and your customers.

AI and automation touch sensitive information. This page explains the questions we work through with you on every project, and is clear about what we do not claim.

  • Data handling
  • Access
  • Review
  • Governance

Why it matters

AI changes who, and what, can reach your data.

  • An assistant connected to your systems can read information people used to look up by hand.
  • Automations can take actions, so mistakes can repeat at speed.
  • Third-party AI providers may process your data under their own terms.
  • Responsibility can blur when several vendors are involved.

How we approach it

Questions we answer with you on every project.

These are the design questions we work through before building. The answers are documented for you.

01

Data handling

Which data is needed, where it is processed and stored, and how long it is kept. We ask for the least data the solution needs.

02

Access

Which people and systems get access to what, scoped to what each one needs.

03

Human oversight

Which actions run automatically, which need approval, and which always stay with a person.

04

Providers

Which AI providers and services would handle your data, and on what terms, so you can decide.

05

Review

Code review, testing and a readiness review before anything goes live, with your security team where you have one.

06

Visibility

Logging and monitoring so you can see what a system did and investigate when something looks wrong.

Governance

Four layers to decide together.

For larger implementations we structure these decisions in layers. Select one to see what is decided there.

Governance

What we decide together
Who approves what, audit trails, model and vendor policies, risk reviews.
What you review
Policies, approval matrix, risk register.

What we do not claim

No certifications we do not hold.

Creatimus does not currently publish security certifications, compliance attestations or audit reports, and this website makes no claim to them. If your project must meet a specific standard or regulation, tell us at the start and we will say plainly what we can and cannot meet.

  • No security guarantee is implied by this page.
  • Requirements for regulated data (for example health or financial information) are reviewed before design begins.
  • Our formal security policy will be published here once it is approved.

Security questions

Can you work within our security policies?

Yes. Share them early and we will plan the work around them.

Will our data be used to train AI models?

Provider choices and their data terms are decided with you before anything is connected, so you can rule this out where needed.

Do you hold certifications?

We do not claim any certifications on this website. Ask us about your specific requirements.

How do I report a security concern about this website?

Email [email protected].

Bring your security requirements early.

Tell us what your organization needs. We will be clear about how we can work within it.

Or call +1 (719) 621-6500 · [email protected]