1. Scope Of This Policy
This Policy applies to all ZyCloudTM product surfaces, including the public landing page, progressive web app install experience, local vault flows, local import and export operations, optional authentication connected through Supabase or successor providers, subscription and plan gating, support channels, entitlement verification, diagnostics, abuse prevention, and any future encrypted remote storage or sync lane activated under the ZyCloudTM brand.
This Policy also applies to offline use. The fact that a user operates ZyCloudTM without a network connection does not remove the legal relationship described here. Instead, it changes which systems are involved. When offline, some processing may occur entirely on the user’s device. When online, the app may interact with managed infrastructure for account verification, service integrity, billing status, push messaging, support, sync orchestration, or remote encrypted storage depending on plan and enabled features.
2. Data We Collect
We collect and process different categories of information depending on whether the user remains on Free Pass, creates an optional account, purchases a paid tier, requests support, or enables remote sync or backup features.
- Local vault data: files, thumbnails, encrypted vault blocks, indexing metadata, format metadata, compression results, recovery export artifacts, and device-side preferences stored locally in browser-managed storage or app-managed storage.
- Session and identifier data: anonymous UUIDs, device-scoped vault identifiers, install state markers, acceptance timestamps, entitlement cache markers, and client-generated recovery references.
- Account data: email address, authentication provider identifiers, account creation timestamps, verification status, profile metadata, and account security events when sign-up or login is used.
- Billing and subscription data: selected plan, billing cadence, entitlement status, renewal markers, grace-state markers, cancellation state, payment provider references, invoice references, and fraud-prevention markers. Full card details should be handled by your payment processor rather than stored by ZyCloudTM directly.
- Support and legal request data: contact details, correspondence, attachments voluntarily sent to support, privacy request logs, dispute materials, incident reports, and verification notes.
- Diagnostics and security data: logs, device/browser capability data, service worker state, error events, abuse signals, suspicious entitlement patterns, and rate-limiting markers used to protect the service.
- Remote backup and sync data: encrypted payload blocks, encrypted manifests, object identifiers, sync queue state, version markers, and metadata required to coordinate a user’s remote backup or device-to-device sync lane.
3. Sources Of Data
We obtain data directly from the user, from the user’s device, from account and payment providers, from storage or delivery infrastructure used to operate the service, and from support interactions. Some data is generated by the app itself during encryption, compression, indexing, backup export, restore operations, integrity checks, and entitlement verification.
If the user uploads content to a remote encrypted storage plan, object metadata such as upload time, block size, storage route, and checksum-related verification markers may be produced even when the operator cannot read the plaintext file contents.
4. How We Use Data
We use data to provide and secure ZyCloudTM, improve reliability, enforce plan boundaries, comply with law, and support users. Typical uses include:
- Creating and maintaining local vault state, file indexes, encrypted blocks, previews, and recovery exports.
- Determining whether the user is on Free Pass, Plus, Pro, or Max, and enforcing the rules associated with each tier.
- Authenticating accounts, confirming subscription status, and preventing free-tier users from improperly unlocking paid capabilities through client-side manipulation.
- Operating remote sync lanes, backup queues, conflict resolution markers, and restore workflows when those features are enabled.
- Responding to support tickets, privacy requests, legal notices, abuse reports, and billing questions.
- Monitoring app health, service-worker readiness, offline capability, crash patterns, entitlement failures, and potential fraud or misuse.
- Complying with tax, accounting, security, consumer-protection, data-protection, and lawful disclosure obligations.
5. Local Storage, Browser Risk, And Device-Side Processing
Free Pass is intentionally local-first. On the web, local vault content may be stored in browser-managed storage such as OPFS, IndexedDB, Cache Storage, service-worker caches, and related browser-resident mechanisms. This design reduces server reliance and can provide strong privacy benefits, but it also creates important user-side risks.
- Clearing browser data may delete local vault content.
- Changing browser profile, reinstalling the browser, using aggressive cleanup tools, or factory resetting the device may delete local vault content.
- Private browsing modes, storage pressure, device-management tools, or browser bugs may reduce persistence.
- If the user has not exported a recovery backup, local-only data loss may be irreversible.
Compression, downscaling, thumbnail generation, metadata stripping, encryption preparation, and some sync packaging may occur fully on the user’s device. When those operations occur locally, the resulting data may never leave the device unless the user later enables an account-bound or paid remote service.
6. Optional Accounts For Free Users And Required Accounts For Paid Plans
Free users may create an account voluntarily. An optional account can improve continuity, future upgrade readiness, and entitlement portability, but local-only use can continue without an account where the app permits it. Once a user purchases or activates a paid plan that depends on account verification, remote sync, remote backup, or subscription enforcement, an account may become mandatory.
We use account data to associate entitlements, protect paid features, recover access, manage subscription state, coordinate devices, and secure service operations. We may also use authentication logs, session revocation records, and suspicious sign-in signals to prevent abuse or unauthorized access.
7. Payments, Entitlements, Anti-Fraud, And Subscription Enforcement
Paid access is not granted merely because the client interface says it is. ZyCloudTM is designed so that paid features should depend on server-verified entitlements, account state, or signed access assertions where applicable. This means browser manipulation, local storage edits, UI spoofing, or similar client-side tricks should not be sufficient to unlock paid storage, premium sync, higher retention, or backup privileges.
Payment processing may involve third-party processors. Those providers may process billing identity data, transaction references, tax or compliance information, chargeback signals, and security checks. ZyCloudTM may store only the limited metadata needed to confirm purchase state, provide support, comply with accounting duties, and defend against fraud.
8. Sync, Backup, Remote Storage, And Future Expansion
Paid plans may introduce device-to-device sync, remote encrypted mirror storage, scheduled backups, or managed restore workflows. When remote storage is enabled, encrypted payloads, manifests, key-wrapped metadata, conflict markers, version references, and object identifiers may be transmitted to and stored on remote infrastructure. The purpose of these flows is to maintain continuity, restore capability, and safer multi-device usage.
Where the service is designed to be zero-knowledge or substantially blind to plaintext content, the operator may still process encrypted objects, request metadata, timestamp metadata, billing identifiers, object counts, storage usage records, and abuse or integrity signals. Even strong client-side encryption does not eliminate all metadata processing.
9. Security Measures And Their Limits
ZyCloudTM uses a defense-in-depth approach that may include client-side encryption, authenticated encryption modes, strong randomness, key derivation, chunked encrypted storage, access-control checks, rate limiting, signed entitlement validation, storage isolation, processor controls, transport security, and abuse monitoring. The app is also designed to strip unnecessary metadata during optimization flows where configured.
No system can promise perfect security. Risks can arise from compromised devices, malware, browser vulnerabilities, stolen sessions, weak user passwords, misconfigured deployments, processor outages, social engineering, user-shared recovery material, or third-party platform limitations. Users remain responsible for securing their device, browser, passcodes, login credentials, exported backups, and any recovery material they choose to keep.
11. International Data Transfers
ZyCloudTM may be accessed globally. If a user remains fully local-only, their primary vault content may stay on their device. If a user creates an account, requests support, subscribes, enables remote features, or otherwise interacts with managed services, personal data may be processed in jurisdictions other than the user’s own. Those jurisdictions may have different data-protection laws than the user’s country of residence.
By using account-bound or paid server-backed features, the user understands and agrees that their data, encrypted payloads, account records, support history, entitlement data, and other necessary service information may be transferred to and processed in other countries where ZyCloudTM, its infrastructure providers, or its processors operate.
12. Data Retention
Retention periods depend on the data category, plan type, legal need, operational need, and whether the data exists only locally or also remotely. Local-only vault data may persist until deleted by the user, removed by browser storage pressure, erased by device changes, or destroyed through resets or clear-data actions. Paid remote records may persist for operational continuity, legal compliance, fraud defense, accounting, dispute handling, and service integrity.
- Acceptance logs may be retained to prove legal notice and consent.
- Account and entitlement records may be retained for subscription administration, fraud prevention, and compliance needs.
- Support and privacy request records may be retained to document response history and regulatory compliance.
- Encrypted remote backups may remain until deleted by the user, removed under plan rules, expired under retention controls, or deleted after account closure subject to operational and legal constraints.
13. Privacy Rights, Requests, And User Choices
Depending on the user’s jurisdiction, the user may have rights to access, correct, delete, restrict, object to, or receive a portable copy of certain personal data, and may have the right to withdraw consent where consent is the legal basis for specific processing. Users may also have the right to complain to a regulator.
Because Free Pass can operate locally on the user’s own device, some data may only be controllable by the user directly through app deletion, browser data removal, file export, backup destruction, or device management choices. For account-bound or server-backed records, requests can be made through the support contact methods listed on the Support page.
14. Age Restrictions, Sensitive Data, And High-Risk Uses
ZyCloudTM is not directed to children under the minimum age required by applicable law for independent use of the service. If local law requires parental or guardian consent, the user must not use the service without it. Users should not upload or sync content they are prohibited from storing or transmitting under applicable law.
The service is not marketed as a medical system, legal records vault, emergency archive, or regulated evidence platform. Users should not rely on it as the sole repository for life-critical, legally mandatory, or regulated records without maintaining independent backups and ensuring the deployment meets the rules applicable to their use case.
15. International Compliance Position
ZyCloudTM is intended to operate in a manner aligned with generally recognized privacy and consumer-protection principles, including transparency, purpose limitation, data minimization where practical, security safeguards, user access pathways, and lawful transfer disclosures. Depending on jurisdiction, this may include alignment efforts with frameworks such as the GDPR, UK GDPR, ePrivacy-related requirements, CCPA and CPRA concepts, consumer protection rules, and other international privacy norms.
This statement does not mean every deployment is automatically compliant merely by using the codebase. Actual compliance depends on operator configuration, payment processor choices, storage region selection, support readiness, notice accuracy, data-processing agreements, and operational behavior. Operators remain responsible for launch-specific compliance work.
16. Changes To This Policy
We may update this Policy as the service evolves, especially when adding new authentication flows, billing processors, analytics, sync routes, storage regions, mobile wrappers, native app capabilities, or business operations. Material changes should be reflected by updating the effective date and posting the revised Policy at this location. Where legally required, additional notice or consent may be provided.
17. Contact, Requests, And Legal Notices
For support and privacy matters, use the public support route listed on the Support page. Do not include raw passwords, payment card details, recovery secrets, or private vault file contents in support messages.
Operator: ZyService SM
Product: ZyCloudTM
Technology Stack: Powered By ZYCEDS ENGINE