# DataGrail Documentation — Full Content > DataGrail is a complete privacy platform built for brands that need to go beyond a box-check solution and build real trust with their consumers. It covers the four pillars of privacy management: data discovery and mapping, DSR (Data Subject Request) management, consent management, and privacy risk assessment. All products are built on the DataGrail platform and powered by patented risk intelligence technology and an industry-best integration network. > > Support: support@datagrail.io | Homepage: https://www.datagrail.io | API Docs: https://docs.datagrail.io/api/v2 | Status: https://status.datagrail.io --- ## Platform Home Source: https://docs.datagrail.io/ DataGrail helps privacy, legal, and security teams reduce privacy risk and scale their privacy program without scaling costs. ### Products **Request Manager** — The #1 automated DSR management platform. Automatically accesses and deletes data across SaaS and internal systems. Supports hundreds of integrations and complete workflow customization aligned to Processing Activities. **DataGrail Consent** — Verifiable cookie and tracker compliance across all web domains. Fast setup via Google Tag Manager. Tracks which trackers are firing in real-time. Supports white-labeled, customizable banners. **Live Data Map** — Superior system detection for a holistic view of applications in your stack. Always up-to-date system inventory, PII details for 2,400+ systems, and dynamic RoPA creation. **Risk Assessments** — Intelligent workflows and auto-populated fields for real-time DPIAs and PIAs. Centrally manage, automate, and export assessments. Covers GDPR, CCPA, CPRA, and AI regulations. **Responsible Data Discovery & Classification** — ML-powered data detection and classification. Automatically identifies personal data on-prem or in the cloud. Auto-populates Processing Activity Reports. --- ## Platform Overview: User Management Source: https://docs.datagrail.io/docs/overview/user-management/managing-users/ DataGrail uses role-based access control (RBAC) across all products. User roles can be managed in Settings > User Admin, which supports Google and Microsoft SSO invitations. DataGrail recommends following the Principle of Least Privilege (PoLP) — assign only the minimum role necessary for a user's tasks. **Key roles include:** - **Super Admin**: Full access to all DataGrail products and settings. - **Connections Manager**: Required to connect integrations and Google Tag Manager. Needed for Consent product integrations. - **Request Admin / Request Agent**: Access to Request Manager settings and request processing. - **Live Data Map Admin**: Full LDM access including adding/removing systems and configuring exports. - **Inventory Manager**: Manage and export Processing Activity Reports. Can be scoped to specific systems. - **Consent Management Admin / Edit / Read**: Tiered access to the Consent product. Modifying roles: Select the user > Edit User > Roles dropdown. For LDM system-level access, use the "Systems to manage in LDM" dropdown. Customers using Group Provisioning or Just-in-Time Provisioning must manage roles in their SAML provider (not in DataGrail directly). ### Inviting New Users Source: https://docs.datagrail.io/docs/overview/user-management/inviting-new-users/ DataGrail restricts access to email domains matching your account's primary domain. To add users with a different domain (e.g., agencies), contact support@datagrail.io to approve the domain. For OIDC providers (Google/Microsoft SSO): Invite via Settings > User Admin > Invite New User. For SAML/SCIM: Assign the user or group to the DataGrail application in your IdP. ### Configuring Okta for SSO Source: https://docs.datagrail.io/docs/overview/user-management/sso/okta/ **Standard configuration**: Install the DataGrail app from the Okta App Catalog, enter your DataGrail subdomain, and copy the IdP Metadata from the SAML Signing Certificates section. Roles are managed within DataGrail. **Group Provisioning** (advanced): Uses a custom Okta App (not the catalog app). Requires creating Okta groups with a consistent prefix (e.g., "DataGrail"), adding Group Attribute Statements in the SAML config filtering by that prefix, then contacting your Account Manager to complete setup. Roles cannot be managed in DataGrail when Group Provisioning is active. **Multibrand Group Permissions**: Map Okta users to Multibrand groups within DataGrail. Configure via Settings > Groups. --- ## Vera (AI Privacy Assistant) Source: https://docs.datagrail.io/docs/vera/overview/ Vera is an AI-powered privacy agent built on responsible design principles. Provides always-on guidance and operational assistance via chat interface or product-embedded actions. ### Key Capabilities - **Context-aware guidance**: Combines connectivity, metadata library, and privacy AI for actionable recommendations specific to your DataGrail environment. - **Customer-specific insights**: Comprehensive risk view across the platform, underscored by the Risk Register. - **Unrivaled security and trust**: Secure, isolated AI agent architecture — zero external training exposure, 100% isolation, time-limited access, sensitive field redaction. ### Example Use Cases - Understanding your data: "Tell me about trends in my activities over the past 3 months." / "What areas of risk should I be aware of?" - Managing workload: "Are there any tickets past due?" / "What risk assessments are in progress and past due?" - Getting guidance: "How should I get started with Consent?" / "Summarize the RoPA Management doc." - Monitoring operations: "Are there any errors processing data subject requests over the past 6 months?" / "What high-risk systems have been detected with a matching integration?" ### Privacy & Security Architecture Core principles: - **Strict tenant isolation**: Architecturally impossible for Vera to access data outside your organization. - **Permission inheritance**: Vera inherits the exact same permissions as the asking user. - **Separation of logic and data**: AI model (Claude Haiku 4.5 on AWS Bedrock) is completely separate from DataGrail's database. No direct database access. - **No training on customer data**: Data is used only as context per request, never for model training. - **Full auditability**: Every data request is logged. Logs available to customers on request. ### Secure Data Access Flow 1. User submits question in Vera chat. 2. A unique short-lived JWT (5-minute) is generated, tied to the user, org, and conversation. 3. Claude Haiku 4.5 on AWS Bedrock processes the question. 4. Vera requests data from DataGrail via a secure MCP API endpoint, presenting the JWT. 5. DataGrail verifies: token authenticity + expiry, tenant match, user match, permission check. 6. Only after all checks pass does DataGrail retrieve org-scoped data. 7. Vera synthesizes the authorized data into a natural language answer. ### Slack Integration Connect via Settings > Slack > Connect Slack Workspace. Map DataGrail users to Slack accounts under User Mapping. Mapped users can DM the Vera bot in Slack with the same capabilities as the web interface. Conversations maintain context within threads. Disconnecting revokes access immediately; user mappings are preserved for reconnection. ### External AI Tools & MCP Source: https://docs.datagrail.io/docs/vera/vera-mcp/introduction-and-use/ DataGrail offers an MCP server for connecting Vera's capabilities to external AI tools and agents as part of broader business operations. Request access through your Account Manager. --- ## Request Manager Source: https://docs.datagrail.io/docs/request-manager/getting-started/ Automates processing of Data Subject Requests (DSRs). Requires three setup components: Foundation Connections, Privacy Request Center, and Integrations. ### Foundation Connections #### Transactional Mailer Enables DataGrail to send emails on your behalf for identity verification and the Direct Contact Workflow. Supported mailers: Amazon SES, SendGrid, MailGun, Mandrill, Emarsys, SendInBlue. Setup: Integrations > Configure New Integration > select mailer > enable only Transactional Mailer capability (not Access/Deletion) > contact support@datagrail.io with Sender Email and Sender Name. Email authentication best practices: Configure Sender Identity verification, SPF records, and DKIM for reliable delivery and spam prevention. Email Templates can be customized post-setup to align with brand and privacy posture. #### Cloud Storage DataGrail stores Privacy Request data in a customer-owned cloud bucket. Data is encrypted at rest and in transit. Supported: Amazon S3, Google Cloud Storage, Microsoft Azure Blob. Setup: Integrations > Configure New Integration > select only Privacy Request Storage capability. Recommended minimum retention policy: 90 days (shorter retention causes errors on in-progress requests). ### Privacy Request Center Hosted on your domain (default: privacy.yourdomain.com). Data subjects submit privacy requests here. Requires CNAME DNS validation. Supports custom text and questions to collect org-specific data needed for processing. **Request Policies**: Determine Privacy Rights offered globally. DataGrail provides default policies for common frameworks. Contact support@datagrail.io to make changes. ### Workflow Automation Source: https://docs.datagrail.io/docs/request-manager/settings/workflow-automation/ Controls for manual review steps. Accessible to Super Admin, Request Agent, Request Admin via Settings > Automation > Request Manager. **Data Subject Requests settings** — Post-verification behavior: - Auto-start extraction + send confirmation email. - Auto-start extraction without confirmation email. - Require manual review before extraction (stays in Active: Wizard State). **Active: Wizard State entry point**: - Step 1: Review all Data Subject information. - Step 5: Jump directly to confirmation email decision. **Deletion Request settings** (optional, must be enabled by Account Manager): - Bypass email verification → move directly to Extracting Personal Data. - Require email verification before extraction. ### Opt Out Requests Source: https://docs.datagrail.io/docs/request-manager/opt-out-requests/ CPRA gives data subjects the Right to Opt-Out of the Sale of their Personal Information. DataGrail handles these through the Privacy Request Center intake form. Upon form submission, DataGrail immediately sets a browser cookie (regardless of verification status) to opt the user out of tracking scripts/pixels on the website. First and Last Name fields are shown but not required for Opt Out Requests. Requests can also be created manually in the Opt Out Requests tab or via the V2 API. The `ccpa_dnsmpi` field can only be set on requests created through the Privacy Request Center. The Opt Out Requests page provides filtering by Verification Status, Request Status, and Location. --- ## DataGrail Consent Source: https://docs.datagrail.io/docs/consent/overview/ DataGrail Consent is a CMP that automates compliance with cookie and tracking opt-in/opt-out. Used by privacy and marketing teams to display region-specific consent options, update policies without developer intervention, audit tracking scripts, and fully customize the consent banner. ### User Roles - **Super Admin**: Full access to all Consent actions. - **Consent Management Admin**: Full access to all Consent actions. - **Consent Management Edit**: Manage containers, policies, banner layouts, tracking services, and publishing. - **Consent Management Read**: View all Consent areas and download Consent Audits. ### Deployment Options **Google Tag Manager (GTM)**: Turnkey integration. DataGrail manages tag execution based on consent preferences and publishes the banner through your GTM account. GTM admin signs in with Google — DataGrail handles the rest. Over 90% of companies use GTM. **Embedded Deployment**: Deploy consent.js directly on your site, with or without GTM. Useful for sites not using GTM or when adding Consent alongside an existing GTM setup. ### Google Consent Mode DataGrail supports Google Consent Mode, which lets Google-owned tags (Analytics, Ads) adapt their behavior to DataGrail consent signals. When a user denies all tracking, Google-owned services continue to fire but send only limited, cookieless, anonymized pings. ### Consent Policies Source: https://docs.datagrail.io/docs/consent/settings/consent-policies/ Geolocation-based policies control tracker execution per region. Each policy corresponds to a regulatory framework (GDPR, CPRA, etc.). **Configuration options per policy:** - **Visibility**: Visible (banner appears until consent is made — required for GDPR) vs. Hidden (banner only accessible via link — common for US opt-out states). - **Layout**: Which banner layout version to show for that region. - **Initial Tracking Behavior**: Opt-in (trackers blocked until explicit consent) vs. opt-out (trackers run until the user opts out). - **Browser Signal Handling**: Whether GPC and DNT signals are honored and which categories are disabled upon receipt. CPRA requires respecting GPC. - **Opt Out Request Handling**: Link offline opt-out requests (from Request Manager) to automatically update online consent preferences. - **US Privacy Strings** (beta): Emit GPP US Privacy Strings (uspv1, usnat) for advertising networks serving personalized ads. Default policies are established by DataGrail under legal counsel guidance. Contact support@datagrail.io to make changes. ### Cookie Management Source: https://docs.datagrail.io/docs/consent/managing-trackers/cookie-management/ Manages first-party cookies only (third-party cookies cannot be blocked due to browser security). If a data subject opts out of a category, matching cookies are blocked and deleted. **Cookie Scanner**: Enable via Plugins > Manage Cookies. Samples cookies from live site traffic (first results in a few hours). Appears in the Unmanaged tab. DataGrail auto-suggests rules based on observed cookies. **Cookie Rules** — wildcard match patterns: - `*` — any characters at end - `{d}` — digit sequences - `{h}` — hexadecimal sequences - `{w}` — alphanumeric sequences Rule fields: Match Criteria, Name, Category, Vendor (optional), Privacy Policy Link (optional), Description (optional), Retention (Time or Session; 400 days default). **Unmanaged Cookie Behavior**: Configure default treatment for unmatched cookies — classify under a category, or block/delete all unmanaged cookies. **Cookie Policy JSON Export**: Copy the JSON URL from Consent Management > Containers > container details. Use this to dynamically generate and display an accurate cookie policy on your website. Best practice: All cookies should be managed. Prioritize script-level blocking first — blocking a tracking script prevents its downstream cookies from being set at all. ### Best Practices for Managing Tracking Services Source: https://docs.datagrail.io/docs/privacy-guides/managing-trackers-best-practices/ Legacy solutions over-rotate on cookie management. DataGrail Consent provides full control over all trackers (scripts, cookies, in-app). Recommended approach: 1. **Tag Manager (GTM, Segment, Adobe Launch)**: Start here — controls the most services with least effort. 2. **CMS Platforms (WordPress, Shopify)**: Use DataGrail browser APIs to pass consent preferences to built-in app control mechanisms. 3. **Inline Scripts (6Sense, AdRoll, HotJar, Drift)**: Use the ScriptControl plugin to gate scripts loaded inline. 4. **Ad Networks** (advanced): Pass consent values to external ad network databases. Note: `