Privacy

What JevDesk keeps about you

Short, because there is not much. JevDesk has no account system of its own: you are a wallet address, and everything below hangs off that. Last changed 11 October 2026.

What it keeps

Your Social profile and conversations, if you join the experiment
Social uses your verified X id, display name, handle, avatar, public bio, profile snapshot, interests, chosen conversation language and introduction. With your consent, up to 300 recent public posts are read through twitterapi.io. Jev suggests topics, language and a sharing focus; these decisions form a short English snapshot and conversation starter. Keyword matching is used as a fallback. Raw post text and X access tokens are not stored. Older 20- or 100-post imports keep their original limit until you explicitly choose the expanded import. Your profile stays hidden until you opt into Discover. Likes, matches, messages and blocks are kept so conversations survive a new visit. Messages are available to the matched participants and the server; they are not end-to-end encrypted. Reports retain the last ten messages from that shared conversation for moderation.
Your wallet address
It is how you are signed in. There is no email, no password and no name: the address is the account. The addresses you link to the same account are kept beside it, so one account can hold a Solana wallet and an EVM one.
What you swiped, and whose posts you watch
A swipe is a post id, a yes or a no, and a time. A watched account is a handle. Both belong to your wallet, because the desk has to show you what you have already seen and who you asked to follow.
The X account you prove is yours, if you claim
A coin launched from someone’s post keeps a fifth of its fee for whoever wrote it. To take it you sign in with X, and what is kept is X’s numeric id for you and your handle — nothing else, and only if you claim. The token X issues is used once, to read who you are, and dropped.
The Instagram account you prove is yours, if you claim
For a coin whose fee names an Instagram account, we keep the handle and the identifier that proved ownership. Instagram Login supplies its account id. Optional message verification uses Manychat’s workspace-scoped contact id and a one-time challenge tied to your wallet. The challenge expires after ten minutes; old challenge records are cleaned up when a later verification starts. These identifiers are kept separate: changing verification methods cannot replace an existing owner.
How much of JevDesk’s own coin your wallet holds
Only a number, and only to know how many accounts you may watch. It is read from the chain, which is public, and refreshed now and then.

What it never has

  • The private key or seed of the wallet you connect. Income escrows and launch vaults are separate: JevDesk controls their keys and can move the funds they hold, as explained on the claim page.
  • An email address, a phone number or a password. Social keeps the public X display name only when you choose to join.
  • Your Instagram password or session cookies. Message verification checks only the verification code and the sender identity supplied by the connected messaging service; it does not request your inbox, posts or followers.
  • A tracker, an advertising pixel or a third-party analytics script. Nothing follows you off this site.

Who else sees it

Manychat (only for message verification)
handles verification messages sent to JevDesk’s Instagram account and passes the code, sender username and workspace contact id to JevDesk. It is connected to JevDesk’s account, not to your account. Instagram Login does not use Manychat.
Vercel
runs the site and sees the ordinary record of a web request — the address it came from, the page asked for, the time.
Supabase
holds the database the rows above live in.
X and Meta
see that you signed in, because you are signing in with them. They are told nothing about you by JevDesk.
twitterapi.io
is how public posts are read from X. If you join Social, it is also asked for your public profile and up to 300 recent public posts after you consent to that import.
TypeSafe (Jev)
analyzes the public X bio and up to 300 authored posts you import into Social to suggest approved conversation interests, a writing language and an evidenced sharing focus. Your snapshot and starter use English copy based on those decisions. Raw post bodies are not stored in the JevDesk database. If Jev is unavailable, keyword suggestions are used.
pump.fun, StonkFun, Raydium, Jupiter and the chains themselves
are public. A coin you launch, and the wallet that launched it, are on a public ledger and nothing here can make them private.

Nothing is sold, and nothing is handed to anyone for advertising. JevDesk would give up what it holds if the law demanded it, which for a wallet address and a handle is not much to give.

The browser extension

It collects nothing at all — no server behind it, no analytics in it, and it never talks to JevDesk in the background. What it does and does not do is set out on its own page.

Having it removed

Social has its own delete button in My profile. It deletes your social sessions, profile, likes, matches and shared conversation history immediately. Moderation reports and blocks other people placed on your X id are retained to prevent abuse and block evasion. Hiding a profile only removes it from discovery; disconnecting only ends the current social session.

Write to privacy@jevdesk.com from the X or Instagram account in question, or sign a message with the wallet, and everything above is deleted: the wallet row, the swipes, the watched accounts, and any X or Instagram link. It is done by hand, within thirty days, and you are told when it is.

Two things cannot be deleted, and it is fairer to say so than to promise otherwise. A coin, once launched, is on a public chain and belongs to nobody — not to JevDesk and not to whoever launched it. And a share already owed to an account stays owed: deleting the link only means there is nothing left to claim it with.

When this changes

This page is written from what the code does, so it changes when the code does. The date at the top is the last time that happened. Questions go to the same address.