You control what Aldwin can access and change.
Aldwin works within the permissions you grant, keeps approvals connected to the work, and records what is released across your systems.
See who a campaign reaches, which path each person takes, and who is held, before anything is sent.
When consent is unclear, the contact is held, not sent. Suppression and frequency rules keep working after launch.
Disconnect a system or narrow its permissions whenever you need to. Aldwin stops using it right away.
Begin with sample data, a sandbox, or a manual handoff, and connect live systems when your team is ready.
Nothing changes without the authority you set.
Review the audience, content, journey logic, sending, warnings, and system actions before consequential work goes live. Aldwin records what was approved, what ran, and what happened next.
Control at every step.
From system access to campaign release, permissions stay scoped, credentials protected, approvals explicit, and activity traceable.
Approval before release
Aldwin prepares changes. Your team decides what runs.
Scoped system access
Aldwin only uses the permissions you grant each connection.
Protected credentials
Connection credentials are encrypted and never shown in the product.
Traceable activity
Drafts, approvals, and syncs are recorded so your team can review what happened.
Your data stays yours
Your data is used to do your work, not shared or used to train models.
What Aldwin reads, and what it writes.
Your systems
Aldwin
Your team
Security review
Review Aldwin before you connect.
Understand how data moves, what Aldwin can access, and how execution is controlled before approving production access.
View the Trust Center- 01
Review the data flow
See what data Aldwin reads, where it is processed, and which subprocessors are involved.
- 02
Define the permissions
Agree on the systems, objects, and permissions Aldwin needs before any connection is made.
- 03
Start in a controlled environment
Use sample data, a sandbox, or a manual handoff when production access is not appropriate.
- 04
Complete the security review
Bring your technical and security reviewers into the process before deployment.
Documents for your review
Security questions
Can Aldwin send anything without approval?
No. Aldwin prepares drafts and changes. Anything consequential, like a send or a write to your CRM, waits for approval of the exact version you reviewed. If that version changes, review reopens.
What does Aldwin need access to in Salesforce?
Only what the work requires, such as reading contacts and leads and creating campaigns. You choose the permissions for each connection before it is made. Salesforce and Account Engagement connections are in development with our design partners.
How are credentials stored?
Connection credentials are encrypted and never shown in the product. They are used only to perform the work you have approved.
Is my data used to train AI models?
No. Your data is used to do your work in Aldwin. It is not shared with other customers or used to train models.
Can we start without production access?
Yes. You can begin with sample data, a sandbox, or a manual handoff, and connect live systems once your team has completed its review.
Do you have SOC 2?
Not yet. SOC 2 is planned. In the meantime, we share our data flow overview, subprocessor list, and standard security answers for your review.