S
Simpleasyty
Trust Center — PLATFORM

PLATFORM

Platform Principles

These are the enduring ideas behind how Simpleasyty builds software. They are written for enterprise reviewers, not for developers, and they are meant to stay true even as the product evolves.

PLATFORM PRINCIPLES

The principles Simpleasyty follows when building Atlassian apps for enterprise customers.

Simplicity First

We keep the product small, understandable, and easy to review so teams can trust it without reading a lot of noise.

Build on Atlassian

We prefer Atlassian-native capabilities and keep the product aligned with the platform customers already administer.

Privacy by Design

We minimize the amount of customer information we process and keep core functionality inside Atlassian where possible.

Least Privilege

We ask only for the access the product actually needs, and we avoid broad permissions that do not support a user-facing benefit.

Transparency

We explain what the product does, what it does not do, and where customers can verify that information.

Long-term Maintainability

We build in a way that can stay understandable and dependable as the product grows over time.

IN PRACTICE

How the principles guide decisions

The principles are not a separate policy layer. They are practical checks used when deciding how a feature should be built, what it should access, and how it should evolve.

Product decisions

When two approaches can achieve the same outcome, we prefer the one with fewer moving parts and the closer fit with Atlassian's native capabilities.

Data and permission decisions

We consider what information and access a feature actually needs, then avoid collecting, processing, or requesting more than that purpose requires.

Long-term decisions

We favour changes that remain understandable, can be explained publicly, and can be maintained without making the product harder for customers to review.

What this means for customers

These principles are why the product aims to stay calm, predictable, and easy to approve. They guide how we make decisions about product design, data handling, and long-term changes.

For the practical architecture behind the product, seeArchitecture. For how the product behaves over time, seeReliability. For customer data protection, seeSecurity.