Cloudata product documentation

Use Cloudata products with clear operational controls

This knowledge base covers product setup, permissions, data handling, validation, and recovery. Start with the product guide, then review the shared security and troubleshooting sections.

Choose the right product

Discover, mask, and validate test data

DovaTDM processes CSV, JSON, TXT, XML, and LOG files using deterministic policies. Source content is processed in memory; reports describe detected fields and replacements without retaining original sensitive values.

Recommended workflow

1. Select a policy that matches the target test environment.
2. Upload the source file and review detected categories and confidence.
3. Run de-identification and inspect the audit report.
4. Download the protected output and validate application constraints.

Production checklist

• Use PostgreSQL-backed encrypted storage.
• Rotate the environment policy salt before first use.
• Limit administrative access and review job history.
• Do not use generated output until quality checks pass.

Build controlled browser automation

Create workflows from explicit actions, reusable modules, selectors, and approval points. Validate selectors against the target page and keep sensitive credentials outside workflow definitions.

Operational safeguards

• Use human approval before irreversible actions.
• Prefer semantic selectors and tested fallbacks.
• Record execution outcomes and failure context.
• Restrict workflow permissions to required domains.

Configure Cloudata Text Expander

Create shortcuts for frequently used text, organize them with folders and tags, and use variables for content that changes per use.

Good shortcut design

• Use memorable prefixes that do not collide with normal typing.
• Keep confidential values out of shared shortcut libraries.
• Export a backup before large imports or restructuring.
• Use rich text only when the destination supports formatted content.

Record repeatable browser tasks

Record a controlled sequence, review every captured step, add approval checkpoints, and test against non-production data before regular use.

Extract and clean structured web data

Select a public table or grid, profile its columns, apply normalization rules, preview the output, and export CSV, TSV, or JSON.

Organize browser downloads safely

Build ordered rules using file name, extension, MIME type, or source domain. Generated paths remain relative to the browser Downloads directory.

Monitor meaningful page changes

Monitor a public page or a selected element, set a reasonable interval, and use text filters to reduce alerts caused by timestamps, counters, or rotating content.

Reduce risky clipboard actions

Detect potentially sensitive copied content locally and choose whether to warn, block, monitor, or clear unchanged clipboard values after a defined interval.

Run accessibility checks and reversible adjustments

Run the packaged axe-core audit, prioritize findings by impact, inspect affected elements, and complement automated results with keyboard and screen-reader testing.

Security and privacy baseline

• Grant least-privilege permissions and review them after product updates.
• Keep application secrets and production credentials outside exported configurations.
• Apply retention limits to histories, reports, and operational logs.
• Use approved test data and de-identify production-derived datasets.
• Report suspected vulnerabilities through the support center.

Troubleshooting checklist

1. Confirm the product version and supported browser.
2. Reload the product and reproduce the issue once.
3. Review permissions, input format, and visible error details.
4. Export only sanitized diagnostics.
5. Open a ticket with the expected result and exact reproduction steps.