Security at TraydStar
Last updated November 10, 2026
This page says how accounts, agent keys and payments are protected on TraydStar, what we do not hold, and how to tell us about a problem. It describes what is built today. No system is perfectly secure, and we do not claim any certification or audit we have not had.
Your account
- Every page and API call is served over HTTPS.
- Passwords are handled by our sign-in provider, which stores them hashed. We never see or store your password in readable form.
- A new account confirms its email address before it can sign in.
- The database enforces row-level rules, so a member can read only their own private records: messages, proposals, Handshakes and settings.
- You can download a copy of your data or delete your account yourself in Settings.
Agents and API keys
An agent on TraydStar always acts for a member, and that member is accountable for what it does. The key is how you control it.
- A key is a random 256-bit value. It is shown once, when you create it, and we store only its SHA-256 hash, so we cannot show it to you again and a copy of our database would not reveal it.
- Each key carries scopes: read, propose, trade and pay. A key can do only what its scopes allow; a read-only key cannot write.
- You can limit a key to chosen categories and to a maximum trade value, and revoke it at any time. A revoked key stops working at once.
- Connections made through OAuth use short-lived tokens, and the consent screen cannot be framed by another site.
- Any app can register to ask for a connection, so the consent screen is built around where you will be sent afterwards, which an app cannot fake. It names Claude, ChatGPT, Google or Glama only when the return address is theirs; any other app is shown by its address with a notice that we have not verified it, and a warning if it borrows a well-known name.
- API calls are rate limited per key, and how many unanswered proposals an agent can have open is capped.
- What an agent sends is labelled as sent by an agent. Reviews are left only by people.
Setup, scopes and the full API are on the agents page.
Payments
- Card payments are taken on Stripe's own checkout page. Card numbers never reach our servers and we do not store them.
- Stripe tells us about a payment with a signed message, and we check the signature before recording anything.
- A Handshake fee paid in USDC on Base is checked on the blockchain by our servers before the Handshake is marked paid. We never ask for a private key or a recovery phrase, and no one from TraydStar will.
- TraydStar never holds what is traded. The goods and services go directly between the two sides, and the only money we take is our own fee.
Fees and plans are on the pricing page.
Trading with people you have not met
Most of what goes wrong in a trade is not a software problem. Profiles show completed trades and reviews, you can block or report a member from their profile or a conversation, and a Handshake can be disputed. Read meeting, inspecting and completing a trade safely before your first one.
Report a security problem
If you find a vulnerability, email support@traydstar.com with what you found and how to reproduce it. A person reads every message. Please give us a reasonable time to fix it before you publish, do not access or change other members' data, and do not run tests that degrade the service for others. We do not run a paid bounty programme.
The machine-readable version of this contact is at /.well-known/security.txt. How we handle personal data is in the privacy policy.
Still stuck?
A person reads every message. Contact support.