Skip to main content
addly

Trust starts where slogans stop.

The Trust Center brings together the questions an administrator, buyer, or security team must resolve before installation. It distinguishes facts, intentions, and evidence that is still absent.

Inspect securityView data

No decorative evidence

No certification, Marketplace badge, customer count, availability claim, or audit without a publishable source.

The evidence register before the brochure.

Each row states what is available today and what must be replaced with real evidence before publication.

Exportable evaluation packetAvailableEach app produces a Markdown register of evidence and blockers.Marketplace security preparationAvailableThe 28 partner-questionnaire topics start empty, then become a sourced local export.Permissions by appDocumented in the showcaseDisplayed scopes remain intentions until a manifest is published.Data flows and retentionStructure readyPublic writes remain blocked until privacy information is complete.Production subprocessorsLocal state publishedNo production provider is connected; the future register will be app-specific.AccessibilitySelf-assessment publishedThe AA target, current controls, and missing tests are separated.Product security advisoriesNot applicableNo versioned product is distributed; the future register format is public.Certifications and complianceNot claimedNo badge or audit is invented.Availability and incidentsModel readyNo uptime percentage is claimed.Support and escalationPath definedProduction channels still need configuration.

A trust profile for every app.

The global register defines the method. Each profile then connects actions, data categories, and evidence to the exact product scenario, with an exportable vendor questionnaire.

Readiness for JiraJira · Issue panel
3 documented actions2 inspectable evidence · intentions and blockers separatedOpen profile
Portfolio InsightsJira · Project page
3 documented actions2 inspectable evidence · intentions and blockers separatedOpen profile
Page SummaryConfluence · Content macro
3 documented actions2 inspectable evidence · intentions and blockers separatedOpen profile
Context LinkerConfluence · Context panel
4 documented actions2 inspectable evidence · intentions and blockers separatedOpen profile

The packet answers in audit order.

This sequence avoids searching for a permission in a FAQ, retention in a PDF, or an incident in a social thread.

  1. 01What can the app do?Scopes, access, and least privilege.Permissions
  2. 02Where does the data go?Input, processing, storage, output, and deletion.Data flow
  3. 03What evidence exists?Controls, attestations, and gaps without a fictional badge.Compliance
  4. 04What happens during an incident?Status, communication, recovery, and retrospective.Availability

A security team should be able to say yes—or no—with the same information.

Review permissions, data, and compliance, then export the evaluation packet with the evidence still required.

Build the packetPrepare a request