Skip to main content

Compliance & Legal Guide

Use this section to satisfy privacy, regulatory, and customer audit requirements. If a term is unfamiliar (for example EvidencePack, Transparency Log, or workspace), open the Glossary.

Evidence & audit trail​

  • EvidencePacks (Dralvia's exportable evidence reports): every scan/email/EDR action produces an EvidencePack with a Merkle proof. Download from scan results or call /evidencepacks/<id>.
  • Transparency log: #/transparency exposes the append-only log so you can prove integrity. Contact support if you need an offline verifier or export.
  • Compliance evidence log: use the admin console exports or API endpoints to pull CSV/JSON evidence that can be attached to your SOC 2 / ISO workpapers.
DocumentLocationNotes
Privacy PolicyLegal Center (#/legal-center?doc=privacy)Public-facing draft ready for counsel review.
Terms of ServiceLegal Center (#/legal-center?doc=terms)Align with your own customer contracts before publication.
Cookies PolicyLegal Center (#/legal-center?doc=cookies)Covers SPA + extension telemetry.
DPA templateRequest from supportCustomize per workspace; include EvidencePack references.
DPIA / ROPARequest from supportBase templates you can adapt to your environment.

Workspace onboarding packet​

  1. Docs link: include the public docs URL (this site).
  2. SLA & Support: share the escalation contacts established with your CSM.
  3. Security posture: attach the latest compliance program summary you received from Dralvia.
  4. Data residency: document where your workspace data is processed (region, cloud account) in your own DPIA/ROPA.

Responding to audits​

  • Change management: export release regression and QA gate results and release notes from the admin console; use them to prove gating controls.
  • Access control: export sign-in and admin audit trails for workspace admins, use EvidencePacks to prove who triggered scans.
  • Data subject requests: use the transparency log + EvidencePacks to trace how a domain/email was processed.

Tip: store the EvidencePack ID inside every customer-facing ticket (Jira, ServiceNow, etc.) so you can instantly pull provenance when auditors ask for it.

Sharing with customers​

  • Link to these public docs from your customer portal or onboarding emails so everyone lands on the latest guidance.
  • Keep your internal GRC tooling synchronized with the EvidencePack + transparency log exports so audits move faster.

Quick start (10 minutes)​

Use this flow to complete your first legal/compliance signing cycle.

  1. Open Legal & Compliance from the workspace menu (#/legal-compliance) and review the Overview posture first.
  2. Click Refresh to load current agreement list.
  3. Open Agreements and select one unsigned agreement from the list.
  4. Review content and version.
  5. Click Sign.
  6. Confirm status changes to Signed, then click Download signed PDF.

Deep dive setup flow (GUI + API parity)​

Prerequisites​

  • Workspace user is authenticated.
  • Your role has permission to sign legal agreements for this workspace.
  • Workspace API key and bearer session are valid.

Exact fields to fill​

This page is primarily action-based, not form-heavy. Required selections:

  • Agreement row (id) from the list.
  • Optional: type and version target you want to complete first.

Step-by-step flow​

  1. List agreements in the UI and identify all entries with Not Signed.
  2. Open each agreement and validate title/type/version/body.
  3. Sign in required order (for example NDA first, then service terms, then SOC2 acknowledgement).
  4. Export signed PDFs and store them in your internal GRC repository.
  5. If automating, mirror the same sequence by API:
    • GET /legal/agreements
    • GET /legal/agreements/{id}
    • POST /legal/agreements/{id}/sign
    • GET /legal/agreements/{id}/pdf

Expected result​

  • Required agreements are all Signed.
  • Signed timestamp is recorded.
  • Downloadable signed PDF exists per agreement.

Rollback path​

  • Signed agreements are audit artifacts and should not be deleted ad hoc.
  • If incorrect signer or legal text is detected, open a legal support ticket and issue a superseding agreement version.
  • Keep both versions in audit history for traceability.

Who this is for​

This guide is for workspace owners, workspace admins, and security operators who need clear, repeatable steps without support intervention for day-to-day execution.

Role-based start here​

  • Workspace Owner: Start with Before you start, then complete Step-by-step and Known limits and rate limits.
  • Workspace Admin: Focus on Step-by-step, What each button does, and API and automation.
  • Security Analyst: Start at Day-2 operations and Troubleshooting, then use API error quick reference.
  • Integrator/Engineer: Start at API and automation, then validate with Step-by-step and FAQ.

Before you start​

Use this short checklist before making changes:

  1. Confirm you are signed into the correct workspace account.
  2. Confirm your role includes the permissions needed for this page.
  3. Confirm your browser session is fresh (if pages behave unexpectedly, sign out/in once).
  4. Confirm required prerequisites (API keys, agent enrollment, license, upstream integrations) are already in place.

Step-by-step​

Follow this sequence for predictable results:

  1. Open the workspace from the workspace menu.
  2. Review current status/health/last update indicators before making changes.
  3. Apply one change at a time and save.
  4. Run the available validate/probe/refresh action.
  5. Confirm the expected output appears (status change, new event, successful result).
  6. If behavior is not as expected, use Troubleshooting below before repeating actions.

Day-2 operations​

After initial setup, keep this surface healthy with a simple routine:

  1. Daily: verify data freshness and error banners.
  2. Weekly: review trends, limits, and failed actions.
  3. Monthly: review permissions, keys/tokens, and stale entities.
  4. After any incident: capture evidence and update your internal operating notes.

What each button does​

Button labels can vary by module, but behavior is consistent:

  • Refresh: reloads the latest data from backend APIs without changing configuration.
  • Save: persists workspace-scoped configuration changes.
  • Run/Probe/Validate: executes a non-destructive health or verification action.
  • Download: fetches workspace-scoped artifact(s) (for example bundle, checksum, signature, or report).
  • Verify: checks integrity/consistency and returns pass/fail details.
  • Enable/Disable: toggles module behavior for your workspace; audit evidence should be recorded.

If a button appears disabled, check role permissions, required fields, and workspace license/feature entitlement first.

Self-check playbook​

Use this 5-step isolation flow before escalating:

  1. Configuration: confirm required inputs are present and formatted correctly.
  2. Permission: confirm your role can perform the action (401/403 usually indicates authz/authn mismatch).
  3. License/feature: confirm the feature is enabled for your workspace plan and module toggles.
  4. Quota/rate limit: check for 429 responses and cooldown windows.
  5. Service health: if you see 5xx, retry once after 30-60 seconds and capture exact error text.

If still failing, escalate with workspace ID, UTC timestamp, route, action, payload shape (no secrets), and screenshot/error response.

Troubleshooting​

Use this quick triage order to reduce time-to-fix:

  1. Auth/session: refresh token by signing out/in.
  2. Workspace context: confirm you are in the correct workspace.
  3. Inputs/config: verify required fields and formats.
  4. Quota/license: confirm limits and feature entitlement.
  5. Service health: retry after short delay if backend is transiently degraded.

For escalation, include workspace ID, timestamp (UTC), route name, action attempted, and full error message.

API and automation​

Everything in this page should remain workspace-scoped. If your team prefers automation, use the corresponding API endpoints with the same guardrails as the UI:

  • Use authenticated requests bound to your workspace context.
  • Use idempotency/retry controls where available.
  • Validate outcomes in the UI after automated runs.

If your endpoint mapping is not obvious, start from Help Center and follow the linked API docs.

Next best actions​

After finishing this page, continue with related workflows so your workspace setup stays end-to-end complete:

FAQ​

Q: I clicked save but nothing changed. A: Refresh once, confirm permissions, and verify required fields.

Q: Why do I see missing API key/unauthorized errors? A: Confirm your workspace API key/session is valid and mapped to the correct workspace scope.

Q: Can non-admin users use this page? A: Usually read-only access is possible; write actions require workspace-admin or equivalent roles.

Next steps​

After finishing this guide:

  1. Validate the result in the related dashboard/workspace.
  2. Export or capture evidence if this affects compliance/incident operations.
  3. Share the same runbook internally so other operators follow identical steps.
  4. Return to Help Center for adjacent workflows.

API error quick reference​

Use this matrix when a UI action fails with an HTTP/API error.

ErrorMeaningWhat to do now
401 UnauthorizedSession token is missing/expired or request is not authenticated.Sign out/in, refresh once, then retry. Confirm your session is active in the correct workspace.
403 ForbiddenYou are authenticated but your role is not allowed to perform this action.Confirm your role includes the required permission for this button/action. Ask workspace admin to grant access.
404 Not FoundThe route/resource does not exist in current workspace context (or feature not enabled).Confirm URL/route, workspace context, and feature availability. Refresh and retry; if persistent, capture timestamp and route and contact support.
429 Too Many RequestsRate limit/quota window was exceeded.Wait for cooldown/reset window, retry once, then reduce burst traffic/backoff if automated.
500 Internal Server ErrorBackend failed unexpectedly while processing the request.Retry after 30-60 seconds. If still failing, escalate with workspace ID, UTC time, route, action, and full error text.

Known limits and rate limits​

These limits can vary by plan and feature, but behavior is consistent:

  • Burst traffic can trigger 429 Too Many Requests.
  • Workspace quotas apply per feature/module and reset on configured windows.
  • Repeated retries without backoff can extend recovery time during saturation.

Recommended operator behavior:

  1. Retry once after cooldown for 429 responses.
  2. Use exponential backoff in automation.
  3. Monitor usage/quota dashboards for sustained high utilization.
  4. Request quota review when normal workload regularly approaches limits.