Policy, controls and account choices
Security Overview
Security involves SuiteDash safeguards and the choices you make for your account. This overview points to the current policies, service status and product settings you can check before putting sensitive client work into a portal.

How data is protected
The current Privacy Policy describes administrative, physical and technical safeguards, including encryption in transit and at rest using industry-standard methods, access controls, audit logging, multifactor authentication for administrative access and regular control review. No electronic transmission or storage method is completely secure, so the policy does not promise absolute security.
Amazon Web Services is listed as a cloud infrastructure subprocessor in that policy. An AWS security report describes AWS controls; it does not by itself certify the SuiteDash application.
Configure account access for your workflow
Two Factor Authentication adds an extra sign-in step. With the PLUS Power-Up, administrators can independently require it for Staff, CRM users, or both; authorized administrators can reset a user’s 2FA when needed. Learn about enforcement and recovery. When enabled, Google and Microsoft sign-in lets users connect their own accounts; email and password sign-in remains available. Use the platform’s Roles, Circles and resource permissions to decide who can see client content. Review the file visibility guidance and test with a user account in each relevant role before sharing sensitive files.
Check service status and incident terms
The service status page is the place to check current availability and its displayed history. The Privacy Policy says SuiteDash will notify customers without undue delay, in accordance with applicable law, if a security incident affects their personal data. For a suspected issue, use the contact page to request the secure reporting path.
This overview does not state a guaranteed uptime percentage, backup frequency, recovery time or fixed incident notice window. Check any separate agreement that governs those commitments for your organization.
Review data storage and retention
The current Privacy Policy explains storage, subprocessors, account retention and residual copies in routine backups. It distinguishes active accounts, inactive trials and cancelled or expired paid accounts. Review that policy and your agreement before deciding what data to upload and how long you need to keep it.
The Terms of Service say customers retain ownership of their uploaded content and remain responsible for lawful use, notices and consents when they work with their own clients.
Match the rules to the data you handle
Protected health information
SuiteDash is HIPAA-capable, not HIPAA-by-default. A Covered Entity or Business Associate must execute a Business Associate Agreement with SuiteDash before storing, transmitting or processing PHI. Read the HIPAA guide, Privacy Policy and Terms before rollout.
EU personal data
Review the GDPR Commitment for the Data Processing Addendum process and the Data Privacy Framework Notice for the scope of SuiteDash’s stated certification. Your organization remains responsible for its own lawful use and configuration.
Payment card claims
The older Security Overview linked to a SecurityMetrics vulnerability-scan result. That result identifies a tested site and date; it is not a current, platform-wide PCI DSS attestation. Review the current subprocessor list and request any additional payment assurance documentation needed for your assessment.
What to verify before launch
- Enable the sign-in controls appropriate for Staff and Clients.
- Test Roles, Circles and file visibility with representative users.
- Review message email settings and any Magic Link use for sensitive data.
- Read the current Privacy Policy, Terms and any BAA or DPA that applies.
Need a specific security answer?
Tell the SuiteDash team what data and workflow you plan to use so they can point you to the applicable agreement or support guidance.


