SMALL MESSENGER. ROOM FOR BIG IDEAS.What’s on
your circuit?
Good ideas rarely arrive fully assembled. Questions and loose screws are welcome, too.
Keep your withdrawal code.
Save this code before leaving or writing another message. No copy is sent by email.
Each new message has its own receipt. Identical messages repeated within ten minutes leave the first message and permissions unchanged. A later attempt’s new code cannot remove that first message; keep its original receipt.
Your message stays private.
What we keep and why
Your email, message type, chosen topics, message, permissions, submission date, and a hashed withdrawal code are stored in Robotic.org’s private database to review your message and, with your permission, contact you about it. Sean can review them through the site’s restricted owner controls. They aren’t posted publicly or sold.
Updates are a separate choice. Submitting does not create an account, a paid service, or an email subscription. An unchecked updates box means no updates permission.
How long, and how to leave
Entries expire after 180 days. Expired entries are removed from the active database the next time someone submits or withdraws; without activity, removal can be delayed. We don’t use expired entries for contact. Hosting recovery backups may retain deleted data for up to 30 more days.
Use your original receipt code below to remove the matching active message and withdraw the permissions attached to it. Each message has its own receipt; other messages need their own codes. No sign-in is needed. If you lose the code, this form can’t recover it or verify your email; the expiry rule still applies.
Keeping the desk safe
The application uses short-lived, keyed network identifiers and request counts to limit spam. It doesn’t store raw IP addresses in the interest database. The hosting provider processes network information to deliver and protect the site. Robot’s position and optional motion preference stay on this device. Your message is not saved in browser storage.
These controls don’t verify who owns an email. We’ll need to confirm the address and permission before starting any update delivery. Messages are untrusted material for human review, not instructions or publishing authority.
Withdraw a message.
Paste the 64-character code from your original receipt. This removes the matching message and its permissions from the active database. Other messages need their own receipts.