Cloud Secure supplied product boxshot
Product identityProduct identity; verify the current supported providers and Windows release.
DECISION

Use Cloud Secure only for its local protection role

Cloud Secure may add PC-side protection around supported cloud-sync folders on Windows. It does not provide provider-side TLS or end-to-end encryption, change share permissions, separate Windows identities or guarantee recovery.

Shared-PC scenario

A small office pilots Cloud Secure with harmless sample folders from each supported provider. It records the current app version, protects a test location, checks sync from another device, tests lock and unlock after restart, and documents what remains visible through the provider.

PROCEDURE

Run the control in five steps

  1. 01Verify the current release, license and supported providers.
  2. 02Use harmless files to test one sync client at a time.
  3. 03Check local lock behavior before and after Windows restart.
  4. 04Confirm remote sync and provider shares separately.
  5. 05Test recovery and document approved uses and exclusions.
RECORD

Preserve an accountable test record

Keep app version, installer source, license, provider, local path, Windows account, sample manifest, sync result, restart test, recovery test, exclusions and review date.

Stop and investigate when

  • Local protection is marketed as provider-side encryption.
  • A product screen is treated as independent proof.
  • Recovery is promised without a successful representative test.
BOUNDARY

State what the control does not prove

Not provider-side encryption, cloud account recovery or permission bypass. Verify provider sharing, locally resident copies, Windows access and recovery separately.

PRODUCT EVIDENCE

Read each supplied interface image with its limit

Cloud Secure supplied provider screen
Provider screenProvider selection does not change provider-side sharing permissions.
Cloud Secure supplied protection screen
Protection screenTest the local protection workflow on the current release.
Cloud Secure supplied access screen
Access screenSeparate Windows account permissions still apply.
Cloud Secure supplied settings screen
Settings screenVerify compatibility, sync state and recovery behavior.
Cloud Secure supplied password screen
Password boundaryA local password does not replace cloud-account recovery.
Supplied visuals are not an independent test

Confirm current compatibility, local protection, provider sharing, sync behavior, Windows account separation and recovery.

QUESTIONS

Cloud-folder privacy questions

Does Cloud Secure change Google, Microsoft or Dropbox sharing?

No. Provider identities and sharing permissions remain separate controls.

Do supplied screenshots prove current behavior?

No. They identify the product; test the current release in the actual Windows and sync environment.

PRIMARY SOURCES

Sources for this decision

These sources support the stated boundaries and do not imply endorsement.