XmegramXmegramLog in
Privacy Policy

Privacy Policy

Learn how Xmegram uses account information, profile settings, country information, messages, media, stories, activity records, paid-access data, and support requests to provide the service.

Scope

What this Privacy Policy covers

This Privacy Policy explains how Xmegram handles information used to create accounts, provide communication features, operate profiles, deliver notifications, support paid access, protect the service, and respond to support requests. It is written for people who use Xmegram at https://xmegram.com.

Privacy on a communication service is not one single setting. Different features require different information. A profile uses identity details. A private chat uses conversation records. A channel or group uses membership and access information. A story uses media and viewer activity. A paid feature uses order and entitlement information. This policy explains those categories and the choices available to you.

Registration

Account information

When you register, Xmegram stores the information needed to operate your account, such as your email address, username, display name, password hash, verification status, account role, theme, and timestamps connected to account creation and updates. Passwords are stored as hashes rather than readable text. If email verification is enabled, the service also stores the information needed to send and validate the verification step.

If you register through Google sign-in, Xmegram receives identity information needed to create or connect your account, such as a verified email address, a provider subject identifier, and a display name when one is supplied. When a user creates an account through Google sign-in, Xmegram records Terms and Conditions and Privacy Policy acceptance automatically at the moment they continue with Google.

Location-related data

Country information and visibility

Xmegram may detect a country from reliable request information or device hints provided during registration or sign-in. The purpose is to fill the country field consistently without asking the user to type it manually. The service does not need to claim or display an official physical location in order to provide this feature.

A detected country is stored as an account value and displayed with its flag inside profile settings. It is read-only so the value remains consistent with the automatic detection process. Country visibility is off by default. Other users do not see your country unless you turn on the related privacy option.

Visibility settings

Profile choices

Your profile may contain a display name, username, biography, profile photo, cover photo, country, and activity information. Xmegram provides privacy settings that let you decide whether selected fields appear to other users. Hiding a field does not necessarily delete the value from your account; it changes how the profile is presented.

These controls are useful when you want a recognizable profile without making every detail visible. For example, you may keep a profile photo visible while hiding your country, or keep a username available for links while hiding your biography. Review your settings whenever your preferences change.

Communication data

Messages and conversations

Xmegram stores messages and related conversation information so private chats, groups, and channels can function. This includes message text, timestamps, sender identifiers, replies, forwards, pins, edits, deletions, delivery or read information where enabled, reactions, attachments, and conversation membership. A direct chat remains tied to the participating accounts and is not presented as a public profile or public space.

Groups and channels use additional information such as the space title, description, username, slug, visibility, membership records, access mode, settings, attached discussion relationship, and notification preferences. This information allows the service to show the correct space, determine who can open it, and apply the settings selected for that conversation.

Activity data

Stories, reactions, polls, and participation

Stories use media, captions, posting timestamps, expiry timestamps, viewer records, reactions, and replies so the story experience can work as expected. Reactions record the selected emoji and the item being reacted to. Polls record the question, options, settings, and votes needed to calculate totals and animate progress changes.

These records are connected to the feature you chose to use. They help show the correct state to you and other eligible viewers. For example, a story poster can see story activity, a poll participant can see updated progress, and a channel reader can see the current reaction totals on a post.

Media data

Photos, videos, files, and voice messages

When you upload media, Xmegram stores information needed to process and serve the file, such as its storage reference, type, size, thumbnail, preview, dimensions, and relationship to the message or story. Some video files may also use generated posters or previews so the interface can load efficiently.

Media may be delivered from configured storage and may use temporary signed links or application routes where needed. The service should avoid exposing a source URL from another website when a media import has been completed. Protect your own privacy by reviewing media before uploading and removing private details that you do not want recipients to see.

Subscriptions and orders

Paid access information

When paid features are used, Xmegram stores information needed to create and track an order, activate access, manage an entitlement, and process later status changes. This can include a plan identifier, space identifier, message identifier, user identifier, amount, currency, order status, subscription status, provider reference, timestamps, and renewal-related information.

External payment services process payment information under their own terms and privacy practices. Xmegram should receive only the references and status information needed to operate access. Do not send full payment-card information through a profile, message, comment, story, or support request.

Protection

Security and technical records

Xmegram may store security and technical records such as login events, verification attempts, recovery requests, rate-limit information, request metadata, server logs, storage diagnostics, and error references. These records help protect accounts, diagnose failures, reduce abuse, and keep the service reliable.

Technical records are not intended to become public profile information. When a server error occurs, the service can show a safe reference code rather than revealing internal file paths or database details. A support request can include that reference code so the issue can be investigated more efficiently.

Contact Us

Support requests

When you submit the Contact Us form, Xmegram stores the information needed to handle your request, including your name, email address, category, subject, message, reference identifier, and status. Provide only the information that is relevant to the question.

Never include your password, a verification code, recovery keys, or full payment-card details in a support request. If your issue concerns a profile, group, channel, or post, share a safe link or username when appropriate. If your issue concerns a technical error, include the visible error reference and a clear description of the steps that led to it.

Controls

Your privacy choices

You can use profile settings to review visibility choices, communication permissions, country visibility, and blocked accounts. You can decide who may send private messages, reply to stories, mention you, or invite you to groups where those preferences are available. You can also block an account when you no longer want contact.

Privacy choices should be reviewed alongside the Terms and Conditions and Community Standards. A setting controls presentation and contact behavior, but it does not authorize harmful conduct. If you have a privacy question that is not answered here, use the Contact Us page and choose the privacy category.

Profiles are the starting point for identity on Xmegram. Each account can use a display name, a unique username, a profile photo, a cover photo, and a biography. A profile helps other people understand who they are speaking with before they follow an update, open a shared link, or start a private conversation. Usernames are designed to be readable and dependable, using lowercase letters, numbers, and underscores. Profile links can be shared outside the service, while privacy settings determine which details appear to other people. The aim is to make identity easy to recognize without forcing every personal detail into public view.

Profiles that feel personal and clear

Profile settings give each person practical control over how they appear. A user may decide whether a biography, username, country, photo, cover image, or activity status is visible to others. Country is entered automatically when the service can identify it from reliable request information, and it stays hidden from other users unless the account holder chooses to display it. These choices allow a profile to be useful for conversation and discovery while remaining appropriately private.
Private chats are designed for one-to-one communication. They support text messages, replies, reactions, message editing where available, pinned messages, voice messages, attachments, photos, and videos. A private conversation remains tied to the two participating accounts, and its content is not presented as a public channel or group. The interface is designed to keep the conversation focused, with a compact message history, clear delivery states, and simple controls for the actions that belong to each message.

Private chats for direct communication

A signed-in user can block another account when contact is no longer welcome. While the block remains active, both accounts disappear from each other's normal user surfaces: private messages and replies stop, activity details such as last seen are hidden, profile discovery is restricted, suggestions and invitations are removed, and authored content is filtered between the pair. Blocking preserves historical records and moderation access so safety review remains possible.
Groups are spaces for shared conversations. A group may be public, private, or available through a subscriber-supported access model when that feature is enabled. Depending on the group settings, members may be allowed to post, reply, react, vote in polls, and take part in ongoing discussions. A group can be used for a focused community, a private circle, a project, a learning space, or a creator-led discussion room.

Groups for shared participation

Group settings make it possible to shape the kind of conversation that takes place. Some groups allow members to publish messages freely, while others keep publishing limited to the people responsible for the space. Poll creation can also be opened to members or reserved for the people managing the group. These options help a group stay useful as it grows and let its structure match the purpose of the conversation.
Channels are designed for publishing updates to an audience. A channel can share announcements, media posts, creator updates, subscriber-only posts, and recurring information in a clean feed. Readers can follow the flow of posts without losing the clarity of a broadcast format. Views, reactions, comments, and share actions help people understand how a post is being received while keeping the channel itself organized.

Channels for broadcasts and updates

A channel may connect to a discussion group so that comments have a natural place to continue. The channel post remains the original source, while the linked group provides the discussion thread. This structure keeps the channel feed readable and gives the audience a clear route into conversation. When a comment is removed from the linked discussion, the visible comment total is updated so the count reflects the remaining discussion accurately.
Stories provide a lighter way to publish updates that are intended to be timely rather than permanent. A story can be shared from a profile and, where enabled, from a group or channel. Viewers can move through stories, react with expressive emoji, and reply when the account or space settings allow it. Story activity gives the person who posted the story a useful overview of views, replies, and reactions.

Stories for timely sharing

Story reactions are designed to feel immediate. When a viewer reacts, animated emoji bubbles create a visible response without interrupting the story. Story replies connect back to the appropriate conversation flow so that a timely update can become a useful private or community discussion when the sender allows it. Stories expire automatically after their active period, keeping the story strip current.
Controls that match the context

Privacy choices across the product

Privacy is not one switch. A profile, private chat, group, channel, story, search result, and paid-access page each have a different purpose. Xmegram uses context-specific rules so information is not treated as public merely because it exists in the service. A public username may help other people find a profile. A private-chat message belongs inside the direct conversation. A private group should not be promoted as a public destination. A subscribers-only post should remain protected until the account has the required access. A country value can remain hidden even while a profile photo is visible.

Profile settings provide practical controls for details that may be shared with other users. Some details are useful for recognition, while others are optional. Country is added automatically when reliable request information is available and remains hidden from other users by default. A person may decide whether to show it later. Xmegram does not require a public physical address or a public location history. It does not ask users to publish where they live in order to participate in normal conversations.

Blocking is another privacy control. When one signed-in account blocks another, both accounts disappear from each other's normal user surfaces while the block remains active. Private messages and replies stop, activity details such as last seen are hidden, suggestions and invitations are removed, and profile discovery is restricted. Blocking does not delete historical records or remove moderation tools. Use blocking when you need a strong personal boundary, and use account privacy settings to manage what signed-out visitors can see on public pages.

Understand what you submit

Retention, deletion, and responsible support requests

Xmegram retains information for as long as reasonably needed to provide the feature, keep account records accurate, support security, handle purchases, and respond to support requests. Different records may have different lifecycles. Stories expire after their active period. Messages remain in a conversation unless removed through the available controls or affected by the lifecycle of the conversation. A local Delete for me action hides a direct-chat message from one user’s own view, while a permitted Delete for both action changes the shared conversation history for both participants. Payment records may need to remain available after access ends so purchases and renewals can be understood.

When contacting support, provide only the information needed to explain the issue. Do not submit passwords, verification codes, recovery keys, active session details, or full payment-card numbers. A useful support request may include a username, a public link, the name of a group or channel, the time of an error, or a visible reference code. Avoid copying private conversation content unless it is necessary to explain the concern and you are authorized to share it.

If you have a privacy question, use the Contact Us page and choose the privacy category. Explain the request clearly so it can be understood without unnecessary personal information. The Privacy Policy should be read together with the Terms and Conditions and Community Standards because privacy choices work best when everyone also follows responsible-use rules.

Protect access

Security-minded use of your account

Your privacy depends partly on how you protect your account. Use a strong password that is not reused on another service. Keep access to your email account secure because verification and recovery messages may be sent there. Treat login codes and recovery links as private. Do not send them to another person, enter them into an unofficial page, or paste them into a support request. Sign out on shared devices and pay attention to unusual login activity.

Links deserve the same care. Check where a link leads before opening it, especially when it appears in a public conversation or arrives unexpectedly in a private chat. Xmegram may display internal links in a clean readable form, but an external destination remains outside the service. If a page asks for your password, verification code, or payment details unexpectedly, leave the page and return to the official Xmegram URL directly.

Privacy is strongest when product controls and careful personal habits work together. Xmegram provides settings and boundaries; each user should use them thoughtfully.