Security Overview

Security posture in plain language

AppDeploy is built for internal app distribution, so the security model focuses on who can publish apps, who can access them, how Apple Business workflows are connected, and how administrators can review rollout activity.

AppDeploy does not currently claim ISO 27001 or SOC 2 certification. This page separates operational controls from formal third-party assurance so procurement teams can review the product clearly.

Current controls

Product traffic is served over HTTPS, workspace users authenticate through secure sessions, and protected actions check roles and permissions before changes are allowed.

Each organisation has its own workspace boundary. Application checks on every signed-in request keep customer data separated, while audit logs, included on every plan, make important administrative and Apple Business events reviewable.

• Role-based workspace access for members, app managers, auditors, organisation admins, and superadmins
• Audit logs on every plan, with actor, IP address, action, entity, timestamp, and metadata
• Apple Business credentials and private integration material encrypted at rest
• SCIM provisioning for supported Enterprise identity providers
• SAML/OIDC single sign-on for configured Enterprise workspaces
• Abuse protection on sign-in, registration, public install, and API surfaces
• Operational logging and monitoring for incident investigation
• Stripe-hosted billing flows for paid subscriptions
• AutoDeploy, AppDeploy's device management, adds managed installs and zero-touch enrolment for the devices you choose to manage; private apps install on enrolled company iPhones and iPads

Workspace isolation model

Every workspace is attached to an organisation, and protected actions are checked against that workspace boundary.

The server takes the workspace from the signed-in session, filters queries on customer data to that workspace, and re-checks that a record belongs to it before changing it. PostgreSQL row-level security policies are also defined in the database schema. They are not relied on at runtime today; making them effective as a second layer behind the application checks is on our engineering backlog.

• Workspace-level separation for customer data
• Role and permission checks on protected admin actions
• Tenancy re-checked before data is changed
• Controlled migration and rollback process for schema changes

What an enterprise review should cover

An enterprise review should walk through the exact rollout paths your users will touch rather than only checking a generic security list.

For most teams, that means reviewing Apple Business token sync, Managed Apple Account matching, Enterprise SCIM provisioning, SAML/OIDC SSO, employee portal access, app upload controls, audit logs, backup expectations, and incident response ownership.

Enterprise readiness roadmap

Upcoming priorities include deeper upload validation and scanning, more install-flow coverage, admin network restrictions, and additional security evidence for larger buyers.

The public security posture will continue to distinguish implemented controls from formal certification work.

Frequently asked questions

Where is my data stored?

Customer data is hosted in Glasgow, UK, on servers ScotiTech operates. Daily backups are kept on the same server; encrypted off-server backups in the EU are being set up. The DPA and the sub-processor page list each provider that processes personal data, and where. Enterprise buyers can ask us about data flows before production rollout.

Are you GDPR compliant?

AppDeploy is designed for UK GDPR-aligned operation, with privacy, DPA, sub-processor, access-control, audit-log, and data-processing commitments available for review. Formal legal review happens through the DPA or commercial agreement.

Do you transfer data to the US?

The public sub-processor list explains current provider jurisdictions and optional services. Enterprise customers can review sub-processors and transfer safeguards before rollout.

How is sensitive material encrypted?

TLS protects data in transit. Apple Business credentials and private keys are encrypted at rest and handled only for authorised workspace operations.

How do you isolate customer workspaces?

Each customer workspace is separated in the application: every signed-in request is tied to the user's workspace on the server, queries on customer data are filtered to that workspace, and role and permission checks guard protected actions.

Are you SOC 2 certified?

Not yet. The public security posture separates implemented controls from formal certification work so procurement teams can review the product clearly before enterprise approval.