What we hold, and what representatives must open

TiedTo publishes what an entity chooses to publish: names, roles, and the stable platform ids an entity has bound. That publication is the product. It is a claim by the entity, not a dossier collected about people.

What the platform stores

Your account email (for sign-in and verification), the entities you own, the representatives you publish, and their bound platform user ids. Check history is kept for 90 days for abuse investigation. We do not sell data, and we do not run ad tracking.

Forwarded messages

Verification by forward works like this: a checker forwards a message from the account they want to check to the official bot; the bot reads the sender id Telegram attaches to the forward and answers with that account's live status. The forwarded content is not stored.

Requirement for representatives

If a representative keeps forwards closed, Telegram strips the sender id from every forward, for everyone, including the bot. That account then cannot be verified by forward at all; checkers will be told the sender is hidden. Representatives who want to be verifiable are expected to open this one privacy setting. Binding an account to TiedTo implies this setting is open.

Removal

An entity can revoke a representative in one action; a bound account can be unbound by its owner. A revoked claim stays visible as revoked, the withdrawal is public by design.