Explore a partnership Versão em português

Security and GDPR

Security and data protection with fixed rules.

How Caetano Core protects the processes and data of the group’s brands and partners. We describe what we do and point out what we do not yet claim.

Principles

Rules that do not depend on who is working.

They apply to all development and all operation of the platform, across every brand in the group.

  1. Security before speed

    No sensitive change is rushed. First the backup and the approval, then the execution.

  2. Least access necessary

    Each person and each partner accesses only what their role allows.

  3. A trail for every action

    Every action in a process is recorded, with date and author.

  4. People make the decisions

    Automation prepares. Official submissions and destructive operations stay with people.

Separate environments

Development never touches real data.

Development and production are separate environments. What is being built or tested does not work on real processes or real data.

Illustrative diagram: the development environment and the production environment are separate. Real data exists only in production.

Roles and permissions

Each role sees what it needs. Nothing more.

Access to the platform is defined by role. One partner cannot see another partner’s processes.

See roles on the platform page

  • Brand teams

    Work on the processes and documents their role allows.

  • Partners

    See their own organisation’s processes, on the terms agreed in each partnership.

  • Clients

    Follow the status of their own process.

Illustrative representation
Illustrative representation of a process audit trail. It does not show a real screen or real data.

Audit trail

Every action is recorded, with date and author.

When someone changes a status, validates a document or submits a request, the action is recorded in the process. It is always clear who did what and when.

The audit trail provides continuity: the knowledge of each process stays in the system and does not depend on any one person.

Backups

First the backup. Then the change.

Every bulk change and every destructive operation follows the same order. No step is skipped.

  1. Change proposed

    A bulk change or a destructive operation is prepared and described.

  2. Backup

    Before anything is executed, a backup is made.

  3. Approval

    A person explicitly approves the operation.

  4. Execution recorded

    The operation is executed and recorded, with date and author.

Human sign-off

Automation prepares. A person validates.

AI agents handle repetitive work within set rules. The limits are fixed and have no exceptions.

See automation and AI on the platform

  • Submissions to government portals

    None is automatic. The person who validates and submits is always a member of the team.

  • Personal credentials

    No automation or AI agent uses personal credentials, including the founder’s.

  • Destructive operations

    They require approval and a backup made beforehand.

  • Documents

    Automatic reading prepares. Each document is validated by a person.

Data protection and GDPR

Personal data processed with a purpose and within limits.

Vehicle processes involve clients’ personal data. Processing follows the General Data Protection Regulation (GDPR) and three simple principles.

  • Purpose

    Personal data is used for the purpose of each process and for no other.

  • Minimisation

    The principle is to request and process only the data each process needs.

  • Limited access

    Only those who need the data for their work can access it, according to their role.

Transparency

What we do not claim.

We would rather describe the rules we follow than display badges we do not have. This list matters as much as the ones above.

  • Security certifications

    We do not claim certifications such as ISO/IEC 27001 or SOC 2. If any are obtained, they will be listed together with the certifying body.

  • Service levels

    We do not publish service levels or availability percentages.

  • Automation without people

    We do not say that automation or AI replaces people. At critical moments, a member of the team decides.

  • Partner and system names

    We do not publish names of partners, clients or systems that have not been confirmed.

For partners

Requests for security information.

Financial institutions, dealers and other partners may need security information before moving forward with a partnership or an integration. Tell us what you need.

What helps to include in your request

  1. The type of partnership or integration being assessed.
  2. The data that would be involved and in which direction it would flow.
  3. Your organisation’s security questionnaire or requirements, if any.

Need technical information to assess a partnership?

Describe the context and what your organisation needs to know. We review each request as part of assessing the partnership or integration.