Data Privacy and Security Overview

    Summary

    This page explains practical data privacy and security guidance for GEVADE CRM users. It helps account owners and administrators review account access, user permissions, sensitive information handling, and configuration responsibilities.

    Important Note

    This page provides general support guidance only. It is not legal, financial, medical, migration, tax, or regulated compliance advice. For account-specific or regulated requirements, users should seek appropriate professional guidance and submit a support request where GEVADE CRM configuration review is needed.

    1. Account access and user permissions

    Account owners should regularly review who has access to the workspace, which users have administrator permissions, and whether staff or contractor access still matches current responsibilities.

    2. Sensitive information handling

    Users should avoid storing unnecessary sensitive information in contact records, conversations, notes, forms, or automations. If sensitive information is required for business operations, it should be handled carefully and only by authorised users.

    3. Communication responsibilities

    If the account uses SMS, email, WhatsApp, phone, or conversation tools, users are responsible for reviewing message content, opt-out handling where relevant, customer consent responsibilities, and appropriate use of communication channels.

    4. AI-assisted tool boundaries

    AI-assisted tools should not be used to guess about private account matters, legal issues, financial issues, medical issues, migration matters, tax questions, complaints, or sensitive customer data. Escalation rules should be reviewed before AI-assisted tools are used with customers.

    5. Data access after staff changes

    When a staff member changes role or leaves the business, account owners should review user access, assigned contacts, conversations, workflows, calendars, billing permissions, and reporting access.

    6. Safe support request preparation

    When submitting a support request, users should include useful examples and screenshots, but should avoid sharing unnecessary sensitive information. Support requests should include the affected area, expected result, actual result, and relevant context.

    Links

    Need account-specific help?

    Submit a request with examples and screenshots.