Skip to content
Security & Trust

Clear about what we protect — and what we can prove.

DETUPAZO is building trust the same way it is building the product: carefully, transparently and without overstating what is not yet verified.

Our approach

Trust starts with clarity.

These are editorial principles for how we talk about trust during early access, not audited policies or certified controls.

01

Truth over marketing

We publish security statements only when the available evidence supports them.

02

Keep boundaries clear

We distinguish this public website from the separate application sign-in destination.

03

Ask for less

The marketing site does not need account credentials or payment details to explain the product.

04

Update with evidence

As verified information becomes available, this page can reflect it. No schedule or outcome is implied.

Verified today

What we can accurately say today.

These statements are limited to behavior and links visible in this website project. They do not describe security controls inside the application.

Verified in website source

Separate destinations

This website links to the DETUPAZO application at app.detupazo.com for sign-in.

Verified in website source

Local contact check

The current Contact form checks entries in the browser. It does not send or store a message.

Verified in website source

No checkout here

The public Pricing page presents commercial information without a billing or payment form.

Access boundaries

Public website and account access are separate.

The pages here explain the product. The Sign In link points to the application on its own domain. This distinction does not imply any particular authentication control in the app.

Public marketing

detupazo.com

Product, solutions, pricing and company information. No marketing-page sign-in form.

Application destination

app.detupazo.com

The configured Sign In link leads to the application.

Sign In
On this website

Collect only what is needed.

This section describes the current marketing website, not the application’s handling of customer data.

Contact form

It checks entries locally and does not send or store messages. The page asks visitors to avoid unnecessary or sensitive information.

Pricing page

It has no payment or billing-detail collection form.

Marketing pages

They do not require account credentials to read product information.

Unclaimed

No badge without proof.

We are not currently making these public claims. An absence of a claim here is not a statement about every practice in the application.

As DETUPAZO matures, verified security and compliance information can be published here when evidence exists.

No public claim
  • SOC 2 or ISO 27001 certification
  • HIPAA or PCI DSS compliance
  • Independent penetration testing or external security audits
  • Audited encryption controls
  • Guaranteed backup frequency or recovery targets
Security questions

Answers with clear limits.

The current public position, based on what this website can verify.

Is DETUPAZO SOC 2 certified?

We are not currently making a public SOC 2 certification claim.

Is DETUPAZO ISO 27001 certified?

We are not currently making a public ISO 27001 certification claim.

Does the marketing site collect sensitive information?

The marketing pages do not ask for account credentials or payment details. Please avoid putting sensitive information in the Contact form.

Where do I sign in?

The Sign In link opens the separate DETUPAZO application at app.detupazo.com/login.

Does the Contact form store my message?

No. The current form validates locally and does not send or store the message. It is not a reporting channel.

Where will future security information appear?

This page is the place for public, verified security information when it becomes available. No publication date is promised.

How can I report a security concern?

Review the Contact page for current options. A dedicated security-reporting channel is not published, and the current form does not deliver messages. Do not enter secrets or customer data there.

Contact guidance

Found a security concern?

Review the Contact page for current options. A dedicated security-reporting channel has not been published, and the current Contact form does not send messages.

Keep sensitive details out of the form

Do not enter passwords, API keys, private tokens, customer data, or exploit payloads containing sensitive information.

The Contact page explains the current delivery limitation.

Explore with confidence in the facts

Trust should be based on evidence.

Explore the product, review the current scope, and use the Contact page for guidance on security or trust questions.

Review current pricing status ↗