Built-in protection

Privacy isn't
a setting.
It's the structure.

Aliases instead of names. Fuzzy location instead of GPS. Automatic expiry instead of archives. Misd is designed so that privacy is the default — not something you have to turn on.

The three rules

Three decisions that
define everything.

These aren't features or settings — they're structural choices made before a single line of code was written.

🎭
Alias-only identity
You are your alias. No real name required to join, post, or match. The person you connect with knows you as "Morning Reader" — not your LinkedIn name.
📍
Fuzzy location
We know you're in the neighborhood — not which building, not which floor. Location is resolved to a radius, not a pin. We can't sell what we don't have.
⏳
Automatic expiry
Every post, every chat, every connection expires automatically. Nothing is archived. Nothing is searchable. The past doesn't follow you here.
Identity layer

Your alias is
the whole profile.

No photo. No bio. No location history. No mutual friends list. The only thing another person knows about you is the name you chose and the city you're in.

When you join Misd, you pick an alias — a two-word handle that becomes your entire identity on the platform. It can't be traced. It doesn't sync with your contacts. It has no connection to your phone number, email, or any other account.
Your alias is permanent for the duration of your session but you can reset it at any time. When you reset, your old alias disappears completely — no thread connects the two.
Why aliases work for connection: You don't need someone's real name to connect with them. You need enough context to recognize each other. The alias does that — plus it removes the social anxiety of revealing your real identity before the connection is made.
No profile to stalk: There's nothing to look at. No post history, no location pins, no timeline. Anyone who finds your alias in the feed sees the same blank slate. Your identity is what you shared in the moment — not a searchable record.
misd.me/morningreader
MR
Morning Reader
Atlanta, GA · active today
3
active posts
1
connections
Not stored · not shown · not accessible
Real name
Photo or avatar
Phone number or email
Post history after expiry
Precise location
Social graph or follows
Read receipts or tracking
Location privacy

Neighborhood-level.
Not building-level.

We resolve your location to a radius — enough to surface relevant posts, not enough to identify your building, floor, or daily routine.

Your device knows exactly where you are. Misd never asks for that. We ask for your neighborhood — either you tell us ("Midtown Atlanta") or we resolve it from an approximate location signal that's immediately discarded after resolving to a 0.5-mile radius.
The posts you see are from that radius. The location on your post is that radius — not a pin, not coordinates, not an address. Someone reading your post knows you were somewhere in Midtown. Not where.
We don't store location history. Each session resolves location freshly and the raw signal is discarded after the radius is computed. There is no "places you've been" dataset to breach or sell.
In Live Mode, geofencing is tighter — we need to know you're inside the venue, not just nearby. But even in Live Mode, we discard the precise signal immediately after checking you're within the geofence boundary.
Location resolution model
📍
GPS precision (not stored)
~5m
Venue-level (Live Mode only)
~50m
Neighborhood radius (stored)
~800m
What others see on posts
neighborhood
Built-in expiry

Everything expires.
Nothing is saved.

Expiry isn't a privacy feature you turn on — it's the default behavior of every piece of content on Misd. There are no archives. There is no search history.

📝
Posts
72 hours
Set by the author at post time. No extensions. When the clock hits zero, the post is deleted from the database — not hidden, not archived. Deleted.
💌
Match chats
Tied to the post
A chat lives exactly as long as the post it opened from. When the post expires, the chat closes. No thread history. No message archive. If you want to keep something, copy it — there's no other backup.
⚡
Live moments
Event duration
Live Mode posts expire when the event ends — sometimes hours, sometimes minutes. The heatmap data from a live session is discarded completely when the space goes offline.
🎭
Alias sessions
Until you reset
Your alias persists until you choose to reset. When you do, the old alias is deleted — any active posts under it expire naturally. There's no way to look up what an old alias posted.
Data retention

What we store.
What we don't.

Plain language. No legal boilerplate. This is the full list of what exists in our systems and for how long.

Data type
Stored?
Retention
Notes
Alias
Yes
Until reset
Two-word handle only. No link to real identity.
City / neighborhood
Yes
Active session
Radius only. Not coordinates, not address.
Post content
Yes
72h then deleted
Deleted on expiry — not archived, not cached.
Match chat messages
Yes
With the post
Expires with parent post. No backup.
Reaction counts
Yes
With the post
Aggregate only — who reacted is never stored.
Match history
No
—
We know a match happened. Not who matched with whom.
GPS / precise location
No
—
Discarded immediately after neighborhood resolution.
Real name, phone, email
No
—
Never collected. Not required to join or post.
Read receipts
No
—
No one can see who read their post or when.
Heatmap / Live data
No
—
Computed and displayed in real-time. Discarded when session ends.
Hard limits

What Misd
will never be.

Some things aren't features we haven't built yet — they're directions we've decided not to go. These are permanent.

✗ What we won't build
✗ Real-name verification or ID checks
✗ Profile photos, bios, or social links
✗ Message requests from strangers (all connections are mutual)
✗ Follower counts or public post histories
✗ Third-party ad tracking or behavioral profiles
✗ Location data sold or shared with data brokers
✗ Archived content accessible after expiry
✗ Screenshot detection or prevention (we trust people)
✓ What we protect
✓ Alias-only identity, always — even in matches
✓ Mutual-only connections — no unsolicited contact
✓ Reaction anonymity — who reacted is never revealed
✓ Automatic content deletion on schedule
✓ The right to reset your alias with no trace left
✓ Location fuzzing at every layer, every time
✓ No cross-session identity stitching
✓ Business analytics that are aggregate, not individual

Private by design.
Mutual by default.

The system only connects people who both want to be connected. That's the whole safety model.

Browse the feed → Full Privacy Policy