Effective date: January 1, 2026
1. Our Privacy Promise
Y Communicator is designed so that we do not know who you are, who you talk to, or what you say.
From the ground up, Y Communicator follows these principles:
- No accounts, no logins. We do not use usernames, emails, phone numbers, or any form of registration.
- No personal data collection. We do not ask for, store, or process your name, email, phone number, contact list, or any other personal identifiers.
- No tracking and no event logging. We do not track your activity, we do not log your conversations, and we do not build profiles of you or your contacts.
- We do not know who is talking to whom. The system is built so that servers see only anonymous, rotating technical addresses and encrypted data - never real-world identities.
- End-to-end encryption with keys only on your device. Messages are encrypted and decrypted exclusively on user devices. Servers never see plaintext and never hold encryption keys.
- Device-protected local storage only. Message history exists only on your device and is encrypted by the operating system. It cannot be read without unlocking your device.
Because of this design, even if we receive a lawful request (such as a subpoena) for your conversations or your identity, we have nothing meaningful to provide. We do not possess message content, user identities, or social graphs that could be handed over.
2. Who We Are
Y Communicator is a secure communication application focused on providing strong technical privacy guarantees through design, not through legal promises alone.
In this Privacy Policy, "Y Communicator," "we," "our," or "us" refers to the Y Communicator project and Y Communications Corp.; "you" refers to a user of the Y Communicator apps and services.
For privacy questions, you can contact:
Email: contact@y-communications.com
3. Scope of This Policy
This Privacy Policy applies to:
- The Y Communicator mobile applications (iOS and Android)
- The Y Communicator backend nodes that temporarily relay encrypted messages between devices
It does not apply to:
- Your device manufacturer (e.g., Apple, Google, your phone vendor)
- Your mobile carrier or internet provider
- Any other apps, services, or websites you use in conjunction with Y Communicator
4. We Do Not Collect Any Personal Data
We specifically do not collect, require, or store:
Personal Identifiers
- No name
- No email address
- No phone number
- No username or handle
- No government IDs
Account Data
- We do not create or maintain user accounts
- We do not store login tokens, session cookies tied to identities, or password hashes
Contact List
- We do not access, upload, or store your phone contacts or address book
- We do not know who your friends, colleagues, or family members are
Message Content on Servers
- We do not store readable message text, images, or attachments on our servers
- All content is end-to-end encrypted; only your device can decrypt it
Conversation Metadata or Social Graph
- We do not store lists of who talked to whom, when, or how often, in a form that links to real identities
Tracking, Profiling, or Analytics
- We do not use advertising IDs
- We do not run behavioral analytics on your usage
- We do not profile you for ads, recommendations, or any other purpose
5. Data That Flows Through the System
While you use Y Communicator, some technical data must transit the system to make communication possible. Our design minimizes what exists and how long it lives.
Anonymous Technical Addresses
Devices communicate using anonymous, rotating identifiers that are derived locally on each device from secret values. These identifiers:
- Are cryptographic hashes (SHA3-256 outputs)
- Do not contain your name, phone number, email, or any direct identifier
- Change over time or per conversation to limit linkability
Servers see these as random strings and cannot reverse them to a human identity.
Encrypted Message Blobs
When you send a message:
- Your device encrypts the message content end-to-end using keys that never leave your device
- The encrypted blob (ciphertext) is sent to relay nodes, tagged only with an anonymous address and a message ID
- Nodes store these encrypted blobs temporarily in RAM until the recipient retrieves them or they expire
Nodes cannot decrypt these blobs and do not know what they contain.
Transport-Level Network Data
Certain transient network data exists at the transport level (e.g., IP address, port, timing of connections). Our design goals are:
- Not to tie these values to any persistent account or identity (because we have none)
- Not to store per-user or per-conversation logs of this information
6. End-to-End Encryption and Device Security
Keys Stored Only on Your Device
All cryptographic keys used to encrypt and decrypt your messages are generated and stored on your device, using the operating system's secure storage (iOS Keychain, Android Keystore).
- We never see your private keys
- We never store your private keys on our servers
- We cannot decrypt your messages
If you lose your device or uninstall the app without backup, your encryption keys may be lost, and your message history cannot be recovered from us.
Encrypted Data on Device
Any message history stored locally by the app remains protected by:
- The device's full-disk or file-based encryption
- The device lock (PIN, passcode, fingerprint, Face ID, etc.)
The only practical way to read your Y Communicator chats is to have access to your unlocked device.
No Server-Side Backups
We do not provide cloud backup or server-side history for your messages. If you rely on device or OS backups (iCloud, Google backups), those are governed by Apple's or Google's policies.
7. Legal Requests and Law Enforcement
Because of the technical design described above:
- We do not have plaintext message content
- We do not maintain user accounts or link messages to real-world identities
- We do not store social graphs or persistent communication logs
If we receive a lawful request asking for:
- Message content - we cannot provide it, because we never see or store it in readable form
- User identity information - we cannot provide it, because we do not collect or store names, emails, phone numbers, or similar identifiers
- "Who talked to whom" records - we cannot provide it in a way that links conversations to real identities
We may be able to provide generic technical information such as that a particular anonymous address existed in the system at a given time. However, this information is not sufficient to reconstruct your identity or conversations.
8. Third-Party Services and App Stores
Y Communicator is distributed through mobile app stores (Apple App Store, Google Play). These platforms may collect their own diagnostic, crash, or analytics data under their own privacy policies.
Within the app itself:
- We do not embed third-party analytics SDKs for profiling or advertising
- We do not share your data with advertisers or external tracking networks
9. Children's Privacy
The app is intended for users aged 18 and older, the coresponding
age rating is applied in app stores. Since we do not collect names, ages, or other identifiers, we do not have a way to distinguish
whether a specific user is a child.
10. International Data Considerations
Because Y Communicator does not maintain user accounts or centralized personal data stores, traditional concepts of "data transfer" are minimal.
Encrypted messages may be temporarily relayed through nodes in different regions. However:
- Nodes do not see plaintext content
- Nodes do not know the real identity of sender or recipient
- We do not store persistent user profiles in any jurisdiction
11. Data Retention
On servers (nodes):
- Encrypted messages exist only in RAM for a short time, until delivery or expiry (maximum 2 hours)
- When a message is delivered and acknowledged, it is deleted from the node
- No long-term logs tie activity to specific devices or users
On devices:
- Message history is retained according to your app settings and device storage
- You can delete conversations locally at any time
- We have no remote control over your device storage
12. Your Choices and Controls
Within the app, you have control over:
- Whether to keep or delete local message history
- Whether to enable any optional diagnostic features (if introduced)
- When to install, uninstall, or reinstall the app
Because we do not maintain accounts, there is no "profile" for us to delete, export, or modify. Uninstalling the app and deleting local data is sufficient to stop using Y Communicator.
13. Subscription Terms
Y Communicator offers both free and paid subscription options:
Free Tier
- Message size limit: 1 MB per message
- Active conversations limit: 5 concurrent sessions
- No payment required
Pro Subscription
- Message size limit: 10 MB per message
- Unlimited active conversations
- Pricing: $1.99/month or $19.99/year
Auto-Renewal
Pro subscriptions automatically renew at the end of each billing period (monthly or annually) unless cancelled at least 24 hours before the end of the current period. Your account will be charged for renewal within 24 hours prior to the end of the current period at the same rate.
Cancellation Policy
You may cancel your subscription at any time through your device's app store account settings:
- iOS: Go to Settings > [Your Name] > Subscriptions > Y Communicator > Cancel Subscription
- Android: Go to Google Play Store > Menu > Subscriptions > Y Communicator > Cancel Subscription
Upon cancellation, you will retain access to Pro features until the end of your current billing period. After that, your account will revert to the Free tier. No refunds are provided for partial billing periods.
Payment Processing
All payments are processed through Apple App Store (iOS) or Google Play Store (Android). We do not collect, store, or have access to your payment information, credit card details, or billing addresses. Please refer to Apple's or Google's respective privacy policies for information on how they handle payment data.
14. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes in software, protocols, or applicable laws. When we make material changes, we will update the "Effective date" at the top of this document and notify you within the app or via our website where appropriate.