Data handled
Account details, form definitions, responses, uploads, and service usage data may be processed to provide and protect the product.
SECURITY AND DATA
Privacy and security for enterprise teams.
Review how EZhog approaches access, data ownership, retention, privacy choices, deletion, and vendor assessment before rollout.
Trust should be based on current controls and evidence.
EZhog does not use an unverified certification badge as a substitute for due diligence. Procurement teams can request the current architecture, controls, subprocessors, backup, retention, and incident-response information needed for review.
DATA LIFECYCLE
Start with the controls that matter to your data.
Use this overview to prepare your vendor review and request supporting details.
Access and ownership
Accounts and workspace permissions control who can create, review, export, or administer business response data.
Retention and privacy requests
Authorized users can request access, correction, export, or deletion. Retention depends on product, legal, backup, and customer requirements.
Evidence-based review
Request current hosting, backup, subprocessor, incident-response, and control information through [email protected].
CUSTOMER CONTROL
Security starts with knowing where business data is used.
EZhog form workflows can include account information, questions, responses, files, and analytics. A buyer should confirm the exact controls required for that data before rollout.
- Define workspace ownership and access requirements
- Confirm response, upload, and retention needs
- Review integrations and subprocessors before rollout
- Use the public contact channel for privacy and incident reports
SECURITY REVIEW
Privacy controls and vendor evidence in one review.
The website provides granular consent choices designed to support GDPR-style requirements. Buyers can request the current evidence for product and vendor controls.
Hosting and data regionsEncryption and key handlingIdentity and access controlsApplication and infrastructure monitoringBackup and recovery practicesSubprocessors and integrationsRetention and deletion handlingIncident reporting and responseCookie consent and withdrawalPrivacy rights request handling
REPORT OR REVIEW
Send security and privacy questions to one public address.
Do not include credentials, access tokens, payment details, or sensitive customer records in the first email.
[email protected]