Privacy

• Your email address — it's how you sign in. Other people on NijigenX never see it.
• Your profile — the display name and profile photo you choose.
• What you send — messages, photos, replies and reactions, plus edits and the fact that a message was unsent.
• Your connections — your friends list, friend requests (including an optional note), your invite links and who arrived through them, the groups you're in, and which conversations you've muted.
• Activity signals — when you were last online, and how far you've read and received in each conversation. These power presence, “last seen” and read receipts.
• Network and diagnostic records — country information inferred by our network provider; mailbox and network-address records used for sign-in and abuse limits; and server logs containing network addresses, request paths and query parameters (including channel search terms), response status, request and response timings, and error details. We use these records to operate, protect and troubleshoot the service.
• App sessions and devices — an installation identifier, platform, optional device name, session creation and last-use times, expiry and revocation state. We store a hash of each app refresh token to manage sign-in and session security.
• Safety and synchronization — accounts you block, your privacy settings, deletion requests, and temporary change records that let your devices catch up. Change records contain references to affected items, not message text or photos.

We store posts, comments, votes, channels you join, reports, appeals, notifications and moderation records.

We also store hashed signals derived from network-address ranges to detect vote manipulation and ban evasion. These can be associated with accounts, posts or reports. Network addresses and these signals are not displayed on public profiles.

• No ads or advertising trackers.
• We don't sell your data or share it with anyone for marketing.
• We don't use your conversations for advertising. Access to private content is limited to providing the service, handling support and safety matters, and complying with applicable legal requirements.

Channels are public: anyone, including search engines, can read what you post there under your display name. Chats are private to the people in them. If someone in a conversation reports a message, the text of that message and who sent it go to NijigenX staff for review; photos in chats are not shared with staff. Blocking someone also lets staff know which account was blocked.

Staff can see who filed a report; moderators can't. Moderators of a channel can see that channel's moderation log. Votes and channel memberships are private.

Messages and photos are visible to the people in that conversation. Your name, photo and online status are visible to your friends and to people you share a group with — never your email address. Friends are made through invite links: someone who opens a link you shared can send you a friend request, and you see their name and photo so you can approve it. They only see more once you do.

Administrators can see account details (email, name, when you joined and last used NijigenX, and how many friends and messages you have — not what the messages say) so they can keep the service safe and suspend accounts that abuse it.

We email you a 6-digit code each time you sign in. That's all — we don't send invitations on your behalf, and we don't send newsletters.

We use a single cookie to keep you signed in, plus the short-lived security cookies the sign-in flow needs. There are no tracking cookies. Your chosen sorting options are saved locally in your browser.

Native apps use access and refresh tokens instead of a browser sign-in cookie. Supported apps keep sign-in credentials in the device's secure storage. Signing out revokes that app session; device identifiers and notification settings help keep different accounts and installations separate.

Our apps store some data on your device, only for the signed-in account, so your chats open quickly, the apps can catch up without downloading everything again, and you don't lose what you write while offline.

• Messages you can see — our iPhone, Android and desktop apps keep the messages and photos you can see on your device: your conversation list, the people in it and recent message history. They are kept in the app's private storage, protected by your device's operating system and, on the desktop, encrypted, and they are deleted when you sign out. The apps keep at most 2,000 messages per conversation and 200 MB of photos, removing the oldest first. Messages and photos in conversations protected with a security code are never written to the device. The website keeps what you see in memory only.
• Sync positions — how far your chats and account updates have been received, with no message content. The apps keep the chat position with the stored messages and the account position in your device's secure credential storage.
• Messages you haven't sent yet — when a message can't go out right away, for example while you're offline, the iPhone, Android and desktop apps keep its text in an encrypted file on the device until our servers have it, so it isn't lost if the app closes. Photos are never stored this way: if the app restarts before they finish uploading, choose them again. The file holds at most 100 messages, and a message that still hasn't been sent after 7 days shows as “Not sent” and leaves the file. Messages in conversations protected with a security code are never written to the device, in this file or anywhere else. The desktop app keeps that file in its local app data folder, encrypted with a key held in your operating system's credential store next to your sign-in. The website keeps unsent messages in memory only.

On iPhone and Android, none of this is synced to the cloud or carried to a new device by a backup or transfer. On the desktop, NijigenX doesn't sync it and marks its files to be skipped by Time Machine; other backup or migration tools can still include them, as they can include your sign-in. Signing out, a revoked or suspended session, and deleting your account remove it from the device; signing in with a different account removes the previous account's stored messages and unsent messages. Turning on Security for a conversation, on this device or another one, hiding or leaving it, being removed from it, or blocking the other person removes that conversation's stored messages and photos, and its unsent messages leave the device and show as “Not sent”.

If you allow notifications, we store your installation's notification address, permission state and notification preferences. Notification addresses are encrypted in our database. Where push delivery is available, Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) processes the device address and notification payload to deliver it to your device.

Notifications hide message details by default. If you enable previews, a notification may include the sender and a message excerpt. Enabling Security for a conversation keeps its notification details hidden. We check current account, membership, blocking, mute and read state before sending. Delivery records distinguish provider acceptance from an app receipt and a read receipt.

You can change app notification preferences and device permissions. A notification already accepted by a delivery provider or displayed by your operating system may remain visible after you sign out, leave a group, block someone or delete content. We cannot guarantee its complete withdrawal.

Everything travels over HTTPS, and messages are stored on our servers so you can read them on any device. Conversations are not end-to-end encrypted, so please don't use NijigenX for anything that needs that level of protection.

You can protect individual conversations with a six-digit security code. We store a salted verifier and temporary unlock records for your sign-in session. This setting applies only to you and hides the conversation's message preview. Leaving the conversation or reopening the app requires the code again; there is no inactivity timer. It does not add end-to-end encryption or erase copies someone already saw.

We keep your data for as long as you have an account. When you unsend a message, its text and photos are removed from the conversation for everyone.

Deleted public content is hidden from public view. Copies of its text and images, report and appeal text, and moderation notes can remain for moderation, appeals and safety handling. These records do not currently have a fixed automatic deletion schedule. Evidence involving child safety may be retained or reported as required by law.

We keep encrypted originals of public image uploads for moderation and evidence preservation. If an uploaded file includes metadata such as EXIF camera details or precise GPS location, that metadata remains in the encrypted original even when we process a separate version for display. Isolated safety evidence is stored separately from publicly served images; access is restricted and recorded.

Search engines and other sites may keep copies for a while after something is deleted; write to us and we'll request removal. Browser and third-party previews can retain cached copies temporarily.

You can request account deletion in the app with a fresh email verification code. If you own a channel with other members, another owner must accept a transfer first. Once your deletion request is accepted, we disable the account and revoke its app sessions and notification registrations. Background cleanup removes the account, clears its message and public contribution content, and removes ordinary attachments and account relationships. Some deleted items may remain as anonymous placeholders so discussions stay coherent.

Account deletion does not bypass required safety-evidence preservation. Restricted safety evidence is retained separately from ordinary account data under that process; cleanup can wait while preservation is in progress. Copies already held by recipients or notification providers are outside the account cleanup process.

For help with deletion or a copy of your data, email [email protected] from the address you sign in with. Data requests may include your channel contributions, votes, memberships, reports, appeals and notifications.

If this policy changes in a way that matters, we'll update the date above and tell you in the app. Questions? Write to [email protected].