PRIVACY POLICY – Zividax (Zy Network)
End-to-End Encrypted Chat • AI Transparency • No Third-Party Push Services
1. Eligibility & Age Restriction
You must be at least 16 years old to access or use Zividax (Zy Network). Accounts believed to belong to individuals under 16 will be removed for compliance. Age verification relies on user declaration; we encourage parents to supervise minors.
2. Information We Collect
- Account data: Username, email, password (hashed), and phone number (required for wallet verification only).
- End-to-end encrypted messages: Chat content is encrypted client-side and stored as Base64-encoded ciphertext. Zividax servers never store plaintext messages. Decryption keys remain on user devices.
- Public content: Posts, comments, media uploads that you choose to share publicly.
- Device & usage: IP address, browser type, device model, and session data (for security and fraud prevention).
- AI interaction data: When you explicitly use @ava, @nyzo, or enable third-party AI, relevant prompts are processed. No data is used for AI without user action.
- Optional settings: Preferences, language, and notification opt-outs (only browser-level, no external push frameworks).
- Media uploaded to Cloudflare R2 cloud services: All images, videos, audios, and profile photos that you upload to Zividax are stored using Cloudflare R2. This includes, but is not limited to: chat media attachments, profile pictures, post images/videos/audio files, and any other multimedia content you provide. Such files are hosted on Cloudflare’s secure object-storage infrastructure and may be delivered via CDN for performance. Access to these stored media files is strictly controlled via time-limited signed URLs and authentication tokens. Zividax ensures that media content is not publicly accessible unless you explicitly share it within the platform (e.g., public posts or shared chats).
2.1 18+ Content & Age-Restricted Content
Zividax treats 18+ and age-restricted content as a sensitive area and requires everyone involved in creating, uploading, purchasing, or accessing such content to meet the applicable age requirements.
- 18+ creators: A creator who creates or uploads nude or other 18+ content must be 18 years of age or older.
- 18+ buyers and viewers: Any person who purchases or accesses age-restricted content must also be 18 years of age or older.
- No minors: Content involving, depicting, or sexualizing anyone under 18 is strictly prohibited, regardless of whether the content is monetized or free.
- No monetization does not remove the age requirement: The 18+ creator and 18+ viewer requirements apply even when the content is not monetized, sold, or otherwise paid for.
- Manual review: Zividax may manually review reported or potentially violating content, creator accounts, purchases, or related activity when necessary to enforce these rules.
- Enforcement: If a creator or other account is found to violate these requirements, Zividax may remove the content, restrict access, suspend related features or monetization, suspend the account, or permanently ban the account depending on the circumstances and applicable rules.
- Reels: The same 18+ age and content requirements apply to Zividax Reels. Reels that violate these requirements may be reviewed, restricted, removed, or result in account action.
- Reporting: Users should report content or accounts that appear to involve someone under 18 or otherwise violate Zividax's age-restricted content rules.
These rules are intended to help protect users and maintain a responsible environment on Zividax. Zividax may apply additional restrictions where required by law, platform rules, payment-provider requirements, or other applicable policies.
Zividax provides Chat With Ava, an AI-powered feature designed to answer questions, provide information, and assist users with conversations and other supported tasks. Ava is an artificial intelligence system and its responses may not always be accurate, complete, or up to date.
- AI processing: Ava uses third-party AI infrastructure, including Groq, to process requests and generate responses.
- Public posts: Where necessary to provide relevant answers, Zividax may provide publicly available Zividax posts or other publicly accessible content to the AI processing system as contextual information.
- Private posts are not used for Ava: Zividax does not intentionally provide private posts, private publications, or content restricted to specific users to Ava for the purpose of generating responses or AI processing.
- Only relevant public content: Public content may be processed only when it is relevant to the user's request or required to provide contextual information to Ava.
- Ava may make mistakes: Ava is an AI system and may produce incorrect, incomplete, misleading, or outdated information. Users should independently verify important information before relying on an AI-generated response.
- No professional advice: Ava's responses should not automatically be treated as professional, legal, financial, medical, safety, or other expert advice unless independently verified by an appropriately qualified professional.
- User responsibility: Users are responsible for reviewing AI-generated responses and deciding whether and how to act on information provided by Ava.
- AI limitations: Ava may misunderstand questions, lack relevant context, or generate responses that do not accurately reflect the information available on Zividax.
- Privacy: Users should avoid entering highly sensitive, confidential, or unnecessary personal information into Chat With Ava.
- Third-party processing: Because Ava relies on third-party AI infrastructure, information submitted to the AI service may be processed according to the applicable third-party service terms and policies.
- Access to public posts: Ava may receive and process content from publicly visible Zividax posts when that content is relevant to a user's question or request. A public post means content that the author has made available for anyone to view on Zividax. This may include the post's text and other information that is publicly displayed with the post. Ava does not need to be given access to a user's private account, private posts, private messages, or other restricted content in order to use publicly available posts as context.
- Private and restricted content: Ava does not use private posts, private messages, drafts, or content restricted to specific users as a source of information for answering questions. Content that is not publicly accessible is not treated as a public post simply because it exists on Zividax.
- Why public posts may be processed: Public posts may be provided to Ava when they help answer a user's request. For example, if a user asks Ava about information discussed in a public Zividax post, the relevant public post may be processed to help Ava provide a more useful response.
By using Chat With Ava, users acknowledge that they are interacting with an artificial intelligence system and understand that AI-generated responses may contain errors. Zividax may modify, restrict, suspend, or discontinue Ava or its AI processing capabilities when necessary for security, privacy, technical, legal, or operational reasons.
3. How We Use Your Data
- Operate platform features, including encrypted messaging and social interactions.
- Provide AI assistance (grammar, translation, Q&A) when triggered by you (@ava / @nyzo).
- Facilitate third-party AI services only after explicit user consent and enablement (with wallet deductions).
- Enforce community guidelines, prevent spam, and protect against abuse.
- Process wallet transactions (withdrawals, holding fees, and AI usage costs).
- Improve security, compliance, and personalize user experience.
- Store, retrieve, and secure all uploaded user media (images, videos, audios, profile photos) via Cloudflare R2 infrastructure.
4. Cookies & Session Tracking
Zividax uses essential cookies for login sessions, security tokens, and preferences. Aggregated analytics cookies (privacy-friendly) help us improve performance. Disabling cookies may affect chat stability and login persistence. No third-party advertising cookies are deployed.
4.1 Advertising
Zividax displays advertisements to support and maintain the platform. We use a combination of third-party advertising services and our own internal advertising system.
- Third-party advertising (Adsterra): We may display ads provided by Adsterra. These ads may use basic, non-personally identifiable data such as device type, browser, and general location to deliver relevant content. Adsterra may use cookies or similar technologies in accordance with their own privacy policies.
- Zividax internal ads: We also run our own advertising system within the platform. These ads are displayed based on general placement and platform activity, not personal user profiling.
- No personal data sharing: Zividax does not sell, share, or provide users’ personal information (such as messages, emails, or identity data) to advertisers.
- Limited analytics: Advertisers may see only aggregated statistics such as total ad views and total clicks. We do not provide individual user tracking data, click identity, or personal behavior details.
- User control: Users can manage certain browser-level settings (such as cookies) to limit ad personalization where supported.
By using Zividax, you agree to the display of advertisements as part of the free service model. We are committed to keeping ads safe, non-intrusive, and respectful of user privacy.
5. End-to-End Encrypted Chat System BETA
How Our E2E Chat System Works:
All direct messages and group chat texts are protected with end-to-end encryption (E2EE). Each message is encrypted on the sender’s device using unique session keys (per conversation). Encrypted payloads are transmitted and stored on our servers as Base64-encoded ciphertext. Decryption happens exclusively on the recipient’s device. Zividax, administrators, or any third party cannot read, access, or decrypt your private messages. The system uses different session keys per conversation (“different season” rotation) for forward secrecy. Session cookies are used for authentication but never store encryption secrets.
Images, videos & audio files (Cloudflare R2 storage): For performance and reliability, all shared images, videos, audio files, and profile photos are stored on Cloudflare R2 cloud servers. Files are encrypted in transit using TLS 1.3 and at rest using AES-256 server-side encryption. Access to media files is strictly enforced via signed URLs that expire after a short period. While these media items are not end-to-end encrypted (to enable cross-device access and efficient delivery), they are protected by strict authentication, authorization checks, and are never exposed publicly unless explicitly shared. Zividax ensures that only the intended recipients or the uploading user can access media based on privacy settings.
Beta status: The E2E chat system is currently in active beta development. Key management improvements are ongoing. Users accept the experimental nature; we recommend keeping apps updated. Encrypted messages are stored Base64-encoded and cannot be read by anyone except the intended recipient.
6. AI Services – Ava, Nyzo & Third‑Party AI Providers
First‑party AI (Ava & Nyzo): Powered by Together.ai API. These AI models are activated only when you explicitly mention @ava or @nyzo in chats or use premium grammar/translation tools. They can view and process only the specific post or chat segment where the AI is triggered. No automatic data collection occurs. Premium users may use built‑in AI to fix grammar or translate messages — those requests are processed via Together.ai and are not shared with external vendors. Ava and Nyzo AI collect and can view only those posts or chat contexts which the AI is explicitly mentioned in.
For additional details about AI data processing or to review your usage logs, contact our support team.
7. Zividax Reels
Zividax Reels allows users to create, upload, view, share, save, repost, and interact with short-form videos. Reels are user-generated content and remain subject to the Zividax Terms, Community Guidelines, copyright requirements, and applicable law.
7.1 Reel Uploads and Storage
- Video uploads: Reels videos uploaded by users may be stored using Cloudflare R2 object storage.
- Media storage: Reel videos, thumbnails, audio, and related media files may be stored in object storage and delivered through Zividax or CDN-enabled URLs.
- User responsibility: You must have the necessary rights and permissions for all video, audio, images, music, and other material included in your Reel.
- Deletion: When a Reel is deleted, associated storage objects may be scheduled for deletion subject to backups, legal requirements, abuse investigations, and normal retention processes.
7.2 Reel Visibility and Shared Links
- Public Reels: A Reel marked as public may be available to other users through the Zividax Reels service.
- Shared Reel links: A person who receives a direct Reel link may be allowed to watch that specific shared Reel without logging in.
- Guest restriction: A guest who opens a shared Reel link is limited to that specific Reel. Scrolling, swiping to additional Reels, or continuing through the Reels feed requires signing in to Zividax.
- Reels homepage: Accessing the main Zividax Reels feed without being signed in may require Zividax login.
- Private or restricted content: Private, restricted, removed, or otherwise protected Reels may not be accessible through a shared link.
7.3 Reel Interaction, Saving and Reposting
- Interactions: Features such as liking, commenting, reposting, and saving a Reel may require a Zividax account.
- Saved Reels: Saved Reels are associated with the user's account and are intended to be visible only to that user unless otherwise stated by Zividax.
- Reposts: Reposted Reels may be displayed publicly on the reposter's profile and may be visible to other users.
- Original Reel: A repost remains associated with the original Reel and does not transfer ownership of the original content to the reposter.
- Removal: A repost may become unavailable if the original Reel is deleted, restricted, removed, or otherwise made unavailable.
7.4 Reel Safety, Moderation and Copyright
- Community rules: Reels must comply with the Zividax Terms, Community Guidelines, copyright rules, and applicable law.
- Moderation: Zividax may review, restrict, remove, disable, or limit access to Reels that violate applicable rules or legal requirements.
- Copyright: Users are responsible for obtaining appropriate rights, licenses, or permissions for copyrighted material used in their Reels.
- Enforcement: Repeated or serious violations may result in removal of content, feature restrictions, monetization restrictions, suspension, or account action as permitted by applicable rules.
7.5 Reel Monetization Eligibility
- Eligibility: Eligible creators may activate Reel monetization after satisfying the applicable Zividax eligibility requirements.
- Account verification: Required phone-number verification must be completed before Reel monetization can be activated.
- No guaranteed earnings: Enabling monetization does not guarantee a minimum level of earnings or payout.
- Content eligibility: Reels may be excluded from monetization when they do not satisfy applicable content, copyright, safety, or monetization requirements.
7.6 Phone Number Verification for Reel Monetization
- Verification requirement: A creator must complete the required phone verification before activating Reel monetization.
- Verification channels: Zividax may provide WhatsApp or Telegram as available verification channels.
- OTP: The verification code may contain 6 digits.
- OTP validity: A generated OTP may remain valid for up to 24 hours, unless it is replaced, cancelled, or invalidated earlier.
- Verification status: Successful verification may be recorded on the user's account as the required monetization verification status.
- Verification abuse: Zividax may limit repeated verification attempts or reuse of the same phone number where necessary to reduce abuse or fraudulent activity.
8. Cloud Storage – Cloudflare R2
Zividax uses Cloudflare R2 for object storage of user-uploaded media and other platform files. This can include images, videos, audio, profile photos, Reel videos, chat attachments, and other files uploaded through Zividax features.
- Access control: Storage access is controlled by Zividax application authorization, object permissions, and signed or authenticated access where applicable.
- Private files: Private media is not intended to be publicly accessible unless the user or an authorized Zividax feature makes it available.
- Public content: Content intentionally published as public may be delivered through public or CDN-enabled URLs as required for the feature.
- Chat media: Chat attachments may be stored separately from encrypted message text. Storing a media file in R2 does not by itself mean that the media is end-to-end encrypted.
- Security: Data is transmitted using encrypted connections where supported, and Zividax applies access controls intended to prevent unauthorized access.
- Deletion: When content or an account is deleted, associated storage objects are scheduled for deletion subject to backups, legal requirements, abuse investigations, and normal system retention processes.
9. Creator Policy Requirements
Creators who use Zividax Wallet: If you choose to use the external Zividax Wallet or Zividax Pay wallet services, you must follow the separate Zividax Wallet Policy. The Wallet Policy applies only when you use wallet-related features, including balances, transactions, withdrawals, fees, verification, or other wallet services.
Creators who use Reel monetization: If you enable or use Zividax Reels monetization, you must follow the applicable Zividax Reels Monetization Policy, including its eligibility requirements, verification requirements, content rules, payment rules, fees, holding periods, and payout requirements.
These policies are separate from this Privacy Policy. A creator who does not use the relevant wallet or Reel monetization feature is not required to use that feature or accept its feature-specific requirements merely to use ordinary Zividax social, messaging, or media features.
9. Zividax Pay & Wallet Terms
Zividax does not make wallet or payment terms part of the general privacy policy. If you choose to use Zividax Pay, you must first agree to the separate Zividax Wallet Policy presented clearly in the Zividax Wallet/Pay area. The Wallet Policy governs wallet-specific features, transactions, fees, verification, withdrawals, balances, and other financial rules.
If you do not use Zividax Pay, you are not required to agree to the Zividax Wallet Policy merely to use ordinary Zividax social, messaging, or media features.
11. Developer Console
Developer Console features are optional. If you access or use the Zividax Developer Console, you must agree to the separate Zividax Developer Console Policy before using developer tools, APIs, keys, applications, integrations, or other developer services.
Users who do not use the Developer Console do not need to agree to the Developer Console Policy. Developer access may be restricted, suspended, or revoked for abuse, security violations, unauthorized access, excessive automated traffic, or other policy violations.
12. Communication Methods
- WhatsApp / Telegram: Used solely for withdrawal confirmations, wallet verification, and critical security alerts (opt‑in).
- Email: Reserved for important policy updates, account security, and support responses.
- No push notification services: Zividax does not use Firebase Cloud Messaging (FCM), OneSignal, or any third‑party push framework. Browser‑level notifications (optional) are handled locally without external SDKs. The entire push notification system has been removed for privacy and compliance.
13. Cloudflare Security & CDN
Zividax utilizes Cloudflare for DDoS mitigation, performance optimization, SSL/TLS encryption, and CDN delivery. Cloudflare may process anonymized request metadata but does not access message content (E2E ciphertext remains inaccessible). Media delivered via Cloudflare R2 may also be accelerated through Cloudflare CDN for improved performance and security.
14. Data Sharing & Disclosure
Zividax does not sell, rent, or trade user personal data. Limited sharing occurs only with:
- Trusted service providers (hosting, wallet infrastructure) under strict confidentiality.
- Cloudflare R2 for media hosting: Media files (images, videos, audio, profile photos) are stored on Cloudflare R2. Cloudflare processes stored object data according to its applicable security and compliance commitments. Zividax retains full control and access management over stored media.
- Law enforcement or legal obligations when required by applicable law and after verification.
- Together.ai API (exclusively for Ava/Nyzo interactions) as per their data processing terms; no data retention beyond request processing.
15. Your Data Rights & GDPR Compliance
- Access: Request a copy of your stored data (excluding decrypted messages, as keys remain local). This includes metadata of your media files stored on Cloudflare R2.
- Rectification: Correct inaccurate profile or contact details.
- Erasure (right to be forgotten): Delete your account and associated data (E2E ciphertext is permanently erased, and all media files (images, videos, audios, profile photos) stored on Cloudflare R2 will be deleted within 30 days).
- Restriction & portability: Obtain machine‑readable format where applicable.
- Withdraw consent: Disable AI features or third‑party AI any time.
EU residents may submit requests via our contact page. We respond within 30 days.
16. Security Measures
We enforce encrypted database storage, hardware security keys, and routine penetration testing. However, no internet platform is 100% immune. Users should enable two‑factor authentication (2FA) and protect their devices. E2E chat messages remain unreadable even in case of server breach because messages are stored as Base64-encoded ciphertext with no server-side decryption capability. Media stored on Cloudflare R2 is protected using server-side encryption (AES-256), strict bucket policies, and temporary signed URLs to prevent unauthorized access.
17. Hosting Infrastructure
Zividax services are hosted on enterprise‑grade cloud infrastructure provided by Hostkooala, ensuring data redundancy and ISO‑certified security controls. Additionally, all user-uploaded media files are stored and managed via Cloudflare R2 (AWS) cloud storage, providing high durability, availability, and geographic redundancy.
18. Account Termination & Bans
Zividax may permanently suspend accounts involved in scams, illegal activity, harassment, or attempts to bypass security. Upon termination, wallet funds may be forfeited if linked to fraud. Users can request account deletion via support. Upon account deletion, all media files (including images, videos, audios, profile photos) stored on Cloudflare R2 will be permanently removed from our systems.
19. Policy Updates & Notification
We may revise this Privacy Policy to reflect legal updates, feature changes, or improved transparency. Material changes will be announced via in‑app banner or email. Continued use after 30 days implies acceptance.
20. Third‑Party Content & External Links
Zividax may contain links to YouTube, Blogger, Amazon, or other external platforms. We are not responsible for their privacy practices. Please review their policies independently.
21. Children’s Privacy (COPPA Compliance)
Zividax does not knowingly collect information from children under 16. If we become aware of such data, we delete it immediately. Parents or guardians may report concerns through our contact page.
22. DMCA & Copyright Infringement
To report copyright violations, submit a DMCA notice via our contact page. We respond promptly to valid takedown requests. Media stored on Cloudflare R2 that infringes copyright will be removed upon verified notice.
23. Zividax Mobile App – In-App Browser
App-specific notice: This section applies only when you use the Zividax Android/mobile application and access a website through the built-in Zividax in-app browser.
The Zividax in-app browser is provided for convenient access to web pages without immediately leaving the Zividax application. It may be used for links, help pages, account flows, payment-related pages, and other web content that you choose to open.
Read the full In-App Browser Policy: Zividax In-App Browser Policy
Important: This additional policy may be applicable only when you are using the Zividax mobile application. Website visitors using Zividax through a normal browser may not be subject to the app-specific behavior described in this section.
24. Contact Us – Privacy Inquiries
For questions about data handling, AI usage, encrypted chat, media storage on Cloudflare R2, or to exercise your rights, reach us through:
📬 Contact page: https://help.zividax.uk
✉️ Email support: [email protected]
🌐 Official AI pricing & docs: zividax.uk/ai/
Data Protection Officer (DPO) contact: Reachable via email with subject “DPO Request”.
