Server authority
Identity approval, business verification and paid entitlement are separate states. Sensitive permissions must be evaluated on the server; a visible badge alone does not grant access.
ATRIUM TRUST
Connecting the real world means designing for trust.
In Atrium, safety is more than a report button or a privacy policy. Identity, visibility, location and the level of interaction people can have are parts of the product architecture.
No social platform can eliminate every risk in the physical world. Atrium aims to reduce risks where possible, make abuse harder and give users control, rather than hide the risks.
Explore the ProjectResearch / Hypothesis
03ATRIUM TRUST
Connecting the real world means designing for trust.
In Atrium, safety is more than a report button or a privacy policy. Identity, visibility, location and the level of interaction people can have are parts of the product architecture.
No social platform can eliminate every risk in the physical world. Atrium aims to reduce risks where possible, make abuse harder and give users control, rather than hide the risks.
Not every user starts with the same permissions.
In development- 01
Email verification
Discover Atrium.
Explore general local activity, businesses, events and privacy-safe density information.
- 02
Phone verification
Move towards social interaction.
Access controlled connection requests and selected social features.
- 03
Identity verification
Access physical features that require higher trust.
Ping, physical meetups, nearby people discovery and similar higher-risk features may require a higher trust level.
Identity verification does not mean that a person is safe. It only means that the identity of the person behind the account has been verified.
Explore the trust architecturePRIVACY-FIRST
Be nearby. Without becoming an exposed target.
A user's real GPS coordinates are not shared with other users, community managers or businesses.
Atrium aims to use approximate distance, spatial areas and privacy-safe aggregation wherever possible.
- No sharing of precise coordinates.
- Businesses see aggregated insights only.
- Spatial precision may be reduced when user density is low.
- Participation does not automatically have to reveal a public identity.
Private account / location
Permissions and visibility boundary
Approximate local context
Aggregated information · user control
Architecture diagram; no real account or GPS data.
CONTEXTUAL IDENTITY
Atrium may know who you are. Not everyone has to.
Real identity verification and a public social profile are different things.
Atrium aims to let people control their visibility by context under one verified account.
Verified accountVisibility by context
You can attend an event.
But everyone does not have to see your name, photo and profile.
If you explicitly choose to be open to meeting people, only the necessary profile information may be shown.
Controlling how visible you are is part of safety.
When a digital connection becomes a physical meeting, the safety level changes.
Atrium aims to treat physical meetups differently from ordinary messaging.
- Mutual agreement
- Verified account level
- Meeting context
- Trusted contact
- Safety check-in
- Easy blocking and reporting
PLANNED SCENARIO
A user may choose to share a planned meeting with someone they trust. Atrium may check in at intervals to ask whether everything is okay, with the safety process continuing according to the user's choices.
ATRIUM
Nearby life doesn't have to stay invisible.
People.
Communities.
Events.
Businesses.
Opportunities.
In the same surroundings. On the same network.
What's happening around you?
Sometimes, what lies in between becomes the centre.