Privacy, explained for a local desktop product

1. Scope

This Privacy Policy applies to:

• the website at ddc.cloudsyncdev.online;
• the DDC Guardian 365 Windows desktop application as currently documented;
• support interactions with CloudSyncDev through support@cloudsyncdev.online.

Your organization's Microsoft 365 tenant, Microsoft identity services and Microsoft Graph are also governed by your agreements and privacy terms with Microsoft. Customer-deployed infrastructure or distributor services may have additional policies.

2. Website data

The current website is a static Azure Static Web Apps–ready project. It does not include an analytics SDK, advertising pixel, behavioral profiling script, contact form or marketing cookie banner because no tracking is enabled by the website code.

Infrastructure providers may process standard technical request information needed to deliver and secure the site, such as IP address, request time, URL, user agent and diagnostic logs, according to their own service terms and configured retention. CloudSyncDev does not use the website code to read Microsoft 365 tenant data.

3. DDC Guardian desktop processing

DDC Guardian 365 is designed as a local Windows workspace. The desktop interface uses Edge WebView2 and local application services. Operational processing and the runtime SQLite database are local to the device.

Local does not mean that no data leaves the device. Microsoft authentication and Microsoft 365 discovery, analysis or governed operations use authenticated Microsoft endpoints, including Microsoft Entra and Microsoft Graph. Licensing or signed revocation-list checks may use a configured CloudSyncDev endpoint unless disabled for an approved fully offline deployment.

4. Microsoft identity

DDC Guardian uses a customer-owned public-client application, authorization code with PKCE and delegated permissions. Microsoft handles the sign-in UI, password and MFA in the system browser. DDC Guardian does not ask the user to enter a Microsoft password into the application.

The application can store an encrypted delegated token cache locally. In the packaged Windows mode, its local encryption key is protected for the current Windows user with DPAPI.

5. Local application data

Depending on your use and configuration, the current application can store the following below the current user's local Windows application-data directory:

• deployment configuration, including Tenant ID and public Application (client) ID;
• local SQLite operational data, inventory, selected targets, results, reports and audit records;
• encrypted delegated token-cache material;
• license state and locally verified entitlement information;
• rotating diagnostic logs with designed redaction of tokens, cookies, session identifiers, secrets and PKCE verifier values.

These data can contain customer Microsoft 365 metadata. Your organization controls the device, account access, backups, local retention and deletion. The current product documentation directs administrators not to synchronize the DDC local data directory to OneDrive.

6. Content and metadata accessed from Microsoft 365

The product may access SharePoint Online, Microsoft Teams–connected content and OneDrive through delegated Microsoft APIs to build inventory, analyze selected files, calculate findings, produce recommendations and, in Professional with prerequisites, perform approved operations.

Actual access is limited by the signed-in account, delegated permissions, tenant policies, target selection and service availability. DDC Guardian does not claim that every tenant location is accessible or that all file types can be processed.

7. Support communications

If you email support, CloudSyncDev receives the information you provide, including your email address, message, attachments and technical context. Use sanitized descriptions and screenshots.

Support information is used to investigate and respond to the request, protect the product and maintain relevant business records. Retention depends on the nature of the request, legal obligations and any separate customer agreement; this public website does not promise a fixed support-data retention period.

8. Professional licensing

Professional licenses are designed to be verified locally using signed license data bound to the tenant and validity period. The application contains public verification keys, not the private signing key. A configured signed revocation-list endpoint can be checked without transmitting Microsoft 365 content to a license center.

9. Security practices and limitations

The current product includes loopback-only desktop services, public-client PKCE authentication, encrypted token-cache material, sanitized diagnostics, edition gates and fail-closed operation checks. No system can be guaranteed completely secure. Customers remain responsible for endpoint security, tenant permissions, administrator roles, backups, retention, incident response and review of approved changes.

10. Retention and deletion

Application retention controls and local file/database deletion are customer-managed. Professional can persist retention and configuration settings; Community configuration is session-only where gated. Deleting the desktop application's local data may remove inventory, results, reports, audit records, configuration and cached sign-in state. Follow the product documentation and organizational retention policy before deletion.

11. Your choices

• Do not use the website beyond basic browsing if you do not want to make ordinary web requests.
• Do not send optional information to support.
• Use Community read-only/dry-run mode where write operations are not needed.
• Select narrow discovery and analysis targets.
• Revoke Microsoft consent or account access through your organization's Microsoft administration process.
• Remove local product data according to your organization's policy and product guidance.

12. Changes

DDC Guardian 365 is in active development. CloudSyncDev may update this policy when the website, product architecture, support process or applicable requirements change. The effective date at the top identifies the current version.

13. Contact

Privacy questions: support@cloudsyncdev.online
Publisher: CloudSyncDev
Product website: https://ddc.cloudsyncdev.online
Publisher website: https://cloudsyncdev.online