Security and privacy
Trust has to be engineered, not implied.
Ethamor is a messenger, which means privacy is not a decorative feature. It has to shape how accounts, chats, groups, channels, feeds, media, demo access, and future production systems are designed from the start.
Current architecture
What is public today, and what stays isolated.
The honest security posture right now is separation. The website and demo should let people understand Ethamor without pretending the public demo is the final production network.
Marketing site
Public information, legal pages, security explanation, demo entry point.
Demo gate
Captures email consent and sends visitors into a contained browser demo.
Browser demo
Populated product walkthrough with realistic messenger flows and clearly limited production claims.
Future live app
The production messaging environment should remain separate until auth, storage, and security reviews are ready.
Live safeguards
Controls that already shape the product direction.
Public demo, separate from the future live app
The browser demo is intentionally separated from the production app surface. It is built to show the product experience without exposing a finished live network before it is ready.
Collect less, explain more
The website asks for an email only when somebody requests demo access. We do not sell that address, and product update emails should always have a clear opt-out path.
Safety where people actually use it
Privacy, account, session, vault, disappearing-message and visibility controls are designed as visible parts of the interface, not buried in distant settings.
No fake certainty
We avoid broad security theatre. If something is simulated in the demo, unfinished, or still being hardened, we would rather say that clearly than decorate it with a badge.
Principles
How Ethamor should differ from ordinary messengers.
We do not need to name other apps to make the point. The problem is familiar: private chats, public social mechanics, weak defaults, and unclear security claims often get mixed together. Ethamor should keep those boundaries visible.
Private by default
A messenger should not require users to hunt for privacy. Defaults should start conservative and then let people expand visibility intentionally.
Metadata matters
Message contents are only one part of privacy. Account links, contact discovery, session state, notifications, media, and timing all deserve careful treatment.
Controls must be understandable
Security that only engineers understand does not protect normal users well. Ethamor should show what a setting affects, where it applies, and what it cannot do.
No ad-machine incentives
The product direction is not built around selling attention, profiling conversations, or pushing people into algorithmic engagement loops.
Smaller trust surface
Every unnecessary integration, data copy, and background process becomes another place to fail. The safest system is often the one that needs less.
Audit before bravado
Strong claims should come after review, testing, and operational discipline. Until then, we describe the roadmap and the current limits plainly.
Decision standard
No security theatre.
If a feature cannot explain its trust boundary in plain English, it is not ready to be presented as safe.
Instead of
A lock icon beside vague privacy copy.
Ethamor should do
Show the control, explain the boundary, and avoid claiming more than exists.
Instead of
A social feed that quietly becomes the whole product.
Ethamor should do
Keep discovery optional and separate from private conversations.
Instead of
Collecting data because it might be useful later.
Ethamor should do
Collect only what the product or demo access actually needs.
Before broad launch
What still needs to be hardened.
This is the part that makes the page credible: some work belongs before a real public messaging network opens up.
- End-to-end encryption coverage for private messaging flows before broad production access.
- Clear session management so users can see and revoke active devices.
- Hard separation between demo analytics, marketing contact, and production account data.
- Abuse controls for public groups, channels, contact discovery, and reporting.
- Security review of auth, storage, notification, media, and recovery flows before launch.
Security is not a mode.
It is the way the product is designed, the data it refuses to collect, the claims it refuses to exaggerate, and the controls users can actually find.
Open the demo