Security and platform trust
Agencies connect client websites and commercial information to Destiny Manage. This page explains the controls in place today, the limits that still exist during beta, and how to report a concern.
Last reviewed 22 July 2026
How the WordPress connection works
The connector uses a limited API key. It does not ask Destiny Manage to retain a WordPress administrator username or password.
Key created once
Destiny Manage generates a random site API key and shows it once. The platform stores a SHA-256 hash and a short prefix, not the original key.
Stored on the connected site
The WordPress plugin stores the original API key in that site's WordPress options so it can authenticate background requests. It is sent as a bearer token over HTTPS.
A narrow permission boundary
The key can call only the connector registration, data push, command polling and command reporting endpoints. It cannot access account billing, team settings or unrelated client data, and it can be revoked from Destiny Manage.
Installing the plugin still gives it the capabilities described in the plugin and command workflow. Agencies should use normal WordPress access controls, keep the site updated and revoke a key immediately if they believe it has been exposed.
Data protection
- In transit: production traffic is served over HTTPS.
- Passwords: account passwords are stored as one-way password hashes.
- Sensitive secrets: supported integration credentials and selected private configuration values are encrypted using AES-256-GCM before storage.
- Client files: uploaded client files are encrypted before being written to platform storage.
- Scope: this does not mean every ordinary database field is encrypted separately. Access controls and account scoping remain part of the protection model.
Permissions and account isolation
- Agency owners, team members and clients have separate account roles.
- Client accounts are restricted to the client records assigned to them.
- Per-client portal menus and permissions control what a client can see.
- Owner-only actions are checked by the API and are not granted by a WordPress site key.
- Connected third-party services require an explicit account action before they are used.
Hosting, residency, recovery and availability
Data residency
Production infrastructure is deployed in a configured Amazon Web Services region. Customer-selected regional hosting is not currently offered. Contact support before onboarding if a contract requires a particular residency location.
Backups and recovery
Persistent storage and service recovery controls are used, but Destiny Manage does not currently publish a platform backup retention or restoration SLA. WordPress pre-update snapshots are temporary rollback copies on the connected site, not full-site or platform backups.
Availability monitoring
Core services use health checks and restart policies. A public status page and contractual platform availability SLA are not currently published during beta.
Incident response and vulnerability reporting
- 1. Triage: establish the affected service, accounts and likely exposure.
- 2. Containment: revoke affected credentials, isolate the path or disable a service where necessary.
- 3. Investigation and repair: preserve relevant evidence, identify the cause, apply a fix and validate the control.
- 4. Communication: notify affected customers and relevant authorities when the nature of the incident or applicable law requires it.
Send a suspected vulnerability to support@destinymanage.com with the subject “Security report”. Include the affected URL or feature, reproduction steps and impact. Do not access data that is not yours or disrupt the service while testing.
Account deletion and data export
Self-service full account export and account deletion are not currently available in the beta product. An account owner can request an export or deletion by contacting support from the account email address. Identity and ownership may be verified before a request is completed.
Some records may be retained where required for security, fraud prevention, tax, payment or other legal obligations. The privacy policy explains the applicable data rights and contact route.
Sub-processors and connected services
A service is used only where it supports the core platform or the account enables the relevant feature. The list is reviewed as the beta platform changes.
| Provider or category | Purpose | When used |
|---|---|---|
| Amazon Web Services | Application hosting, managed infrastructure and background queues | Core platform |
| Stripe | Subscription and payment processing | When billing is used |
| Google Gemini | Optional AI-assisted product features | Only when an AI feature is used |
| Google PageSpeed Insights | Optional website performance analysis | When a PageSpeed audit is requested |
| Configured email provider | Transactional and support email delivery | When email is sent |
| Customer-connected services | Slack, Jira, GitHub, Linear and other integrations selected by the account owner | Only after an authorised connection |
Sub-processor information last reviewed 22 July 2026.