Cloud Replicator Documentation
Index

Privacy Policy

This document describes how Cloud Replicator handles data and what information is processed during operation.

Overview

Cloud Replicator is a data replication tool that transfers data from your Business Central environment to Azure cloud destinations that you configure and control. Understanding data handling is important for compliance and privacy considerations.

Data Processing

What Data is Processed

Cloud Replicator processes:

  • Business Central table data that you configure for replication
  • Field values from selected tables
  • System fields (SystemId, SystemCreatedAt, SystemModifiedAt, etc.)
  • Company name information

What Data is NOT Accessed

Cloud Replicator does not:

  • Access tables not configured for replication
  • Process data from companies not included in filters
  • Access user passwords or credentials (except cloud access keys stored in setup)
  • Access Business Central user account information beyond system fields

Data Flow

Replication Flow

Business Central (Source)
    |
    | Read configured tables
    v
Cloud Replicator (Processing)
    |
    | Transform and format data
    v
Your Azure Resources (Destination)

Data Stays Within Your Control

  • Source: Your Business Central tenant
  • Processing: Within your Business Central session
  • Destination: Your Azure subscription and resources

Cloud Replicator does not transmit your business data to Hougaard or any third party.

Credentials and Authentication

Cloud Credentials

You provide credentials (access keys) for your Azure resources:

  • Stored in the Cloud Replicator Setup table
  • Stored within your Business Central database
  • Displayed as masked (hidden) in the user interface
  • Used only for connecting to your specified Azure resources

License Validation

For license validation, Cloud Replicator contacts the Hougaard license server:

Data Transmitted:

  • Registration key (license key)
  • Business Central tenant identifier
  • License validation request

Data NOT Transmitted:

  • Business Central data
  • User personal information
  • Cloud destination credentials

Purpose:

  • Validate license authenticity
  • Determine license expiration
  • Enable/disable features based on license status

License Server Communication

Endpoint Purpose
check.hougaardlicense.com License validation

Communication is:

  • Encrypted (HTTPS)
  • Only occurs during license registration/validation
  • Does not transmit business data

Data Residency

Business Central Data

Your Business Central data resides in:

  • Your Business Central tenant region
  • Microsoft's Business Central infrastructure

Replicated Data

Your replicated data resides in:

  • The Azure region where you create your resources
  • Under your Azure subscription control
  • Subject to your Azure configuration and policies

Recommendations

For compliance requirements:

  • Choose Azure regions that meet your data residency requirements
  • Configure appropriate access controls on Azure resources
  • Review Azure compliance certifications for your industry

Security Considerations

Access Control

Component Access Control
Cloud Replicator Setup Business Central user permissions
Table Mappings Business Central user permissions
Azure Resources Your Azure access policies

Credential Security

Protect your cloud credentials:

  • Limit who can access Cloud Replicator Setup
  • Rotate access keys periodically
  • Use Azure security best practices

Data in Transit

All data transmission uses:

  • HTTPS (TLS encrypted)
  • Azure service authentication
  • No unencrypted data transfer

Data at Rest

In destinations:

  • Azure services encrypt data at rest by default
  • Additional encryption options available per Azure service
  • Configure per your security requirements

Compliance Considerations

Your Responsibilities

As the data controller, you are responsible for:

  • Determining which data to replicate
  • Ensuring compliance with applicable regulations
  • Configuring appropriate security controls
  • Managing access to replicated data

Cloud Replicator's Role

Cloud Replicator:

  • Provides the mechanism for data transfer
  • Does not independently determine what data to process
  • Acts under your configuration and control

GDPR Considerations

If you process EU personal data:

  • Evaluate your Azure region selection
  • Consider field-level exclusions for sensitive data
  • Review Data Processing Agreements with Microsoft/Azure
  • Document your data flows

Industry Regulations

For regulated industries:

  • Review Azure compliance certifications
  • Configure appropriate audit logging
  • Implement access controls
  • Document data handling procedures

Data Retention

In Business Central

Cloud Replicator stores:

  • Configuration settings (indefinite)
  • Replication logs (accumulate over time)
  • Engine pulse records (temporary, overwritten)

Manage retention by:

  • Archiving old replication logs
  • Deleting obsolete table mappings

In Azure Destinations

Data retention in Azure is:

  • Controlled by you
  • Based on your Azure policies
  • Independent of Cloud Replicator

Implement retention by:

  • Configuring TTL in Cosmos DB
  • Setting lifecycle policies in Table Storage
  • Managing indexes in AI Search

Changes to This Policy

This privacy policy may be updated to reflect:

  • New features and capabilities
  • Changes in data handling
  • Regulatory requirements

Review this document with Cloud Replicator updates.

Contact Information

For privacy-related questions:

Hougaard Website: https://hougaard.com Privacy inquiries: https://hougaard.com/privacy